[Hewlett-Packard Pavilion ze5300 (DC964A)] suspend/resume failure

Bug #351558 reported by Joel Shprentz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Colin Ian King

Bug Description

Laptop took 10 seconds to shutdown. It stayed in low power state for 10 more seconds. Then fan came on, but the screen remained blank and there was no disk activity.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
CurrentDmesg: [ 49.648040] eth1: no IPv6 routers present
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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 046d:c510 Logitech, Inc. Cordless Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard Pavilion ze5300 (DC964A)
Package: linux-image-2.6.28-11-generic 2.6.28-11.38
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=99dfa558-a6e1-4a6a-8bed-dd0863f9303a ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
SourcePackage: linux
Tags: resume suspend
Title: [Hewlett-Packard Pavilion ze5300 (DC964A)] suspend/resume failure
UserGroups:

Revision history for this message
Joel Shprentz (jshprentz) wrote :
Revision history for this message
banyanleaf (ximhot) wrote :

The problem didn't happen with Ubuntu 8.10. I found out that there is a BIOS upgrade from HP that is supposed to be able to improve the advanced power management. I remember that under Windows XP, ze5300 had problem returning from hibernation, too.

But the BIOS flash doesn't work under Wine. I have no Windows on my computer now to give that BIOS flash a try. Maybe someone can give it a shot?

Revision history for this message
Colin Ian King (colin-king) wrote :

@banyanleaf:

Looks like a faulty driver is breaking the resume. Please can you follow through the debugging steps as described in: https://wiki.ubuntu.com/DebuggingKernelSuspend

Please attach the dmesg output once you have rebooted the machine so that I can check to see which driver is causing the problem. Thanks!

Changed in linux (Ubuntu):
status: New → Incomplete
assignee: nobody → Colin King (colin-king)
importance: Undecided → Medium
Revision history for this message
Colin Ian King (colin-king) wrote :

This bug report was marked as Incomplete a while ago and has not had any feedback to provide the requested information. As a result this bug is being closed. Please reopen if this is still an issue in the latest Karmic 9.10 Alpha release http://cdimage.ubuntu.com/releases/karmic/ . 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.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
Revision history for this message
treehouseman (106-5theend) wrote :

I have a ze5300 running ubuntu 9,10 and i have the same problem

Changed in linux (Ubuntu):
status: Won't Fix → New
Revision history for this message
John Ke (johnjka) wrote :

I changed the power management setting so that PC never goes into standby. Old equipment can be difficult and sometimes requires inelegant solutions to address an issue.

Revision history for this message
Colin Ian King (colin-king) wrote :

Can somebody with this hardware follow through the debugging steps as described in: https://wiki.ubuntu.com/DebuggingKernelSuspend

Please attach the dmesg output once you have rebooted the machine so that I can check to see which driver is causing the problem. Thanks!

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
treehouseman (106-5theend) wrote :
Download full text (55.5 KiB)

here is my dmesg.txt

[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.31-14-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 (Ubuntu 2.6.31-14.48-generic)
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] NSC Geode by NSC
[ 0.000000] Cyrix CyrixInstead
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Transmeta GenuineTMx86
[ 0.000000] Transmeta TransmetaCPU
[ 0.000000] UMC UMC UMC UMC
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000d8000 - 00000000000e0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000002bf70000 (usable)
[ 0.000000] BIOS-e820: 000000002bf70000 - 000000002bf7c000 (ACPI data)
[ 0.000000] BIOS-e820: 000000002bf7c000 - 000000002bf80000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000002bf80000 - 000000002c000000 (reserved)
[ 0.000000] BIOS-e820: 000000003bf80000 - 000000003c000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
[ 0.000000] DMI 2.3 present.
[ 0.000000] Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] last_pfn = 0x2bf70 max_arch_pfn = 0x100000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-CFFFF write-protect
[ 0.000000] D0000-DBFFF uncachable
[ 0.000000] DC000-DFFFF write-back
[ 0.000000] E0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask FE0000000 write-back
[ 0.000000] 1 base 020000000 mask FF8000000 write-back
[ 0.000000] 2 base 028000000 mask FFC000000 write-back
[ 0.000000] 3 base 02BF80000 mask FFFF80000 uncachable
[ 0.000000] 4 base 03BF80000 mask FFFF80000 uncachable
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] Scanning 0 areas for low memory corruption
[ 0.000000] modified physical RAM map:
[ 0.000000] modified: 0000000000000000 - 0000000000010000 (reserved)
[ 0.000000] modified: 0000000000010000 - 000000000009f800 (usable)
[ 0.000000] modified: 000000000009f800 - 00000000000a0000 (reserved)
[ 0.000000] modified: 00000000000d8000 - 00000000000e0000 (reserved)
[ 0.000000] modified: 00000000000e4000 - 0000000000100000 (reserved)
[ 0.000000] modified: 0000000000100000 - 000000002bf70000 (usable)
[ 0.000000] modified: 000000002bf70000 - 000000002bf7c000 (ACPI data)
[ 0.000000] modified: 000000002bf7c000 - 000000002bf80000 (ACPI N...

Revision history for this message
treehouseman (106-5theend) wrote :

took me some looking but i finally found the text file i extracted here it is if you find it easier to use

Revision history for this message
Colin Ian King (colin-king) wrote :

Thanks treehouseman.

The debugging reported back the following magic number:

  Magic number: 1:134:157
[ 0.917340] bdi 1:9: hash matches

..which indicates the error is in bdi, but I'm finding that hard to believe. The debug magic is derived from the real time clock (RTC), I suspect the hash from the RTC maybe giving a false hit. Do you mind repeating the debugging step again and make sure the time between the resume hang and the reboot is kept to below a 60 seconds or so? Thanks!

Changed in linux (Ubuntu):
status: Incomplete → In Progress
status: In Progress → Won't Fix
status: Won't Fix → Incomplete
Revision history for this message
treehouseman (106-5theend) wrote :

well i did it again and it has a different hash match this time

Revision history for this message
Colin Ian King (colin-king) wrote :

[ 0.907489] PM: Resume from disk failed.
[ 0.907512] registered taskstats version 1
[ 0.907747] Magic number: 1:645:144
[ 0.907825] block ram9: hash matches

From what I can see, we are not getting any useful/stable debug information back from the RTC debug mechanism. At this point it's hard to tell which part of the kernel resume the failure is occurring in.

Revision history for this message
treehouseman (106-5theend) wrote :

maybe we should look for a different error in another driver causing it because one thing i found odd about this computer is that the video ram is part of the physical ram instead of a memory chip on the video card its self i think it might not recognize the difference in the ammount of usuable ram and or that the video ram is part of the physical ram

Revision history for this message
Colin Ian King (colin-king) wrote :

@treehousman,

I think the next step to do is to see if the bug has gone with the current upstream kernels. Perhaps you could select the latest kernel from the upstream kernel daily build http://kernel.ubuntu.com/~kernel-ppa/mainline/daily and see if this fixes the suspend/resume issue. If it does, we can work from there to see if a fix can be back-ported.

Colin

Changed in linux (Ubuntu):
status: Incomplete → In Progress
status: In Progress → Incomplete
Revision history for this message
banyanleaf (ximhot) wrote : Re: [Bug 351558] Re: [Hewlett-Packard Pavilion ze5300 (DC964A)] suspend/resume failure

Upgraded to 9.10 Karmic and the bug is gone. Thanks!

On Mon, Feb 15, 2010 at 12:00 PM, Colin King <email address hidden> wrote:

> @treehousman,
>
> I think the next step to do is to see if the bug has gone with the
> current upstream kernels. Perhaps you could select the latest kernel
> from the upstream kernel daily build http://kernel.ubuntu.com/~kernel-
> ppa/mainline/daily<http://kernel.ubuntu.com/%7Ekernel-%0Appa/mainline/daily>and see if this fixes the suspend/resume issue. If it
> does, we can work from there to see if a fix can be back-ported.
>
> Colin
>
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => In Progress
>
> ** Changed in: linux (Ubuntu)
> Status: In Progress => Incomplete
>
> --
> [Hewlett-Packard Pavilion ze5300 (DC964A)] suspend/resume failure
> https://bugs.launchpad.net/bugs/351558
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Incomplete
>
> Bug description:
> Laptop took 10 seconds to shutdown. It stayed in low power state for 10
> more seconds. Then fan came on, but the screen remained blank and there was
> no disk activity.
>
> ProblemType: KernelOops
> Annotation: This occured during a previous suspend and prevented it from
> resuming properly.
> Architecture: i386
> CurrentDmesg: [ 49.648040] eth1: no IPv6 routers present
> 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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 002: ID 046d:c510 Logitech, Inc. Cordless Mouse
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> MachineType: Hewlett-Packard Pavilion ze5300 (DC964A)
> Package: linux-image-2.6.28-11-generic 2.6.28-11.38
> ProcAttrCurrent: unconfined
> ProcCmdLine: root=UUID=99dfa558-a6e1-4a6a-8bed-dd0863f9303a ro quiet splash
> ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
> ProcEnviron: PATH=(custom, no user)
> ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
> SourcePackage: linux
> Tags: resume suspend
> Title: [Hewlett-Packard Pavilion ze5300 (DC964A)] suspend/resume failure
> UserGroups:
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/351558/+subscribe
>

--
Close Windows, and you see a whole new world.

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