Bug#763431: linux-image-3.16-2-amd64: Doesn't finish booting
We need the kernel log up to this point - the on-screen messages are not sufficient. They should have made it into /var/log/messages. If there are any error messages in the log file from udev, those should also be informative. (Sorry if my reply comes out as garbled HTML mail. I'm not too familiar with the webmail interface I'm using.) Anyway my boot problem doesn't produce any logs in /var because errors prevent prevent /var from being mounted. However I managed to pipe the output of dmesg to file. The part where the boot first stalls is reproduced below (with two lines of context included before and after). I'm also attaching as a tar.xz file the complete dmesg output from the failed boot under linux-image-3.16-2 and, for comparison, the dmesg from a successful boot under linux-image-3.16-1. [ 12.658117] systemd-udevd[417]: renamed network interface wlan0 to wlan2 [ 12.798356] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off [ 153.192245] Adding 8388604k swap on /dev/sda10. Priority:-1 extents:1 across:8388604k FS [ 153.245182] EXT4-fs (sda11): re-mounted. Opts: (null) [ 153.762270] EXT4-fs (sda11): re-mounted. Opts: errors=remount-ro [ 240.061772] INFO: task kworker/2:1:46 blocked for more than 120 seconds. [ 240.061870] Not tainted 3.16-2-amd64 #1 [ 240.064844] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 240.067911] kworker/2:1 D 8800d22a8468 046 2 0x [ 240.067940] Workqueue: pm pm_runtime_work [ 240.067944] 8800d22a8010 0046 00014240 8800d22affd8 [ 240.067950] 00014240 8800d22a8010 8800368eff08 8800d22afc60 [ 240.067955] 8800368eff0c 8800d22a8010 8800368eff10 [ 240.067961] Call Trace: [ 240.067974] [81508e35] ? schedule_preempt_disabled+0x25/0x70 [ 240.067983] [8150a8f3] ? __mutex_lock_slowpath+0xd3/0x1c0 [ 240.067990] [8150a9fb] ? mutex_lock+0x1b/0x2a [ 240.068021] [a00dd5b6] ? rtsx_usb_suspend+0x26/0x80 [rtsx_usb] [ 240.068045] [a0017d0a] ? usb_suspend_both+0x9a/0x1d0 [usbcore] [ 240.068062] [a001913e] ? usb_runtime_suspend+0x2e/0x70 [usbcore] [ 240.068068] [813a68cc] ? __rpm_callback+0x2c/0x80 [ 240.068074] [813a693f] ? rpm_callback+0x1f/0x80 [ 240.068080] [813a6aa7] ? rpm_suspend+0x107/0x5f0 [ 240.068086] [813a7e3c] ? __pm_runtime_suspend+0x5c/0x80 [ 240.068102] [a00191c6] ? usb_runtime_idle+0x26/0x30 [usbcore] [ 240.068108] [813a68cc] ? __rpm_callback+0x2c/0x80 [ 240.068113] [813a71f8] ? rpm_idle+0x198/0x290 [ 240.068119] [813a7f67] ? pm_runtime_work+0x97/0xa0 [ 240.068128] [8107f4a2] ? process_one_work+0x172/0x420 [ 240.068135] [8107fb35] ? worker_thread+0x115/0x520 [ 240.068141] [81508591] ? __schedule+0x2b1/0x710 [ 240.068148] [8107fa20] ? rescuer_thread+0x2d0/0x2d0 [ 240.068154] [81085dcd] ? kthread+0xbd/0xe0 [ 240.068160] [81085d10] ? kthread_create_on_node+0x180/0x180 [ 240.068165] [8150c1bc] ? ret_from_fork+0x7c/0xb0 [ 240.068171] [81085d10] ? kthread_create_on_node+0x180/0x180 [ 240.068181] INFO: task kworker/u8:5:111 blocked for more than 120 seconds. [ 240.070936] Not tainted 3.16-2-amd64 #1 [ 240.073676] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 240.076462] kworker/u8:5D 880119a245a8 0 111 2 0x [ 240.076484] Workqueue: kmmcd mmc_rescan [mmc_core] [ 240.076487] 880119a24150 0046 00014240 8800364e7fd8 [ 240.076492] 00014240 880119a24150 8800369c0090 8800369c0140 [ 240.076497] 8800369c0200 8800364e7c30 [ 240.076502] Call Trace: [ 240.076509] [813a7501] ? rpm_resume+0x191/0x5d0 [ 240.076517] [81070980] ? ftrace_raw_event_tick_stop+0xb0/0xb0 [ 240.076524] [810a57f0] ? prepare_to_wait_event+0xf0/0xf0 [ 240.076530] [813a763a] ? rpm_resume+0x2ca/0x5d0 [ 240.076535] [813a763a] ? rpm_resume+0x2ca/0x5d0 [ 240.076541] [813a7988] ? __pm_runtime_resume+0x48/0x70 [ 240.076551] [a0173858] ? sdmmc_set_ios+0x318/0xa20 [rtsx_usb_sdmmc] [ 240.076561] [a0173b15] ? sdmmc_set_ios+0x5d5/0xa20 [rtsx_usb_sdmmc] [ 240.076573] [a019a8ba] ? mmc_power_up+0x7a/0x2a0 [mmc_core] [ 240.076585] [a019a0c2] ? mmc_power_off.part.19+0x72/0xe0 [mmc_core] [ 240.076591] [812b2b02] ? delay_tsc+0x42/0x70 [ 240.076605] [a019b71e] ? mmc_rescan+0x26e/0x320 [mmc_core] [ 240.076612] [8107f4a2] ? process_one_work+0x172/0x420 [ 240.076619] [8107fb35] ? worker_thread+0x115/0x520 [ 240.076626] [8107fa20] ? rescuer_thread+0x2d0/0x2d0 [ 240.076631] [81085dcd] ? kthread+0xbd/0xe0 [ 240.076637] [81085d10] ?
Bug#763431: linux-image-3.16-2-amd64: Doesn't finish booting
Package: linux-image-3.16-2-amd64 Version: 3.16.3-2 Severity: grave Dear Maintainer, The kernel image installed by the linux-image-3.16-2-amd64 package fails to boot into a working system. The boot stalls at the following error (manually reproduced from a cellphone photograph so there may be typographical errors): INIT: version 2.88 booting [info] Using makefile-style concurrent boot in runlevel S. [ok] Starting the hotplug events dispatcher: udevd. [ok] Synthesizing the initial hotplug events...done [] Waiting for /dev to be fully populated... [ 240.062008] INFO: task kworker/u8:5:113 blocked for more than 120 seconds. [ 240.062104]Not tainted 3.16-2-amd64 #1 [ 240.062159] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message The last three lines of the boot message extract repeats with only the time stamps changing. Pressing Ctrl-C allows the boot to proceed but only to an emergency root shell, not a fully working system. Under the emergency shell, the filesystem is mounted read-only. From the shell prompt, I can shut down but not reboot the computer. Any attempt at a soft reboot (via the command shutdown now -r or simply reboot) results in the shutdown of system processes but doesn't actually restart the computer. I must then press the hardware power button to shut down the computer before turning it back on. Invoking shutdown now -h, however, does result in a successful shutdown. The above boot failure does NOT affect the previous kernel image package of the Linux 3.16 series (linux-image-3.16-1-amd64). This is the kernel I am currently using to type this bug report. The boot failure also does NOT affect Debian kernel images of the Linux 3.14 series. I have reinstalled the problematic kernel image package twice to rebuild the initrd but the result is the same. The kernel fails to boot the computer into a usable condition. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: ZOTAC product_name: ZBOXNANO-ID63/ID64/ID65 product_version: XX chassis_vendor: NA chassis_version: NA bios_vendor: American Megatrends Inc. bios_version: 4.6.5 board_vendor: ZOTAC board_name: ZBOXNANO-ID63/ID64/ID65 board_version: XX ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:a247] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: ivb_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:2111] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 45 Region 0: Memory at f780 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at e000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at f000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI]) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:a247] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 42 Region 0: Memory at f7d0 (64-bit, non-prefetchable) [size=64K] Capabilities: access denied Kernel driver in use: xhci_hcd 00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:a247] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 44 Region 0: Memory at f7d1b000 (64-bit, non-prefetchable) [size=16] Capabilities: access denied Kernel driver in use: mei_me 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI])
Bug#763431: linux-image-3.16-2-amd64: Doesn't finish booting
Control: severity -1 important Control: tag -1 moreinfo On Mon, 2014-09-29 at 22:20 -0400, bugrepor...@safe-mail.net wrote: Package: linux-image-3.16-2-amd64 Version: 3.16.3-2 Severity: grave Dear Maintainer, The kernel image installed by the linux-image-3.16-2-amd64 package fails to boot into a working system. The boot stalls at the following error (manually reproduced from a cellphone photograph so there may be typographical errors): [...] We need the kernel log up to this point - the on-screen messages are not sufficient. They should have made it into /var/log/messages. If there are any error messages in the log file from udev, those should also be informative. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
