Bug#560126: xserver-xorg-video-radeon: Launching GL Apps Corrupts System
Leo L. Schwab wrote:
> Package: xserver-xorg-video-radeon
> Version: 1:6.12.3-1
> Severity: critical
> Justification: breaks the whole system
> After launching virtually any GL screensaver, the system appears to
> become corrupted beyond usability.
> After exiting the screensaver, any one of several system-wide errors
> manifest themselves, preventing the launch of any new program (including
> programs to shut the system down). The only way to regain control of the
> system is a hard reboot.
> Among the errors observed so far:
> - Errors reporting system libraries are corrupt.
> - Errors reporting the requested program isn't a valid binary image.
> - Errors reporting a corrupt filesystem.
> - Running daemons, which were running fine before, suddenly
> reporting segfaults.
> This strongly suggests the graphics (or related) driver is
> clobbering random system memory.
> I've upgraded to the 'unstable' mesa libraries, and to the
> 2.6.32-rc8 kernel. Same problems.
You may try upgrading to experimental now...
> I realize this report is terribly vague -- I haven't been able to
> more concretely characterize the problem.
> To reproduce on this system (at least, how I've been doing it):
> - Launch X, any window server/desktop environment.
> - Open a terminal.
> - Issue the command: "xscreensaver-command -activate". Iterate
> until you get a GL screensaver.
> - Allow the screensaver to run for a few seconds, then press a key
> to exit back to the desktop.
> You should be unable to run any new program. More specifically, you
> should be unable to run any program that isn't cached. (Example: After
> exiting the screensaver, you can (probably) run 'xscreensaver-command'
> again, but attempts to run 'ls' or any other utility will likely fail.)
I can't reproduce this on my Radeon X300 (rv370).
When did this problem start? What did you upgrade when it started?
Since nobody else has ever reported such a critical problem (while the
radeon driver has many users), I suggest your check your installation
(with debsums for instance) and maybe check your hardware as well
(memtest, smartctl, is there some sort of memtest for video?). Something
strange is going on here...