From: David Brownell <david-b@pacbell.net>
To: j.derudder@btinternet.com
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Kernel panic from usb-ohci
Date: Sun, 30 Dec 2001 19:21:04 -0800 [thread overview]
Message-ID: <04b201c191aa$2e84af80$6800000a@brownell.org> (raw)
The problem is the driver you're using on top of usb-ohci,
seemingly whatever talks to that ADSL modem. It might
be fixed in a more recent kernel, I wouldn't know.
> usb-ohci.c : bus 00:0c.0 devnum 2 deletion in interrupt
> Kernel BUG at usb_ohci.c: 886!
As it says in the comment on line 884, the problem is likely
(all but certainly) that "some interface's driver has a refcount
bug". Specifically, the OHCI driver is being told the device
has gone away. Because it's in_interrupt(), that's a lie ...
only khubd is allowed to declare that, and of course that can't
ever say that in_interrupt().
- Dave
next reply other threads:[~2001-12-31 3:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 3:21 David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-30 23:56 Kernel panic from usb-ohci Jean-Francois De Rudder
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='04b201c191aa$2e84af80$6800000a@brownell.org' \
--to=david-b@pacbell.net \
--cc=j.derudder@btinternet.com \
--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