Bug 11733 - Possible btusb refcount leak
Summary: Possible btusb refcount leak
Status: CLOSED OBSOLETE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_bluetooth@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-10 12:09 UTC by Andrey Rahmatullin
Modified: 2012-05-22 14:51 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.27
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Andrey Rahmatullin 2008-10-10 12:09:04 UTC 
I insert my dongle. 

btusb                  10200  0       
bluetooth              44964  1 btusb 

Then I start hcid from bluez-utils 3.36. 

bridge                 40340  0       
stp                     2244  1 bridge
llc                     5840  2 bridge,stp
bnep                   11328  2           
rfcomm                 29076  4           
l2cap                  17028  16 bnep,rfcomm
btusb                  10200  2             
bluetooth              44964  8 bnep,rfcomm,l2cap,btusb

I stop it and remove all modules.

btusb                  10200  1
bluetooth              44964  1 btusb

Now I remove the dongle.

usb 4-2: USB disconnect, address 3
btusb_intr_complete: hci0 urb da1d7480 failed to resubmit (19)
btusb_send_frame: hci0 urb cf87a700 submission failed

btusb                  10200  0
bluetooth              44964  1 btusb
Comment 1 Michael Long 2008-12-27 04:56:12 UTC 
I'm having a similar issue after waking up from s2ram and only if "USB selective suspend/resume and wakeup" (CONFIG_USB_SUSPEND) is enabled. As far as I remember correctly this happend beginning 2.6.27:

[91031.250453] btusb_intr_complete: hci0 urb f683b200 failed to resubmit (19)
[91031.250466] btusb_bulk_complete: hci0 urb f6319780 failed to resubmit (19)
[91031.251447] btusb_bulk_complete: hci0 urb f6319300 failed to resubmit (19)
[91031.254432] btusb_send_frame: hci0 urb e529ad80 submission failed
[91031.254505] __set_isoc_interface: hci0 setting interface failed (19)

Now after reinserting it seems that the bt-subsystem is even completly dead. (2.6.28). In 2.6.27.* reinserting was often sufficient to get bt work again.
Comment 2 Alan 2012-05-22 14:51:02 UTC 
Is this still present in recent kernels - closing as obsolete, re-open if it is.
Note You need to log in before you can comment on or make changes to this bug.