From: Robert Love <rml@tech9.net>
To: Johannes Erdfelt <johannes@erdfelt.com>
Cc: Duncan Sands <duncan.sands@math.u-psud.fr>,
Kernel List <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: 2.5.8-pre3: kernel BUG at usb.c:849! (preempt_count 1)
Date: 10 Apr 2002 13:00:07 -0400 [thread overview]
Message-ID: <1018458007.6524.2.camel@phantasy> (raw)
In-Reply-To: <20020410114144.N8314@sventech.com>
On Wed, 2002-04-10 at 11:41, Johannes Erdfelt wrote:
> > <3>error: rmmod[1787] exited with preempt_count 1
>
> I don't like the looks of that.
That error means a task exited with a nonzero preempt_count, in this
case 1. This means a lock was held after exit (or, a lock was never
unlocked - e.g. it was dynamic and just deleted, but the lock counting
code can't know that).
In this case it may just be because the task oopsed while holding the
lock and then exited. This may point to the lock being the BKL since it
would be trivial to have it reschedule and then die while holding it.
While the main point of that error is to point out code that does rude
things with preemption, in this case we probably just have another
problem and this is another sign of it.
Robert Love
next prev parent reply other threads:[~2002-04-10 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 13:11 2.5.8-pre3: kernel BUG at usb.c:849! (preempt_count 1) Duncan Sands
2002-04-10 15:41 ` Johannes Erdfelt
2002-04-10 16:40 ` [linux-usb-devel] " David Brownell
2002-04-10 16:51 ` Duncan Sands
2002-04-10 17:23 ` David Brownell
2002-04-10 22:20 ` Duncan Sands
2002-04-10 17:00 ` Robert Love [this message]
2002-04-10 17:11 ` Duncan Sands
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 16:47 Duncan Sands
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=1018458007.6524.2.camel@phantasy \
--to=rml@tech9.net \
--cc=duncan.sands@math.u-psud.fr \
--cc=johannes@erdfelt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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