Ubuntu
acpi package

Unable to resume from suspend, Natty narwhal

Asked by Phil Evans

I have a Dell l501x laptop (Studio XPS15). Since upgrading to Natty Narwhal (Kubuntu flavour, 11.04, 64 bit), I can no longer resume after suspending to RAM. When I try to resume, the laptop appears to wake -- the power light illuminates and the screen comes on, showing my KDE desktop, but everything is locked up; the only thing that works is to hold the power button down until the computer powers off. So far as I can see, nothing appears in the syslog during this failed resume. Note that, on Maverick Meerkat (10.10) suspend/resume worked perfectly, and all services (even wireless network!) came back up flawlessly.

Any help would be very gratefully received.

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu acpi Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Phil Evans (pae9) said : 		#1

In case it helps, I've just done another suspend/resume fail and here's the syslog from around the time:

May 12 13:17:10 kestrel kernel: [22348.723447] dell-wmi: Unknown key e026 pressed
May 12 13:17:10 kestrel kernel: [22348.738447] dell-wmi: Unknown key e025 pressed

+++++ I SELECTED "SUSPEND TO RAM" NOW +++++

May 12 13:23:23 kestrel NetworkManager[931]: <info> sleep requested (sleeping: no enabled: yes)
May 12 13:23:23 kestrel NetworkManager[931]: <info> sleeping or disabling...
May 12 13:23:23 kestrel NetworkManager[931]: <info> (wlan1): now unmanaged
May 12 13:23:23 kestrel NetworkManager[931]: <info> (wlan1): device state change: 8 -> 1 (reason 37)
May 12 13:23:23 kestrel NetworkManager[931]: <info> (wlan1): deactivating device (reason: 37).
May 12 13:23:23 kestrel NetworkManager[931]: <info> (wlan1): canceled DHCP transaction, DHCP client pid 6322
May 12 13:23:23 kestrel kernel: [22721.805181] wlan1: deauthenticating from 00:18:39:8c:9c:a8 by local choice (reason=3)
May 12 13:23:24 kestrel kernel: [22722.022631] cfg80211: All devices are disconnected, going to restore regulatory settings
May 12 13:23:24 kestrel kernel: [22722.022639] cfg80211: Restoring regulatory settings
May 12 13:23:24 kestrel kernel: [22722.022647] cfg80211: Calling CRDA to update world regulatory domain
May 12 13:23:24 kestrel kernel: [22722.028809] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
May 12 13:23:24 kestrel kernel: [22722.028818] cfg80211: World regulatory domain updated:
May 12 13:23:24 kestrel kernel: [22722.028820] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
May 12 13:23:24 kestrel kernel: [22722.028825] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 12 13:23:24 kestrel kernel: [22722.028830] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
May 12 13:23:24 kestrel kernel: [22722.028834] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
May 12 13:23:24 kestrel kernel: [22722.028837] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 12 13:23:24 kestrel kernel: [22722.028841] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 12 13:23:24 kestrel wpa_supplicant[977]: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
May 12 13:23:24 kestrel avahi-daemon[859]: Withdrawing address record for 192.168.5.100 on wlan1.
May 12 13:23:24 kestrel avahi-daemon[859]: Leaving mDNS multicast group on interface wlan1.IPv4 with address 192.168.5.100.
May 12 13:23:24 kestrel avahi-daemon[859]: Interface wlan1.IPv4 no longer relevant for mDNS.
May 12 13:23:24 kestrel NetworkManager[931]: <info> (wlan1): cleaning up...
May 12 13:23:24 kestrel NetworkManager[931]: <info> (wlan1): taking down device.
May 12 13:23:24 kestrel avahi-daemon[859]: Interface wlan1.IPv6 no longer relevant for mDNS.
May 12 13:23:24 kestrel avahi-daemon[859]: Leaving mDNS multicast group on interface wlan1.IPv6 with address fe80::226:c7ff:feb6:ee2c.
May 12 13:23:24 kestrel avahi-daemon[859]: Withdrawing address record for fe80::226:c7ff:feb6:ee2c on wlan1.
May 12 13:23:24 kestrel NetworkManager[931]: <info> (eth1): now unmanaged
May 12 13:23:24 kestrel NetworkManager[931]: <info> (eth1): device state change: 2 -> 1 (reason 37)
May 12 13:23:24 kestrel NetworkManager[931]: <info> (eth1): cleaning up...
May 12 13:23:24 kestrel NetworkManager[931]: <info> (eth1): taking down device.
May 12 13:23:24 kestrel avahi-daemon[859]: Interface eth1.IPv6 no longer relevant for mDNS.
May 12 13:23:24 kestrel avahi-daemon[859]: Leaving mDNS multicast group on interface eth1.IPv6 with address fe80::f24d:a2ff:fe5a:c842.
May 12 13:23:24 kestrel avahi-daemon[859]: Withdrawing address record for fe80::f24d:a2ff:fe5a:c842 on eth1.
May 12 13:23:25 kestrel anacron[8017]: Anacron 2.3 started on 2011-05-12
May 12 13:23:25 kestrel anacron[8017]: Normal exit (0 jobs run)
May 12 13:23:26 kestrel kernel: [22723.836533] xhci_hcd 0000:05:00.0: remove, state 4
May 12 13:23:26 kestrel kernel: [22723.836548] usb usb3: USB disconnect, address 1
May 12 13:23:26 kestrel kernel: [22723.900401] xhci_hcd 0000:05:00.0: Host controller not halted, aborting reset.
May 12 13:23:26 kestrel kernel: [22723.900720] xhci_hcd 0000:05:00.0: USB bus 3 deregistered
May 12 13:23:26 kestrel kernel: [22723.901331] xhci_hcd 0000:05:00.0: PCI INT A disabled

++ THIS NEXT LOT SEEMS TO BE RELATED TO THE THING BEING POWERED BACK ON ++

May 12 13:24:45 kestrel kernel: imklog 4.6.4, log source = /proc/kmsg started.
May 12 13:24:45 kestrel rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="832" x-info="http://www.rsyslog.com"] (re)start
May 12 13:24:45 kestrel rsyslogd: rsyslogd's groupid changed to 103
May 12 13:24:45 kestrel rsyslogd: rsyslogd's userid changed to 101
May 12 13:24:45 kestrel rsyslogd-2039: Could no open output pipe '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]
May 12 13:24:45 kestrel kernel: [ 0.000000] Initializing cgroup subsys cpuset
May 12 13:24:45 kestrel kernel: [ 0.000000] Initializing cgroup subsys cpu
May 12 13:24:45 kestrel kernel: [ 0.000000] Linux version 2.6.38-9-generic (buildd@king) (gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4) ) #43+kamal~mjgbacklight4-Ubuntu SMP Fri Apr 29 04:33:59 UTC 2011 (Ubuntu 2.6.38-9.43+kamal~mjgbacklight4-generic 2.6.38.4)
May 12 13:24:45 kestrel kernel: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-2.6.38-9-generic root=UUID=617a431c-de25-452a-a79b-dee9b520bc0f ro quiet splash acpi_backlight=vendor dell_laptop.backlight=0 pciehp.pciehp_force=1 vt.handoff=7
May 12 13:24:45 kestrel kernel: [ 0.000000] BIOS-provided physical RAM map:
May 12 13:24:45 kestrel kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009c400 (usable)
May 12 13:24:45 kestrel kernel: [ 0.000000] BIOS-e820: 000000000009c400 - 00000000000a0000 (reserved)
<etc>

Revision history for this message
Launchpad Janitor (janitor) said : 		#2

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
Phil Evans (pae9) said : 		#3

I'm still having this problem, even though the bug has been marked "expired"!

Following the advice on https://wiki.ubuntu.com/DebuggingKernelSuspend I used the system RTC to gain some information. The relevant dmesg entries appear to be:

[ 1.549795] Magic number: 0:846:372
[ 1.549797] hash matches /build/buildd/linux-2.6.38/drivers/base/power/main.c:535
[ 1.549831] pci 0000:ff:00.0: hash matches
[ 1.549834] pci 0000:02:00.0: hash matches

Where lspci gives me:

ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 05)
and
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)

among other things. I am guessing this means the problem is in the control of the Intel graphics card? But I am not an expert (or anywhere near) in these matters. As I say, there were no problems in Ubuntu 10.10.....!

Revision history for this message
Eliah Kagan (degeneracypressure) said : 		#4

>> I'm still having this problem, even though the bug has been marked "expired"!

This is not a bug. This is a question (i.e., a request for support); it was automatically expired because nobody answered it (or requested more information from you) in two weeks. This, in turn, is probably because nobody (who has looked at it) knows the answer. In any case, your latest post just automatically reopened this question.

I recommend that you report a bug for this. First, read https://help.ubuntu.com/community/ReportingBugs carefully. Then search to see if the bug has already been reported. If not, file a report (you should use Apport to initiate this, because it automatically attaches valuable information). Make sure that you include all the information you've posted here in your bug report, since your bug report should be complete and self-contained--it should not be necessary for the Ubuntu developers to refer to this question in order to fully understand and appreciate your bug. After filing your bug report, you should link it and this question together using the "Link existing bug" link near the top of this question page.

Revision history for this message
Launchpad Janitor (janitor) said : 		#5

This question was expired because it remained in the 'Open' state without activity for the last 15 days.