mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: erik@debian.franken.de (Erik Tews)
To: Alex Riesen <fork0@users.sourceforge.net>,
	Alan Stern <stern@rowland.harvard.edu>,
	USB development list <linux-usb-devel@lists.sourceforge.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] Re: Oops with bluetooth dongle
Date: Tue, 6 Apr 2004 21:27:08 +0200	[thread overview]
Message-ID: <20040406192708.GA5327@debian.franken.de> (raw)
In-Reply-To: <20040406184736.GA1413@steel.home>

On Tue, Apr 06, 2004 at 08:47:36PM +0200, Alex Riesen wrote:
> Alan Stern, Tue, Apr 06, 2004 18:49:51 +0200:
> > I've seen a couple of different problems coming up with this bluetooth 
> > stuff.  One of them may be fixed by a recent patch, as David Brownell 
> > mentioned.  Below is the relevant part excerpted from that patch; maybe it 
> > will help some of you.
> > 
> > --- 1.47/drivers/usb/core/message.c	Tue Mar 30 01:04:29 2004
> > +++ edited/drivers/usb/core/message.c	Tue Mar 30 17:34:54 2004
> 
> no change for me. Still oopses.

I have been running 2.6.5 with the bk-usb patch broken out of mm1. I
still got the problem.

If I rmmod uhci-hcd, the kernel oopses too.

Still any ideas?

  reply	other threads:[~2004-04-06 19:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44L0.0404061036480.1042-100000@ida.rowland.org>
     [not found] ` <Pine.LNX.4.44L0.0404061247490.1042-100000@ida.rowland.org>
2004-04-06 18:47   ` Alex Riesen
2004-04-06 19:27     ` Erik Tews [this message]
2004-04-06 20:59       ` [linux-usb-devel] " Alan Stern
2004-04-06 22:24         ` Erik Tews

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=20040406192708.GA5327@debian.franken.de \
    --to=erik@debian.franken.de \
    --cc=fork0@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.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

all inboxes | Powered by JetHome®