From: David Brownell <david-b@pacbell.net>
To: Stephen Marz <smarz@host187.south.iit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel BUG in usb-ohci.c:902!
Date: Sun, 29 Sep 2002 14:45:54 -0700 [thread overview]
Message-ID: <3D977492.4070604@pacbell.net> (raw)
In-Reply-To: Pine.LNX.4.44.0209291549390.1911-100000@host187.south.iit.edu
> code. Here is my call trace:
>
> uhci-irq [uchi-hcd]
> usb_hcd_irq_Rfba60562 [usbcore]
> handle_IRQ_event
> do_IRQ
> ...
>
> I am apparently hitting a different bug, but it inevitably comes from
> the uhci-hcd driver (according to the panic).
As I said: you're not seeing "this problem". And it's not a BUG().
So now we agree ... ;-)
You might try sending the full oops report to the maintainer
of that driver, or at least to the linux-usb-devel list.
(The 2.5.39 code gives more info than you snipped...) So far
as I know, this problem has not been reported there.
- Dave
> Regards,
>
> Stephen Marz
>
>
>>>I have noticed this problem in 2.5.39 except it occurs with the module
>>>uhci-hcd.
>>
>
>>No you haven't. It doesn't have a file of that name, so you
>>didn't see such a BUG(). And I don't know about you, but my
>>copy of 2.5.39 has no BUG() anywhere in the ohci-hcd driver,
>>so it'd be hard seeing _any_ BUG() coming from there.
>
>
>>You might be hitting a different BUG(), but in that case you
>>would need to get your bug reports straight.
>
>
>>- Dave
>
>
>
>
>
>
>
next prev parent reply other threads:[~2002-09-29 21:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 20:48 PROBLEM: kernel BUG in usb-ohci.c:902! David Brownell
2002-09-29 20:57 ` Stephen Marz
2002-09-29 21:45 ` David Brownell [this message]
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=3D977492.4070604@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=smarz@host187.south.iit.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