On Mon, 10 Nov 2014, Naveen Kumar Parna wrote: > I am sorry for the late response. > > I applied the patch and here is the dmesg log: > > [ 713.125709] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token > 80108d46 overlay token 80108d46 > [ 713.125796] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token > 80108d46 overlay token 80108d46 > [ 713.125853] hci4 urb ffff8800b89a7c00 status -32 count 0 > [ 713.125857] hci3 urb ffff8800b7399c00 status -32 count 0 > Does it gives the reason for -32 status code? More or less. The last (status) byte in the "token" values is 0x46, and the 0x04 status bit is documented in the EHCI spec as follows: Missed Micro-Frame. This bit is ignored unless the QH.EPS field indicates a full- or low-speed endpoint and the queue head is in the periodic list. This bit is set when the host controller detected that a host-induced hold-off caused the host controller to miss a required complete-split transaction. If the host controller sets this bit to a one, then it remains a one for the duration of thetransfer. This means the host controller is telling you it was unable to carry out the CSPLIT part of the transaction, which means it really is a hardware problem (and not a bad memory chip). Either the controller isn't working right or else your system is somehow overloaded. The 0x42 bits indicate that the Queue Head was halted and a CSPLIT is pending (which we already knew). The "halted" status bit is the reason why you got a -32 status code. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
