XGL causes crash when resuming from suspend with NVIDIA cards

Bug #111380 reported by Luke12
6
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.20 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: nvidia-glx-new

I have done some experimenting with my Ubuntu Feisty + nvidia drivers in order to make suspend-to-ram and -disk work, and I have discovered that the GLX option is the one which actually crashes the suspend. I have tested this on my Dell Inspiron 6400, with NVIDIA 7300 card, TL5600 core duo processor. My xorg.conf file at the graphics card section reads so, using the latest nvidia driver (have not tested it with the nvidia-glx):

Section "Device"
    Identifier "nVidia Corporation G72M [Quadro NVS 110M/GeForce Go 7300]"
    Driver "nvidia"
    Option "NoLogo" "True"
    Option "RenderAccel" "True"
    Option "AddARGBGLXVisuals" "False"
    Option "AllowGLXWithComposite" "False"
EndSection

The suspend works fine but beryl/compiz do not function well: beryl for example gives the following error: Xlib: extension "GLX" missing on display ":0.0".
If I change the two last options to "True" and reboot, beryl/compiz will work, but when resuming from suspend-to-ram/disk the screen will be black with the cursor floating, no option of calling the terminal screen (ctrl+alt+f1), forcing a reboot. I think therefore that it is not the NVIDIA driver itself, but rather the GLX option which causes the crash.
I also have to report that I think I met this same bug once before, on my old laptop, an IBM Thinkpad R50e with a i810 graphics card. While I was trying to fix suspend on that machine I accidentally ruined my driver, in that I was no more able to launch xgl/aiglx applications such as beryl or compiz, and as a consequence suspend began to work. I do not remember how I did it and in fact I was no more able to repeat the accident, but these two experiences combined make me suspect that it is the xgl/aiglx projects which are causing the suspend bugs.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Thank you for your bug report.

This sounds like Bug #96240 ...

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Luke12:
Does disabling sync to vblank as described in Bug #96240 make any difference?

Changed in linux-restricted-modules-2.6.20:
status: Unconfirmed → Needs Info
Revision history for this message
Tim Richardson (tim-richardson) wrote :

Thanks Luke12, your suggested changes to xorg.conf finally let resume work for me. No other suggestions (and I've tried everything) worked.

Revision history for this message
Tim Richardson (tim-richardson) wrote :

PS Sitsofe, I looked at Bug #96240.
Before making the changes suggested by Luke12: on resume, the display worked. For example, I would first get a text console with warning messages about USB problems.
Then the display would show a blank black background, with a mouse pointer that I could move. To me this sounds like Bug #96240 is completely different.
I have 7.04 Feisty with Desktop effects enabled), nvidia 1.0-9755 driver, and kernel 2.6.20-16-generic

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux-restricted-modules-2.6.20 (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.