From: Eric Valette <eric.valette@free.fr>
To: Len Brown <len.brown@intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Karol Kozimor <sziwan@hell.org.pl>
Subject: Re: 2.6.8-rc4-mm1 : Hard freeze due to ACPI
Date: Thu, 12 Aug 2004 12:40:45 +0200 [thread overview]
Message-ID: <411B492D.4030206@free.fr> (raw)
In-Reply-To: <1092167817.5021.89.camel@dhcppc4>
Len Brown wrote:
> I'd be interested to know if the latest bk-acpi.patch is related to
> the issue...
I finaly found the time to test it : result is that 2.6.8-rc4 +
bk-acpi.patch boots fine. The thermal problem is also gone. SO something
must corrupt the data used by thermal.c in 2.6.8-rc4-mm1 :-( Did not
managed to wake up from S3 once. Will retry to be sure...
I think a minimal check on THRM value should be performed (-129°C) is
crazy as 150 probably...
--
__
/ ` Eric Valette
/-- __ o _. 6 rue Paul Le Flem
(___, / (_(_(__ 35740 Pace
Tel: +33 (0)2 99 85 26 76 Fax: +33 (0)2 99 85 26 76
E-mail: eric.valette@free.fr
next prev parent reply other threads:[~2004-08-12 10:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 9:08 2.6.8-rc4-mm1 : radeon_monitor.c broken vs CONFIG_FB_MODE_HELPERS + Hard freeze Eric Valette
2004-08-10 10:35 ` 2.6.8-rc4-mm1 : Hard freeze due to ACPI Eric Valette
2004-08-10 15:29 ` Len Brown
2004-08-10 15:44 ` Karol Kozimor
2004-08-11 12:01 ` Eric Valette
2004-08-10 18:51 ` Eric Valette
2004-08-10 19:53 ` Eric Valette
2004-08-10 19:56 ` Len Brown
2004-08-10 20:09 ` Eric Valette
2004-08-12 10:40 ` Eric Valette [this message]
2004-08-10 16:07 ` Andrew Morton
[not found] ` <4123AC79.5000709@free.fr>
2004-08-19 0:00 ` 2.6.8.1-mm1 and Asus L3C : problematic change found, can be reverted. Real fix still missing Karol Kozimor
2004-08-19 7:16 ` Eric Valette
2004-08-10 21:06 ` 2.6.8-rc4-mm1 : Hard freeze due to ACPI Karol Kozimor
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=411B492D.4030206@free.fr \
--to=eric.valette@free.fr \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sziwan@hell.org.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.