[Dell Computer Corporation Latitude D600] suspend/resume failure

[Stuart Read]

Upon opening the lid of my laptop, the resume process hung at a black screen. I was forced to power-off the machine and when I turned it back on, Apport suggested I submit this report.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Computer Corporation Latitude D600
Package: linux-image-2.6.28-11-generic 2.6.28-11.41
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=d362de65-67b3-4298-aeba-d41d528734c3 ro splash quiet
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.41-generic
SourcePackage: linux
Tags: resume suspend
Title: [Dell Computer Corporation Latitude D600] suspend/resume failure
UserGroups:

[Andres Mujica (andres.mujica)]

Hi Stuart Read

 Thanks for your report, as you reported this bug a while ago we need your help with this tests, so we can work on this issue.

1. Can you confirm this issue exists with the most recent Karmic Koala 9.10 Alpha release? ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/

2. If the issue remains with Karmic, it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine it. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds

3. Finally, if you can take a look at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume and provide answers to the questions mentioned under the "Information Gathering" section that would be great.

Thank you so much, and sorry for the late reply.

[Stuart Read (sread)]

Hi Andres,
I have tested the latest alpha of Karmic, the problem does not appear to still exist (although it was intermittent to begin with). Also, suspend/resume is _much_ faster than in Jaunty!
-Stuart

[Jim Brumbaugh (bleumyst)]

Note: Same here, except I have a Dell Latitude X300. The processor was running full tilt when I took it out of it's case. Computer was quite hot!

This has happened twice, and to report this the laptop was sucessfully suspended once before I sent this report.

(This comment was originally in the text, I removed it and put it here..)

[Stuart Read (sread)]

Seems to me it's probably a different bug since my laptop is really
old. You should probably file a new one, this one is basically closed.
Good luck!
-Stuart

On Fri, Sep 11, 2009 at 6:41 PM, Jim Brumbaugh <email address hidden> wrote:
> Note:  Same here, except I have a Dell Latitude X300. The processor was
> running full tilt when I took it out of it's case. Computer was quite
> hot!
>
> This has happened twice, and to report this the laptop was sucessfully
> suspended once before I sent this report.
>
> (This comment was originally in the text, I removed it and put it
> here..)
>
> ** Description changed:
>
>  Upon opening the lid of my laptop, the resume process hung at a black
>  screen. I was forced to power-off the machine and when I turned it back
>  on, Apport suggested I submit this report.
> +
> + Note:  Same here, except I have a Dell Latitude X300. The processor was
> + running full tilt when I took it out of it's case. Computer was quite
> + hot!
>
>  ProblemType: KernelOops
>  Annotation: This occured during a previous suspend and prevented it from resuming properly.
>  Architecture: i386
>  DistroRelease: Ubuntu 9.04
>  ExecutablePath: /usr/share/apport/apportcheckresume
>  Failure: suspend/resume
>  InterpreterPath: /usr/bin/python2.6
>  Lsusb:
>   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>  MachineType: Dell Computer Corporation Latitude D600
>  Package: linux-image-2.6.28-11-generic 2.6.28-11.41
>  ProcAttrCurrent: unconfined
>  ProcCmdLine: root=UUID=d362de65-67b3-4298-aeba-d41d528734c3 ro splash quiet
>  ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
>  ProcEnviron: PATH=(custom, no user)
>  ProcVersionSignature: Ubuntu 2.6.28-11.41-generic
>  SourcePackage: linux
>  Tags: resume suspend
>  Title: [Dell Computer Corporation Latitude D600] suspend/resume failure
>  UserGroups:
>
> ** Description changed:
>
>  Upon opening the lid of my laptop, the resume process hung at a black
>  screen. I was forced to power-off the machine and when I turned it back
>  on, Apport suggested I submit this report.
> -
> - Note:  Same here, except I have a Dell Latitude X300. The processor was
> - running full tilt when I took it out of it's case. Computer was quite
> - hot!
>
>  ProblemType: KernelOops
>  Annotation: This occured during a previous suspend and prevented it from resuming properly.
>  Architecture: i386
>  DistroRelease: Ubuntu 9.04
>  ExecutablePath: /usr/share/apport/apportcheckresume
>  Failure: suspend/resume
>  InterpreterPath: /usr/bin/python2.6
>  Lsusb:
>   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>  MachineType: Dell Computer Corporation Latitude D600
>  Package: linux-image-2.6.28-11-generic 2.6.28-11.41
>  ProcAttrCurrent: unconfined
>  ProcCmdLine: root=UUID=d36...

[Stuart Read (sread)]

Apparently I spoke too soon: I'm still getting the resume failure with the latest updates of Karmic. I haven't had a chance to test the mainline kernel yet, but here is the answers to the Suspend/Resume questions listed above:

Did the machine break while going to sleep or waking up?
 - Machine sleeps perfectly. When waking up from sleep (by lifting the laptop lid) it resumes in the normal way except I am presented with a black (or blank, not sure) screen and an unresponsive system. Only hard-powering off works (ie re-sleeping, vterms, etc don't work)

Is it reproducible?
 - I'd say 1-2 out of every 10. Symptoms are identical each time.

Did it work before?
 - I think it's always been like this.

Do you end up with flashing caps-lock or similar?/
 - No, the machine looks just like it woke up correctly, except it's completely unresponsive.

Hopefully this helps. If I get a chance to try the mainline kernel I'll update the bug.
-Stuart

[NickA (sdnick484-gmail)]

I ran into this Suspend bug on a D600 with Karmic as well (2.6.31-14-generic #48 i686) and was able to identify the culprit as the yenta-socket module (for PCMCIA). I found the culprit by using the pm_trace as suggested at https://wiki.ubuntu.com/DebuggingKernelSuspend (the PCI address came up which I mapped with lspci -v). When I blacklisted yenta-socket, rsrc-nonstatic, and pcmcia-core, I rebooted the machine and suspend now works.

This is my brother's D600, and I will only have access to this machine for the next couple days before my brother heads back to CalTech, so if you need any more info, let me know asap (I normally run Gentoo on a Lenovo T400).

[Andreas Modinos (blueturtl)]

Bug still lurks in the latest Lucid Lynx (10.04) alpha (kernel 2.6.32-16-generic)

This is on a D600 with BIOS revision A14.

Blacklisting yenta or other pcmcia related modules did not fix it for me.

[Andreas Modinos (blueturtl)]

Ok, I updated the BIOS to the latest revision (A16): did not fix problem. I then installed and tested the mainline kernel (linux-image-2.6.32-02063209-generic). With the mainline kernel, suspending works (I tested twice).

Since apport is offline, I have attached my apport report file for further analysis.

[Jeremy Foshee (jeremyfoshee)]

Andreas,
     Thanks for your continued testing, and for following up on this bug. I will make the information you submitted available to the Kernel Engineer for review.

~JFo

[Kevin K (stafio)]

I have encountered the same issue on my dell laptop. Adding "nomodeset" to the end of the "linux /boot/vmlinuz-2.6.31-19-gener..." line in /boot/grub/grub.cfg. fixes the issue for me.

[Andreas Modinos (blueturtl)]

Kevin K, are you on a D600 or some other model notebook?

I tried adding nomodeset to the kernel boot parameters and now the system doesn't even go to sleep.

[Kevin K (stafio)]

Sorry, I was mistaken here. I have a D600 (Bios A16) and suspend/resume is working for me without nomodeset. Maybe I'm not remembering correctly, but I do believe it wasn't working at one point. Having said all of that, my machine still goes to sleep properly even with nomodeset added to the boot parameters.

Regarding the nomodeset: I was getting my model confused with a friends laptop, a D505. Suspend/resume was not working on that machine and adding nomodeset worked there.

[Andreas Modinos (blueturtl)]

Bug is still present on kernel 2.6.32-17-generic, Kevin K is on Karmic so I've marked this bug as regression-potential.

[Andreas Modinos (blueturtl)]

Still happening with kernel 2.6.32-18-generic

[Andreas Modinos (blueturtl)]

Still happening with kernel 2.6.32-19-generic

[Andreas Modinos (blueturtl)]

I've attempted to troubleshoot the issue by following the wiki at
https://wiki.ubuntu.com/DebuggingKernelSuspend

After following the steps there I got the following clues in my dmesg output:
[ 0.487733] PM: Resume from disk failed.
[ 0.487752] registered taskstats version 1
[ 0.488050] Magic number: 0:53:725
[ 0.488054] hash matches /build/buildd/linux-2.6.32/drivers/base/power/main.c:433
[ 0.488075] block loop5: hash matches
[ 0.488128] pci 0000:01:00.0: hash matches

lspci:
00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 02)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705M Gigabit Ethernet (rev 01)
02:01.0 CardBus bridge: O2 Micro, Inc. OZ711EC1 SmartCardBus Controller (rev 20)
02:01.1 CardBus bridge: O2 Micro, Inc. OZ711EC1 SmartCardBus Controller (rev 20)
02:03.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)

If I interpret the dmesg output correctly, the relevant offender is the video card:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 02)

I've tried blacklisting the radeon module but that appears impossible at the moment (it loads anyway).
I then added it to the suspend modules list it in /etc/pm/config.d/config but that didn't do anything.

[Andreas Modinos (blueturtl)]

Still happening with kernel 2.6.32-20-generic

[Kevin K (stafio)]

Still happening with kernel 2.6.32-21-generic

[P4man (duvel123)]

Same problem here. Worked fine on karmic, ever since Lucid alpha 2 (first Lucid I tried) resume has been broken on my D600. Goes to sleep fine, but gives a black screen and total freeze on resume.

FWIW, I just tried a beta from fedora 13 which comes with 2.6.33.1-24 kernel, and resume is also broken there as well.

[Timo Jyrinki (timo-jyrinki)]

I hope you don't mind, but I'll mark this as duplicate of bug #559163, another Dell D600 suspend/resume bug. I believe this bug _was_ fixed in Ubuntu 9.10 (or not just believe, it worked fine on my D600), but regressed again on 10.04 LTS. Since the bug is new (again) to 10.04 LTS, 559163 is better suited to handle it (and the number of it doesn't give an impression it's a bug that was never fixed).

Please add your "affects me" clicks on the top part of that page.