Re: 2.6.21-rc6-mm1 USB related boot hang - bisection result

[Andrew Morton]

On Fri, 27 Apr 2007 23:04:58 +0200
Helge Hafting <helgehaf@xxxxxxxxxxxxx> wrote:

> On Fri, Apr 27, 2007 at 12:39:19AM +0200, Jiri Kosina wrote:
> > On Fri, 27 Apr 2007, Helge Hafting wrote:
> > 
> > > 2.6.21-rc6 boots up fine.  Both rc6 and rc7 has a different problem - 
> > > the machine tends to hang after some minutes work in X.  That hang is 
> > > unusual in that moving the mouse still move the X cursor, but everything 
> > > else stops and sysrq fails me. But that is another story.
> > [...]
> > > The (first) "hanging" patch in 2.6.21-rc6-mm1 is: git-acpi.patch
> > 
> > Hi Helge,
> > 
> > thanks for the effort. If you take stock rc6-mm1 and revert just 
> > git-acpi.patch, doesn the machine behave correctly?
> 
> Just compiled & booted such a kernel - it came up fine!
> So it looks like USB is fine then, and the problem is in
> that ACPI patch.
> 

OK, thanks.  Len&co: we've established that 2.6.21-rc6-mm1's git-acpi.patch
causes this:

> 2.6.21-rc6 boots up fine.  Both rc6 and rc7 has a different problem - the
> machine tends to hang after some minutes work in X.  That hang is
> unusual in that moving the mouse still move the X cursor, but
> everything else stops and sysrq fails me. But that is another story.
> 
> rc6 boots, rc6-mm1 hangs at the "usbcore registered hiddev" message.
> Bisection:
> 1, 2, 3: the three first hangs at "usbcore registered hiddev"
> 4, 5, 6: the next three hangs at a message about ACPI  PCI[A]->IRQ17
> I decided to keep bisecting these hangers as "bad", I don't really know
> if this could be the same thing or completely different issues.  If they are
> different, then one problem will mask the other anyway, so
> calling every hanging kernel "bad" will at least find the first broken 
> patch.
> 7: boots up ok!
> 8,9,10: hangs at the aboce mentioned ACPI message
> The (first) "hanging" patch in 2.6.21-rc6-mm1 is: git-acpi.patch
> 
> 
-
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/