From: Eric Valette <eric.valette@free.fr>
To: "Brown, Len" <len.brown@intel.com>
Cc: eric.valette@free.fr, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Karol Kozimor <sziwan@hell.org.pl>
Subject: 2.6.8-rc4-mm1 : Hard freeze due to ACPI
Date: Tue, 10 Aug 2004 12:35:44 +0200 [thread overview]
Message-ID: <4118A500.1080306@free.fr> (raw)
In-Reply-To: <41189098.4000400@free.fr>
Eric Valette wrote:
> I tried 2.6.8-rc4-mm1 on my ASUS L3800C laptop (radeon 7500), defined
> CONFIG_FB_MODE_HELPERS and I have got a hard freeze when starting X and
> framebuffer console with a lot of yellow dot on the bottom screen.
> Suddently I hear the fan meaning the machine is dead
OK I've reverted the most suspect change
(remove-unconditional-pci-acpi-irq-routing.patch) and it did not fix the
problem. As Karol Kozimor suspected ACPI, I then tried with acpi=off and
then it boot but I will burn my CPU as fans are ACPI controlled...
So it is probably due to the bk-acpi.patch and more precisely the
difference between what was in 2.6.8-rc3-mm1 and 2.6.8-rc4-mm1.
Len, any proposal as candidate patches to revert?
-- eric
next prev parent reply other threads:[~2004-08-10 10:40 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 ` Eric Valette [this message]
2004-08-10 15:29 ` 2.6.8-rc4-mm1 : Hard freeze due to ACPI 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
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=4118A500.1080306@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.