Re: Control message failures kill entire XHCI stack

2015-03-11 Thread Devin Heitmueller
On Tue, Mar 10, 2015 at 8:34 PM, Lu, Baolu baolu...@linux.intel.com wrote: Devin, I'd like you to provide output of lspci -xv. I want to know which xHC devices (PCI vendor and device ID) you are working with. Sorry, I misread your email. The lspci output is below. Devin 00:00.0 Host bridge:

Re: Control message failures kill entire XHCI stack

2015-03-10 Thread Lu, Baolu
Hi Devin, Do you mind to post output of lspci -xv on the machine where you saw this problem? We are facing the same problems in other cases. I could provide a patch for it later. Thanks, Baolu On 01/19/2015 04:55 AM, Devin Heitmueller wrote: Hello, I'm debugging some issues on a couple

Re: Control message failures kill entire XHCI stack

2015-03-10 Thread Devin Heitmueller
Hello Baolu, I'm doing most of my testing on a 2014 Retina Macbook Pro. lsusb output below. I've also seen the issue on an Intel NUC D34010WYKH, which I don't have in front of me or I would provide the lsusb output for that as well. Apologies to Mathias for not getting back to this sooner.

Re: Control message failures kill entire XHCI stack

2015-03-10 Thread Lu, Baolu
On 03/10/2015 11:10 PM, Devin Heitmueller wrote: Hello Baolu, I'm doing most of my testing on a 2014 Retina Macbook Pro. lsusb output below. I've also seen the issue on an Intel NUC D34010WYKH, which I don't have in front of me or I would provide the lsusb output for that as well. Devin,

Re: Control message failures kill entire XHCI stack

2015-03-05 Thread Mathias Nyman
On 04.03.2015 15:27, Alistair Grant wrote: Hi Mathias, On Tue, Mar 3, 2015 at 8:40 PM, Alistair Grant akgrant0...@gmail.com wrote: Hi Mathias, On Tue, Mar 3, 2015 at 2:21 PM, Mathias Nyman mathias.ny...@linux.intel.com wrote: On 28.02.2015 09:16, Alistair Grant wrote: ... * 3.19.0

Re: Control message failures kill entire XHCI stack

2015-03-05 Thread Alistair Grant
Hi Mathias, On Thu, Mar 5, 2015 at 4:25 PM, Mathias Nyman mathias.ny...@linux.intel.com wrote: On 04.03.2015 15:27, Alistair Grant wrote: On Tue, Mar 3, 2015 at 8:40 PM, Alistair Grant akgrant0...@gmail.com wrote: On Tue, Mar 3, 2015 at 2:21 PM, Mathias Nyman mathias.ny...@linux.intel.com

Re: Control message failures kill entire XHCI stack

2015-03-04 Thread Alistair Grant
Hi Mathias, On Tue, Mar 3, 2015 at 8:40 PM, Alistair Grant akgrant0...@gmail.com wrote: Hi Mathias, On Tue, Mar 3, 2015 at 2:21 PM, Mathias Nyman mathias.ny...@linux.intel.com wrote: On 28.02.2015 09:16, Alistair Grant wrote: ... * 3.19.0 with the following patches: * xhci: Allocate

Re: Control message failures kill entire XHCI stack

2015-03-03 Thread Mathias Nyman
On 28.02.2015 09:16, Alistair Grant wrote: Hi Mathias Devin, On Thu, Feb 19, 2015 at 3:18 PM, Mathias Nyman mathias.ny...@linux.intel.com wrote: Got one more patch added to the for-usb-next-branch. It makes sure we allocate enough scratchpad memory for xhci. It's one possible cause.

Re: Control message failures kill entire XHCI stack

2015-03-03 Thread Alistair Grant
Hi Mathias, On Tue, Mar 3, 2015 at 2:21 PM, Mathias Nyman mathias.ny...@linux.intel.com wrote: On 28.02.2015 09:16, Alistair Grant wrote: ... * 3.19.0 with the following patches: * xhci: Allocate correct amount of scratchpad buffers * xhci: Don't touch TRBs memory if those are no longer on

Re: Control message failures kill entire XHCI stack

2015-02-27 Thread Alistair Grant
Hi Mathias Devin, On Thu, Feb 19, 2015 at 3:18 PM, Mathias Nyman mathias.ny...@linux.intel.com wrote: Got one more patch added to the for-usb-next-branch. It makes sure we allocate enough scratchpad memory for xhci. It's one possible cause. Patch will anyway go to 3.20, but you can try it

Re: Control message failures kill entire XHCI stack

2015-02-20 Thread Devin Heitmueller
Got one more patch added to the for-usb-next-branch. It makes sure we allocate enough scratchpad memory for xhci. It's one possible cause. Patch will anyway go to 3.20, but you can try it out first to see if it helps Hi Mathias, Thanks, I'll see if I can get this tested out over the

Re: Control message failures kill entire XHCI stack

2015-02-19 Thread Mathias Nyman
On 05.02.2015 00:02, Alistair Grant wrote: Hi Mathias, On Wed, Feb 4, 2015 at 5:26 PM, Mathias Nyman mathias.ny...@linux.intel.com wrote: On 27.01.2015 00:20, Alistair Grant wrote: I've come across what appears to be another xHCI issue - attempting to format a disk with gparted is causing

Re: Control message failures kill entire XHCI stack

2015-02-04 Thread Mathias Nyman
On 27.01.2015 00:20, Alistair Grant wrote: I've come across what appears to be another xHCI issue - attempting to format a disk with gparted is causing a kernel Oops. This may not be related to the issue you're currently investigating, but wanted to pass it on in case it is (if it isn't let

Re: Control message failures kill entire XHCI stack

2015-02-04 Thread Alistair Grant
Hi Mathias, On Wed, Feb 4, 2015 at 5:26 PM, Mathias Nyman mathias.ny...@linux.intel.com wrote: On 27.01.2015 00:20, Alistair Grant wrote: I've come across what appears to be another xHCI issue - attempting to format a disk with gparted is causing a kernel Oops. This may not be related to the

Re: Control message failures kill entire XHCI stack

2015-01-26 Thread Alistair Grant
On Mon, Jan 26, 2015 at 4:37 AM, Devin Heitmueller dheitmuel...@kernellabs.com wrote: Hi Mathias, Here's an interesting development: as a result of a related thread on linux-media, I came across a patch they are distributing in openelec:

Re: Control message failures kill entire XHCI stack

2015-01-26 Thread Mathias Nyman
On 26.01.2015 05:37, Devin Heitmueller wrote: Hi Mathias, Here's an interesting development: as a result of a related thread on linux-media, I came across a patch they are distributing in openelec: https://github.com/OpenELEC/OpenELEC.tv/commit/b636927dec20652ff020e54ed7838a2e9be51e03

Re: Control message failures kill entire XHCI stack

2015-01-26 Thread Alistair Grant
I've come across what appears to be another xHCI issue - attempting to format a disk with gparted is causing a kernel Oops. This may not be related to the issue you're currently investigating, but wanted to pass it on in case it is (if it isn't let me know and I'll either keep quiet or raise it

Re: Control message failures kill entire XHCI stack

2015-01-25 Thread Devin Heitmueller
Hi Mathias, Here's an interesting development: as a result of a related thread on linux-media, I came across a patch they are distributing in openelec: https://github.com/OpenELEC/OpenELEC.tv/commit/b636927dec20652ff020e54ed7838a2e9be51e03 Now I'm not saying that reverting the commit in

Re: Control message failures kill entire XHCI stack

2015-01-25 Thread Devin Heitmueller
Hi Mathias, I've done additional debugging and found a few things that might be noteworthy. When I originally reported the issue, I noted that it was some sort of recovery problem related to failed control messages. So while you've been focused on why stopping the endpoint failed when it came

Re: Control message failures kill entire XHCI stack

2015-01-22 Thread Mathias Nyman
On 21.01.2015 21:16, Alistair Grant wrote: Hi Matthias, On Tue, Jan 20, 2015 at 10:22 AM, Mathias Nyman mathias.ny...@linux.intel.com wrote: On 19.01.2015 22:02, Devin Heitmueller wrote: Hi Mathias, Thanks for getting back to me. There are a couple of xhci bugs triggered by dvb devices:

Re: Control message failures kill entire XHCI stack

2015-01-22 Thread Alistair Grant
Hi Matthias, On Thu, Jan 22, 2015 at 12:22 PM, Mathias Nyman mathias.ny...@linux.intel.com wrote: On 21.01.2015 21:16, Alistair Grant wrote: Hi Matthias, On Tue, Jan 20, 2015 at 10:22 AM, Mathias Nyman mathias.ny...@linux.intel.com wrote: On 19.01.2015 22:02, Devin Heitmueller wrote: Hi

Re: Control message failures kill entire XHCI stack

2015-01-21 Thread Devin Heitmueller
I've been following this as it somewhat resembles the problems I'm experiencing, which I've just formally reported in Hauppauge USB-Live2 recording fails on USB3 port. Yeah, it happens with the cx231xx as well, although the sequencing of events leading to the failure is a bit different (I

Re: Control message failures kill entire XHCI stack

2015-01-21 Thread Alistair Grant
Hi Matthias, On Tue, Jan 20, 2015 at 10:22 AM, Mathias Nyman mathias.ny...@linux.intel.com wrote: On 19.01.2015 22:02, Devin Heitmueller wrote: Hi Mathias, Thanks for getting back to me. There are a couple of xhci bugs triggered by dvb devices:

Re: Control message failures kill entire XHCI stack

2015-01-20 Thread Mathias Nyman
On 19.01.2015 22:02, Devin Heitmueller wrote: Hi Mathias, Thanks for getting back to me. There are a couple of xhci bugs triggered by dvb devices: https://bugzilla.kernel.org/show_bug.cgi?id=75521 https://bugzilla.kernel.org/show_bug.cgi?id=65021 The first one (75521) I believe is

Re: Control message failures kill entire XHCI stack

2015-01-19 Thread Mathias Nyman
Hi On 18.01.2015 22:55, Devin Heitmueller wrote: Hello, I'm debugging some issues on a couple of different USB TV tuners which boil down to the following error: xhci_hcd :00:14.0: xHCI host not responding to stop endpoint command. This is followed by the XHCI driver disconnecting

Re: Control message failures kill entire XHCI stack

2015-01-19 Thread Devin Heitmueller
Hi Mathias, Thanks for getting back to me. There are a couple of xhci bugs triggered by dvb devices: https://bugzilla.kernel.org/show_bug.cgi?id=75521 https://bugzilla.kernel.org/show_bug.cgi?id=65021 The first one (75521) I believe is mostly fixed by patches in 3.18 and early 3.19-rc, so

Control message failures kill entire XHCI stack

2015-01-18 Thread Devin Heitmueller
Hello, I'm debugging some issues on a couple of different USB TV tuners which boil down to the following error: xhci_hcd :00:14.0: xHCI host not responding to stop endpoint command. This is followed by the XHCI driver disconnecting *all* USB devices from the controller. I've done a bit of