Bug 60752 - USB 3.0 and drop endpoint problem
Summary: USB 3.0 and drop endpoint problem
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: XHCI bugs virtual user
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-16 06:27 UTC by Stanislav
Modified: 2014-07-04 12:43 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.2, 3.4, 3.9, 3.10
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Stanislav 2013-08-16 06:27:55 UTC
Have a little problem with usb 3.0 module(xhci_hcd).Using soundcard(any usb soundcard)and when an application using the audio device connected to usb 3.0, was crashed, or not properly shut down after that the is no way to use USB 3.0 port before reboot system. In dmesg there is several messages when I try to use usb ports after program crashing:

[ 2370.366770] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep f63ac100
[ 2370.366774] xhci_hcd 0000:00:14.0: Trying to add endpoint 0x2 without dropping it.
[ 2370.366778] usb 3-2: Not enough bandwidth for altsetting 1
[ 2370.366780] 2:1:1: usb_set_interface failed (-22)

Use different kernel version(3.2, 3.5, 3.9, 3.10, and 3.11 rc) and there is no changes. Search in Google gave no results.

For example to quickly repeat it, you can connect any usb soundcard to usb 3.0 ports, then run:

speaker-test -D hw:0,0(or another number of your device),

and then terminate it using Ctrl+C, after that there is no way to use this soundcard. And in dmesg there 4 lines after each attempt to gain access to an audio device.
Comment 1 Greg Kroah-Hartman 2013-08-16 12:43:30 UTC
On Fri, Aug 16, 2013 at 06:27:55AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=60752
> 
>             Bug ID: 60752
>            Summary: USB 3.0 and drop endpoint problem

Please send this to the linux-usb@vger.kernel.org mailing list.
Comment 2 Alan 2014-04-09 15:36:34 UTC
Please test 3.14
Comment 3 Stanislav 2014-07-04 12:43:23 UTC
Fixed on 3.14-1 Thanks.

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