From: Lee Revell <rlrevell@joe-job.com>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
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: Wed, 12 Oct 2005 14:17:29 -0400 [thread overview]
Message-ID: <1129141049.10599.24.camel@mindpipe> (raw)
In-Reply-To: <1128948118.23434.13.camel@localhost>
On Mon, 2005-10-10 at 14:41 +0200, Soeren Sonnenburg wrote:
> On Sat, 2005-10-08 at 07:25 +1000, Benjamin Herrenschmidt wrote:
> > On Thu, 2005-10-06 at 21:19 +0200, Soeren Sonnenburg wrote:
> > > On Mon, 03 Oct 2005 07:12:24 +0000, Soeren Sonnenburg wrote:
> > >
> > > > Hi all,
> > > >
> > > > when a dvd featuring some iso content is in the dvd-drive and the
> > > > machine is put to sleep mode, it will give the following oops on resume.
> > > > It is working without problems if no media is in the drive.
> > > > Voluntary preemption is ON.
> > > > Find below the dmesg output when a dvd is in the drive.
> > >
> > > now it is:
> [incomplet oops]
>
> ok, here is the complete one:
>
> BUG: soft lockup detected on CPU#0!
This isn't an Oops. What the soft lockup detector is telling you is
that one CPU detected that another CPU was running something in the
kernel for a LONG time without rescheduling which is considered a bug.
The fix is to make ide_wait_not_busy() preemptible.
Lee
prev parent reply other threads:[~2005-10-12 18:20 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
2005-10-11 10:50 ` Soeren Sonnenburg
2005-10-12 18:17 ` Lee Revell [this message]
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=1129141049.10599.24.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.