From: Ahmed Ragab <elmasri.ahmed@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Kernel panic when dongle is disconnected during sco connection
Date: Sat, 30 Jan 2010 06:40:58 +0200 [thread overview]
Message-ID: <f97b2b971001292040hf7537d2yeef91fecf4189c50@mail.gmail.com> (raw)
In-Reply-To: <f97b2b971001292024u7ddf84b6gd063280efa6c1a4e@mail.gmail.com>
I Forgot to mention kernel version 2.6.26 however i have the latest
bluez package
Please confirm this bug, Linux kernel hangs when usb bluetooth dongle
is disconnected
During SCO connection stream (read, write).
I don't think it's a problem of the dongle however i am using dongle
trust bluetooth 2 USB Adapter 100m BT-2305p
which has a Cambridge silicon radio chip set 2.1
next prev parent reply other threads:[~2010-01-30 4:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f97b2b971001292013i3edd6bdajde0d9e39ed021fbd@mail.gmail.com>
2010-01-30 4:24 ` Kernel panic when dongle is disconnected during sco connection Ahmed Ragab
2010-01-30 4:40 ` Ahmed Ragab [this message]
2010-01-30 4:54 ` Liang Bao
2010-01-30 11:39 ` Ahmed Ragab
2010-02-02 13:35 ` Stefan Seyfried
2010-02-04 19:43 ` Ahmed Ragab
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=f97b2b971001292040hf7537d2yeef91fecf4189c50@mail.gmail.com \
--to=elmasri.ahmed@gmail.com \
--cc=linux-bluetooth@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