Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325

[Rafael J. Wysocki]

On Monday, 16 of June 2008, Maciej W. Rozycki wrote:
> On Mon, 16 Jun 2008, Rafael J. Wysocki wrote:
> 
> > On Sunday, 15 of June 2008, Rafael J. Wysocki wrote:
> > > On Friday, 13 of June 2008, Stephen Rothwell wrote:
> > > > Hi all,
> > > > 
> > > > Changes since next-20080612:
> > > > 
> > > > New tree: kgdb
> > > > Dropped trees (temporary): ldp (it is unfetchable - probably something to
> > > > do with the new Staging tree)
> > > > Restored trees: block
> > > > 
> > > > The x86 tree gained a conflict with Linus' tree.
> > > > 
> > > > The acpi tree gained a conflict with the pci tree.
> > > > 
> > > > The mtd tree gained a trivial conflict with the avr32 tree.
> > > > 
> > > > The rr tree lost its conflict with the net-current tree.
> > > > 
> > > > The block tree gained several conflict with various other trees.  It also
> > > > required a build fix patch.
> > > > 
> > > > The firmware tree lost its build fix patch.
> > > > 
> > > > The patches for known build problems are no longer needed.
> > > 
> > > 20080613 doesn't boot on my HP nx6325.  Bisecting ...
> > 
> > Okay, with the following commit reverted, the kernel boots normally on this
> > box:
> > 
> > commit 7e3530cd98a0c6ab38f5898e855a5beffab26561
> > Author: Maciej W. Rozycki <macro@xxxxxxxxxxxxxx>
> > Date:   Tue May 27 21:19:51 2008 +0100
> > 
> >     x86: I/O APIC: timer through 8259A second-chance
> > 
> >     Signed-off-by: Maciej W. Rozycki <macro@xxxxxxxxxxxxxx>
> >     Signed-off-by: Ingo Molnar <mingo@xxxxxxx>
> 
>  Can I have .config used and a full bootstrap log from that system with
> the patch still applied?

That may be difficult, because with the patch applied the box either doesn't
boot at all, or works unreliably when booted (depending on the set of patches
applied on top of it).

I'll try to get one later today.

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