FS#42918 - [linux] 3.17.4 is blocked to start-up for tens of minutes and could not shutdown

Attached to Project: Arch Linux
Opened by Nguyễn Duy Hùng (nodohoung) - Thursday, 27 November 2014, 03:03 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 25 June 2016, 15:40 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After upgrading kernel to 3.17.4, my system is blocked for tens of minutes at starting up. It is blocked at some tasks (for ex udevd manager, kworker) many times. Even when I do shutting down, the system is freeze. After dmesg -kHT, i encountered something in log:

#Boot from 08:48:18 to 09:06:24

[Thu Nov 27 08:52:18 2014] INFO: task kworker/0:1:38 blocked for more than 120 seconds.
[Thu Nov 27 08:52:18 2014] Tainted: P O 3.17.4-1-ARCH #1
[Thu Nov 27 08:52:18 2014] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[Thu Nov 27 08:52:18 2014] INFO: task mtp-probe:292 blocked for more than 120 seconds.
[Thu Nov 27 08:52:18 2014] Tainted: P O 3.17.4-1-ARCH #1
[Thu Nov 27 08:52:18 2014] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[Thu Nov 27 08:54:18 2014] INFO: task kworker/0:1:38 blocked for more than 120 seconds.
[Thu Nov 27 08:54:18 2014] Tainted: P O 3.17.4-1-ARCH #1
[Thu Nov 27 08:54:18 2014] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[Thu Nov 27 08:54:18 2014] INFO: task systemd-udevd:175 blocked for more than 120 seconds.
[Thu Nov 27 08:54:18 2014] Tainted: P O 3.17.4-1-ARCH #1
[Thu Nov 27 08:54:18 2014] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[Thu Nov 27 08:54:18 2014] INFO: task mtp-probe:292 blocked for more than 120 seconds.
[Thu Nov 27 08:54:18 2014] Tainted: P O 3.17.4-1-ARCH #1
[Thu Nov 27 08:54:18 2014] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[Thu Nov 27 08:54:18 2014] INFO: task rtsx_usb_ms_5:417 blocked for more than 120 seconds.
[Thu Nov 27 08:54:18 2014] Tainted: P O 3.17.4-1-ARCH #1
[Thu Nov 27 08:54:18 2014] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

The kworker error appears more than three times. The mtp-probe error appears two times. And my system is also blocked at logging in to KDE for minutes.

Additional info:
* package version(s): 3.17.4 x86_64
* my system: Asus K43SJ Intel (R) Core i5-2430M CPU @2.4GHz, NVIDIA Geforce GT520M, 4GB Memory
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 25 June 2016, 15:40 GMT
Reason for closing:  No response
Comment by patrick (potomac) - Thursday, 27 November 2014, 19:14 GMT
is it a random bug ?

or you have this problem at each boot ?

if you downgrade the kernel to 3.17.3 the bug is gone ?

check also this bugreport  FS#42692 
Comment by Nguyễn Duy Hùng (nodohoung) - Friday, 28 November 2014, 02:13 GMT
it's not a random bug. It doesn't always happen but mostly.
I have problem that often could not shutdown with kernel >= 3.16.3 (3.16.3,3.16.4,3.17.1,3.17.3..), reported at https://bugs.archlinux.org/task/42038 but has not been resolved until now. I was expected 3.17.4 will resolve this bug but it didn't. So I have to downgrade the kernel to 3.16.2 and everything is working fine now.
I will check the bugreport you suggested.
Comment by t-ask (tAsk) - Saturday, 10 January 2015, 13:36 GMT
Please set BIOS back to failsave defaults. Take an USB flash drive and install raw Arch (Kernel 3.17.x) installation on it. Then begin to install package by package while rebooting your system with each package installed. Yes, it may be a time-consuming task, while you may find the cause faster/immediately, who knows. It is certainly better than waiting for someone else having the same problem. Also, you may find something important to know.
Comment by Nguyễn Duy Hùng (nodohoung) - Saturday, 10 January 2015, 13:48 GMT
thanks for your suggestion. I have built kernel myself without any problem. I think I won't use stock kernel in the future.
Comment by t-ask (tAsk) - Saturday, 17 January 2015, 23:49 GMT
I assume, you've got it solved by compiling your own kernel. If you want, you can diff your current kernel config to Arch's one which you can find in "/proc/config.gz". This way you may possibly find the settings causing you problems with Arch's kernel. Also, you could attach your kernel config here.
Comment by Samantha McVey (samcv) - Thursday, 09 June 2016, 05:27 GMT
Last commented on a year and a half ago, as well as for an old kernel version. In addition it does not appear the opener of this bug is still having the problem since building their own kernel. If nodohoung the opener of this bug could comment on whether this is still occurring for them on the current stock Arch Kernel or not that would be great.

Loading...