From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide_wait_not_busy oops still with 2.6.14-rc3 (Re: 1GHz pbook 15", linux 2.6.14-rc2 oops on resume)
Date: Tue, 11 Oct 2005 20:36:26 +1000 [thread overview]
Message-ID: <1129026986.17365.206.camel@gaston> (raw)
In-Reply-To: <1129026807.21318.15.camel@localhost>
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.
next prev parent reply other threads:[~2005-10-11 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 7:12 1GHz pbook 15", linux 2.6.14-rc2 oops on resume Soeren Sonnenburg
2005-10-06 19:19 ` ide_wait_not_busy oops still with 2.6.14-rc3 (Re: 1GHz pbook 15", linux 2.6.14-rc2 oops on resume) Soeren Sonnenburg
2005-10-07 21:25 ` Benjamin Herrenschmidt
2005-10-10 12:41 ` Soeren Sonnenburg
2005-10-10 22:06 ` Benjamin Herrenschmidt
2005-10-11 10:33 ` Soeren Sonnenburg
2005-10-11 10:36 ` Benjamin Herrenschmidt [this message]
2005-10-11 10:50 ` Soeren Sonnenburg
2005-10-12 18:17 ` Lee Revell
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=1129026986.17365.206.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox