Suspend fails on Dell Latitude X1 after dist-upgrade to Feisty

Bug #107447 reported by Stein Magnus Jodal
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: linux-source-2.6.20

After dist-upgrade from Edgy to Feisty yesterday suspend no longer works on my Dell Latitude X1. When suspending the monitor, network and disk are turned off as normally, but the power LED, disk LED and wlan/bluetooth LED is still on and the machine still produces heat. Normally only the power LED is pulsating when suspend works properly. To awaken the computer again the power must be cycled. No combination of closing and opening the lid, de-/increasing display brightness or pressing the power button awakens the machine.

To reproduce:
1. Boot with Feisty's kernel (2.6.20-15.27)
2. Press suspend button on keyboard (Fn+Esc) or System->Quit->Suspend.

From /var/log/messages between power button push and hard reboot:
Apr 18 11:43:41 myh gnome-power-manager: (jodal) Suspending computer because the suspend button has been pressed
Apr 18 11:43:42 myh kernel: [69498.708000] ADDRCONF(NETDEV_UP): eth1: link is not ready
Apr 18 11:43:42 myh kernel: [69498.816000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 18 11:43:44 myh kernel: [69500.856000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 18 11:43:46 myh ifplugd.agent[22543]: Stopping ifplugd for eth0
Apr 18 11:43:46 myh kernel: [69502.340000] ACPI: PCI interrupt for device 0000:01:00.0 disabled
Apr 18 11:43:46 myh ifplugd.agent[22591]: Stopping ifplugd for eth1
Apr 18 11:43:47 myh kernel: [69502.956000] ACPI: PCI interrupt for device 0000:02:03.0 disabled

Output from 'lspci -vvvn' will be attached to the report.

Revision history for this message
Stein Magnus Jodal (jodal) wrote :
Revision history for this message
Stein Magnus Jodal (jodal) wrote :
Revision history for this message
exactt (giesbert) wrote :

I added your bug here: https://wiki.ubuntu.com/LaptopTestingTeam/DellLatitudeX1

Sorry I can't help you myself!

Revision history for this message
Andreas Schildbach (schildbach) wrote :

If you are talking about Suspend-to-RAM, this is strange because on my Dell X1 it worked with Feisty Beta. I'll see as soon as I upgrade tomorrow.

Revision history for this message
Stein Magnus Jodal (jodal) wrote :

When booting with the Edgy kernel (2.6.17.1-10.37) again, suspend works. dmesg from that boot attached, as requested by tfheen.

Revision history for this message
Stein Magnus Jodal (jodal) wrote :

Make that 2.6.17.1-11.37, not 10.37.

Revision history for this message
Stein Magnus Jodal (jodal) wrote :

Also attaches /var/log/messages from Feisty running Edgy kernel, which shows that 'Freezing cpus ...' is the next step in the suspend process when it works, as compared to the pasted log in the initial bug report.

Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-kernel-acpi
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Stein Magnus Jodal (jodal) wrote :

This bug is not fixed by 2.6.20-16.28.

Revision history for this message
Andreas Schildbach (schildbach) wrote :

On my X1, it works with feisty final. Though 50% of resumes, I get a popup message saying "suspend failed" (or sth similar). The system is usable nevertheless.

Revision history for this message
Stein Magnus Jodal (jodal) wrote :

After dist-upgrade to Gutsy today, with 2.6.22-6.13 kernel, suspend now works again.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

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!

Revision history for this message
Andreas Schildbach (schildbach) wrote :

Looks like the bug can be closed now.

Revision history for this message
Andreas Moog (ampelbein) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in linux:
status: Incomplete → Fix Released
Curtis Hovey (sinzui)
Changed in linux-source-2.6.20 (Ubuntu):
assignee: Registry Administrators (registry) → nobody
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.