Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) causing crashes
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 10 lines · Christopher Waid
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?
Quoted 2 lines
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
Quoted 4 lines · Greg KH
Quoted 3 lines · Christopher Waid
Bus 001 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Quoted 8 lines
Quoted 6 lines
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
Quoted 9 lines
Quoted 3 lines
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
Quoted 11 lines · Christopher Waid
Quoted 10 lines · Greg KH
Quoted 9 lines · Christopher Waid
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.
Quoted 5 lines
Quoted 2 lines
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
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 22 lines · Christopher Waid
Quoted 21 lines · Gustavo Padovan
Quoted 11 lines · Christopher Waid
Quoted 10 lines · Greg KH
Quoted 9 lines · Christopher Waid
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.
Quoted 4 lines
Quoted 2 lines
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.
Quoted 7 lines
Quoted 4 lines
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.
Hi Christopher,
Quoted 32 lines · Christopher Waid
Quoted 31 lines · Christopher Waid
Quoted 29 lines · Gustavo Padovan
Quoted 11 lines · Christopher Waid
Quoted 10 lines · Greg KH
Quoted 9 lines · Christopher Waid
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.
Quoted 4 lines
Quoted 2 lines
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.
Quoted 6 lines
Quoted 3 lines
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