[Dell Computer Corporation Latitude D400] suspend/resume failure

[ThomasMartitz]

This kernel panic occured after resuming from suspend to RAM/standby. It took a few seconds actually after the system was back (I could move the mouse within that few seconds), but it then just crashed with blinking LEDs.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kugel 1565 F.... xfce4-mixer-plu
                      kugel 1571 F.... pulseaudio
                      kugel 1604 F.... xfce4-volumed
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with STAC9750,51 at irq 5'
   Mixer name : 'SigmaTel STAC9750,51'
   Components : 'AC97a:83847650'
   Controls : 38
   Simple ctrls : 24
CurrentDmesg:
 [ 37.200035] Clocksource tsc unstable (delta = -184674391 ns)
 [ 44.736245] eth0: no IPv6 routers present
 [ 88.653057] NET: Registered protocol family 24
Date: Sun Sep 27 15:49:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=e11f3fe4-8ff7-4887-97f0-4daaa951b159
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Computer Corporation Latitude D400
Package: linux-image-2.6.31-11-generic 2.6.31-11.36
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: root=UUID=71ee3417-f8bf-4e5e-bdd3-9c5fb98e6cb5 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
RelatedPackageVersions: linux-firmware 1.19
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: resume suspend
Title: [Dell Computer Corporation Latitude D400] suspend/resume failure
Uname: Linux 2.6.31-11-generic i686
UserGroups:

WpaSupplicantLog:

dmi.bios.date: 06/28/2005
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A08
dmi.board.name: 0G5842
dmi.board.vendor: Dell Computer Corporation
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComputerCorporation:bvrA08:bd06/28/2005:svnDellComputerCorporation:pnLatitudeD400:pvr:rvnDellComputerCorporation:rn0G5842:rvr:cvnDellComputerCorporation:ct8:cvr:
dmi.product.name: Latitude D400
dmi.sys.vendor: Dell Computer Corporation

[ThomasMartitz (thomas47-deactivatedaccount)]

I forgot to mention: I'm running karmic alpha 6 with latest updates, and xfce. Upgraded from an initial jaunty installation.

PS: 'ubuntu-bug -p linux' doesn't seem to work.
PS2: Can I only attach 1 file at a time?

[Tim Smith (auxiliary.chipmunk)]

i have installed Karmic Beta 9.1 daily release live DVD as of 03-10-09, this can be recreated on the Dell Latitude D400.

i will try to test on other dell laptops.

[Brian D (turbo)]

I have a Dell Latitude D400 as well.

Initial Linux installation was Linux Mint 7 (Gloria) (~ Ubuntu 9.04 / Jaunty). Suspend/ Resume worked flawlessly.

Upgraded to Linux Mint 8 (Helena) (~ Ubuntu 9.10 / Karmic).

Fn-Suspend no longer works, even after re-adding key sequence to enable it. Choosing Suspend from the menu (in Mint, it's Quit | Suspend, not sure in pure Ubuntu) works fine. If I allow the laptop to automatically go into suspend (first the screensaver kicks in, then the machine eventually suspends), it cannot be woken up. Power button, keystroke, mouse movement, etc do nothing -- screen is black. Only option is to hold the Power button until the machine shuts down.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.