From: "Nicholas A. Preyss" <nalp@gmx.net>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Oops with 2.6.5-mh3
Date: Sat, 17 Apr 2004 11:24:04 +0200 [thread overview]
Message-ID: <20040417092404.GA1880@gmx.net> (raw)
In-Reply-To: <1082161132.4489.33.camel@pegasus>
On 0, Marcel Holtmann <marcel@holtmann.org> wrote:
> > I get a kernel Oops with 2.6.5-mh3 (with and without preempt) and an
> > Acer BT-700 USB dongle on a Vaio Notebook, not when unplugging it, but
> > when plugging it back in.
>
> check the latest 2.6.6-rc or Bitkeeper snapshots, because there are many
> USB patches that are not merged into 2.6.5. If it still fails send a
> report the USB mailing list, because I don't think that this is our
> fault.
The problem was already submitted to lkml (i found at least 3reports)
and one time declared impossible by Andrew Morton. I can't reproduce
this error with 2.6.6-rc1 because, the usb dongle ain't even working
at all. It seems USB is a bit messed up in that release.
In 2.6.5 there is an easy workaround. If you don't need the hci_usb
SCO (CONFIG_BT_HCIUSB_SCO) support, disable it in your kernelconfig.
nicholas
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-04-17 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 20:20 [Bluez-devel] Oops with 2.6.5-mh3 Matthias Thomae
2004-04-17 0:18 ` Marcel Holtmann
2004-04-17 9:24 ` Nicholas A. Preyss [this message]
2004-04-17 9:01 ` Marcel Holtmann
2004-04-17 9:09 ` Simone Gotti
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=20040417092404.GA1880@gmx.net \
--to=nalp@gmx.net \
--cc=bluez-devel@lists.sourceforge.net \
/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