You are not logged in.
Hello,
I keep getting kernel taints upon boot. I'm guessing this has to do with the nvidia driver. I'm not sure if the two are related, but since I've been having this problem, the system refuses to shut down correctly. It gets to the final step and some of the workers die, which leads to the system stalling. It says something about something waiting for more than 120 seconds.
Versions:
* extra/nvidia-390xx 390.67-11
* extra/xorg-server 1.20.0-9
* core/linux 4.17.9-1
The system is up to date as of yesterday.
The biggest problem is that the system doesn't properly shut down. The system works fine otherwise.
Last edited by dragos240 (2018-07-26 09:08:54)
Offline
Frankly, this post is pointless without the actual error messages.
https://wiki.archlinux.org/index.php/Co … ow_to_post
https://wiki.archlinux.org/index.php/Systemd#Journal
Offline
Frankly, this post is pointless without the actual error messages.
https://wiki.archlinux.org/index.php/Co … ow_to_post
https://wiki.archlinux.org/index.php/Systemd#Journal
Ah. I didn't realize journalctl kept logs that far back. I thought it was wiped upon boot. Well, then I have the error I was getting upon power off.
Jul 26 05:29:08 ThinkTop kernel: INFO: task kworker/6:2:213 blocked for more than 120 seconds.
Jul 26 05:29:08 ThinkTop kernel: Tainted: P W O 4.17.9-1-ARCH #1
Jul 26 05:29:08 ThinkTop kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 26 05:29:08 ThinkTop kernel: kworker/6:2 D 0 213 2 0x80000000
Jul 26 05:29:08 ThinkTop kernel: Workqueue: usb_hub_wq hub_event [usbcore]
Jul 26 05:29:08 ThinkTop kernel: Call Trace:
Jul 26 05:29:08 ThinkTop kernel: ? __schedule+0x282/0x890
Jul 26 05:29:08 ThinkTop kernel: schedule+0x32/0x90
Jul 26 05:29:08 ThinkTop kernel: schedule_preempt_disabled+0x14/0x20
Jul 26 05:29:08 ThinkTop kernel: __mutex_lock.isra.0+0x220/0x530
Jul 26 05:29:08 ThinkTop kernel: ? _dev_info+0x6c/0x90
Jul 26 05:29:08 ThinkTop kernel: usb_disconnect+0x52/0x2a0 [usbcore]
Jul 26 05:29:08 ThinkTop kernel: hub_event+0xc7d/0x15c0 [usbcore]
Jul 26 05:29:08 ThinkTop kernel: process_one_work+0x1d1/0x3b0
Jul 26 05:29:08 ThinkTop kernel: worker_thread+0x2b/0x3d0
Jul 26 05:29:08 ThinkTop kernel: ? process_one_work+0x3b0/0x3b0
Jul 26 05:29:08 ThinkTop kernel: kthread+0x112/0x130
Jul 26 05:29:08 ThinkTop kernel: ? kthread_flush_work_fn+0x10/0x10
Jul 26 05:29:08 ThinkTop kernel: ret_from_fork+0x35/0x40The kernel taint message is pretty much the same when the system is running.
EDIT: This may be due to a USB device. I'm going to remove the device, reboot and report back.
EDIT2: Yeah. After removing the USB device, the same problem occurred. I booted up afterwards and shutdown with the USB device not plugged in and it powered off just fine. I'll see if someone else had this problem now.
Last edited by dragos240 (2018-07-26 10:29:07)
Offline
The error is beyond me, something about shutting down usb devices?
As for the taint, the kernel is just saying there is an out of tree, proprietary module loaded. Probably the nvidia. https://www.kernel.org/doc/html/v4.15/a … rnels.html
Offline
Yeah, it looks like for whatever reason, my system does not like this new external SSD I bought. It sometimes registers correctly and is shown to have done so with dmesg, but other times, this same error appears in dmesg when the system is running. I'm looking into it to see if someone else had this problem.
EDIT: I can't find any other instances of this problem. I searched "blocked for more than 120 seconds usbcore" and couldn't find anything.
Last edited by dragos240 (2018-07-26 10:54:55)
Offline