You are not logged in.
Pages: 1
Topic closed
Hi,
when I run lspci there is no output and the process will use 100% of one CPU core.
The process cannot be killed with SIGTERM nor with SIGKILL
There is no lspci output even with -vv switch.
When I shutdown the machine, systemd starts to complain about a process it cannot kill and I have to use the power button to poweroff.
These are the only errors in the journal:
(~) > journalctl -p 3 -b
-- Logs begin at szo 2014-06-14 14:33:02 CEST, end at szo 2014-06-21 13:48:35 CEST. --
jún 21 13:17:00 Yoko kernel: mei_me 0000:00:16.0: version message write failed: ret = -5
jún 21 13:17:00 Yoko kernel: mei_me 0000:00:16.0: hbm_start failed ret = -5
jún 21 13:17:03 Yoko ntpd[1386]: bind(23) AF_INET6 fe80::6a17:29ff:fe85:9fad%3%3#123 flags 0x11 failed: Cannot assign requested address
jún 21 13:17:03 Yoko ntpd[1386]: unable to create socket on wlan0 (4) for fe80::6a17:29ff:fe85:9fad%3#123
jún 21 13:17:13 Yoko kernel: nouveau E[ PIBUS][0000:01:00.0] HUB0: 0x6013d4 0xffff5704 (0x1a708200)
jún 21 13:17:13 Yoko kernel: nouveau E[ PIBUS][0000:01:00.0] GPC0: 0x4188ac 0x00000001 (0x1b70822e)
jún 21 13:17:13 Yoko kernel: nouveau E[ DRM] Pointer to TMDS table invalid
jún 21 13:17:13 Yoko kernel: nouveau E[ DRM] Pointer to flat panel table invalid
After 2 minutes of starting lspci this appears in the journal:
jún 21 12:11:42 Yoko kernel: INFO: task lspci:3111 blocked for more than 120 seconds.
jún 21 12:11:42 Yoko kernel: Tainted: G O 3.15.1-1-ARCH #1
jún 21 12:11:42 Yoko kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
jún 21 12:11:42 Yoko kernel: lspci D 0000000000000006 0 3111 3108 0x00000001
jún 21 12:11:42 Yoko kernel: ffff880447103d78 0000000000000086 ffff88043f75f010 0000000000014700
jún 21 12:11:42 Yoko kernel: ffff880447103fd8 0000000000014700 ffff88043f75f010 ffffffff810136c1
jún 21 12:11:42 Yoko kernel: ffff88045f391bc0 000000015f394700 ffff88043f75f608 ffff8803ed90db00
jún 21 12:11:42 Yoko kernel: Call Trace:
jún 21 12:11:42 Yoko kernel: [<ffffffff810136c1>] ? __switch_to+0x1f1/0x540
jún 21 12:11:42 Yoko kernel: [<ffffffff8109816a>] ? finish_task_switch+0x4a/0xf0
jún 21 12:11:42 Yoko kernel: [<ffffffff81509429>] ? __schedule+0x3b9/0x980
jún 21 12:11:42 Yoko kernel: [<ffffffff81509a19>] schedule+0x29/0x70
jún 21 12:11:42 Yoko kernel: [<ffffffff81399d0d>] __pm_runtime_barrier+0xad/0x170
jún 21 12:11:42 Yoko kernel: [<ffffffff810b1bd0>] ? __wake_up_sync+0x20/0x20
jún 21 12:11:42 Yoko kernel: [<ffffffff8139b1eb>] pm_runtime_barrier+0x5b/0xc0
jún 21 12:11:42 Yoko kernel: [<ffffffff812ccbab>] pci_config_pm_runtime_get+0x3b/0x60
jún 21 12:11:42 Yoko kernel: [<ffffffff812d0bdb>] pci_read_config+0x9b/0x2d0
jún 21 12:11:42 Yoko kernel: [<ffffffff8122e1d7>] sysfs_kf_bin_read+0x47/0x70
jún 21 12:11:42 Yoko kernel: [<ffffffff8122d8dd>] kernfs_fop_read+0x9d/0x160
jún 21 12:11:42 Yoko kernel: [<ffffffff811b4367>] vfs_read+0x97/0x160
jún 21 12:11:42 Yoko kernel: [<ffffffff811b51fa>] SyS_pread64+0x9a/0xc0
jún 21 12:11:42 Yoko kernel: [<ffffffff81515b35>] tracesys+0xd0/0xd5
Last edited by ijanos (2014-06-21 12:41:09)
Offline
Blacklisting the nouveau module solves this problem.
Offline
This thing just happened to me on an MSI GE62 6QD laptop, and this thread saved my day. I know this is an old thread, but I just wanted to add my laptop model here so hopefully people looking for it on a search engine will find what the problem is. This was also the cause of my Xserver failing to start.
Offline
This one saved me too, also from the issues with the X server not starting. Thanks!!
Edit:: I'm on an ASUS F550V in case it helps anyone else.
Last edited by Branau (2017-01-04 05:52:24)
Offline
Mod note: taking this opportunity to close this old thread.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Pages: 1
Topic closed