[Hewlett-Packard Pavilion dv4000 (EC315UA#ABA)] suspend/resume failure

[Rolando Garza]

1)
Description: Ubuntu karmic (development branch)
Release: 9.10
2)
linux:
  Installed: (none)
  Candidate: 2.6.31.11.22
  Version table:
     2.6.31.11.22 0
        500 http://archive.ubuntu.com karmic/main Packages
3)
I did expect to receive a warning or something, since I suspended instead of hibernating.
4)
I got a warning about a severe Kernel bug; the warning was unsettling.

I suspended instead of hibernating, unplugged and later plugged it in again... I don't know if I should report this bug, since my laptop's battery is defective.

But, since I don't know what is the expected result of running out of power during suspend is... I opted to proceed and report this bug.

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: rolandog 1518 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with AD1981B at irq 17'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 34
   Simple ctrls : 23
Date: Tue Oct 6 11:25:05 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=54c3abe3-a313-4b06-bc3e-1a5247555428
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 002 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 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 005 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: Hewlett-Packard Pavilion dv4000 (EC315UA#ABA)
Package: linux-image-2.6.31-11-generic 2.6.31-11.38
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=3fb5d21d-d8e9-4a16-a277-849730f81c76 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-11-generic N/A
 linux-firmware 1.20
RfKill:

SourcePackage: linux
Tags: resume suspend
Title: [Hewlett-Packard Pavilion dv4000 (EC315UA#ABA)] suspend/resume failure
Uname: Linux 2.6.31-11-generic i686
UserGroups:

WpaSupplicantLog:

dmi.bios.date: 06/02/2005
dmi.bios.vendor: Phoenix
dmi.bios.version: F.13
dmi.board.name: 09BC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 35.2D
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnPhoenix:bvrF.13:bd06/02/2005:svnHewlett-Packard:pnPaviliondv4000(EC315UA#ABA):pvr:rvnHewlett-Packard:rn09BC:rvr35.2D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: Pavilion dv4000 (EC315UA#ABA)
dmi.sys.vendor: Hewlett-Packard

[^_Pepe_^ (jose-angel-fernandez-freire)]

Hi all,

Please, can you tell us whether this is still an issue for you? If not, please, consider update this bug as 'Fix Released', else, can you please, fill a little form, with questions contained in this wiki? https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume

It will definitely help developers to find the fix or help you to detect that you don't really have real bug. Please, pay special attention to the "Encrypted Home-Swap" issue and the flashing caps-lock.

Information below, will also help you

https://wiki.ubuntu.com/UnderstandingSuspend

I'd also encourage you to try this tests https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting to gather more information to developers

Thank you in advance.

[Jeremy Foshee (jeremyfoshee)]

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.]