public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 10 Aug 2004 20:51:21 +0200	[thread overview]
Message-ID: <41191929.4090305@free.fr> (raw)
In-Reply-To: <1092151779.5028.40.camel@dhcppc4>

Len Brown wrote:

> asus_acpi.c from Karol
> http://linux-acpi.bkbits.net:8080/linux-acpi-test-2.6.7/gnupatch@4117a219yRjkVomavWT8WoMdRg7KHA
> 
> pci_link.c - resume fix from Nathan
> http://linux-acpi.bkbits.net:8080/linux-acpi-test-2.6.7/gnupatch@41114fe37ez5dnzmR96KT2DHr4-elA
> 
> I'll poke around the mm patch to see if anything else looks suspicious.

Thanks for answering Len. Due to the usual delay, I had the time to 
revert the paches myself before your answer and found that as expected 
the problem still persist (I browsed the patch quickly directly from 
bitkkeper acpi tree and found a priori nothing suspicious).

Curious that :
	- acpi=off boot option makes the problem vanish,
	- it looks like a deadlock due to an asynchronous event as it does not 
always occur at the same time after the boot finishes,
	- even without typing anything on the keyboard in single mode it deadlocks,
	- I never saw the fan suddenly wake-up (except of couse when 
temeratuire is too high) without a hard immediate reboot on this laptop. 
Here, during video (framebuffer) initialization, while the screen it 
still black they start spinning,

Will try andrew suggestion for the video-mode-handling-* patch

-- eric



  parent reply	other threads:[~2004-08-10 18:57 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 [this message]
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=41191929.4090305@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox