From: Jiri Slaby <jirislaby@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-acpi@vger.kernel.org,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Fan runs full speed after S3 sometimes (regression)
Date: Fri, 20 Aug 2010 08:39:54 +0200 [thread overview]
Message-ID: <4C6E233A.5000209@gmail.com> (raw)
In-Reply-To: <20100820063107.GB1607@ucw.cz>
On 08/20/2010 08:31 AM, Pavel Machek wrote:
> On Tue 2010-08-10 20:39:44, Jiri Slaby wrote:
>> On 08/10/2010 01:20 PM, Jiri Slaby wrote:
>>> Hi,
>>>
>>> till I was running on 2.6.34-rc5-mm1 (mmotm) and earlier everything was
>>> fine. Now, I'm running 2.6.35-rc6-mm1 (.35-rc5-mm1 was the same) and
>>> sometimes when the computer (desktop) returns from S3, the CPU fan is
>>> running at full speed making a big noise.
>>
>> Just to add, full power cycle is needed to get rid of that. Warm reboot
>> is not enough.
>
> Seems like bios problem... Update bios?
I don't think so, it had been working for more than 2 years before this
issue appeared.
>>> I don't know how to debug that. Bisection is out of question -- it
>>> happens once in 10 or 20 cases. There are no fan entries in /sys.
>
> Well, doing 20 suspends in a row from a script should not be too bad.
20 is just a guess. I haven't seen it for pretty few days until the day
before yesterday. And it looks like CPU1 is brought up a half way. When
the fan was at full speed I tried:
echo 0 > /sys/devices/system/cpu/cpu1/online
and whole system freezed. Otherwise this commands succeeds.
I'll load a crash kernel prior turning the CPU off next time.
thanks,
--
js
next prev parent reply other threads:[~2010-08-20 6:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 11:20 Fan runs full speed after S3 sometimes (regression) Jiri Slaby
2010-08-10 18:39 ` Jiri Slaby
2010-08-20 6:31 ` Pavel Machek
2010-08-20 6:39 ` Jiri Slaby [this message]
2010-08-20 23:30 ` Rafael J. Wysocki
2010-08-21 17:05 ` Pavel Machek
2010-09-08 13:27 ` Jiri Slaby
2010-09-08 20:26 ` Rafael J. Wysocki
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=4C6E233A.5000209@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
/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).