Most recent kernel where this bug did not occur: unknown Distribution: Kubuntu 6.06 (Dapper), SUSE 10.0 (liveCD), SUSE 10.1 (liveCD) Hardware Environment: Notebook nx7000, Thinkpad R40 Software Environment: Standard installation Problem Description: As soon as a Vivanco bluetooth usb dongle is plugged in, the syslog is flooded with "hci_scodata_packet: hci0 SCO packet for unknown connection handle 0" messages. The flood rate is ~5000 entries/second. This Bug was originally filed in https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/39414 but as it also occurs with the SUSE liveCDs, I think this is an upstream bug.
On Tue, 18 Jul 2006 18:32:25 +0200 Marcel Holtmann <marcel@holtmann.org> wrote: > Hi Andrew, > > > Date: Fri, 14 Jul 2006 07:49:19 -0700 > > From: bugme-daemon@bugzilla.kernel.org > > To: bugme-new@lists.osdl.org > > Subject: [Bugme-new] [Bug 6833] New: Syslog flooded with "hci_scodata_packet: hci0 SCO packet for unknown connection handle 0" messages > > > > > > http://bugzilla.kernel.org/show_bug.cgi?id=6833 > > > > Summary: Syslog flooded with "hci_scodata_packet: hci0 SCO packet > > for unknown connection handle 0" messages > > Kernel Version: 2.6.15-26-686 > > Status: NEW > > Severity: high > > Owner: greg@kroah.com > > Submitter: uwe.menges@web.de > > > > > > Most recent kernel where this bug did not occur: unknown > > Distribution: Kubuntu 6.06 (Dapper), SUSE 10.0 (liveCD), SUSE 10.1 (liveCD) > > Hardware Environment: Notebook nx7000, Thinkpad R40 > > Software Environment: Standard installation > > > > Problem Description: > > > > As soon as a Vivanco bluetooth usb dongle is plugged in, the syslog is flooded > > with "hci_scodata_packet: hci0 SCO packet for unknown connection handle 0" > > messages. The flood rate is ~5000 entries/second. > > > > This Bug was originally filed in > > https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/39414 > > but as it also occurs with the SUSE liveCDs, I think this is an upstream bug. > > this is broken hardware from RTX Telecom. I have a fix for it. You need > to activate the quirk to disable the ISOC transfers. > Let's cc Uwe and bugzilla then. Is there any patch which Uwe can test? I assume "the quirk" refers to a quirk which is implemented in that patch?
Hi Andrew, > > > Date: Fri, 14 Jul 2006 07:49:19 -0700 > > > From: bugme-daemon@bugzilla.kernel.org > > > To: bugme-new@lists.osdl.org > > > Subject: [Bugme-new] [Bug 6833] New: Syslog flooded with "hci_scodata_packet: hci0 SCO packet for unknown connection handle 0" messages > > > > > > > > > http://bugzilla.kernel.org/show_bug.cgi?id=6833 > > > > > > Summary: Syslog flooded with "hci_scodata_packet: hci0 SCO packet > > > for unknown connection handle 0" messages > > > Kernel Version: 2.6.15-26-686 > > > Status: NEW > > > Severity: high > > > Owner: greg@kroah.com > > > Submitter: uwe.menges@web.de > > > > > > > > > Most recent kernel where this bug did not occur: unknown > > > Distribution: Kubuntu 6.06 (Dapper), SUSE 10.0 (liveCD), SUSE 10.1 (liveCD) > > > Hardware Environment: Notebook nx7000, Thinkpad R40 > > > Software Environment: Standard installation > > > > > > Problem Description: > > > > > > As soon as a Vivanco bluetooth usb dongle is plugged in, the syslog is flooded > > > with "hci_scodata_packet: hci0 SCO packet for unknown connection handle 0" > > > messages. The flood rate is ~5000 entries/second. > > > > > > This Bug was originally filed in > > > https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/39414 > > > but as it also occurs with the SUSE liveCDs, I think this is an upstream bug. > > > > this is broken hardware from RTX Telecom. I have a fix for it. You need > > to activate the quirk to disable the ISOC transfers. > > > > Let's cc Uwe and bugzilla then. > > Is there any patch which Uwe can test? > > I assume "the quirk" refers to a quirk which is implemented in that patch? the patch looks like this: diff --git a/drivers/bluetooth/hci_usb.c b/drivers/bluetooth/hci_usb.c index d73eb10..963c014 100644 --- a/drivers/bluetooth/hci_usb.c +++ b/drivers/bluetooth/hci_usb.c @@ -124,8 +124,9 @@ static struct usb_device_id blacklist_id /* ISSC Bluetooth Adapter v3.1 */ { USB_DEVICE(0x1131, 0x1001), .driver_info = HCI_RESET }, - /* RTX Telecom based adapter with buggy SCO support */ + /* RTX Telecom based adapters with buggy SCO support */ { USB_DEVICE(0x0400, 0x0807), .driver_info = HCI_BROKEN_ISOC }, + { USB_DEVICE(0x0400, 0x080a), .driver_info = HCI_BROKEN_ISOC }, /* Belkin F8T012 and F8T013 devices */ { USB_DEVICE(0x050d, 0x0012), .driver_info = HCI_WRONG_SCO_MTU }, The hardware from RTX Telecom is simply buggy. Even the new dongle has this problem. Regards Marcel
Great, am now closing, thanks.
I observed the same issue with device 0a12:0001 (Cambridge Silicon Radio, Ltd Bluetooth Dongle). It is interesting, that this does not happen when the device is plugged into an external USB 2.0 hub (Kensington PocketHub 7 Port), but it does appear if the dongle is plugged directly to a USB contoller, either onboard (nforce4 4x) or PCI addon card (NEC chipset). Kernel version is 2.6.24-23 (Kubuntu)
@Pavel Chromy I can confirm it. I've observed the same behaviour with my Bluetooth USB dongle; this is the same model (and the same device address, 0a12:0001). Should this bug be closed? Is it another issue?