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
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
|
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
Tuesday, 10 December 2019, 09:51 GMT
Reason for closing: No response
* journalctl -k
* lspci
* /car/cache/pacman.log
Could help to track the problem
lspci.log (11.7 KiB)
pacman.log (53.6 KiB)
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.
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/