Xorg freeze after suspend blank screen

Bug #527527 reported by Akshay Guleria
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Binary package hint: xorg

After the machine has been suspended by either closing the laptop lid or by manually calling suspend from shut down menu. And I try to wake it up by opening the lid, I get a blank screen. Nothing works. Ctrl+Alt+F1 ror Ctrl+Alt+F7 nothing works. I do not see anything on the screen. All the LEDs, however, light up which means machine might be up and running - i just am not able to see it.
I have tried the quirks @ https://wiki.ubuntu.com/X/Quirks#Force%20Pipe%20A%20Quirk but this does not help either.

gnome-power-manager is version 2.29.1-0ubuntu2
Ubuntu version is ... Ubuntu lucid (development branch)
Kernel version is ... linux-generic-2.6.32.12.12.

ProblemType: Bug
Architecture: i386
Date: Wed Feb 24 20:44:32 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: virtualbox-ose, 3.1.2, 2.6.32-12-generic, i686: installed
MachineType: TOSHIBA TECRA M8
Package: xorg 1:7.5+1ubuntu2
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=0f021f5e-8b62-428e-a2a8-0fa92b0c0dfd ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
RelatedPackageVersions:
 xserver-xorg 1:7.5+1ubuntu2
 libgl1-mesa-glx 7.7-0ubuntu8
 libdrm2 2.4.17-0ubuntu2
 xserver-xorg-video-intel 2:2.9.1-1ubuntu3
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
Uname: Linux 2.6.32-12-generic i686
dmi.bios.date: 12/02/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V5.00
dmi.board.name: TECRA M8
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV5.00:bd12/02/2008:svnTOSHIBA:pnTECRAM8:pvrPTM80U-04C00E:rvnTOSHIBA:rnTECRAM8:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: TECRA M8
dmi.product.version: PTM80U-04C00E
dmi.sys.vendor: TOSHIBA
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.32-12-generic

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03)
     Subsystem: Toshiba America Info Systems Device [1179:ff50]

Revision history for this message
Akshay Guleria (axayg) wrote :
Timo Aaltonen (tjaalton)
affects: xorg (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
Bryce Harrington (bryce)
tags: added: resume
tags: added: black-screen
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Thanks for reporting this bug to help making the Intel graphics driver
better. We hear from upstream that a number of bugs (possibly including
this one) have been fixed in the newer DRM code from the 2.6.33 kernel.
I don't know if your bug is one of the ones fixed in this release,
though, but we've prepared a PPA with this DRM update. Would you mind
installing this, rebooting, and testing if the original issue can be
reproduced with it or not?

The DRM PPA is here:

    https://edge.launchpad.net/~apw/+archive/red

Note there could be new bugs... please file these as new reports using
the command 'ubuntu-bug linux' (for kernel or DRM or KMS bugs) or
'ubuntu-bug xorg' if you suspect them to be X.org issues.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Akshay Guleria (axayg) wrote :
Download full text (4.2 KiB)

Installed the ppa:apw/red from the link ..
   https://edge.launchpad.net/~apw/+archive/red

Did my testing below with limited stuff running on the desktop. Only scenario 4 was successful - rest failed. Please see the testing results below. In short, the bug exists if I carry out suspend by closing laptop lid (a common scenario) as compared to do a manual suspend. Attaching the /var/log/pm-suspend log file. The only thing that happened between the scenarios is reboots - check the last 4-5 entries - i carried out my testing in the below order.

Scenario 1:
- Close laptop lid. Laptop is set to suspend in powermanager settings.
- LED indicate the laptop did not suspend properly. The powerstate LED is expected to blink on successful suspend
- Open the lid. The screen is blank. No response to Ctrl+Alt+F1 to F7.
- Need to hard reboot.

Scenario 2:
- Use the shutdown menu to choose "Sleep" option. This should suspend the system.
- Same as Scenario 1
- Need to hard reboot.

Scenario 3
- Comment out the quirk in xorg.conf. Above 2 scenarios had this option turned "on".
- service gdm restart
# from ... https://wiki.ubuntu.com/X/Quirks#Force%20Pipe%20A%20Quirk
#Option "ForceEnablePipeA" "true"
- Close laptop lid. Laptop is set to suspend in powermanager settings.
- Powerstate LED starts blinking indicating a successful suspend
- Open the lid
- LEDs start getting into action indicating waking up of laptop
- But, no display - blank screen. system frozen, no response to any keys. Ctrl+Alt+F1-F7
- Need to hard reboot.

Scenario 4
- Comment out the quirk in xorg.conf. Above 2 scenarios had this option turned "on".
- service gdm restart
# from ... https://wiki.ubuntu.com/X/Quirks#Force%20Pipe%20A%20Quirk
#Option "ForceEnablePipeA" "true"
- Use the shutdown menu to choose "Sleep" option. This should suspend the system.
- LEDS indicate the suspend is successful. Screen blanks out
- Wait for about 30 seconds.
- Press Power on button
- System is back to normal state.

Only Scenario 4 is successful. Rest of the scenarios are not successful.

$ uname -a
Linux x7073046wu-lin 2.6.32-15-generic #22-Ubuntu SMP Tue Mar 2 02:24:17 UTC 2010 i686 GNU/Linux

$ dpkg -l |grep power
rc devicekit-power 014-3 abstraction for power management
ii gnome-power-manager 2.29.91-0ubuntu5 power management tool for the GNOME desktop
ii libdevkit-power-gobject1 1:0.9.1-1 abstraction for power management - shared li
ii libgnomecanvas2-0 2.26.0-1 A powerful object-oriented display - runtime
ii libgnomecanvas2-common 2.26.0-1 A powerful object-oriented display - common
ii libimlib2 1.4.2-5 powerful image loading and rendering library
ii libupower-glib1 0.9.1-1 ...

Read more...

Revision history for this message
Akshay Guleria (axayg) wrote :

Even for Scenario#4, I am finding that it sometimes does NOT work. That is, I manually suspend the machine using menu or Fn+F3 switch combination, it does NOT suspend properly. The LED does not blink, screen does not blank out, network etc. gets disconnected. And on pressing the power key, the system does NOT wake up from sleep. Its in frozen - just like Scenario#1 to 3.

Bryce Harrington (bryce)
description: updated
Revision history for this message
Chris Halse Rogers (raof) wrote :

It's quite possible that in scenarios 1 & 3 you're running into a manifestation of bug #535640. There is also a new 2.6.32-17 kernel in Lucid that will soon become the default, and that has some drm fixes.

It seems like, apart from the lid-close problem, disabling the ForcePipeA quirk makes things significantly better at least!

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.