[RV250 9200] No more X on resume after hibernate

[Snark]

I'm using breezy on an ASUS A2D laptop and can hibernate and resume from console
without problem (which means I setup my swap partition correctly in
/boot/grub/menu.lst).

The failing occurs in the following situations :
- hibernating from X and coming back from hibernation doesn't work ;
- switching to console, hibernating and coming back works, but then switching to
X again fails.

I think the problem is related to reenabling the video memory : when the laptop
boots up, it displays a centered "ASUS", then proceeds with resuming ; and when
X restarts, "ASUS" is displayed, repeated several times over the display. And
the box is crashed...

I'm using the radeon driver (not fglrx) with the following card (lspci): VGA
compatible controller: ATI Technologies Inc RV250 5c61 [Radeon Mobility 9200
M9+] (rev 01).

Hope I wrote enough information -- in case it's needed I can do tests and report.

[Daniel Stone (daniels)]

does setting POST_VIDEO=true help? or false, if it's currently set. matt,
thoughts?

[Snark (julien-puydt)]

(In reply to comment #1)
> does setting POST_VIDEO=true help? or false, if it's currently set. matt,
> thoughts?

I tried toggling this in /etc/default/acpi-support, but didn't see any difference...

[Matthew Garrett (mjg59)]

Try commenting out the

unset VIDEO_POST

line in /etc/acpi/hibernate.sh

[Snark (julien-puydt)]

I commented out the #unset POST_VIDEO as suggested, then retried to hibernate
with POST_VIDEO=true/false, but still no change.

Someone here http://forum.ubuntu-fr.org/viewtopic.php?pid=106989#p106989
suggests hibernate and 3D boost should probably be considered incompatible... is
it true ?

[Snark (julien-puydt)]

Uh... I had forgotten I had reported the problem here... just discovered it again.

I have both suspend&hibernate working with 2.6.15-27-k7 (not perfectly for hibernate : I have to switch back&forth from console before getting my screen back -- and it's not locked).

Disabling DRI made it work.

More recent kernels just don't work.

[Greg Michalec (greg-primate)]

I have this same problem. I have a ATI Mobility Radeon 9600 M10 (RV350) and an AMD Athlon64 3000+ cpu. I've tried both the radeon and fglrx drivers and neither seem to work - it's the same scenario as above: when I hit "hibernate", the machine seems to shut down fine, starts back up, but when it gets to X it hangs, with a garbled screen similar to this: http://beework.isgreat.org/var/log/screenshot.JPG
(from bug #72417, which may be a duplicate).

Also, if I hibernate from the console, it resumes fine, but once I switch back to X, i get a screen like above and the system is hung.

I'm not sure what further steps to take to debug this.

Thanks.

[Greg Michalec (greg-primate)]

I just did some more testing, and it turns out that I *can* ssh into the machine after it has stopped responding. I even shut down gdm via ssh, but still was unable to make the machine respond to the local keyboard.
Also, I should note that I am running Edgy with all the current updates, and that at one point hibernate did work.

[Snark (julien-puydt)]

@Greg Michalec: did you try to disable DRI? That's what makes it mostly work for me.

[Marco Trevisan (Treviño) (3v1n0)]

If you use AiGLX the only way is upgrade to Xorg 7.2 or applying the patch attached at https://launchpad.net/ubuntu/+source/xorg-server/+bug/86753

[Snark (julien-puydt)]

1) when dri is disabled, suspend/resume just works in any case ;
2) when dri is enabled, and I suspend/resume from inside an xterm, X blocks on
resume (black screen, flashing lights, magic system key reboot required) ;
3) when dri is enabled, but I suspend/resume from console, things run
smoother... until I switch back to X, in which case we're back to the crashy
case ;
4) finally, if I boot without X and suspend/resume, then launch X with dri, then I get the crash.

So it looks like something in DRI-land doesn't like when a box has been resumed.

Here is what lspci -vvv says about my video system :
01:00.0 VGA compatible controller: ATI Technologies Inc M9+ 5C61 [Radeon
Mobility 9200 (AGP)] (rev 01) (prog-if 00 [VGA])
        Subsystem: ASUSTeK Computer Inc. Unknown device 1811
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (2000ns min), Cache Line Size: 256 bytes
        Interrupt: pin A routed to IRQ 10
        Region 0: Memory at c0000000 (32-bit, prefetchable) [size=128M]
        Region 1: I/O ports at d000 [size=256]
        Region 2: Memory at feaf0000 (32-bit, non-prefetchable) [size=64K]
        Expansion ROM at feac0000 [disabled] [size=128K]
        Capabilities: <access denied>

[Snark (julien-puydt)]

I forgot (!) to mention that I'm running debian/unstable with a distribution-supplied linux 2.6.20 kernel.

[Michel-tungstengraphics (michel-tungstengraphics)]

Suspend to RAM or disk? Note that this could also be an AGP driver issue. Please attach (as opposed to paste) X config and log files and the dmesg output.

[Snark (julien-puydt)]

Created an attachment (id=9996)
Running dmesg after a clean startup

[Snark (julien-puydt)]

Created an attachment (id=9997)
Xorg log after a clean startup

[Snark (julien-puydt)]

Created an attachment (id=9998)
Running dmesg after a resume in console

[Snark (julien-puydt)]

Created an attachment (id=9999)
Xorg log after the resume

[Snark (julien-puydt)]

Created an attachment (id=10000)
My xorg.conf

There's a commented Disable "dri" line because I usually prefer having hibernation than 3d.

[Snark (julien-puydt)]

Ah, yes, I forgot to answer the first question : It's about hibernating (suspend to disk).

If I can provide more information...

[Simon Hepburn (sth)]

I have the same issue with feisty/Xorg 7.2. Hardware is a Compaq Evo 510 desktop and a Radeon 9550 [RV350 AS] AGP card. When resuming from suspend I get a blank (but backlit) screen. I cannot switch to Console mode and have to reboot. I have tried modifying /etc/default/acpi-support but it made no difference.

Resume works fine if I disable DRI.

[Snark (julien-puydt)]

I reported it upstream as :
http://bugs.freedesktop.org/show_bug.cgi?id=10975

The more we will be interested and ready to give information about the matter, the faster it will get fixed. The ideal situation is if one of us had a clue about the code itself.

[Snark (julien-puydt)]

I did some more tests this morning : suspend to disk or to ram shows the same problem.

I noticed that radeon(4) says AGP is enabled only with DRI... is there a way to still enable AGP without DRI, to see whether that's the problem as suggested?

[Michel-tungstengraphics (michel-tungstengraphics)]

(In reply to comment #9)
> I noticed that radeon(4) says AGP is enabled only with DRI... is there a way to
> still enable AGP without DRI, to see whether that's the problem as suggested?

The point is that AGP is only used by the DRI, so even if it could be 'enabled' without it that would hardly matter. Another way to test this could be Option "BusType" "PCI" to make the driver not use AGP.

[Bugzi09-fdo-tormod (bugzi09-fdo-tormod)]

I notice that you have an AGP 8X card, but is running it in 4X. There has been reported trouble when the BIOS sets it for one speed, and Xorg uses another. Although this was supposed to be fixed, can you try setting (in xorg.conf):
 Option "AGPMode" "8"
or look at your BIOS settings?

[Snark (julien-puydt)]

I made the suggested tries :
- the BIOS doesn't give advanced settings about display ;
- setting the AGPMode to 8 didn't give improvement ;
- setting BusType to PCI makes resume work even with DRI.

So it looks like an AGP bug ; what more can I do to track the issue further?

[Snark (julien-puydt)]

Notice that if it's a matter of doing an apt-get source, patch the source (to enable more debugging output, for example), then compile a newer package, I'm used to it.

Waiting for directions : a dead bug always makes my day :-)

[Timo Jyrinki (timo-jyrinki-hut)]

*** Bug 11216 has been marked as a duplicate of this bug. ***

[Bryce Harrington (bryce)]

I don't know if this will fix this specific issue, but I've backported a bunch of high importance patches that upstream recommended, that fix problems sort of like this one, so I think it would be worth the time to test. Please try this .deb and report what you find:

http://people.ubuntu.com/~bryce/Testing/ati/

If we can determine that the patches in this deb fix this bug, they may be candidates for backporting to Hardy.

[Tormod Volden (tormodvolden)]

Can you please test with the -ati and -radeon packages from my PPA? See https://wiki.ubuntu.com/XorgOnTheEdge. A similar issue has been solved (bug #148408).

[Bryce Harrington (bryce)]

Based on the description of the symptoms, it sort of sounds like this might be caused by an incorrect AGPMode setting, which is relevant when DRI is enabled. You should test if changing this makes the issue go away. In your /etc/X11/xorg.conf set AGPMode to various values like this:

Section "Device"
   ...
   Option "AGPMode" "2"
EndSection

Possible values include 1, 2, 4, 8. You can see what it's currently set to by looking in /var/log/Xorg.0.log. It's worthwhile to test all four values even once you find one that works. If this takes care of it for you, we may be able to establish a quirk to set it for your hardware combo, if you can provide the following data:

  * AGPMode value(s) that work
  * Make/Model of laptop or motherboard
  * Output of lspci -vvnn
  * Is the system all factory hardware, or have any parts been replaced?
  * Is there an AGP Mode in the system BIOS?
    - If so, is it set to the factory default?

For more details on this, please see the "ATI AGP Mode Quirk" section at https://wiki.ubuntu.com/X/Quirks

[Bryce Harrington (bryce)]

Thank you for reporting this bug, however not enough information was included for us to troubleshoot this problem as an X.org issue. If you are still able to reproduce this issue on the current development release and wish to continue the investigation please refer to http://wiki.ubuntu.com/X/Reporting for guidance on how to report X.org bugs, and file a new bug or reopen this one with additional information.

[Martin-peres-n (martin-peres-n)]

Hi,

Freedesktop's Bugzilla instance is EOLed and open bugs are about to be migrated to http://gitlab.freedesktop.org.

To avoid migrating out of date bugs, I am now closing all the bugs that did not see any activity in the past year. If the issue is still happening, please create a new bug in the relevant project at https://gitlab.freedesktop.org/drm (use misc by default).

Sorry about the noise!