Re: xHCI reports “ERROR Unknown event condition 20, HC probably busted”

2015-09-21 Thread Steinar H. Gunderson
On Mon, Sep 21, 2015 at 02:01:51PM +0300, Mathias Nyman wrote: > Now this suddenly makes more sense to me. > > Initial problem is very much related to U1 and U2 power saving states. > Either the device can't handle these states or then we set the max exit > latency values incorrectly. There's ce

Re: xHCI reports “ERROR Unknown event condition 20, HC probably busted”

2015-09-21 Thread Mathias Nyman
On 20.09.2015 03:14, Steinar H. Gunderson wrote: On Mon, Aug 31, 2015 at 05:28:10PM +0300, Mathias Nyman wrote: The "ERROR Transfer event TRB DMA ptr not part of curren..." errors are a bit worrying. I was hoping these would no longer occur after the last off by one fix: commit 7895086afde2a05

Re: xHCI reports “ERROR Unknown event condition 20, HC probably busted”

2015-09-19 Thread Steinar H. Gunderson
On Mon, Aug 31, 2015 at 05:28:10PM +0300, Mathias Nyman wrote: > The "ERROR Transfer event TRB DMA ptr not part of curren..." errors are a bit > worrying. > I was hoping these would no longer occur after the last off by one fix: > > commit 7895086afde2a05fa24a0e410d8e6b75ca7c8fdd > xhci: fix

Re: xHCI reports “ERROR Unknown event condition 20, HC probably busted”

2015-08-31 Thread Steinar H. Gunderson
On Mon, Aug 31, 2015 at 06:03:17PM +0300, Mathias Nyman wrote: > It's in 4.2-rc6. > I understood you were running 4.2-rc8, so it should be there. Yes, the error was with 4.2-rc8. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To unsubscribe from this list: send the line "unsubscribe linux-u

Re: xHCI reports “ERROR Unknown event condition 20, HC probably busted”

2015-08-31 Thread Mathias Nyman
The "ERROR Transfer event TRB DMA ptr not part of curren..." errors are a bit worrying. I was hoping these would no longer occur after the last off by one fix: commit 7895086afde2a05fa24a0e410d8e6b75ca7c8fdd xhci: fix off by one error in TRB DMA address boundary check That's in 3.12? Th

Re: xHCI reports “ERROR Unknown event condition 20, HC probably busted”

2015-08-31 Thread Steinar H. Gunderson
On Mon, Aug 31, 2015 at 05:28:10PM +0300, Mathias Nyman wrote: > The max exit latency should tell how long it can maximum take for the entire > link between host > and device to wake up and be fully functional. Isoc transfer will send a PING > TP max exit > latency before the first data transfer

Re: xHCI reports “ERROR Unknown event condition 20, HC probably busted”

2015-08-31 Thread Mathias Nyman
On 29.08.2015 17:06, Steinar H. Gunderson wrote: On Sat, Aug 29, 2015 at 12:17:25AM +0200, Steinar H. Gunderson wrote: I've noticed (with the CONFIG_PM=y kernel) that sometimes this comes up when inserting the device: [ 136.370917] usb 3-2: Set SEL for device-initiated U2 failed. I don't know

Re: xHCI reports “ERROR Unknown event condition 20, HC probably busted”

2015-08-29 Thread Steinar H. Gunderson
On Sat, Aug 29, 2015 at 12:17:25AM +0200, Steinar H. Gunderson wrote: > I've noticed (with the CONFIG_PM=y kernel) that sometimes this comes up when > inserting the device: > > [ 136.370917] usb 3-2: Set SEL for device-initiated U2 failed. > > I don't know if it's relevant. I've also noticed th

Re: xHCI reports “ERROR Unknown event condition 20, HC probably busted”

2015-08-28 Thread Steinar H. Gunderson
On Thu, Aug 27, 2015 at 12:26:28AM +0200, Steinar H. Gunderson wrote: > However, at the same time I get these in dmesg: > > [ 221.350440] xhci_hcd :00:14.0: ERROR Unknown event condition 20, HC > probably busted > [ 221.350559] xhci_hcd :00:14.0: ERROR Unknown event condition 20, HC

xHCI reports “ERROR Unknown event condition 20, HC probably busted”

2015-08-26 Thread Steinar H. Gunderson
Hi, I have an USB3 device which I'm using through libusb (so usbfs) pulling relatively large amounts of isochronous data (uncompressed 720p60 video, so a bit under a gigabit per second) down to my X240 laptop. I submit four isochronous requests of about ~2MB each, which seems to be enough to keep