linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Großhäuser" <michael.grosshaeuser@t-online.de>
To: linux-pm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fans at full speed after resume
Date: Mon, 27 May 2013 22:36:19 +0200	[thread overview]
Message-ID: <ko0g1j$fc1$1@ger.gmane.org> (raw)
In-Reply-To: 1369631068.2159.2.camel@rzhang1-mobl4

Zhang Rui wrote:

> On Thu, 2013-05-23 at 22:22 +0200, Michael Großhäuser wrote:
>> Zhang Rui wrote:
>> 
>> > On Wed, 2013-05-22 at 20:46 +0200, Michael Großhäuser wrote:
>> >> Zhang Rui wrote:
>> >> 
>> >> > On Wed, 2013-05-15 at 12:26 +0800, Zhang Rui wrote:
>> >> >> please
>> >> >> 
>> >> >> On Tue, 2013-05-14 at 21:18 -0700, Sonny Rao wrote:
>> >> >> > Hi, I've seen a regression in kernels since 3.7 on x86 devices
>> >> >> > where the kernel turns the system fans on to max speed after
>> >> >> > resuming from
>> >> >> > ram.  Other people have noticed it as well, for example see
>> >> >> > https://bugzilla.redhat.com/show_bug.cgi?id=895276
>> >> >> > 
>> >> >> please check if this is a duplicate of bug
>> >> >> https://bugzilla.kernel.org/show_bug.cgi?id=56591
>> >> > or you can try 3.10-rc1 to see if the problem still exists or not.
>> >> > 
>> >> > thanks,
>> >> > rui
>> >> 
>> >> 
>> >> Hi,
>> >> 
>> >> I can confirm the same problem on a HP/Compaq 2510p with 3.10-rc2.
>> >> 
>> > please check if this is a duplicate of bug
>> > https://bugzilla.kernel.org/show_bug.cgi?id=58301
>> > 
>> > please try the patch at comment #7 and see if it helps or not.
>> > 
> Good to know.
> then could you please try the four patches in comment #10, #11, #12 and
> #13 in
> https://bugzilla.kernel.org/show_bug.cgi?id=58301
> without the previous patch and check if they help?
> 
> These four patches are the fixes that I would push for upstream.

Hi,

I applied the patches to 3.10-rc2 and it works well after several suspend 
resume cycles. Feel free to add me as Tested-by.

Best regards,
Michael 

> thanks,
> rui
>> > thanks,
>> > rui
>> 
>> Hi,
>> 
>> the patch fixes the problem for me.
>> 
>> Thanks,
>> Michael
>> 
>> 
>> >> Best Regards,
>> >> Michael
>> >> 
>> >> --
>> >> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
>> >> the body of a message to majordomo@vger.kernel.org
>> >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



      reply	other threads:[~2013-05-27 20:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15  4:18 Fans at full speed after resume Sonny Rao
2013-05-15  4:26 ` Zhang Rui
2013-05-15  4:29   ` Zhang Rui
2013-05-15  4:34     ` Sonny Rao
2013-05-15  4:56       ` Sonny Rao
2013-05-15  9:46         ` Sonny Rao
2013-05-15  4:34     ` Olof Johansson
2013-05-22 18:46     ` Michael Großhäuser
2013-05-23  2:25       ` Zhang Rui
2013-05-23 20:22         ` Michael Großhäuser
     [not found]         ` <1Ufc0I-09RzDk0@fwd03.t-online.de>
2013-05-27  5:04           ` Zhang Rui
2013-05-27 20:36             ` Michael Großhäuser [this message]

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='ko0g1j$fc1$1@ger.gmane.org' \
    --to=michael.grosshaeuser@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@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).