From: David Brownell <david-b@pacbell.net>
To: Franco Saliola <saliola@polygon.math.cornell.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel BUG in usb-ohci.c:902!
Date: Sun, 29 Sep 2002 13:48:38 -0700 [thread overview]
Message-ID: <3D976726.4070909@pacbell.net> (raw)
Hmm, if I look at that line in the 2.4.20-pre7 kernel, I see:
/* likely some interface's driver has a refcount bug */
err ("bus %s devnum %d deletion in interrupt",
ohci->ohci_dev->slot_name, usb_dev->devnum);
BUG ();
That BUG() has been an "oops now predictably, or oops later randomly"
situation, and EVERY (!!!) time it's been an issue, the problem has
been traced to exactly what that comment says: some interface's
driver has bogus disconnect() processing, and is not cleaning up. (*)
It's likely the problem is in the driver for one of your USB devices.
Given what I saw, it sure looks like "prism2_usb" is the problem.
And from what I saw last time I looked at that driver, I can VERY
easily believe that ... in fact I think I've seen similar reports
show up before, that's why I took a look at it. The prism2_usb folk
need to make sure their disconnect() routine (a) prevents all further
driver requests to that device, (b) unlinks all urbs it submitted,
and (c) waits for them to finish unlinking.
- Dave
(*) Maybe a better response would be to just leak memory, but
that's how the ohci driver evolved ... it took a long time
to establish that the oopsing was really caused by bogus
disconnect() processing in the layered usb device handling.
next reply other threads:[~2002-09-29 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 20:48 David Brownell [this message]
2002-09-29 20:57 ` PROBLEM: kernel BUG in usb-ohci.c:902! Stephen Marz
2002-09-29 21:45 ` David Brownell
2002-09-29 21:57 ` Stephen Marz
-- strict thread matches above, loose matches on Subject: below --
2002-09-29 20:30 David Brownell
2002-09-29 19:29 Franco Saliola
2002-09-29 19:45 ` Stephen Marz
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=3D976726.4070909@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=saliola@polygon.math.cornell.edu \
/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