Screen shows grey bars after resuming from suspend

Bug #568005 reported by databubble
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I have a Dell Latitude C400 laptop with Intel 82830M graphics hardware running Lucid 10.04 beta , kernel 2.6.32-21-generic.

The laptop suspends, and on occasion resumes fine. However, more often-than-not, on resume the display will turn on (an improvement over karmic) but will be corrupted. Normally this takes the form of 3 or 4 wide horizontal grey bars and a sort of bleeding of white to grey across the screen. Occasionally there is one or more wide vertical bars, looking a little like a grey-plaid pattern.

The laptop is fully responsive and working, and can be shut down or suspended again (note, once the display corruption happens, it never seems to work again until the system is rebooted.) I can switch between CTRL-ALT-F7 and CTRL-ALT-F1, but the only change in the display is that on the graphical display the screen starts white and begins to bleed to grey, while on the test screen starts grey and beings to bleed to black.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: I82801CAICH3 [Intel 82801CA-ICH3], device 0: Intel ICH [Intel 82801CA-ICH3]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: phil 1245 F.... knotify4
                      phil 1271 F.... kmix
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801CAICH3'/'Intel 82801CA-ICH3 with CS4205 at irq 7'
   Mixer name : 'Cirrus Logic CS4205 rev 3'
   Components : 'AC97a:4352595b'
   Controls : 42
   Simple ctrls : 27
Date: Wed Apr 21 13:37:20 2010
HibernationDevice: RESUME=UUID=e0c38232-53a2-4ca5-9a76-2f11824d4ec1
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Computer Corporation Latitude C400
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V 32-bit PC Card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=5ab83fd8-ac45-49fc-b541-6a05c9aabb98 ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 03/01/2004
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A12
dmi.board.name: Latitude C400
dmi.board.vendor: Dell Computer Corporation
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComputerCorporation:bvrA12:bd03/01/2004:svnDellComputerCorporation:pnLatitudeC400:pvr:rvnDellComputerCorporation:rnLatitudeC400:rvr:cvnDellComputerCorporation:ct8:cvr:
dmi.product.name: Latitude C400
dmi.sys.vendor: Dell Computer Corporation

Revision history for this message
databubble (phil-linttell) wrote :
Revision history for this message
databubble (phil-linttell) wrote :

I did some further testing of using pm_suspend from tty1. I noted that the same behaviour occurred... that is that on the first, or second attempt resuming worked... but then on subsequent attempts it did not work, with the whole display going white, and then bleeding to black.

Noting this, I then tried simply running the following, repeated:

# vbetool dpms off; sleep 10; vbetool dpms on

On the fourth iteration the screen went white and bled to black. Further iterations did not restore the screen.

The system was still responding fully.... I initiated a shutdown by pressing the power key.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi databubble,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kernel-suspend
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
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.