public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jake Edge <jake@lwn.net>
To: hpa@linux.intel.com, rjw@sisk.pl, linux-kernel@vger.kernel.org
Subject: sleep/fan problem bisected to 73201dbec64aebf6b0dca855b523f437972dc7bb
Date: Fri, 12 Apr 2013 12:08:31 -0600	[thread overview]
Message-ID: <20130412120831.1402b440@chukar.edge2.net> (raw)


Hi Peter,

I have been having a problem on my laptop (HP Compaq 2510p) over the
last two months with >= 3.7 kernels.  After the first resume, it turns
on the fan and leaves it running at top speed no matter what the system
is doing.  I finally bisected it over the last two days and that points
the finger at your patch 73201dbec64aebf6b0dca855b523f437972dc7bb:

 x86, suspend: On wakeup always initialize cr4 and EFER
    
    We already have a flag word to indicate the existence of
 MISC_ENABLES, so use the same flag word to indicate existence of cr4
 and EFER, and always restore them if they exist.  That way if
 something passes a nonzero value when the value *should* be zero, we
 will still initialize it.

I should note that the bisection (between 3.6, which works, and 3.7,
which doesn't) did not exhibit the same symptoms as I see with any 3.7
or 3.8 kernel (either from Fedora or built myself), but would instead
refuse to come out of sleep (but still have the fan running at top
speed) ... so maybe I've really bisected the "fails to come out of
sleep" problem, rather than the "fan runs at top speed after resume"
problem, dunno ... but it would seem that code is still present in 3.7+
and I have no trouble resuming using those kernels (other than the damn
noisy fan :)

The output of "sensors" is interesting ... for "temp6" in
"acpitz-virtual-0" it sits at +100C (near the +110C critical level)
when things have gone bad (just in Fedora or my kernels >=3.7, not in
the bisect, cuz those don't come back from the sleep) ... in the "good"
case, it normally sits around 30, but goes as high as 50 (and sometimes
reports 0 for a try or two -- frozen motherboard! :) ...

thoughts on this?  Other info you need or things I should be trying?

thanks,

jake

-- 
Jake Edge - LWN - jake@lwn.net - http://lwn.net

             reply	other threads:[~2013-04-12 18:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12 18:08 Jake Edge [this message]
2013-04-12 23:18 ` sleep/fan problem bisected to 73201dbec64aebf6b0dca855b523f437972dc7bb Jake Edge
2013-04-13  4:48 ` auxsvr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130412120831.1402b440@chukar.edge2.net \
    --to=jake@lwn.net \
    --cc=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox