[i965gm] system unresponsive after recovery from screensaver

Bug #328760 reported by Bernhard
24
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-screensaver (Ubuntu)
Invalid
Undecided
Unassigned
xserver-xorg-video-intel (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

It happened to me a handful of times in the last weeks that I have (approximately) firefox, gnome-terminal, and amarok running, I leave the computer for a while so the screensaver starts ... then I come back, move the mouse, and I see the desktop wallpaper but nothing else! (Not even the icons on it.) The screen is completely frozen, I cannot enter anything, not even key combinations like CTRL-ALT-F1 or CTRL-ALT-REMOVE. Nothing works, completely frozen. But funny enough, amarok is still playing music!
The only way to get out of it for me was to press the "Quit" button for 5 sec and cut off power.

I don't really know what's going on there, couldn't do anything so I couldn't check the system monitor either. But since music was still playing normally I think that Xorg was still working, just unresponsive. Maybe it's a screensaver bug since it always happens when I recover from screensaver. Anyway, I would be interested if other people have experienced the same, it's a pretty nasty bug because you have to cut off power to get back on.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03)
     Subsystem: Fujitsu Siemens Computers Device [1734:111f]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03)
     Subsystem: Fujitsu Siemens Computers Device [1734:111f]

Tags: freeze
Bernhard (b.a.koenig)
description: updated
description: updated
Revision history for this message
George Lesica (oldmanstan) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please attach your X server configuration file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.0.log) to the bug report as individual uncompressed file attachments using the "Attachment:" box below. Could you please also try to run without any /etc/X11/xorg.conf and let Xorg autodetect your display and video card? Please also attach the /var/log/Xorg.0.log from this attempt. Thanks in advance.

Revision history for this message
Bernhard (b.a.koenig) wrote :

> uname -a
Linux amilo 2.6.27-12-generic #1 SMP Thu Feb 5 09:26:42 UTC 2009 x86_64 GNU/Linux

Revision history for this message
Bernhard (b.a.koenig) wrote :
Revision history for this message
Bernhard (b.a.koenig) wrote :
Revision history for this message
Bernhard (b.a.koenig) wrote :
Revision history for this message
Bernhard (b.a.koenig) wrote :

As for autodetect of display and video card: my current Xorg.0.log must contain the autodetected display and video card because I never messed around with that file ever.

Revision history for this message
Ted Gould (ted) wrote :

Marking as invalid in gnome-screensaver. It looks like an issue with multiple GL contexts.

Changed in gnome-screensaver:
status: New → Invalid
Bryce Harrington (bryce)
Changed in xorg:
status: New → Confirmed
Revision history for this message
FabioV (fabiovigolo) wrote :

I've got exactly the same problem. The only difference is that I use random screen savers and when the display is frozen I see the screen saver image frozen and not the desktop wallpapaer as Bernhard does.
I'll attach same files you asked Bernhard for.

My uname -a output is:
Linux U-PT250 2.6.24-24-generic #1 SMP Thu Feb 19 08:00:07 UTC 2009 i686 GNU/Linux

Thank you for assistance.
Fabio

Revision history for this message
FabioV (fabiovigolo) wrote :
Revision history for this message
FabioV (fabiovigolo) wrote :
Revision history for this message
FabioV (fabiovigolo) wrote :

My current Xorg.0.log must contain the autodetected display and video card because I never messed around with that file ever.

Bryce Harrington (bryce)
description: updated
Bryce Harrington (bryce)
summary: - system unresponsive after recovery from screensaver with only desktop
- wallpaper showing
+ [i965gm] system unresponsive after recovery from screensaver with only
+ desktop wallpaper showing
Bryce Harrington (bryce)
tags: added: freeze
Revision history for this message
Mike.lifeguard (mikelifeguard) wrote : Re: [i965gm] system unresponsive after recovery from screensaver with only desktop wallpaper showing

Are we sure this involves showing only the wallpaper? My laptop freezes under near-identical conditions, but shows only a blank screen (actually it is powered off, not just black or blank), as reported at https://bugs.freedesktop.org/show_bug.cgi?id=22383#c2

Revision history for this message
Bernhard (b.a.koenig) wrote :

@Mike: I guess there can be variations, as FabioV also had a slightly difference experience. But this bug has to do with a freeze after recovery from screensaver.

Bernhard (b.a.koenig)
summary: - [i965gm] system unresponsive after recovery from screensaver with only
- desktop wallpaper showing
+ [i965gm] system unresponsive after recovery from screensaver
Revision history for this message
Bryce Harrington (bryce) wrote :

Well, next I'd like to forward this issue upstream, but first it must be retested on latest development version of Karmic to make sure the issue still happens there with the latest code. ISO images are available at http://cdimages.ubuntu.com/releases/karmic/. If you can reproduce it in the LiveCD environment, you shouldn't need to modify your installed system. Also please attach a fresh Xorg.0.log and dmesg from this testing.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Bernhard (b.a.koenig) wrote :

I actually stopped having freezes after recovery from screensaver when I switched from intrepid to jaunty. So there's one thing that worked better for me in jaunty. :)
Cannot reproduce it anymore on my machine at the moment.

Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks for letting us know the issue is resolved.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Bernhard (b.a.koenig) wrote :

Well, not sure if this is "Fix committed". I didn't have anymore problems with it since jaunty, but Mike.lifeguard has. He might have a different type of freeze though.

Revision history for this message
Mike.lifeguard (mikelifeguard) wrote :

I /think/ we're OK... I haven't needed to leave my laptop running overnight in a while, but I'll do so tonight.

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

Other bug subscribers

Related questions

Remote bug watches

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