From: Christopher Waid <chris@thinkpenguin.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) causing crashes
Date: Wed, 20 Mar 2013 14:13:14 -0400 [thread overview]
Message-ID: <5149FC3A.4070208@thinkpenguin.com> (raw)
In-Reply-To: <20130318191335.GA11242@kroah.com>
On 03/18/2013 03:13 PM, Greg KH wrote:
> On Mon, Mar 18, 2013 at 02:57:43PM -0400, Christopher Waid wrote:
>> Bus 001 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd
>> Bluetooth Dongle (HCI mode)
>>
>> Code for a CSR bluetooth chipset appears broken in recent kernel
>> releases. After a device is paired the kernel panics. This has been
>> tested with a dozen USB dongles / systems and is consistently a
>> problem. On the rare occasion it might not cause a kernel panic
>> although it will definitely still crash after a few minutes. This
>> does not happen with older kernel releases.
> What kernel version is crashing, and what is the exact text of the
> kernel panic?
It goes black and disappears off the screen with a lot of other text so
I'm unsure.
It has done it with various kernel versions including 3.2 and 3.8. I
tested it with the mainline kernel 3.8:
Linux penguin 3.8.0-030800-generic #201302181935 SMP Tue Feb 19 00:36:19
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>
>> Please let me know how I can help solve this issue. We have lots of
>> dongles and can try and get any information needed to fix it.
> You might want to ask the Linux bluetooth developers (now added to the
> cc of this response.)
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2013-03-20 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <514763A7.4020800@thinkpenguin.com>
2013-03-18 19:13 ` Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) causing crashes Greg KH
2013-03-20 18:13 ` Christopher Waid [this message]
2013-03-20 18:57 ` Gustavo Padovan
[not found] ` <514A2DDE.8060801@thinkpenguin.com>
2013-04-03 18:58 ` Christopher Waid
2013-04-04 8:34 ` Johan Hedberg
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=5149FC3A.4070208@thinkpenguin.com \
--to=chris@thinkpenguin.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-usb@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