[HP Pavilion dv6t-6b00 CTO Quad Edition Entertainment Notebook PC] System freezes periodically when I try to suspend to RAM

[slowtrain]

About a couple times a week, my system freezes when I suspend to RAM (only way out is hard power off--alternative terminals are inaccessible). These seems to be happening more in KDE than when I was using Unity.

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 3598 F.... pulseaudio
CurrentDesktop: KDE
Date: Tue Jun 10 18:25:42 2014
HibernationDevice: RESUME=UUID=5d23be8c-e134-466b-8698-0344f70809a4
InstallationDate: Installed on 2014-04-20 (51 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)
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.

[slowtrain (pmuhl830)]

Hi Chris: So i installed a newer kernel today, 3.16-rc1. So far, no system crashes, which is very promising.

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). I noticed the attach bug report three times right before a crash (always the same bug report). Looks like the bug is in the MEI driver, which could mean that other Intel systems are affected.

If, as now seems likely, the new kernel will resolve my issues, I'd like to use it in earnest, but this raises many questions. For example, VirtualBox refuses to work under this new kernel, and the kernel wants me to install nearly 100 new packages, but I suspect this would mess things up for the old kernel and I may need to go back to that when things like VB won't work. Should I check with the Ubuntu forum bboards to get these kinds of questions answered?

Cheers!

[slowtrain (pmuhl830)]

Well, the new kernel was more stable for a week, but I've now had two system crashes, one waking from sleep (a new phenomenon) and one going to sleep (same old). Also had it wake spontaneously right after I tried to put it to sleep. Whether these are exactly the same problem as in the existing kernel I do not know. I went through my kernel and dmesg logs and didn't see an error that might explain what I'm experiencing. I did send in automatic bug reports after the crashes. As was true in earlier versions of Ubuntu, the latest crash hosed my audio--no sound at all. This is the first time a crash wrecked my audio since moving to 14.04.

[penalvch (penalvch)]

slowtrain, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc2-utopic/ and advise to the results?

[slowtrain (pmuhl830)]

I've switched to 3.16-rc2. May take a while for anything to manifest. Oddly, with rc1 everything seemed stable for the first week of use. During the 2nd week I got the full stream of issues I had w/ 3.13 (it spontaneously fell asleep today for the 1st time).

[slowtrain (pmuhl830)]

After a few days of using 3.16-rc2, I can report that I'm experiencing similar problems to what I experienced in 3.13. The system has frozen once, on being put to sleep. It has also on multiple occasions spontaneously fallen asleep during computer use and woken up spontaneously right after I tried to put it into suspend. It may be coincidence (because the problems seem to appear in clusters), but the problems seem to be occurring far more frequently than in rc1.

[penalvch (penalvch)]

slowtrain, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc3-utopic/ and advise to the results?

[slowtrain (pmuhl830)]

Just installed it & will let you know how it goes. Will be out of town for several weeks shortly, so may not get back soon. Would be helpful to know whether anything is being done in these kernels to address the problems I've been having or whether this is entirely trial and error.

[slowtrain (pmuhl830)]

Just fyi, rc3 had the same problems as ever: crashes either going to and waking from sleep; system spontaneously waking after trying to put it to sleep, a rare instance or two of the system falling asleep spontaneously while being used.

A little over a week ago, I installed rc7. Same problems. If you're beginning to think that this is a hardware problem, you should know that the system also has windows on it (dual boot). When windows is running, I have never had a problem with sleep or system freezes.

It's not clear to me that apport is reporting these problems to you. When I hard shutdown and restart after a crash, I get the dialog boxes asking me whether I want to report a problem (in fact, I get these boxes whether the system crashes or shuts down gracefully). I indicate I do, but then don't get a dialog box from apport 'ubuntu crash' that asks me for my password.

On my last crash the screen filled with what looked like dmesg output and something to the effect that there was a 'recursive error'

I'm wondering if there's a deliberate effort to address the problems I'm having or whether the kernel team is simply working on a better kernel and the hope is that it will by chance fix these problems.

[penalvch (penalvch)]

slowtrain, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[slowtrain (pmuhl830)]

I'm a little unclear as to what you'd like me to do with DebuggingKernelSuspend. The system crashes are not deterministic--they happen about once a week at my current use rate. So, I can't make them happen. My last crash was last night, but I had to hard reboot 4 times before I had a functioning system. The first time was to restart after the crash, the last 3 times were because the system froze as it tried to load KDE. On the last reboot, KDE came back, so it's on this reboot that I'm collecting data.

As far as I can tell, the DebuggingKernelSuspend document suggests obtaining the two pieces of output I've attached. There are no instances of "hash matches" in the enclosed dmesg output.

Anyway, hope this helps. If there's anything else I can do, let me know. Incidentally, I told the system to report bugs (these appeared in dialog boxes on reboot), but the usual apport password authentication and other dialogs never came up, so I don't know whether the bug reports were sent (probably not).

BTW, I can't make sense out of what DebuggingKernelSuspend is saying about the clock. There don't seem to be any commands listed that make use of that.

Peter

[penalvch (penalvch)]

Extracted from compressed file.

[penalvch (penalvch)]

slowtrain, thank you for posting the dmesg.txt that contained a call trace (next time, please don't tar/compress attachment). The call trace would be sufficient for this bug report to be scoped to. With this in mind, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc1-utopic/ and advise if you still get a crash?

As well, did this problem not occur in a release prior to Trusty?

[slowtrain (pmuhl830)]

I've been using v3.17-rc1-utopic for a few weeks now. It didn't crash for more than a week, then I had two system freezes on the same day. Hasn't crashed again in more than a week. I do get some 'sleep effects'--initially going into suspend right after I tried to wake it, more recently spontaneously going into suspend and waking immediately after I suspend it. Overall, seems like pretty much the same set of problems. I created a script to save the dmesg output right before a suspend because it's on suspend or wake that the system freezes and the dmesg right before a freeze usually contains a bug trace. Just have to wait for it to crash again.

[penalvch (penalvch)]

slowtrain, would the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc3-utopic/ improve upon your experience with the 3.17-rc1?

[slowtrain (pmuhl830)]

Hi Christopher:

First, to let you know about a crash: I was running 3.13.0-35 and it spontaneously woke up from sleep and froze on me, with the screen repeating an error message approximately like: mei_me no destination server found. I have a dmesg copy from what I believe is right before the crash (when it went to sleep and before spontaneously waking) but do not see anything obvious in it. Just in case, it's attached.

I'll try out the most recent kernel when I get a chance. I've not been able to use rc1 much and have been waiting to catch it in the act of crashing--with my dmesg on suspend code running. Would like to get that to you so perhaps the problem could be identified. I haven't used rc1 heavily in part because I can't compile dkms for virtualbox, which I need for attaching to my workplace infrastructure. Apparently, it's not available for that version of the kernel yet. Given that this laptop has been out for several years, it's not a good thing that ubuntu still has problems with it.

Cheers

[slowtrain (pmuhl830)]

Just had a crash with 3.17.0 rc7. When it woke from sleep, the login screen appeared but neither the keyboard or mouse externally attached or the keyboard or trackpad on the machine would respond. Had to hard reboot. dmesg output from the time the computer was put to sleep and shortly after I hard rebooted the machine are attached. There are a lot of error msgs about hal, which I installed because otherwise I couldn't watch video from Amazon or Hulu(?). I think there are hal error messages even w/o a crash.

I tried to install 3.18 rc2 but there are error messages during the install to the effect that it can't compile dkms and vmlinux or something like that. When I try to boot into 3.18 rc2, I get kicked to some kind of system prompt after it says it can't load something.

Cheers

[slowtrain (pmuhl830)]

Seems I can only attach one file at a time. Here's the post-crash dmesg for the previous msg.

[slowtrain (pmuhl830)]

Whoops:

[penalvch (penalvch)]

slowtrain, would 3.18-rc1 provide a testing environment?

[slowtrain (pmuhl830)]

Hi Christopher:

I've been using 3.18-rc1 for a few weeks now. Initially seemed quite stable, except for fairly consistent 'double wakings'--that is, I'd wake it from a suspend and it would automatically fall asleep again in a few seconds. It would stay awake after a couple wakings. In the last couple weeks, I've had a number of crashes. One crash while waking from sleep (by crash I mean a complete system freeze, couldn't switch to an alternative terminal for a graceful shutdown), a couple crashes while booting up (KDE would not load and then I couldn't do anything but a hard reboot), and probably a couple more crashes the specifics of which I cannot now remember. Still, more stable than the current kernel for this computer.

Do you think I could try anything more advanced than 3.18-rc1 given that X wouldn't load with 3.18-rc2?

Happy holidays!

[penalvch (penalvch)]

slowtrain, happy holidays. it would be helpful to test out the latest mainline kernel 3.19-rc1 to see if this gives you a later environment to test with.

[slowtrain (pmuhl830)]

I've now tested 3.19-rc1 for about a month. First couple weeks it was rock steady--no weird behavior involving sleep (spontaneously falling asleep either on wake up or spontaneously waking up when I try to put to sleep) and no crashes. At the end of two weeks, I began to get 'double wakings' (i.e., I had to unsuspend twice before it stayed unsuspended and didn't fall asleep spontaneously), shortly thereafter I had a couple system freezes, requiring hard shutdown. Each time I had plugged in something to the USB port(s) while it was in suspend and crashed occurred while waking. It's been double-waking consistently since the first freeze, for a couple weeks. Had my third system freeze today, also on wake from suspend.

I'll update to the latest kernel....

[slowtrain (pmuhl830)]

Updated to 3.19-rc5. Attached are install error, mostly module issues with radeon and virtualbox, I think.

[penalvch (penalvch)]

slowtrain, build errors for virtualbox is discussed in https://wiki.ubuntu.com/Kernel/MainlineBuilds .

[Launchpad Janitor (janitor)]

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