Bug#565344: [xserver-xorg-video-radeon] Black screen after resume from suspend to disk/RAM

[Michel Dänzer]

On Fri, 2010-01-15 at 16:19 +0100, Bruno Kleinert wrote: 
> Am Freitag, den 15.01.2010, 15:57 +0100 schrieb Michel Dänzer:
> > On Fri, 2010-01-15 at 12:59 +0100, Bruno Kleinert wrote: 
> > > Am Freitag, den 15.01.2010, 10:58 +0100 schrieb Michel Dänzer:
> > > > > after an upgrade to version 6.12.4-2 from 6.12.3-1 I get nothing but a
> > > > > mouse cursor and a black screen when I resume the machine from suspend
> > > > > to disk or RAM.
> > > > 
> > > > Would be interesting to try building 6.12.3-1 against current
> > > > xserver-xorg-dev and see if that still works with the current
> > > > xserver-xorg-core.
> > > I'll give it a try tomorrow as I can't access the machine today.
> > > 
> > > In the meantime I found out something interesting: I can reproduce the
> > > same bug on a completely different machine, my Intel-based notebook.
> > > It's only a 32bit system and, in contrast to my other machine, it runs
> > > KMS.
> > > 
> > > Right after installing the mesa 7.7 packages from experimental and
> > > restarted X, I can suspend the notebook and after resume the notebook
> > > ends up with a completely black screen (not even the mouse pointer is
> > > visiable) but everything else apperently works: I blindly switched to a
> > > console and could reboot the notebook. When switching to the KMS
> > > framebuffer console the screen also remains all black.
> > > 
> > > I upgraded libgl1-mesa-dri, libgl1-mesa-glx, libglu1-mesa and mesa-utils
> > > to 7.7-1 on the notebook (it's the same on my other machine) to
> > > reproduce the bug. After downgrading to mesa 7.6.1 packages on the
> > > notebook suspend+resume worked fine again and without a black screen.
> > > 
> > > I'll try downgrading mesa on my other machine with the Radeon GPU
> > > tomorrow to check out if that will fix the bug on that machine.
> > > 
> > > Ok, obviously I addressed this bug report to the wrong package, but I
> > > need to do some more testing to find out the right package where to
> > > forward the report ;)
> > 
> > It could also be different problems with similar symptoms. Log in via
> > ssh and check the X log file, the gdm/kdm log file and dmesg for any
> > relevant output when the screen is black.
> I did have a look at the log files on my amd64 machine, but there's
> nothing in them when the screen and the text console stay black. Nothing
> in Xorg.log, .xsession-errors and kern.log. TBH I forgot to look into
> gdm.log.
> 
> On the Intel-based notebook I didn't look into .xsession-errors and
> gdm.log. Xorg.log and kern.log don't contain any hints about what's
> going wrong, not even anything from the - usually more verbose - i915
> kernel module KMS/GEM code.

Things like assertion failures or unresolved symbols are only visible on
the X server stderr output, which should be captured in the gdm log
file.


-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer