Ask Your Question
1

lspci results in soft lockup

asked 2017-07-31 04:28:06 -0500

kthommy gravatar image

I've had a problem for a while that seemed to be common with nvidia graphic cards: trouble on boot, a soft lockup on shutdown. No big deal, there are tutorials to help with that.

The real problem is that when I simply try to lspci, I get the same soft lockup. It also happens when I try to fall back on a xorg session just in case it would be wayland causing this. Also, I've seen soft lockups described as "something that slows down your computer" but on my machine it just freezes completely, even the tty don't answer. I'm feeling pretty helpless there.

I retrieved the details of my computer specs from a website (because I don't want to freeze before I post this message), this should be correct :

Processor : Intel Core i7-7700HQ 2.8 GHz (Intel Core i7)
Graphics adapter : NVIDIA GeForce GTX 1050 (Notebook) - 4096 MB, Core: 1354 MHz, Memory: 7008 MHz, GDDR5, 373.06, Optimus
Memory : 16384 MB, 1300 MHz, Dual-Channel, 17-17-17-39, 2x SODIMM

As far as fedora goes, I have upgraded to fedora 26 just today. The nvidia / nouveau bug was there before, but nowhere that bad. I think if I could at least use lspci again I could start fixing whatever is causing the rest of it.

Anyone has any idea about where I could start?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2017-07-31 05:50:50 -0500

ozeszty gravatar image

Nouveau is far from stable on newer GPUs, Nvidia makes nouveau devs' lives more and more difficult...

Go to https://nouveau.freedesktop.org/wiki/ for troubleshooting and bug reporting instructions.

For now the easiest workaround is to install proprietary drivers: https://rpmfusion.org/Howto/NVIDIA

edit flag offensive delete link more

Comments

Yeah, I got that part, but the very basic first instruction they have is always to check lspci =_= I guess I'll report to them, then. Thanks for the link!


Edit: I went blind and installed the nvidia drivers anyway for what I suspected was my graphic card (following this tutorial), and it appears to be working, more or less. I'll wait and give more precise feedback on what works and what doesn't before closing this question.

kthommy gravatar imagekthommy ( 2017-07-31 07:13:41 -0500 )edit

lspci won't show you much more than you already know, try lspci -vvv > lspcioutput (> will direct output to a file, so you can later check what system managed to save in there; -vvv will add more info).

You can try inxi -v7z or fpaste --printonly --sysinfo, but those might also lead to a lockup. You'll probably find some useful information in dmesg and journalctl.

After startup don't login but press Ctrl+Alt+F2, login and execute dmesg -Tw > dmesgoutput then login again in Ctrl+Alt+F3 and start lspci. Or follow https://nouveau.freedesktop.org/wiki/...

ozeszty gravatar imageozeszty ( 2017-07-31 09:01:01 -0500 )edit

Wayland support is also not 100 percent yet, so you might consider disabling Wayland. Your nvidia driver version of 373.06 is really old, might consider updating that, to see if any bug fixes make it better. I am running 384.59 with kernel 4.11.11-300 on fc26 with no issues. used dkms to update when kernels are installed, and have had no issues.

SteveEbey73701 gravatar imageSteveEbey73701 ( 2017-07-31 14:57:11 -0500 )edit

Question Tools

Stats

Asked: 2017-07-31 04:28:06 -0500

Seen: 248 times

Last updated: Jul 31 '17