Bug 4453

Could you try 2.6.12-rc2 please?

Created attachment 4871 [details]
Screen picture (camera snapshot) representing the issue described.

Note that radeonfb isn't doing much on suspend/resume on non-pmacs. it basically
blanks the screen on suspend, and re-sets the mode & unblanks the screen on
resume. I don't know what could cause it to get "scrambled" (can you explain
what you actually mean by "scrambled" ? best is to get a snapshot of the screen
with a digital camera). Probably yet another interaction with the BIOS ...

Ah ok, here it is. Thanks. Weird ... what if you kill and restart X ? Does that
fixes it ? radeon "old" driver is really the same as 2.6.9 one so I suspect it's
something else causing this, like some ACPI update or something, causing the
BIOS to do something to the chip that triggers that issue...

More info: the video card is reported as: ATI Radeon Mobility M9. I have
attached a picture taken from the screen with a digital camera. You may see in
the picture  dotted vertical lines. The picture only represents a static
snapshot, however those lines "vibrate" through the screen making reading
impossible. The only workaround in this situation is a shutdown. I will be too
happy to supply further information if required.

Mauro

Killing and restarting X does not solve the problem, in fact when leaving X the
same effect applies to console mode.

I will try 2.6.12-rc2, however I will have to build from scratch and it will
take some time (tomorrow, is 1:25am here now).

Mauro

I have tested 2.6.11-rc2 with both old and new driver and the same problem occurs.
Mauro

I think I have the same problem here. I do not resume from suspend but just
boot. Setup: Kernel 2.6.11.7 (debian source), ATI Radeon Mobility 9000 (M9)

After booting, sometimes the screen is scrambled like described and shown in the
picture above. Then, moving the mouse cursor over some gui element (a button for
example), this part of the screen gets rendered correctly (it only works
sometimes, unreproducibly). In this state, killing the X server restores X and
console to a correct state. 

If I can help with providing more info, please contact me.

Guys, are these problems still happening in 2.6.12-rc5?

I have 2.6.12rc5 now running for one week and until now, no problems regarding 
this bug occurred. Hope it stays this way, otherwise, I will post again. Thanks 
very much! 

Dirk Reiss' problem sounds like a different one to me. I have the same hardware
(Inspiron 8200 + Radeon 9000 Mobile), running Mandriva LE2005 with kernel
2.6.11-6mdk. After s3 suspend to ram, the screen is black with no backlight. If
I instead do the following (from console):

vbetool dpms off; echo "3" > /proc/acpi/sleep; vbetool dpms on; vbetool post

the screen comes back scrambled most of the time.  It clearly is a video issue
since I can type away at the terminal without problems. The strange thing is
that every ten times or so the screen comes back just fine!

I have tried all sorts of things, including:
- Booting without framebuffer
- Suspending from Xorg with VBERestore = true
- Kernel options acpi_sleep=s3_bios or acpi_sleep=s3_mode (gives reboot without
backlight, so probably not applicable)
- Kernel patch acpi_sleep=s3_late_bios
- Various alternatives to vbetool: radeontool, boot-radeon, video_post

The same thing happens with unpatched kernels 2.6.11.11 and 2.6.12.1.

Unfortunately, 2.6.12.1 still lets this problem occur, less frequently, but still.
 
Regarding comment #11: I am not sure if it is the same problem, but the screen
actually looks like the image attached to this report, the console in this
scrambled state looks also broken (blinking and colored characters all over),
the only difference seems to be that it gets broken even if not resuming. 

I'll close this just because it's been almost 2 years since the last comment. 
Reopen if the problem persist.

Guys, I am now at Fedora 7, two years later this bug is still unresolved: when I suspend my Inspiron 8200, after it comes back the picture still looks like the one posted two years ago. The only solution is a shutdown and reboot. Nedless to say that there are no problems with Windoze.

Is anyone looking at this issue?

Please try s2ram (http://en.opensuse.org/s2ram).

Also, there is an important fix that may be related to this problem in the current Linus' tree (2.6.23-rc7-git4 as of today).  Please test it.

Update:
Please try 2.6.23 and s2ram.

[If there's no response within 2 weeks, I will stop tracking this bug.]

As I said, I'm closing this bug.  Please reopen if necessary, thanks.