[SOLVED] Boot sometimes hangs: kworker/0:1:42 blocked for more than 120 seconds
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Boot sometimes hangs: kworker/0:1:42 blocked for more than 120 seconds
On my Arch laptop the boot process sometimes hangs several minutes.
When that happens, typically also the shutdown will hang.
This is what gets printed to the journal log in these cases:
Course, that might lock out your power management software and just end up causing you a different problem, however fortune favors the bold
Thanks for the suggestion. I refrained from doing so because I read that this might also turn off temperature control and thus lead to overheating. Not sure if I am bold enough for such a move :-)
Thanks for the idea. One of the things I find most exciting about Arch is running a bleeding edge kernel. But I agree with you, this is worth trying to see if it makes the problem go away. I'll give this a shot and report back.
Meanwhile I am happy for any further input on how to debug this...
Ok, I tried this, but it seems even worse. The boot freezed completely when trying to bring up udev. After 5 minutes without any output whatsoever I killed it by hard reset.
System back up and running with the standard kernel now. Crash message from the previous (failed) boot with the lts-kernel is this:
Code:
Jul 06 22:50:54 ideapad kernel: iwlwifi 0000:02:00.0: Detected Intel(R) Wireless N 7260, REV=0x144
Jul 06 22:50:54 ideapad kernel: iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
Jul 06 22:50:54 ideapad kernel: iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
Jul 06 22:50:54 ideapad systemd-udevd[282]: Process '/usr/lib/systemd/systemd-vconsole-setup' failed with exit code 1.
Jul 06 22:50:54 ideapad systemd-udevd[281]: Process '/sbin/modprobe -r psmouse' failed with exit code 1.
Jul 06 22:51:53 ideapad systemd-udevd[270]: seq 1376 '/devices/pci0000:00/0000:00:03.0' is taking a long time
Jul 06 22:51:53 ideapad systemd-udevd[270]: seq 1375 '/devices/pci0000:00/0000:00:02.0' is taking a long time
Jul 06 22:51:53 ideapad systemd-udevd[270]: seq 1394 '/devices/pci0000:00/0000:00:1b.0' is taking a long time
Jul 06 22:51:54 ideapad systemd-udevd[270]: seq 1616 '/devices/virtual/vtconsole/vtcon1' is taking a long time
Jul 06 22:53:53 ideapad systemd-udevd[270]: seq 1375 '/devices/pci0000:00/0000:00:02.0' killed
Jul 06 22:53:53 ideapad systemd-udevd[270]: seq 1376 '/devices/pci0000:00/0000:00:03.0' killed
Jul 06 22:53:53 ideapad systemd-udevd[270]: seq 1394 '/devices/pci0000:00/0000:00:1b.0' killed
Jul 06 22:53:53 ideapad systemd-udevd[270]: worker [274] terminated by signal 9 (Killed)
Jul 06 22:53:53 ideapad systemd-udevd[270]: worker [274] failed while handling '/devices/pci0000:00/0000:00:1b.0'
Jul 06 22:53:54 ideapad systemd-udevd[270]: seq 1616 '/devices/virtual/vtconsole/vtcon1' killed
Jul 06 22:53:54 ideapad systemd-udevd[270]: worker [286] terminated by signal 9 (Killed)
Jul 06 22:53:54 ideapad systemd-udevd[270]: worker [286] failed while handling '/devices/virtual/vtconsole/vtcon1'
After changing the init system, the initial ramdisk creation tool and even the distro (none of this helped) I now finally seem to have found a solution to this.
Sometimes in the dmesg.log the last line before hangs of approximately a minute would be
Code:
Switched to clocksource tsc
So I tried changing the clocksource to hpet using the following kernel parameter:
Code:
clocksource=hpet
I have now booted about 10 times and no hangs... Will mark as solved.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
