From: Marcel Holtmann <marcel@holtmann.org>
To: "Nicholas A. Preyss" <nalp@gmx.net>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] kernel oops when usb dongle plugged in with module loaded
Date: Sat, 17 Apr 2004 02:20:30 +0200 [thread overview]
Message-ID: <1082161230.4489.36.camel@pegasus> (raw)
In-Reply-To: <20040415232702.GA24097@gmx.net>
Hi Nicholas,
> I face the same problem as Matthias Thomae with an Acer BT600 and
> utils/libs 2.6. I investigated the Oops after reinserting usb dongle
> problem a bit. And noticed that it Oops only, when hci_usb module had
> been loaded before the dongle was plugged in. So unloading the module
> before plugging in the device and everthing works fine (of course only
> when the module was loaded thereafter automaticalls or manually).
> If you pull out the dongle and then unload the module, you can reinsert
> the BT dongle. If you manually modprobe the module before plugging in
> the device, it Oops too.
>
> I tested 2.6.4 which doesn't seem to be affected, but 2.6.5 and
> 2.6.5-mh3 show this behaviour.
check the latest 2.6.6-rc or better Bitkeeper snapshot and tell the USB
guys if it still exists.
Regards
Marcel
-------------------------------------------------------
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
prev parent reply other threads:[~2004-04-17 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 23:27 [Bluez-devel] kernel oops when usb dongle plugged in with module loaded Nicholas A. Preyss
2004-04-17 0:20 ` Marcel Holtmann [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=1082161230.4489.36.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=nalp@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.