On Tue, 2005-10-11 at 12:33 +0200, Soeren Sonnenburg wrote:
> On Tue, 2005-10-11 at 08:06 +1000, Benjamin Herrenschmidt wrote:
> > > ok, here is the complete one:
> > >
> > > BUG: soft lockup detected on CPU#0!
> >
> > Gack, the soft lockup thing. Can you disable that ? If you do so, does
> > it crashes instead of oopsing or just "pauses" for a little while on
> > wakeup ? The problem is that ide_do_request does a synchronous wait for
> > the drive to get out of busy state which can take a while with some
> > optical drives on wakeup. It might be possible to allow scheduling
> > there, I have to look at it. In the meantime, disable the lockup
> > detector (CONFIG_DETECT_SOFTLOCKUP) and tell me if that's enough.
>
> Hmmhh, I already compiled 2.6.14-rc4 but did not disable
> soft-lockup-ing, should I still do it - the oops looks better as it is
> not followed by a ATAPI reset anymore:
It's still pretty annoying. I'll see what I can do but it won't be for
2.6.14 timeframe, so in the meantime, just ignore it or remove soft
lockup detection.
Ben.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
