Hi Sarah, On Mon, 2011-08-08 at 14:40 -0700, Sarah Sharp wrote: > On Mon, Aug 08, 2011 at 03:08:09PM -0400, jason@xxxxxxxxxxxxxx wrote: > > hey folks.. im having problems with a plantronics usb headset using fedora 15 on a thinkpad W510 laptop.. this same headset works fine on > > an older desktop running the same os. on the laptop, I see the following when I plug it in > > > > [ 2046.523638] usb 3-3: Not enough bandwidth for altsetting 1 > > [ 2046.523643] ALSA sound/usb/pcm.c:223: 5:2:1: usb_set_interface failed > > [ 2046.524243] xhci_hcd 0000:0f:00.0: ERROR: unexpected command completion code 0x11. > > [ 2046.524255] usb 3-3: Not enough bandwidth for altsetting 1 > > [ 2046.524260] ALSA sound/usb/pcm.c:223: 5:2:1: usb_set_interface failed > > [ 2046.524993] xhci_hcd 0000:0f:00.0: ERROR: unexpected command completion code 0x11. > > [ 2046.525004] usb 3-3: Not enough bandwidth for altsetting 1 > > [ 2046.525009] ALSA sound/usb/pcm.c:223: 5:2:1: usb_set_interface failed > > Which kernel are you running? ISTR a similar issue with the same > unexpected command completion code that was fixed with commit > b513d44751bfb609a3c20463f764c8ce822d63e9 (in the 3.0 kernel). That > should fix was released in the 2.6.39.1 stable kernel. > I just note something when checking the description of commit b513d44751bfb609a3c20463f764c8ce822d63e9: "...the host controller would return a very odd error message(0x11 means "Slot Not Enabled", which isn't true because the slot was enabled). Probably the host controller was getting very confused with the bad encoding." Actually 0x11 is 17, means "Parameter Error" - the context parameter is invalid, which exactly describes the cause of this issue. Maybe you just want to print the TRB completion code as %d to avoid this kind of confusion. Thanks, Andiry -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
