Created attachment 49578 [details] [review]
X.org server log
Sometimes when locking my screen manually, X.org simply crashes with a segmentation fault in the log (attached). I think this occurs shortly after pressing lock screen but not immediately, since I usually only notice when I get back. I'm running a dual-head radeon setup.
The only relevant lines I could find were the stack with the segmentation fault and several lines preceding it about a busy resource:
[1543050.722] (WW) RADEON(0): divisor 0 get vblank counter failed: Device or resource busy
[1543050.747] (WW) RADEON(0): divisor 0 get vblank counter failed: Device or resource busy
[1543050.752] (WW) RADEON(0): divisor 0 get vblank counter failed: Device or resource busy
Can you get a full backtrace with gdb? See the instructions here:
Your radeon_drv.so seems kind of old, can you try updating it?
I'm trying to do just that. Running with gdb attached it hasn't occurred yet though. Not sure if that's because there's some other factor that triggers it that I'm missing, or because interaction with gdb covers the bug. I'll keep trying.
I'm using the latest version of Ubuntu and I have no idea how to swap out display drivers easily. Is there a way that doesn't involve compiling X from scratch?
Wim De Smet, Ubuntu 11.04 reached EOL on October 28, 2012. For more on this, please see https://wiki.ubuntu.com/Releases .
If this is reproducible in a supported release, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
Also, please feel free to subscribe me to it.
For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.
on Mar 27, 2017 at 18:23:19.
(provided by the Example extension).