sleep/fan problem bisected to 73201dbec64aebf6b0dca855b523f437972dc7bb
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
Signature · 1 line
Jake Edge - LWN - [email protected] - http://lwn.net
Quoted 15 lines · On Fri, 12 Apr 2013 12:08:31 -0600 Jake Edge wrote:
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.
Quoted 7 lines
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 ...
As you've undoubtedly surmised, I was in fact tracking down the resume failure which was caused by the above and fixed by another of your
patches: 1396adc3c2bdc556d4cdd1cf107aa0b6d59fbb1e ... neither of which were related to the fan issue as far as I can tell ... now I am off bisecting while applying those ...
sorry for the noise ...
jake
Signature · 1 line
Jake Edge - LWN - [email protected] - http://lwn.net
Quoted 14 lines · Jake Edge
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.
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! :) ...
Quoted 1 line
thoughts on this? Other info you need or things I should be trying?
This is known, see https://lkml.org/lkml/2012/12/4/428 for more details.
Quoted 3 lines
thanks,
jake
Regards,
Peter