* Rafael J. Wysocki <rjw@sisk.pl> wrote:

quoted text
> Hi Ingo,
> 
> On Friday, 11 of July 2008, Rafael J. Wysocki wrote:
> > On Friday, 11 of July 2008, Ingo Molnar wrote:
> > > 
> > > * Rafael J. Wysocki <rjw@sisk.pl> wrote:
> [--snip--]
> > 
> > Well, it turns out that linux-next from today doesn't boot on my box too
> > (64-bit) and I don't see anything obviously suspicious.  Bisection time.
> 
> I have identified the source of the breakage on my box, but I don't 
> really think it's the same problem that Edwin is observing.
> 
> Namely, it turns out that some code in arch/x86/kernel/acpi/boot.c, as 
> in today's linux-next, doesn't really make sense, because we have two 
> conflicting DMA-based quirks in there for the same set of boxes (HP 
> nx6325 and nx6125) and one of them actually breaks my box.
> 
> I have reported that already, but it probably got lost somewhere.
> 
> Below is a patch that fixes things for me, on top of today's 
> linux-next. Please apply.

thanks Rafael, i have applied your fix to tip/x86/core and to 
auto-x86-next as well.

what happened is a case of too many fixes for the same problem :-/

	Ingo
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/