public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <syrjala@sci.fi>
To: Jake Edge <jake@lwn.net>, Zhang Rui <rui.zhang@intel.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Eduardo Valentin <eduardo.valentin@ti.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Roberto Oppedisano <roberto.oppedisano@gmail.com>,
	Salvatore Sisinni <s.sisinni@gmail.com>,
	auxsvr@gmail.com
Subject: Re: still in 3.9-rc6 - fan speed at 100% after suspend/resume regression
Date: Sun, 14 Apr 2013 02:46:46 +0300	[thread overview]
Message-ID: <20130413234646.GH25821@sci.fi> (raw)
In-Reply-To: <20130413214359.GG25821@sci.fi>

On Sun, Apr 14, 2013 at 12:44:00AM +0300, Ville Syrjälä wrote:
> On Sat, Apr 13, 2013 at 10:02:21AM -0600, Jake Edge wrote:
> > Hi Zhang Rui,
> > 
> > The problem reported in https://lkml.org/lkml/2012/12/4/428 (and
> > incorrectly attributed to a suspend patch by me here:
> > https://lkml.org/lkml/2013/4/12/314) still exists in 3.9-rc6, at least
> > for my HP/Compaq 2510p laptop. It appeared that some folks were seeing
> > some improvement with earlier 3.9-rcs (?) but I just tested rc6 and saw
> > substantially the same behavior.  This all works fine in <= 3.6.11.
> > 
> > A brief recap: after resuming, the fan on the laptop spins up to full
> > speed and stays there. "temp6" in "acpitz-virtual-0" (as shown by
> > "sensors") is 100°C and stays there, which is presumably what is making
> > the fan stay on.
> 
> My HP Compaq NC6000 exhibits slightly different behaviour. For me the
> reported temp is always accurate but the trip points get out of sync
> with the actual temperature.
> 
> With 3.7 I saw two different kinds of problems coming out of resume.
> In one case the fan stays on until the temp rises high enough to get the
> trip points back into sync. In the other case the fan goes off, and stays
> off even when the temperature rises above the highest active trip point,
> but it does appear to get back into sync when the temp starts to come back
> down. I think the difference might stem from resuming when the laptop has
> cooled down fully vs. when it's still warm.
> 
> I also just tried 3.9-rc6, and that one appears to behave differently
> to 3.7, but still wrong. There the fan goes off after resume, and comes
> back on as the temperature rises, but it never slows back down after
> that.
> 
> I'll try to collect some more detailed dumps of all three cases.

I filed a new bug and attached all my logs:
https://bugzilla.kernel.org/show_bug.cgi?id=56591

-- 
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/

  reply	other threads:[~2013-04-13 23:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130413100221.70c040fa@chukar.edge2.net>
     [not found] ` <1365877215.2221.8.camel@rzhang1-mobl4>
2013-04-13 20:07   ` still in 3.9-rc6 - fan speed at 100% after suspend/resume regression Jake Edge
2013-04-13 21:44 ` Ville Syrjälä
2013-04-13 23:46   ` Ville Syrjälä [this message]
2013-04-15 13:30     ` Eduardo Valentin
2013-04-16  1:35       ` Zhang Rui

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=20130413234646.GH25821@sci.fi \
    --to=syrjala@sci.fi \
    --cc=auxsvr@gmail.com \
    --cc=eduardo.valentin@ti.com \
    --cc=jake@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=roberto.oppedisano@gmail.com \
    --cc=rui.zhang@intel.com \
    --cc=s.sisinni@gmail.com \
    /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