[HP Pavilion dv6t-6b00 CTO Quad Edition Entertainment Notebook PC] System spontaneously awakes from sleep

[slowtrain]

I added KDE to an Ubuntu installation. When suspending, a few seconds later, the computer woke up without my doing anything (did not touch the keyboard, etc.). This has happened numerous times. For a while, I had to suspend twice whenever I wanted the suspend to take hold.

I'm attaching logs from --pm-suspend and pm-powersave.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-29-generic 3.13.0-29.53
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: peterm 3016 F.... pulseaudio
BootDmesg:

CurrentDesktop: KDE
Date: Sat Jun 7 17:47:52 2014
HibernationDevice: RESUME=UUID=5d23be8c-e134-466b-8698-0344f70809a4
InstallationDate: Installed on 2014-04-20 (48 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
ProcFB:
 0 inteldrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic root=UUID=905a5deb-feac-448c-9f59-7040a9ea9942 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-29-generic N/A
 linux-backports-modules-3.13.0-29-generic N/A
 linux-firmware 1.127.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:

dmi.bios.date: 10/23/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1B
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 17FB
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 10.5A
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/23/2012:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058D110002204720000622100:rvnHewlett-Packard:rn17FB:rvr10.5A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: 058D110002204720000622100
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

slowtrain, could you please provide the full computer model as noted on the sticker (ex. HP Pavilion dv6-6b00 Entertainment Notebook PC series)?

[slowtrain (pmuhl830)]

There's no sticker giving specifics on the computer, at least that I could find. The order form for the computer says it's a HP Pavilion dv6t Quad Edition Laptop, product # A2Z57AV. That product number suggests, according to a google search, that the specific version of the dv6t it is is dv6t-6b00.

I've also filed a bug report when the system froze on trying to suspend. It is bug #1328708. The system has frozen on suspend three times in the last three days.

The install of Ubuntu 14.04 was a fresh install about 2 months ago w/ KDE on top of it. Started having these problems with suspend from almost the day I started using KDE.

[slowtrain (pmuhl830)]

Hi Chris:

I updated my bios a few days ago. I can confirm that two sleep problems continue to occur: About half the time I try to suspend to RAM, the system wakes back up spontaneously a few seconds after apparently shutting down. And, once so far, the system has fallen asleep on its own, and then wakes back up again a few seconds later. The system has not yet frozen on attempting to suspend to RAM, but that has typically occurred in clusters a week or two apart, so no certainty that has been relieved.

[slowtrain (pmuhl830)]

The output of "sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date" is:

F.1C
01/23/2013

To my knowledge, that's the most recent BIOS for this computer.

Cheers

[penalvch (penalvch)]

slowtrain, could you please test the latest upstream kernel available from the first line at the top page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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-3.15

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

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.

[slowtrain (pmuhl830)]

I'm a little unclear as to which kernel I should try. If I go to:

http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

The first kernel is v3.15-utopic/, but I'm running trusty. So, should
I try the first trusty kernel in the list, namely: v3.15-rc2-trusty/ ?

[penalvch (penalvch)]

slowtrain, sorry for the confused wording, I've changed this going forward. I should have asked:
Could you please test the latest upstream kernel available from the very top line at the top of the page? In this case, this is 3.16-rc1.

[slowtrain (pmuhl830)]

I installed the new kernel. Have done 10 RAM suspends and so far no spontaneous wakings. On the other hand, yesterday I tried running two sequences of five suspends (system reboot in between) and got no spontaneous waking, but did get two system crashes and a third one in Unity (am using the computer somewhat differently than in past months). So, jury is not entirely in on spontaneous wakings, but looking good so far.

[Launchpad Janitor (janitor)]

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

[penalvch (penalvch)]

slowtrain, the next step is to fully reverse commit bisect the kernel in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

[Launchpad Janitor (janitor)]

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