[Hewlett-Packard HP ProBook 4530s] suspend/resume failure

Bug #1219498 reported by Sander Jonkers
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

The usual crash after a fresh boot after the battery went empty.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-4-generic 3.11.0-4.9
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.12.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sander 1804 F.... pulseaudio
Date: Sat Aug 31 18:55:52 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=8347ea18-a02a-451a-a889-44f76dfe095b
InstallationDate: Installed on 2013-08-09 (22 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130809)
InterpreterPath: /usr/bin/python3.3
MachineType: Hewlett-Packard HP ProBook 4530s
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic root=UUID=4751d5cf-0d0a-4d15-aa76-3859947c3f7a ro persistent quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-4-generic N/A
 linux-backports-modules-3.11.0-4-generic N/A
 linux-firmware 1.113
SourcePackage: linux
Title: [Hewlett-Packard HP ProBook 4530s] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/12/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SRR Ver. F.40
dmi.board.name: 167C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 22.24
dmi.chassis.asset.tag: CNU1290ZYV
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.40:bd03/12/2013:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.24:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4530s
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Sander Jonkers (jonkers) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
penalvch (penalvch)
tags: added: bios-outdated-f.41 regression-potential
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Sander Jonkers (jonkers) wrote :

Thank you for your reply!

I did the BIOS upgrade. I'll force an empty battery occurence, and check what Ubuntu says upon boot afterwards.

sander@HPtje:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
68SRR Ver. F.41
05/22/2013
sander@HPtje:~$

penalvch (penalvch)
tags: added: latest-bios-f.41
removed: bios-outdated-f.41
Revision history for this message
Sander Jonkers (jonkers) wrote :

Update:

Still happens with that BIOS.

[Hewlett-Packard HP ProBook 4530s] suspend/resume failure

sander@HPtje:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
68SRR Ver. F.41
05/22/2013
sander@HPtje:~$

Revision history for this message
penalvch (penalvch) wrote :

Sander Jonkers, did this problem not occur in a release prior to Saucy?

Revision history for this message
Sander Jonkers (jonkers) wrote :

I'm not sure, but that could very well be.

Does that change the case?
Should I just click on "ignore"?

Revision history for this message
penalvch (penalvch) wrote :

Sander Jonkers, for regression testing purposes, could you please test for this in Precise via http://releases.ubuntu.com/precise/ ?

Revision history for this message
Sander Jonkers (jonkers) wrote :

OK: I just installed 12.04.3 (32-bit, not 64-bit, if that matters) on the same machine. Fully updated.

I'll force the empty-battery and see what happens afterwards.

sander@sander12043:~$ uname -a
Linux sander12043 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 15:31:16 UTC 2013 i686 i686 i386 GNU/Linux
sander@sander12043:~$

sander@sander12043:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
68SRR Ver. F.41
05/22/2013
sander@sander12043:~$

Revision history for this message
Sander Jonkers (jonkers) wrote :

An interesting result:

With 13.10, when I close the laptop lid and remove the power cable, after one night the battery will be empty and upon a fresh, powered boot I will get the crash reported here.
With 12.04.3, with the closed lid & removed power cable, after one night the laptop could just start up on it's own battery that was still 100% full. IMHO this is behaviour as expected

So: two problems (battery going empty and crash-report-after-boot), or one combined problem?

I will now force an empty battery on 12.04.3 by keeping the lid open while the laptop is unpowered

Revision history for this message
penalvch (penalvch) wrote :

Sander Jonkers, to clarify https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1219498/comments/10 , you want/are hibernating when you close the lid in Precise?

tags: added: needs-bisect regression-release
removed: regression-potential
Revision history for this message
Sander Jonkers (jonkers) wrote :

Results from 12.04.3:

I kept the lid open with no power cord inserted. So the battery went empty.
After putting in the power cord and powering up 12.04.3 ... NO crash report. So that's better than with 13.10 that always report a crash message.

"you want/are hibernating when you close the lid in Precise?" I don't dare to answer that question as I don't know the subtle differences between hibernate/sleep/S1/S2/S3/S4/S5/etc/etc. But 12.04.3 shows the behaviour I want: close lid -> laptops goes to sleep with very little power consumption, open lid within a few days -> laptop wakes up and starts where it left.

On 13.04 that does not work: opening the lid after a few hours results in an emptied battery, and then a crash report after restarting.

Both is on the same hardware, with everything on default. Both installs are fresh installs.

Changed in linux (Ubuntu):
importance: Undecided → Low
Revision history for this message
penalvch (penalvch) wrote :

Sander Jonkers, the next step is to bisect between Precise and Raring, in order to identify the offending regression commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

tags: added: raring
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.