KDE hangs on resume from RAM

0:00.0 Host bridge: Intel Corporation 82830 830 Chipset Host Bridge (rev 02)
 Subsystem: IBM ThinkPad A/T/X Series
 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 d0000000 (32-bit, prefetchable) [size=256M]
 Capabilities: [40] Vendor Specific Information
 Capabilities: [a0] AGP version 2.0
  Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
  Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>

00:01.0 PCI bridge: Intel Corporation 82830 830 Chipset AGP Bridge (rev 02) (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: 96
 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
 Memory behind bridge: c0100000-c01fffff
 Prefetchable memory behind bridge: e0000000-ebffffff
 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 82801CA/CAM USB (Hub #1) (rev 01) (prog-if 00 [UHCI])
 Subsystem: IBM ThinkPad A/T/X Series
 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 1800 [size=32]

00:1d.1 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #2) (rev 01) (prog-if 00 [UHCI])
 Subsystem: IBM ThinkPad A/T/X Series
 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 1820 [size=32]

00:1d.2 USB Controller: Intel Corporation 82801CA/CAM USB (Hub #3) (rev 01) (prog-if 00 [UHCI])
 Subsystem: IBM ThinkPad A/T/X Series
 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 1840 [size=32]

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 41) (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: 0
 Bus: primary=00, secondary=02, subordinate=08, sec-latency=64
 I/O behind bridge: 00002000-00006fff
 Memory behind bridge: c0200000-cfffffff
 Prefetchable memory behind bridge: f0000000-f7ffffff
 Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
 BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-

00:1f.0 ISA bridge: Intel Corporation 82...

Perhaps this bug should have been posted to the ACPI list.
Suspend/resume worked on kubuntu release 6.10
Upgraded from 6.10 to Feisty via kubuntu upgrade path

Upgrade to 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 GNU/Linux did not change behavior.
One point: after a Ctl-Alt-F1 and a log into root, do not have any network. However, if I do a ifdown on eth1 and then a ifup eth1 the network comes back. However, kde is still locked. The dmesg also shows
197.092000] ndiswrapper: changing interface name from 'wlan0' to 'eth1' which is does not do on a normal boot.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Leann,

Thank you very much for this response. However, since this bug was reported, I have upgraded all my systems to Ubuntu 8.04. The Thinkpad t23 that this was reported on now works with suspend/resume to memory. But, it just so happens that I have a Dell 8400 desktop system that I wish to use suspend/resume with and although it goes into suspend, resuming is problematic. Some times there is a blank screen and sometime only the sound is out. When I have time I have been researching the solution. If your recommendation might help the desktop system then I might try the kernel upgrade.

Thanks again,

Rob Peters

---------[ Received Mail Content ]----------

 Subject : [Bug 117264] Re: KDE hangs on resume from RAM

 Date : Fri, 29 Aug 2008 06:44:51 -0000

 From : Leann Ogasawara <email address hidden>

 To : <email address hidden>

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the

upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would

appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.

There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-

image-2.6.27-* package is currently available for you to install and

test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer

2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4.

Please watch http://www.ubuntu.com/testing for Alpha5 to be announced.

You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the

bug reported here or if the issue remains. More importantly, please

open a new bug report for each new bug/regression introduced by the

2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please

specifically note if the issue does or does not appear in the 2.6.26

kernel. Thanks again, we really appreicate your help and feedback.

** Tags added: cft-2.6.27

--

KDE hangs on resume from RAM

https://bugs.launchpad.net/bugs/117264

You received this bug notification because you are a direct subscriber

of the bug.

Hi Rob,

Thanks for the update. I'm going to mark this bug "Fix Released". If you could open a new bug report regarding the Dell 8400 Suspend/Resume issue that would be great. It's helpful to the development teams if bug reports target a specific issue against a specific set of hardware. You actually might want to test that system using a LiveCD for the upcoming Alpha5 release. That should be the easiest and quickest way to tell if the issue should be resolved. Note that you can test Suspen via a LiveCD, not Hibernate. Hope that helps. Thanks again.