On Thu, Jun 15, 2006 at 08:48:56AM +0200, Michel Dänzer wrote: > On Wed, 2006-06-14 at 21:09 +0200, ruben wrote: > > > > Jun 14 20:11:07 guava kernel: [drm] Initialized drm 1.0.1 20051102 > > Jun 14 20:11:07 guava kernel: [drm] Initialized radeon 1.24.0 20060225 on minor 0 > > Jun 14 20:11:19 guava kernel: agpgart: Putting AGP V2 device at 0000:00:0b.0 into 1x mode > > Jun 14 20:11:19 guava kernel: agpgart: Putting AGP V2 device at 0000:00:10.0 into 1x mode > > Jun 14 20:11:19 guava kernel: [drm] Setting GART location based on old memory map > > This looks like you could be hitting > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369167 . Your patch attached to this bug does not solve my problem. I also tried updating to the latest DRM module from CVS which did not help either. It doesn't matter if I enable "UseFBDev". > > Also beware of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=363120 , > so one has to make sure suspend/resume switches to console. First switching to a VT with a Text Console does not solve the problem. I tried to anlalyse the problem a little bit further by looking at the Xserver logs: If I switch VTs back to X under normal Operations I see the following log messages: (**) RADEON(0): RADEONEnterVT (II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware. (II) RADEON(0): [agp] Mode 0x07000201 [AGP 0x106b/0x0066; Card 0x1002/0x4e50] (**) RADEON(0): EngineRestore (32/32) (**) RADEON(0): EngineRestore (32/32) (**) RADEON(0): RADEONSaveScreen(2) (II) Configured Mouse: ps2EnableDataReporting: succeeded Synaptics DeviceOn called (--) Synaptics Touchpad auto-dev sets device to /dev/input/event7 (**) Option "Device" "/dev/input/event7" (--) Synaptics Touchpad touchpad found If I switch back the first time after resuming from Suspend-to-Disk I see: (**) RADEON(0): RADEONEnterVT (II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware. (II) RADEON(0): [agp] Mode 0x07000201 [AGP 0x106b/0x0066; Card 0x1002/0x4e50] (**) RADEON(0): EngineRestore (32/32) After that I see a garbled screen and the XServer hangs hard (can not kill it with SIGKILL). I'm also unable to further switch VTs. Gaudenz > > > Jun 14 20:11:19 guava kernel: [drm] Loading R300 Microcode > > Jun 14 20:11:19 guava kernel: [drm] writeback test failed > > > > Normally, that last line looks like this: > > Jun 14 20:19:43 guava kernel: [drm] writeback test succeeded in 1 usecs > > > > I don't know whether that's important... > > It could be a symptom of the underlying problem. > > > it seems one can disable writeback with a parameter for the radeon module. > > It'll be disabled automatically if the test fails. > > > -- > Earthling Michel Dänzer | http://tungstengraphics.com > Libre software enthusiast | Debian, X and DRI developer > -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~
Attachment:
pgpWRX5xJjsnr.pgp
Description: PGP signature