resuming suspend leads to screen corruption

Bug #77736 reported by Martijn Faassen
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I have a Dell Inspiron 8600. The video hardware is reported to be ATI Technologies Inc Radeon R250 Lf [FireGL 9000] (rev 01); this is some kind of ATI Mobility Radeon. I'm running the plain 'ati' drivers that ship with Ubuntu, *not* the fglrx drivers.

Suspend appears to work fine (and it did work with this machine in the past, early on with Dapper and before), but resuming does not lead to the desktop.
Instead, the screen shows an effect that almost looks like a screensaver (but de-installing screensavers doesn't help, and it's not a screensaver I recognize anyway):

The screen start black but then slowly bleeds white from the edges of the screen, until the whole screen is more or less white (there is a bit of a greyscale pattern). There are also a number of colored vertical lines. The bleeding effect looks very screensaver like, though the vertical lines don't. After a while the screen is entirely white and the effect restarts.

The screen stays in this mode no matter what I do. There does seem to be some response to keyboard input: ctrl-alt-delete triggers a reboot after a while. ctrl-alt-backspace appears to have no effect, though.

I first encountered this problem midway during Dapper. It must've been introduced by an upgrade as early on in Dapper and before Suspend did work. Initially I thought this was my own fault - I installed the fglrx drivers, de-installed them again, and the suspend started flaking out about the same time. I started realizing something deeper was wrong than a hanging screensaver when de-installing all screensavers in the system failed to make the problem go away.

Nothing I tried seemed to make this problem go away, and recently I decided to do a clean reinstall of the OS with Edgy. No fglrx drivers have touched this installation. Exact same problem.

I fiddled some with the settings in /etc/default/acpi-support but this had no effect at all.

Tags: edgy-close
Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for your bug report. Could you please add the full output of 'lspci -vv' and 'lspci -vvn' to your bug report as an attachment? Thanks in advance.

Revision history for this message
Martijn Faassen (faassen) wrote : Re: [Bug 77736] Re: resuming suspend leads to screen corruption
Download full text (15.7 KiB)

The information is attached.

00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03)
 Subsystem: Dell Unknown device 016a
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
 Latency: 0
 Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
 Capabilities: <access denied>

00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03) (prog-if 00 [Normal decode])
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 32
 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
 I/O behind bridge: 0000c000-0000cfff
 Memory behind bridge: fc000000-fdffffff
 Prefetchable memory behind bridge: e8000000-efffffff
 Secondary status: 66MHz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
 BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-

00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) (prog-if 00 [UHCI])
 Subsystem: Dell Unknown device 016a
 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: 0
 Interrupt: pin A routed to IRQ 11
 Region 4: I/O ports at bf80 [size=32]

00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) (prog-if 00 [UHCI])
 Subsystem: Dell Unknown device 016a
 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: 0
 Interrupt: pin B routed to IRQ 11
 Region 4: I/O ports at bf40 [size=32]

00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) (prog-if 00 [UHCI])
 Subsystem: Dell Unknown device 016a
 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: 0
 Interrupt: pin C routed to IRQ 11
 Region 4: I/O ports at bf20 [size=32]

00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01) (prog-if 20 [EHCI])
 Subsystem: Dell Unknown device 016a
 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: 0
 Interrupt: pin D routed to IRQ 11
 Region 0: Memory at f4fffc00 (32-bit, non-prefetchable) [size=1K]
 Capabilities: <access denied>

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81) (prog-if 00 [Normal decode])
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSE...

Revision history for this message
Brian Murray (brian-murray) wrote :

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Changed in linux-source-2.6.17:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Changed in linux-source-2.6.17:
status: Confirmed → Invalid
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
offby1 (offby1) wrote :

Thanks, Sergio (I'd forgotten about this bug). Hardy works great!

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Ok, set it fixed.
Thanks.

Changed in linux:
status: Incomplete → Fix Released
Revision history for this message
Martijn Faassen (faassen) wrote :

Unfortunately in my case my video card broke last year in that laptop,
so I'm unable to test. Thanks for the attention anyhow!

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

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

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.