All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Eric Valette <eric.valette@free.fr>
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: 10 Aug 2004 15:56:57 -0400	[thread overview]
Message-ID: <1092167817.5021.89.camel@dhcppc4> (raw)
In-Reply-To: <411927C9.9040300@free.fr>

On Tue, 2004-08-10 at 15:53, Eric Valette wrote:
> Eric Valette wrote:
> 
> > Will try andrew suggestion for the video-mode-handling-* patch
> 
> Tried without success. Will wait until other find other symptoms for
> the 
> same problem.
> 

I suppose with the patches available  broken out, you can apply them
in groups and divide & conquor.

I'd be interested to know if the latest bk-acpi.patch is related to
the issue...

thanks,
-Len



  reply	other threads:[~2004-08-10 19: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
2004-08-10 19:53       ` Eric Valette
2004-08-10 19:56         ` Len Brown [this message]
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=1092167817.5021.89.camel@dhcppc4 \
    --to=len.brown@intel.com \
    --cc=akpm@osdl.org \
    --cc=eric.valette@free.fr \
    --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.