Bug 452177 - Syslog flooded with "hci_scodata_packet: hci0 SCO packet for unknown connection handle 92" message
Syslog flooded with "hci_scodata_packet: hci0 SCO packet for unknown connecti...
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
8
All Linux
low Severity low
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-19 16:56 EDT by John Westlund
Modified: 2008-06-27 13:34 EDT (History)
0 users

See Also:
Fixed In Version: 2.6.25.6-27.fc8
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-06-27 13:34:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Linux Kernel 9027 None None None Never

  None (edit)
Description John Westlund 2008-06-19 16:56:50 EDT
Description of problem:
See kernel bug 9027:
http://bugzilla.kernel.org/show_bug.cgi?id=9027

I have a usb bluetooth dongle. when plugged, syslog is flooded with 

   hci_scodata_packet: hci0 SCO packet for unknown connection handle 92

Is this the same as Bug 6833 ?

Bus 002 Device 002: ID 0e5e:6622
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass          224 Wireless
  bDeviceSubClass         1 Radio Frequency
  bDeviceProtocol         1 Bluetooth
  bMaxPacketSize0        16
  idVendor           0x0e5e
  idProduct          0x6622
  bcdDevice            1.34
  iManufacturer           0
  iProduct                0
  iSerial                 0
  bNumConfigurations      1

Version-Release number of selected component (if applicable):
Appears to still be an issue in 2.6.24.7-92.fc8

How reproducible:
Plug in bluetooth device with broken SCO support.
Comment 1 Chuck Ebbert 2008-06-27 13:34:19 EDT
Already in 2.6.25

Note You need to log in before you can comment on or make changes to this bug.