{"action":"created","issue":{"url":"https://api.github.com/repos/raspberrypi/linux/issues/1414","repository_url":"https://api.github.com/repos/raspberrypi/linux","labels_url":"https://api.github.com/repos/raspberrypi/linux/issues/1414/labels{/name}","comments_url":"https://api.github.com/repos/raspberrypi/linux/issues/1414/comments","events_url":"https://api.github.com/repos/raspberrypi/linux/issues/1414/events","html_url":"https://github.com/raspberrypi/linux/issues/1414","id":148920289,"number":1414,"title":"RPI2 does not boot anymore (using latest 4.4 or 4.1)","user":{"login":"drtyhlpr","id":16102535,"avatar_url":"https://avatars.githubusercontent.com/u/16102535?v=3","gravatar_id":"","url":"https://api.github.com/users/drtyhlpr","html_url":"https://github.com/drtyhlpr","followers_url":"https://api.github.com/users/drtyhlpr/followers","following_url":"https://api.github.com/users/drtyhlpr/following{/other_user}","gists_url":"https://api.github.com/users/drtyhlpr/gists{/gist_id}","starred_url":"https://api.github.com/users/drtyhlpr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/drtyhlpr/subscriptions","organizations_url":"https://api.github.com/users/drtyhlpr/orgs","repos_url":"https://api.github.com/users/drtyhlpr/repos","events_url":"https://api.github.com/users/drtyhlpr/events{/privacy}","received_events_url":"https://api.github.com/users/drtyhlpr/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-04-17T05:25:32Z","updated_at":"2016-04-17T16:19:19Z","closed_at":"2016-04-17T13:37:00Z","body":"Hi,\r\nthanks for this great kernel github, thanks for your time and work!\r\n\r\nI created a debian-jessie rpi2 bootstrapping script that was running fine (on latest script release date) - 22 days ago. Yesterday I found out that the created Images (with compiled kernel) do not boot anymore. I tried to investigate whats the problem - but failed so far.\r\n\r\n`Uncompressing :Linux... done, booting the kernel.`\r\n\r\nAfter the \"uncompressing kernel\" message I don't get any more messages and I struggle to find out more about the problem. Is there any other debugging option except using JTAG to debug this early boot step? (the only general debugging options I found dtdebug=1 needs userland to see debugging logs)\r\n\r\nThe kernel compilation works fine without errors. I am using default bcm2709_defconfig (classic kernel make and install (zImage modules dtbs - modules_install, firmware_install, headers_install), finally the copy ./boot/dts and overlays to /boot/).\r\n\r\nOf course I am using the latest boot binaries from firmware github - dts and overlays look very similar.\r\n\r\nIs there any major change inside the /boot directory or the dtbs, overlays structure - that I miss - or I am to blind to see?\r\n\r\nhere is the bootstrapping script (I am not posting this as PR, lol):\r\nhttps://github.com/drtyhlpr/rpi2-gen-image\r\n(-> https://github.com/drtyhlpr/rpi2-gen-image/blob/master/bootstrap.d/13-kernel.sh)\r\n\r\nListing of my generated boot directory (compiled kernel, copied dtbs and overlays, latest rpi firmware files):\r\n```\r\n/mnt/bcm2709-rpi-2-b.dtb\r\n/mnt/bcm2710-rpi-3-b.dtb\r\n/mnt/bootcode.bin\r\n/mnt/cmdline.txt\r\n/mnt/config.txt\r\n/mnt/fixup_cd.dat\r\n/mnt/fixup.dat\r\n/mnt/fixup_x.dat\r\n/mnt/kernel7.img\r\n/mnt/start_cd.elf\r\n/mnt/start.elf\r\n/mnt/start_x.elf\r\n\r\n/mnt/overlays:\r\nads7846.dtbo\r\nakkordion-iqdacplus.dtbo\r\nat86rf233.dtbo\r\nbmp085_i2c-sensor.dtbo\r\nboomberry-dac.dtbo\r\nboomberry-digi.dtbo\r\ndht11.dtbo\r\ndpi24.dtbo\r\ndwc2.dtbo\r\ndwc-otg.dtbo\r\nenc28j60.dtbo\r\ngpio-ir.dtbo\r\ngpio-poweroff.dtbo\r\nhifiberry-amp.dtbo\r\nhifiberry-dac.dtbo\r\nhifiberry-dacplus.dtbo\r\nhifiberry-digi.dtbo\r\nhy28a.dtbo\r\nhy28b.dtbo\r\ni2c0-bcm2708.dtbo\r\ni2c1-bcm2708.dtbo\r\ni2c-gpio.dtbo\r\ni2c-mux-pca9548a.dtbo\r\ni2c-pwm-pca9685a.dtbo\r\ni2c-rtc.dtbo\r\ni2s-mmap.dtbo\r\niqaudio-dac.dtbo\r\niqaudio-dacplus.dtbo\r\nlirc-rpi.dtbo\r\nmcp2515-can0.dtbo\r\nmcp2515-can1.dtbo\r\nmmc.dtbo\r\nmz61581.dtbo\r\npi3-act-led.dtbo\r\npi3-disable-bt.dtbo\r\npi3-miniuart-bt.dtbo\r\npiscreen2r.dtbo\r\npiscreen.dtbo\r\npitft28-capacitive.dtbo\r\npitft28-resistive.dtbo\r\npps-gpio.dtbo\r\npwm-2chan.dtbo\r\npwm.dtbo\r\nqca7000.dtbo\r\nraspidac3.dtbo\r\nREADME\r\nrpi-backlight.dtbo\r\nrpi-dac.dtbo\r\nrpi-display.dtbo\r\nrpi-ft5406.dtbo\r\nrpi-proto.dtbo\r\nrpi-sense.dtbo\r\nsdhost.dtbo\r\nsdio.dtbo\r\nsdtweak.dtbo\r\nsmi-dev.dtbo\r\nsmi.dtbo\r\nsmi-nand.dtbo\r\nspi1-1cs.dtbo\r\nspi1-2cs.dtbo\r\nspi1-3cs.dtbo\r\nspi2-1cs.dtbo\r\nspi2-2cs.dtbo\r\nspi2-3cs.dtbo\r\nspi-gpio35-39.dtbo\r\ntinylcd35.dtbo\r\nuart1.dtbo\r\nvc4-kms-v3d.dtbo\r\nvga666.dtbo\r\nw1-gpio.dtbo\r\nw1-gpio-pullup.dtbo\r\nwittypi.dtbo\r\n```\r\n\r\nthanks for your help, If you need more output or maybe have ideas to generate more debugging output please tell me\r\n\r\nps. I also tried the 4.1.y kernel (fetching -b 4.1.y and using firmware \"kernel: bump to 4.1.21\") -> same problem"},"comment":{"url":"https://api.github.com/repos/raspberrypi/linux/issues/comments/211051083","html_url":"https://github.com/raspberrypi/linux/issues/1414#issuecomment-211051083","issue_url":"https://api.github.com/repos/raspberrypi/linux/issues/1414","id":211051083,"user":{"login":"anyc","id":1723735,"avatar_url":"https://avatars.githubusercontent.com/u/1723735?v=3","gravatar_id":"","url":"https://api.github.com/users/anyc","html_url":"https://github.com/anyc","followers_url":"https://api.github.com/users/anyc/followers","following_url":"https://api.github.com/users/anyc/following{/other_user}","gists_url":"https://api.github.com/users/anyc/gists{/gist_id}","starred_url":"https://api.github.com/users/anyc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/anyc/subscriptions","organizations_url":"https://api.github.com/users/anyc/orgs","repos_url":"https://api.github.com/users/anyc/repos","events_url":"https://api.github.com/users/anyc/events{/privacy}","received_events_url":"https://api.github.com/users/anyc/received_events","type":"User","site_admin":false},"created_at":"2016-04-17T16:19:19Z","updated_at":"2016-04-17T16:19:19Z","body":"Does someone have an idea what could be wrong if I can boot 4.1.21 but not 4.4.7? I am using Uboot and I can see the device tree in Uboot and also pass it to the kernel."}}