[Dell XPS m1530] Resume fails after hibernate/suspend

Bug #366264 reported by Robinson Tryon on 2009-04-24
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

I haven't been able to get hibernate/suspend working with 8.10 or 9.04 on this laptop.

Under 8.10:
When I try to hibernate the machine it appears to hibernate and power down. When I power-on the machine, the ubuntu splash screen appears and the progress bar moves (small bar moving back and forth inside the progress bar), but then it freezes after a few seconds. A few moments later the screen will go to black for half a second, then back to the frozen splash screen + progress bar.

After giving it some time, I have to restart the machine.

I've appended a chunk of my kernel log to the forum thread here:
http://ubuntuforums.org/showthread.php?t=1131224

Under 9.04:
Basically the same behavior.

I'm highly motivated to get this fixed, as this is my primary work laptop and not having hibernate/suspend working on it is a royal pain and tempts me to boot into WinXP instead of Ubuntu.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=/dev/mapper/vgBarley-swap
MachineType: Dell Inc. XPS M1530
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
ProcCmdLine: root=/dev/mapper/vgBarley-root ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: linux

Robinson Tryon (colonelqubit) wrote :
Robinson Tryon (colonelqubit) wrote :

Following the notes at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume, here's some more information:

=> Is it reproducible?
Yes -- I've tried to hibernate or suspend the machine several times, and it has never been able to resume.

=> Did it work before?
I've never gotten the machine to resume using Ubuntu 8.10 or 9.04.

The machine came with a Dell-specific version of Ubuntu installed, but I wiped it almost immediately and installed a dual-boot of WinXP and Ubuntu 8.10. I can suspend/resume correctly using WinXP.

=> Do you end up with flashing caps-lock or similar?

I do not believe so. I'll check.

jtholmes (jtholmes) on 2009-05-07
tags: added: hibernation
Robinson Tryon (colonelqubit) wrote :

https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume

=> Did the machine break while going to sleep or waking up?

The machine appears to power-off when I send it into hibernation, and only freezes when I try to power it back on. So I'd say that the machine is "breaking" when it's waking up.

Robinson Tryon (colonelqubit) wrote :

https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume

Per the instructions, I've done a test of suspending from text mode. Here's what I see during the suspend (see attached image), which here in my kernel log:

May 31 18:49:07 mash kernel: [ 65.651437] PM: Syncing filesystems ... done.
May 31 18:49:07 mash kernel: [ 65.662716] PM: Preparing system for mem sleep
May 31 18:49:07 mash kernel: [ 65.662719] Freezing user space processes ... (elapsed 0.00 seconds) done.
May 31 18:49:07 mash kernel: [ 65.663096] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
May 31 18:49:07 mash kernel: [ 65.663149] PM: Entering mem sleep
May 31 18:49:07 mash kernel: [ 65.702904] btusb_intr_complete: hci0 urb ffff88011dd443c0 failed to resubmit (1)
May 31 18:49:07 mash kernel: [ 65.703901] btusb_bulk_complete: hci0 urb ffff88011e8453c0 failed to resubmit (2)
May 31 18:49:07 mash kernel: [ 65.703974] btusb_bulk_complete: hci0 urb ffff88011dd44540 failed to resubmit (1)
May 31 18:49:07 mash kernel: [ 66.500055] Clocksource tsc unstable (delta = -493787176 ns)
May 31 18:49:07 mash kernel: [ 66.536263] sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 31 18:49:07 mash kernel: [ 66.536466] sd 0:0:0:0: [sda] Stopping disk
May 31 18:49:07 mash kernel: [ 66.864132] ricoh-mmc: Suspending.
May 31 18:49:07 mash kernel: [ 66.864142] ricoh-mmc: Controller is now re-enabled.
May 31 18:49:07 mash kernel: [ 66.865206] sdhci-pci 0000:03:09.1: PCI INT B disabled
May 31 18:49:07 mash kernel: [ 66.980314] ata5: port disabled. ignoring.
May 31 18:49:07 mash kernel: [ 66.980374] ata_piix 0000:00:1f.1: PCI INT A disabled
May 31 18:49:07 mash kernel: [ 66.980510] ehci_hcd 0000:00:1d.7: PCI INT A disabled
May 31 18:49:07 mash kernel: [ 66.996274] uhci_hcd 0000:00:1d.2: PCI INT C disabled
May 31 18:49:07 mash kernel: [ 66.996318] uhci_hcd 0000:00:1d.1: PCI INT B disabled
May 31 18:49:07 mash kernel: [ 66.996367] uhci_hcd 0000:00:1d.0: PCI INT A disabled
May 31 18:49:07 mash kernel: [ 67.028255] HDA Intel 0000:00:1b.0: PCI INT A disabled
May 31 18:49:07 mash kernel: [ 67.044318] ehci_hcd 0000:00:1a.7: PCI INT C disabled
May 31 18:49:07 mash kernel: [ 67.060278] uhci_hcd 0000:00:1a.1: PCI INT B disabled
May 31 18:49:07 mash kernel: [ 67.060321] uhci_hcd 0000:00:1a.0: PCI INT A disabled
May 31 18:49:07 mash kernel: [ 67.060410] PM: suspend devices took 1.400 seconds

Robinson Tryon (colonelqubit) wrote :

After talking with johanbr on #ubuntu-kernel, here's a much larger piece of the log showing going into suspend and failing to resume.

Robinson Tryon (colonelqubit) wrote :

I just did some testing with hibernation and finally got something to resume!

Unfortunately, the method is:
- Boot Ubuntu with quiet/splash off and no_console_suspend on
- Go immediately to Virtual Terminal 1
- 'sudo pm-hibernate'

(The computer hibernates)

- Start up the machine
- (Again) Boot Ubuntu with quiet/splash off and no_console_suspend on

I was dropped right back where I started on Virtual Terminal 1, with the preceding lines showing in the terminal, etc. Although this method of hibernation worked, when I tried to go to Virtual Terminal 7 (which is running X), the system froze up.

These three lines appeared when I was entering hibernation. They're the same as what I saw when entering suspend:

Jun 1 13:20:16 mash kernel: [ 108.090910] btusb_intr_complete: hci0 urb ffff880117ce4f00 failed to resubmit (1)
Jun 1 13:20:16 mash kernel: [ 108.091898] btusb_bulk_complete: hci0 urb ffff880117ce4d80 failed to resubmit (2)
Jun 1 13:20:16 mash kernel: [ 108.091971] btusb_bulk_complete: hci0 urb ffff880117ce4e40 failed to resubmit (1)

I've attached the appropriate chunk of kern.log, annotated with what happened and when.

Robinson Tryon (colonelqubit) wrote :

This forum thread looks interesting: http://ubuntuforums.org/showthread.php?t=959712

"Lenovo T400 Suspend / Hibernate / Resume Problems

...Sometimes, it flashes some text on the screen really quickly...like this:

btusb_intr_complete failed to resubmit
btusb_send_frame submission failed

UPDATE: If I suspend or hibernate after I've dropped down to a console, then resume works fine. So it looks like it's a GNOME / X / Intel driver problem."

I'm thinking that there's a correlation between these "btusb" errors and hibernation failing in relation to X.

Robinson Tryon (colonelqubit) wrote :

Interesting: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/292515

"x86 ACPI: Fix breakage of resume on 64-bit UP systems with SMP kernel"

Of course, I'm running a dual-core processor here so it's not a "UP" (Uniprocessor) system.

Robinson Tryon (colonelqubit) wrote :

I've already linked the other way, but as I don't see a "Links to here" tool in Launchpad, I'll make the second link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/361852

That bug is "[Jaunty] Resume from hibernate doesn't work on a Dell XPS M1330," and has some similar-looking errors: "[111.386123] btusb_intr_complete: hci0 urb f5ec5900 failed to resubmit (1)"

dunxd (d-drury) wrote :

On my EEE PC 1000 running Jaunty Netbook Remix, I see something similar. On hibernating I see the "btusb_bulk_complete failed to resubmit" messages and then nothing appears to happen. But eventually the machine goes off. When I power it back on, it goes to the Waking up screen, takes a long time, but then works fine.

On Suspend it appears to work fine, then I briefly see the "btusb_bulk_complete failed to resubmit" lines before the system is restored.

It is currently faster to shut down and reboot than to return from hibernation.

Jeremy Foshee (jeremyfoshee) wrote :

Hi qubit,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 366264

Also, if you could 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: kernel-hibernate
tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete

Ubuntu 9.10 Have exactly the same situation (word by word) as dunxd on my Laptop Samsung Q310. I can't try “the latest development release of Ubuntu” or “the latest upstream kernel”, as it is my working laptop and I need my system to by stable. Though I'm getting weekly updates from default repos. Hope greatly that this problem will be solved in Lucid.

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  Edit
Everyone can see this information.

Other bug subscribers