Reproducible crash on second resume from hibernate

[dgatwood]

Binary package hint: linux-source-2.6.20

I'm seeing a reproducible crash the second time I resume from hiberation.

The first time it hibernates, the screen goes back to a text console, displays some stuff on the screen, and everything works correctly. On resume, the text console shows an Ubuntu boot screen. The progress bar is later partially obliterated by a thin horizontal white box that goes all the way across the screen, but everything else is okay. It appears to be functional, and I've used it for a significant period of time after the first wake with no obvious problems (other than some known issues with lirc and mythtv).

The second time it hibernates, the screen goes to what should be a text console, but instead, it's a black screen with bunch of scattered orange and green lines that are quickly replaced by orange boxes, often with what appear to be blinking, white underscore cursors at the top of the boxes. The severely corrupted console notwithstanding, it powers down successfully.

Upon resume, it never makes it. I see the Ubuntu text boot screen. The progress bar is quickly covered by a thinner-than-usual horizontal blue box with four false-color Ubuntu logos below it, evenly tiled across the screen. At this point, the machine hangs. It is responsive to pings and responds with a connection refused on unopen ports. Connections to open ports open, but do not send back any data. The UI never changes from a text console back to X11.

Hardware is a micro-ATX Pentium M/Intel 915GM box w/ integrated Intel video. In addition to the Intel chipset, it also has built-in FireWire (Agere Systems FW323) and Gig-E (Realtek RTL-8169), but otherwise is about as much a stock Intel board as you can get.

Apart from hibernation problems, it has been working flawlessly for months, so I'm pretty sure it doesn't have any hardware problems to speak of. Today was the first time I've tried hibernation. I was hoping to be able to hibernate my MythTV setup with the power button on the remote, but it looks like I'm going to have to do a full shutdown for now.

Will attach log files after I submit the bug.

[dgatwood (dgatwood)]

I'm not able to attach the other logs because your server's backend process is crashing. I'll try pasting. Apologies for the formatting problems this causes, but I did try to do what you asked... several times.

First, lspci -vvnn results, then a complete /var/log/messages for one cycle of boot, hibernate, resume, hibernate, resume (no log messages generated for this part), then the first couple of lines of the next boot.

00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 04)
 Subsystem: AOPEN Inc. Unknown device [a0a0:0589]
 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
 Capabilities: [e0] Vendor Specific Information

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) (prog-if 00 [VGA])
 Subsystem: AOPEN Inc. Unknown device [a0a0:0589]
 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
 Interrupt: pin A routed to IRQ 19
 Region 0: Memory at d0180000 (32-bit, non-prefetchable) [size=512K]
 Region 1: I/O ports at ea00 [size=8]
 Region 2: Memory at c0000000 (32-bit, prefetchable) [size=256M]
 Region 3: Memory at d0200000 (32-bit, non-prefetchable) [size=256K]
 Capabilities: [d0] Power Management version 2
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 04)
 Subsystem: AOPEN Inc. Unknown device [a0a0:0589]
 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 d0100000 (32-bit, non-prefetchable) [size=512K]
 Capabilities: [d0] Power Management version 2
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 04) (prog-if 00 [UHCI])
 Subsystem: AOPEN Inc. Unknown device [a0a0:0589]
 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 16
 Region 4: I/O ports at eb00 [size=32]

00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 04) (prog-if 00 [UHCI])
 Subsystem: AOPEN Inc. Unknown device [a0a0:0589]
 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...

[Ralph Janke (txwikinger)]

Thanks for reporting this issue.

Would it be possible to test this against the newest kernel for hardy and tell us if it still exists there?

Thanks.

[dgatwood (dgatwood)]

Hmm. Just got notification on this bug two months after the last comment.... *shrugs*

I'm assuming the kernel won't be in the Feisty apt repo, and I'm assuming you don't just build from a stock kernel.org tree or something, so where's the easiest place to grab an updated kernel binary package (or a source tarball would be okay, too)? I'll try to pull a new kernel and test it this weekend.

[Launchpad Janitor (janitor)]

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!

[Leann Ogasawara (leannogasawara)]

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 Ogasawara (leannogasawara)]

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".