Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613
On 2024-02-17 18:53 +0100, Sven Joachim wrote: > Control: severity -1 grave > > On 2024-02-17 13:35 +0100, Lorenzo Beretta wrote: > >> Package: libgl1-mesa-dri >> Version: 24.0.1-1 >> Severity: important >> >> Dear Maintainer, >> >> after the latest upgrade it's impossible for me to run a display manager >> or startx any window manager; after at most a few seconds / keypresses / >> mouse movements the screen freezes, completely unresponsive to anything >> other than the power button; the log below suggests a null pointer. >> >> Running "sleep 30; killall -u lorenzo" as root before startx returns me >> to a tty. >> >> Reverting to the previous version everything works. >> >> I'm running this on a debian derivative, devuan; afaik it shouldn't make >> a difference, as the package is unmodified from debian - I don't know >> how to verify that other than by installing debian in some partition, >> can one start some window manager from a debian chroot/whatever? >> >> If it's ok in debian or you need any more info please do let me know. > > I can reproduce that on my laptop which runs pure Debian, and at least > one other user seems to have the same problem. > >> VGA-compatible devices on PCI bus: >> ---------------------------------- >> 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. >> [AMD/ATI] Oland [Radeon HD 8570 / R5 430 OEM / R7 240/340 / Radeon 520 >> OEM] [1002:6611] > > I have the following graphics hardware: > > ,---- > | 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, > | Inc. [AMD/ATI] Mullins [Radeon R3 Graphics] [1002:985\ 0] (rev 40) > `---- > > This is also using the radeonsi driver, and the symptoms and the > backtrace are the same as yours. > > Bumping severity to keep this mesa version out of testing, but I will > not be able to investigate the problem because I need the machine and > have already downgraded all packages from src:mesa. There does not seem > to be an upstream report yet. Looks like there is one now and it even has a patch which seems to have been applied in Archlinux and Ubuntu, but not committed upstream. :-( Cheers, Sven