Re: Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) causing crashes

Re: Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) causing crashes

[Greg KH]

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?

> 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

Re: Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) causing crashes

[Christopher Waid]

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

Re: Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) causing crashes

[Gustavo Padovan]

* Christopher Waid <chris@thinkpenguin.com> [2013-03-20 14:13:14 -0400]:

> 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.

This text you are seeing in probably the crash dump of the failure, could you
try to take a picture of the screen so we can check if there is some useful
information there.

Also if the kernel doesn't panic instantly you could check if there is some
issue in the kernel log after pairing and save it somewhere so we can take a
look. Use the 3.8 kernel. 

	Gustavo

Re: Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) causing crashes

[Christopher Waid]

On 03/20/2013 05:45 PM, Christopher Waid wrote:
> On 03/20/2013 02:57 PM, Gustavo Padovan wrote:
>> * Christopher Waid <chris@thinkpenguin.com> [2013-03-20 14:13:14 -0400]:
>>
>>> 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.
>> This text you are seeing in probably the crash dump of the failure, 
>> could you
>> try to take a picture of the screen so we can check if there is some 
>> useful
>> information there.
>>
>> Also if the kernel doesn't panic instantly you could check if there 
>> is some
>> issue in the kernel log after pairing and save it somewhere so we can 
>> take a
>> look. Use the 3.8 kernel.
>>
>
> I'm attaching kern.log and a picture of the screen when it crashes / 
> dumps.
>

I was wondering if anybody had a chance to look into this. I don't seem 
to be on the mailing list even though I attempted to subscribe.

Re: Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) causing crashes

[Johan Hedberg]

Hi Christopher,

On Wed, Apr 03, 2013, Christopher Waid wrote:
> On 03/20/2013 05:45 PM, Christopher Waid wrote:
> >On 03/20/2013 02:57 PM, Gustavo Padovan wrote:
> >>* Christopher Waid <chris@thinkpenguin.com> [2013-03-20 14:13:14 -0400]:
> >>
> >>>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.
> >>This text you are seeing in probably the crash dump of the
> >>failure, could you
> >>try to take a picture of the screen so we can check if there is
> >>some useful
> >>information there.
> >>
> >>Also if the kernel doesn't panic instantly you could check if
> >>there is some
> >>issue in the kernel log after pairing and save it somewhere so
> >>we can take a
> >>look. Use the 3.8 kernel.
> >>
> >
> >I'm attaching kern.log and a picture of the screen when it crashes
> >/ dumps.
> >
> 
> I was wondering if anybody had a chance to look into this. I don't
> seem to be on the mailing list even though I attempted to subscribe.

I never saw the mail with the attachments from you. It was probably
blocked from the linux-bluetooth list (probably linux-usb too) due to a
too big size. You might want to put the picture on some website and just
send the link to it in your email.

Johan