FS#53293 - mesa 17.0.1-2 causes hangs when executing xrandr, lspci, lshw

Attached to Project: Arch Linux
Opened by David Thiede (davet) - Monday, 13 March 2017, 17:44 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 10 December 2019, 09:51 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: The upgrade to mesa-17.0.1.2 seems to have broken a number of tools. the xrandr command locked up the GUI completely. running the lspic and lshw commands causes the shell in use to be unresponsive. it is possible to kill the shell from another shell but the commands themselves are in 'D' (Task Uninterruptible) state and cannot be killed. A cut/paste from one shell to another also has now apparently caused a similar GUI lockup.
I attempted to downgrade the packages but there is a dependency on 'opengl-driver' that i haven't resolved so haven't been able to verify which upgrade exactly caused the issue.

Additional info:
* package version(s)
the mesa-17.0.1.2 package obsoleted the mesa-libgl-17.0.1-1 package so that might be related.

* config and/or log files etc.

Steps to reproduce:
open an xterm and type in either lspci or lshw. it doesn't seem to matter if you have root (sudo) privileges or not.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 10 December 2019, 09:51 GMT
Reason for closing:  No response
Comment by Laurent Carlier (lordheavy) - Monday, 13 March 2017, 18:41 GMT
It should not be related to a mesa upgrade. Do you have any logs?
* journalctl -k
* lspci
* /car/cache/pacman.log

Could help to track the problem
Comment by David Thiede (davet) - Monday, 13 March 2017, 21:18 GMT
hope this helps. machine crashed trying to get lspci log. got from multi-user mode. logging in from another machine via ssh still causes the hangs.
Comment by David Thiede (davet) - Thursday, 16 March 2017, 14:45 GMT
work keeps interfering with testing on the system where i first found this issue. i upgraded an older machine and have experienced the same issue. lshw and lspci will hang. This system also has NVIDIA cards. dual Quadro FX 580 in this case. Additionally the desktop didn't come up when i ran startxfce4. i dug around on various forums and found a references to possible issues with the nouveau module. they suggested blacklisting the module and configuring the nvidia drivers. i added the blacklist entry and of course it keeps the graphics from coming up but the lshw and lspci commands now don't hang. I haven't tried the nvidia drivers.

I agree that this is not really from the the mesa upgrade but not really sure where to point. None of the virtual machine installs have this issue. The full upgrade has also been applied to a laptop that is running intel graphics and it had no issue. This seems to be NVIDIA specific. I've attached the pacman log from the time of this second upgrade trial described above.
Comment by Emil (xexaxo) - Monday, 18 September 2017, 10:17 GMT
David as you look in the journal.log (or dmesg) you'll see that the nouveau kernel module tries to power off the card.
At this point it gets stuck and volla, a surprise.

AFAICT this is not a Mesa problem - Mesa simply made the issue visible.

Please report this upstream to the nouveau people
https://nouveau.freedesktop.org/wiki/

Loading...