linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ville Syrjala <syrjala@sci.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: regression in linux 3.7 - fan speed at 100% after suspend/resume at 100%
Date: Sun, 3 Mar 2013 00:22:45 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130303T010825-770@post.gmane.org> (raw)
In-Reply-To: 50BDF345.60804@gmail.com

Roberto Oppedisano <roberto.oppedisano <at> gmail.com> writes:

> 
> Hello,
>      with recent kernels after a suspend/resume cycle on my laptop (HP 
> 6730b) the fans stays at full speed.

I too have been hit by this regression w/ a HP Compaq NC6000 laptop.

>From what I can tell 3.7.x gets confused about trip points after resume. Based
on the information in sysfs, it seems to always think that the CPU temp > 65C,
when in fact it's usually 40C or so. Loading the CPU enough to rise the
temperature past the trip point where the kernel thinks we're at seems to
re-synchronize the kernel's reality with the firmware's reality. On a few
occasions however the fan did stop, but the trip points were still confused the
same way. So what happened is that the fan didn't come back to life until I hit
the next higher trip point at 80C. Under normal conditions I've never reached
the 80C trip point on this laptop.

I also tried this tree:
git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git next
$ git describe
v3.8-rc2-72-gf5b6d45

Sadly I must report that it's even worse than 3.7. Even without any
suspend/resume cycles, the system gets confused. When I heat up the CPU the fan
comes on correctly and speeds up as the temperature rises. Unfortunately when
the temperature drops the fan doesn't slow down at all. So once I hit a high
trip point the fan stays at that speed forever.



  parent reply	other threads:[~2013-03-03  0:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 12:57 regression in linux 3.7 - fan speed at 100% after suspend/resume at 100% Roberto Oppedisano
2012-12-04 14:11 ` Zhang Rui
2012-12-05  7:30   ` Roberto Oppedisano
2012-12-19 14:30     ` Roberto Oppedisano
2013-02-19 17:54       ` Salvatore Sisinni
2013-02-20  0:20         ` Zhang Rui
2013-02-20 13:41           ` Roberto Oppedisano
2013-02-21 17:17             ` Salvatore Sisinni
2013-03-06 14:44               ` Salvatore Sisinni
2013-02-15 23:30   ` Michael Grosshaeuser
2013-02-16  6:55     ` auxsvr
2013-03-03  0:22 ` Ville Syrjala [this message]
2013-03-04 12:29   ` Roberto Oppedisano
2013-03-04 13:25     ` Roberto Oppedisano
2013-03-09 17:50 Sascha Wilde
2013-03-10 15:47 ` Sascha Wilde

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=loom.20130303T010825-770@post.gmane.org \
    --to=syrjala@sci.fi \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).