[Hewlett-Packard 520-1138cb] suspend/resume failure [non-free: wl]

Bug #1201674 reported by Ken
30
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Low
Unassigned

Bug Description

suspend resume failure again

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.10.0-2-generic 3.10.0-2.11
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelModules: wl
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kenn 1675 F.... pulseaudio
Date: Mon Jul 15 23:48:08 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=f60e696f-fe9d-4216-86ec-ce13930c9c34
InstallationDate: Installed on 2013-07-10 (5 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130709)
InterpreterPath: /usr/bin/python3.3
MachineType: Hewlett-Packard 520-1138cb
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.10.0-2-generic root=UUID=ee63e052-abe5-4316-8499-10528ed15dd7 ro recovery nomodeset rootflags=subvol=@
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-3.10.0-2-generic N/A
 linux-backports-modules-3.10.0-2-generic N/A
 linux-firmware 1.112
SourcePackage: linux
Title: [Hewlett-Packard 520-1138cb] suspend/resume failure [non-free: wl]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/23/2012
dmi.bios.vendor: AMI
dmi.bios.version: 7.09
dmi.board.asset.tag: 3CR22302J0
dmi.board.name: 2ADC
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.05
dmi.chassis.asset.tag: 3CR22302J0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAMI:bvr7.09:bd11/23/2012:svnHewlett-Packard:pn520-1138cb:pvr1.00:rvnPEGATRONCORPORATION:rn2ADC:rvr1.05:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: 520-1138cb
dmi.product.version: 1.00
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Ken (ken3-burtinsky) 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
Revision history for this message
penalvch (penalvch) wrote :

Ken, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: latest-bios-7.09 needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ken (ken3-burtinsky) wrote :

No luck with Mainline kernel v3.11-rc1 I get black screen and even using REISUB it would not reboot had to use power button

tags: added: kernel-bug-exists-upstream v3.11-rc1
removed: amd64 apport-kerneloops latest-bios-7.09 needs-upstream-testing resume saucy suspend third-party-packages
Ken (ken3-burtinsky)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Low
Revision history for this message
penalvch (penalvch) wrote :

Ken, thank you for testing the newest mainline kernel. For regression testing purposes, could you please test for this in Precise via http://releases.ubuntu.com/precise/ and report the results?

tags: added: amd64 apport-kerneloops latest-bios-7.09 resume saucy suspend third-party-packages
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ken (ken3-burtinsky) wrote :

I was using 12.04.2 on another partition and was having the same suspend resume problems thats why I tried 13.04 then 13.10. After installing 13.10 grub does not show 12.04 any longer but I can see and access files from 13.10.

penalvch (penalvch)
tags: added: precise
tags: added: kernel-bug-exists-upstream-v3.11-rc1
removed: kernel-bug-exists-upstream v3.11-rc1
Revision history for this message
Ken (ken3-burtinsky) wrote :

It looks like the suspend resume problem has been fixed as I have tried suspending ad resumeing about 5 times and everything seems normal. I am not sure which update over the past day or so fixed the problem but so far so good.
I am using the 3.11 rc1 kernel still and the Graphics driver is Gallium 0.4 on llvmpipe (LLVM 3.2, 256 bits) which is not what it was .

Revision history for this message
Ken (ken3-burtinsky) wrote :

I am not sure what or how it happened but after a reboot I had to go to recovery mode after REISUB and now my graphics driver is VESA: Intel® Sandybridge/Ivybridge Graphics and apport says Xorg crashed per bug [Bug 1202763] [NEW] Xorg crashed with SIGABRT in raise() I don't know if these 2 issues are related

Revision history for this message
penalvch (penalvch) wrote :

Ken, could you please capture a suspend log following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

tags: added: regression-potential
tags: added: needs-suspend-log
Revision history for this message
Ken (ken3-burtinsky) wrote :

Installed latest kernel Daily from Mainline builds. I see many error messages in attached dmesg txt file but not sure what they mean or how to fix them. I only tried one suspend resume so far sometimes I get resume failure after 2 or 3 suspends. Will let you know if it fails later today.

Revision history for this message
Ken (ken3-burtinsky) wrote :

Tried another suspend after screen is turned off by power saving When I resume and the screen turns back on when I move the mouse but then everything is locked up keyboard and mouse do not work except for REISUB

Revision history for this message
penalvch (penalvch) wrote :

Ken, could you please advise if this is reproducible with http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/ ? Please note, testing the daily folder wouldn't be helpful. As well, if reproducible in v3.11-Saucy, could you please provide all the information requested in https://wiki.ubuntu.com/DebuggingKernelSuspend ?

Revision history for this message
Ken (ken3-burtinsky) wrote :

Tried directions on Debugging Kernel Suspend and after the first try it seemed to resume properly. But after a 2nd suspend it only partly resumed as the screen came on but mouse and keyboard did not work. This as with the 3.11 saucey kernel.
Did not see any hash matches in dmesg.txt

Revision history for this message
Ken (ken3-burtinsky) wrote :

I cannot seem to send any attachments as every time I click on Post Comment nothing happens so here is /proc/acpi/wakeup
Device S-state Status Sysfs node
P0P1 S4 *disabled
USB1 S3 *disabled
USB2 S3 *disabled
USB3 S3 *disabled
USB4 S3 *disabled
USB5 S3 *disabled
USB6 S3 *disabled
USB7 S3 *disabled
RP01 S4 *disabled pci:0000:00:1c.0
PXSX S4 *enabled pci:0000:01:00.0
RP02 S4 *disabled pci:0000:00:1c.1
PXSX S4 *disabled pci:0000:02:00.0
RP03 S4 *disabled pci:0000:00:1c.2
PXSX S4 *disabled pci:0000:03:00.0
RP04 S4 *disabled pci:0000:00:1c.3
PXSX S4 *disabled pci:0000:04:00.0
RP05 S4 *disabled pci:0000:00:1c.4
PXSX S4 *disabled
RP06 S4 *disabled pci:0000:00:1c.5
PXSX S4 *enabled pci:0000:06:00.0
RP07 S4 *disabled
PXSX S4 *disabled
RP08 S4 *disabled
PXSX S4 *disabled
PEG0 S4 *disabled
PEGP S4 *disabled
GLAN S4 *disabled
EHC1 S3 *enabled pci:0000:00:1d.0
EHC2 S3 *enabled pci:0000:00:1a.0
XHC S3 *disabled
HDEF S4 *disabled pci:0000:00:1b.0

Revision history for this message
penalvch (penalvch) wrote :

Ken:
>"Did not see any hash matches in dmesg.txt"

Still need to attach it with v3.11 kernel so others may analyze it.

tags: added: needs-upstream-testing
tags: added: kernel-bug-exists-upstream-v3.11
removed: kernel-bug-exists-upstream-v3.11-rc1
Revision history for this message
Ken (ken3-burtinsky) wrote :

Same thing happeed again first resume went fine but on 2nd resume the screen comes on and looks fine but there is no mouse or keyboard except for REISUB

Revision history for this message
penalvch (penalvch) wrote :

ken, just to clarify, not Ubuntu, but mainline v3.11 via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/ .

tags: removed: kernel-bug-exists-upstream-v3.11
Revision history for this message
Ken (ken3-burtinsky) wrote :

3.11 Mainline same story

penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-v3.11
removed: needs-suspend-log needs-upstream-testing
Revision history for this message
Ken (ken3-burtinsky) wrote :

Sorry I am not very good at command line so I was afraid to mess up the whole system as I could not figure out the partitions on 10.04
server. I tried my original install disk for 10.04 but only got the wallpaper no desktop or anything else so unable to test.
Tried Ubuntu 3.11.0.6 this morning and the second resume I got desktop and mouse and keyboard control but I could not see the pointer for mouse but as I moved it around it would affect desktop icons.

Revision history for this message
Ken (ken3-burtinsky) wrote :

Downloaded Lucid again but when I tried to run it I got to the screen where it asks if you want to try it or install I chose try but then I only got a blank screen with no desktop. Could not even open a terminal.

Revision history for this message
Ken (ken3-burtinsky) wrote :

Tried latest ubuntu kernel 3.11.0.7 and after second suspend it would not resume fully- mouse and keyboard not working and network
would not come on. Also lately the HUD pops up when I resume.

Revision history for this message
penalvch (penalvch) wrote :

Ken, would Natty provide a Live test via http://old-releases.ubuntu.com/releases/natty/ ?

tags: added: unable-to-test-lucid
Revision history for this message
Ken (ken3-burtinsky) wrote :

Managed to do a live test of 10.04 and 11.04 using noapic and nolapic but both only resumed to a black screen after 1 suspend

penalvch (penalvch)
tags: added: lucid natty
removed: unable-to-test-lucid
tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

Ken, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Please test latest development kernel (3.11.0-7.14)

Given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We are approaching release and would like to confirm if this bug is still present. Please test again with the latest development kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.11.0-7.14
Revision history for this message
Ken (ken3-burtinsky) wrote :

Bug still exists - after first resume the screen comes back on normaly but network is off and mouse does not respond after a few seconds the sreen flickers and goes black for a second then back on with network and mouse working and the HUD is also on. But after 2nd resume the sreen comes back on and nothing else works except for REISUB to reboot.
Kernel 3.11.0-7.14

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Ken (ken3-burtinsky) wrote :

Just updated to 3.11.0-8 and had same resuls as above

Revision history for this message
penalvch (penalvch) wrote :

Ken, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc2-saucy/ and advise on the results?

As well, could you please provide an upstream mailinglist archive URL of when you initially posted?

tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ken (ken3-burtinsky) wrote :

As well, could you please provide an upstream mailinglist archive URL of
when you initially posted? -- This launchpad.net site is all I know.
Tested 3.12-rc2-saucy and got same results with resume failing on 2nd suspend

Revision history for this message
Ken (ken3-burtinsky) wrote :

Tried suspend and resume again following instructions "resume-trace" debugging procedure for finding buggy drivers.
using sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" I suspended and resumed 3 times in a row and everything resumed properly.
Then I tried normal suspend from menu on desktop and screen again was on but locked up.Used alt ctrl f1 to get to tty and did dmesg > dmesg.txt

Revision history for this message
Ken (ken3-burtinsky) wrote :

Tried same thing again 4 times in a row with "sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" and again everything resumed correctly.
Then after normal suspend again mouse locked up so I powered down and rebooted and dmesg > dmesg.txt I do not know if there is any different info in this 2nd dmesg

Revision history for this message
penalvch (penalvch) wrote :

Ken, then you would want to follow the instructions noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201674/comments/27 so upstream may be made aware of this problem.

penalvch (penalvch)
tags: added: bot-stop-nagging kernel-bug-exists-upstream-v3.12-rc2
removed: kernel-bug-exists-upstream-v3.11 kernel-request-3.11.0-7.14
tags: removed: needs-upstream-testing
Revision history for this message
Ken (ken3-burtinsky) wrote :

Tested 3.12.0-rc3 and had same results as rc2. Then tried same kernel with nomodeset and only get black screen and only power button can reboot. Got hash match--Magic number: 0:884:740
[ 0.579806] hash matches /home/apw/COD/linux/drivers/base/power/main.c:649

penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-v3.12-rc3
removed: kernel-bug-exists-upstream-v3.12-rc2
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Ken (ken3-burtinsky) wrote :

I have been running Mint 15 for a few weeks now and everything is running well. When I first installed Mint with the 3.8.0-19 kernel I again had problems with resume from suspend but I am now using 3.11.3-031103-generic and all is good with resume.

penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.