From: Greg KH <greg@kroah.com>
To: Martin Devera <devik@cdi.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG and OOPS in USB-OHCI again
Date: Wed, 15 May 2002 08:35:18 -0700 [thread overview]
Message-ID: <20020515153518.GC24420@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0205151742210.12674-100000@luxik.cdi.cz>
On Wed, May 15, 2002 at 05:52:29PM +0200, Martin Devera wrote:
> Hi Greg,
>
> I read post of some people having problems with OHCI. Well
> I'm having them too.
> We use pwc.o module (without closed-source compression support)
> on two machines with OHCI add-on card.
> It fails regulary (twice a day) with:
> BUG at usb-ohci.h:464 and it panics. With onboard UHCI it works
> well !! When I sumarized other posts on the list we can see that
> there was the same problems with OHCI+modem so that the bug
> should not be related to camera.
> Kernel is vanilla 2.4.18.
>
> Any tips ?
I don't know the specifics of that driver, sorry, but I'd recommend
asking this on the linux-usb-devel mailing list, as the ohci driver
authors are there. I don't think they read lkml much.
thanks,
greg k-h
prev parent reply other threads:[~2002-05-15 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 15:52 BUG and OOPS in USB-OHCI again Martin Devera
2002-05-15 15:35 ` Greg KH [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=20020515153518.GC24420@kroah.com \
--to=greg@kroah.com \
--cc=devik@cdi.cz \
--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