Bug 11733
Summary: | Possible btusb refcount leak | ||
---|---|---|---|
Product: | Drivers | Reporter: | Andrey Rahmatullin (wrar) |
Component: | Bluetooth | Assignee: | drivers_bluetooth (drivers_bluetooth) |
Status: | CLOSED OBSOLETE | ||
Severity: | normal | CC: | alan, chris.l, harn-solo |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.27 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Andrey Rahmatullin
2008-10-10 12:09:04 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. Is this still present in recent kernels - closing as obsolete, re-open if it is. |