* Re: btusb_intr_complete returns -EPIPE
[not found] <CAG0bkv+DL0bVs9irE7eUB3rC-J16Ue=b9+_TqeuTHJYMJDkC0g@mail.gmail.com>
@ 2014-11-06 16:44 ` Alan Stern
2014-11-10 6:38 ` Naveen Kumar Parna
2014-11-10 9:29 ` Naveen Kumar Parna
0 siblings, 2 replies; 45+ messages in thread
From: Alan Stern @ 2014-11-06 16:44 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Thu, 6 Nov 2014, Naveen Kumar Parna wrote:
> > Any idea why you see the CSPLITs now but didn't see them before?
>
> It looks like , I failed to locate the exact portion of the analyzer
> log that corresponds to one of those -32 events in the usbmon log.
Well, I still don't understand that, but never mind...
> USB Analyzer records several megabytes of data very quickly, so it’s
> very hard to find the portion of the analyzer log that corresponds to
> one of those -32 events in the usbmon log. To avoid this difficulty I
> applied the attached patch
> (0002-btusb-clear-halt-if-intr-in-stalls.patch – got it from Oliver
> Neukum) to btusb driver and reloaded this driver.
>
> The applied patch calls usb_clear_halt() on receiving the stall
> response, so now I can easily search for ClearFeature(ENDPOINT_HALT)
> request in the analyzer log. It can be found at "2.304 252 217" &
> "2.316 264 600" time instance in the attached log.
>
> Re ran the Analyzer again and attached it’s exported text
> log([2014-11-06 session 125138] Trace0000_only_ep0_ep1.txt). Here
> filtered out the BulkIN transactions.
>
> usbmon log:
> ffff8800b7670a80 506095728 C Ii:1:108:1 -32:1 0
> ffff8800affdccc0 506107757 C Ii:1:108:1 -32:1 0
> Here is the portion of the log that corresponds to “ffff8800b7670a80
> 506095728 C Ii:1:108:1 -32:1 0”:
>
> Start of Frame (6) HS 553.2 -> 553.7 2.302 964 717
> SSPLIT IN transaction 105 1 HS No data 2.303 590 367
> SSPLIT IN transaction 106 1 HS No data 2.303 591 283
> SSPLIT IN transaction 107 1 HS No data 2.303 600 283
> SSPLIT IN transaction 108 1 HS No data 2.303 601 350
> Start of Frame (2) HS 554.0 -> 554.1 2.303 714 817
> CSPLIT IN transaction 105 1 NAK HS No data 2.303 840 400
> CSPLIT IN transaction 106 1 NAK HS No data 2.303 842 033
> CSPLIT IN transaction 107 1 NAK HS No data 2.303 855 317
> Start of Frame (3) HS 554.2 -> 554.4 2.303 964 850
Obviously, there aren't any CSPLITs for device 108 ep 1.
> Here is the portion of the log that corresponds to “ffff8800affdccc0
> 506107757 C Ii:1:108:1 -32:1 0":
>
> Start of Frame (6) HS 565.2 -> 565.7 2.314 966 383
> SSPLIT IN transaction 105 1 HS No data 2.315 592 033
> SSPLIT IN transaction 106 1 HS No data 2.315 592 967
> SSPLIT IN transaction 107 1 HS No data 2.315 612 800
> SSPLIT IN transaction 108 1 HS No data 2.315 613 850
> Start of Frame (2) HS 566.0 -> 566.1 2.315 716 483
> CSPLIT IN transaction 105 1 NAK HS No data 2.315 842 067
> CSPLIT IN transaction 106 1 NAK HS No data 2.315 843 683
> CSPLIT IN transaction 107 1 NAK HS No data 2.315 928 750
> Start of Frame (3) HS 566.2 -> 566.4 2.315 966 517
> In both the cases, CSPLIT of Dev-108 is missing in this portion of the log.
>
> So, Does this test log gives some conclusion?
It indicates that the EHCI host controller hardware isn't working
right. Every now and then it skips sending CSPLIT packets when it
should send them.
I suppose it's possible that the host controller is okay and the
problem is a bad memory chip. That could also cause this sort of
error. Regardless, it has to be a hardware problem.
Now, this doesn't explain why you get the -32 status code. Maybe the
patch below will provide more information. Try running your test with
this patch installed and see what shows up in the dmesg log.
Alan Stern
Index: usb-3.18/drivers/usb/host/ehci-q.c
===================================================================
--- usb-3.18.orig/drivers/usb/host/ehci-q.c
+++ usb-3.18/drivers/usb/host/ehci-q.c
@@ -346,6 +346,12 @@ qh_completions (struct ehci_hcd *ehci, s
/* always clean up qtds the hc de-activated */
retry_xacterr:
if ((token & QTD_STS_ACTIVE) == 0) {
+ u32 info2 = hc32_to_cpu(ehci, hw->hw_info2);
+
+ if ((info2 & QH_SMASK) && (token & 0x7e))
+ ehci_info(ehci, "split intr info2 %x token %x overlay token %x\n",
+ info2, token, hc32_to_cpu(ehci,
+ hw->hw_token));
/* Report Data Buffer Error: non-fatal but useful */
if (token & QTD_STS_DBE)
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-11-06 16:44 ` btusb_intr_complete returns -EPIPE Alan Stern
@ 2014-11-10 6:38 ` Naveen Kumar Parna
2014-11-10 16:56 ` Alan Stern
2014-11-10 9:29 ` Naveen Kumar Parna
1 sibling, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-11-10 6:38 UTC (permalink / raw)
To: Alan Stern; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
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
[ 713.126801] hci4
[ 713.127003] hci3
[ 3046.032153] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 3046.032227] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 3046.032272] hci3 urb ffff8800b30f5a80 status -32 count 0
[ 3046.032278] hci4 urb ffff8800b30f53c0 status -32 count 0
[ 3046.033326] hci4
[ 3046.033344] hci3
Does it gives the reason for -32 status code?
Thanks,
Naveen
On Thu, Nov 6, 2014 at 10:14 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Thu, 6 Nov 2014, Naveen Kumar Parna wrote:
>
>> > Any idea why you see the CSPLITs now but didn't see them before?
>>
>> It looks like , I failed to locate the exact portion of the analyzer
>> log that corresponds to one of those -32 events in the usbmon log.
>
> Well, I still don't understand that, but never mind...
>
>> USB Analyzer records several megabytes of data very quickly, so it’s
>> very hard to find the portion of the analyzer log that corresponds to
>> one of those -32 events in the usbmon log. To avoid this difficulty I
>> applied the attached patch
>> (0002-btusb-clear-halt-if-intr-in-stalls.patch – got it from Oliver
>> Neukum) to btusb driver and reloaded this driver.
>>
>> The applied patch calls usb_clear_halt() on receiving the stall
>> response, so now I can easily search for ClearFeature(ENDPOINT_HALT)
>> request in the analyzer log. It can be found at "2.304 252 217" &
>> "2.316 264 600" time instance in the attached log.
>>
>> Re ran the Analyzer again and attached it’s exported text
>> log([2014-11-06 session 125138] Trace0000_only_ep0_ep1.txt). Here
>> filtered out the BulkIN transactions.
>>
>> usbmon log:
>> ffff8800b7670a80 506095728 C Ii:1:108:1 -32:1 0
>> ffff8800affdccc0 506107757 C Ii:1:108:1 -32:1 0
>
>> Here is the portion of the log that corresponds to “ffff8800b7670a80
>> 506095728 C Ii:1:108:1 -32:1 0”:
>>
>> Start of Frame (6) HS 553.2 -> 553.7 2.302 964 717
>> SSPLIT IN transaction 105 1 HS No data 2.303 590 367
>> SSPLIT IN transaction 106 1 HS No data 2.303 591 283
>> SSPLIT IN transaction 107 1 HS No data 2.303 600 283
>> SSPLIT IN transaction 108 1 HS No data 2.303 601 350
>> Start of Frame (2) HS 554.0 -> 554.1 2.303 714 817
>> CSPLIT IN transaction 105 1 NAK HS No data 2.303 840 400
>> CSPLIT IN transaction 106 1 NAK HS No data 2.303 842 033
>> CSPLIT IN transaction 107 1 NAK HS No data 2.303 855 317
>> Start of Frame (3) HS 554.2 -> 554.4 2.303 964 850
>
> Obviously, there aren't any CSPLITs for device 108 ep 1.
>
>> Here is the portion of the log that corresponds to “ffff8800affdccc0
>> 506107757 C Ii:1:108:1 -32:1 0":
>>
>> Start of Frame (6) HS 565.2 -> 565.7 2.314 966 383
>> SSPLIT IN transaction 105 1 HS No data 2.315 592 033
>> SSPLIT IN transaction 106 1 HS No data 2.315 592 967
>> SSPLIT IN transaction 107 1 HS No data 2.315 612 800
>> SSPLIT IN transaction 108 1 HS No data 2.315 613 850
>> Start of Frame (2) HS 566.0 -> 566.1 2.315 716 483
>> CSPLIT IN transaction 105 1 NAK HS No data 2.315 842 067
>> CSPLIT IN transaction 106 1 NAK HS No data 2.315 843 683
>> CSPLIT IN transaction 107 1 NAK HS No data 2.315 928 750
>> Start of Frame (3) HS 566.2 -> 566.4 2.315 966 517
>
>> In both the cases, CSPLIT of Dev-108 is missing in this portion of the log.
>>
>> So, Does this test log gives some conclusion?
>
> It indicates that the EHCI host controller hardware isn't working
> right. Every now and then it skips sending CSPLIT packets when it
> should send them.
>
> I suppose it's possible that the host controller is okay and the
> problem is a bad memory chip. That could also cause this sort of
> error. Regardless, it has to be a hardware problem.
>
> Now, this doesn't explain why you get the -32 status code. Maybe the
> patch below will provide more information. Try running your test with
> this patch installed and see what shows up in the dmesg log.
>
> Alan Stern
>
>
>
> Index: usb-3.18/drivers/usb/host/ehci-q.c
> ===================================================================
> --- usb-3.18.orig/drivers/usb/host/ehci-q.c
> +++ usb-3.18/drivers/usb/host/ehci-q.c
> @@ -346,6 +346,12 @@ qh_completions (struct ehci_hcd *ehci, s
> /* always clean up qtds the hc de-activated */
> retry_xacterr:
> if ((token & QTD_STS_ACTIVE) == 0) {
> + u32 info2 = hc32_to_cpu(ehci, hw->hw_info2);
> +
> + if ((info2 & QH_SMASK) && (token & 0x7e))
> + ehci_info(ehci, "split intr info2 %x token %x overlay token %x\n",
> + info2, token, hc32_to_cpu(ehci,
> + hw->hw_token));
>
> /* Report Data Buffer Error: non-fatal but useful */
> if (token & QTD_STS_DBE)
>
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-11-06 16:44 ` btusb_intr_complete returns -EPIPE Alan Stern
2014-11-10 6:38 ` Naveen Kumar Parna
@ 2014-11-10 9:29 ` Naveen Kumar Parna
1 sibling, 0 replies; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-11-10 9:29 UTC (permalink / raw)
To: Alan Stern; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Thu, Nov 6, 2014 at 10:14 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Thu, 6 Nov 2014, Naveen Kumar Parna wrote:
>
>> > Any idea why you see the CSPLITs now but didn't see them before?
>>
>> It looks like , I failed to locate the exact portion of the analyzer
>> log that corresponds to one of those -32 events in the usbmon log.
>
> Well, I still don't understand that, but never mind...
>
>> USB Analyzer records several megabytes of data very quickly, so it’s
>> very hard to find the portion of the analyzer log that corresponds to
>> one of those -32 events in the usbmon log. To avoid this difficulty I
>> applied the attached patch
>> (0002-btusb-clear-halt-if-intr-in-stalls.patch – got it from Oliver
>> Neukum) to btusb driver and reloaded this driver.
>>
>> The applied patch calls usb_clear_halt() on receiving the stall
>> response, so now I can easily search for ClearFeature(ENDPOINT_HALT)
>> request in the analyzer log. It can be found at "2.304 252 217" &
>> "2.316 264 600" time instance in the attached log.
>>
>> Re ran the Analyzer again and attached it’s exported text
>> log([2014-11-06 session 125138] Trace0000_only_ep0_ep1.txt). Here
>> filtered out the BulkIN transactions.
>>
>> usbmon log:
>> ffff8800b7670a80 506095728 C Ii:1:108:1 -32:1 0
>> ffff8800affdccc0 506107757 C Ii:1:108:1 -32:1 0
>
>> Here is the portion of the log that corresponds to “ffff8800b7670a80
>> 506095728 C Ii:1:108:1 -32:1 0”:
>>
>> Start of Frame (6) HS 553.2 -> 553.7 2.302 964 717
>> SSPLIT IN transaction 105 1 HS No data 2.303 590 367
>> SSPLIT IN transaction 106 1 HS No data 2.303 591 283
>> SSPLIT IN transaction 107 1 HS No data 2.303 600 283
>> SSPLIT IN transaction 108 1 HS No data 2.303 601 350
>> Start of Frame (2) HS 554.0 -> 554.1 2.303 714 817
>> CSPLIT IN transaction 105 1 NAK HS No data 2.303 840 400
>> CSPLIT IN transaction 106 1 NAK HS No data 2.303 842 033
>> CSPLIT IN transaction 107 1 NAK HS No data 2.303 855 317
>> Start of Frame (3) HS 554.2 -> 554.4 2.303 964 850
>
> Obviously, there aren't any CSPLITs for device 108 ep 1.
>
>> Here is the portion of the log that corresponds to “ffff8800affdccc0
>> 506107757 C Ii:1:108:1 -32:1 0":
>>
>> Start of Frame (6) HS 565.2 -> 565.7 2.314 966 383
>> SSPLIT IN transaction 105 1 HS No data 2.315 592 033
>> SSPLIT IN transaction 106 1 HS No data 2.315 592 967
>> SSPLIT IN transaction 107 1 HS No data 2.315 612 800
>> SSPLIT IN transaction 108 1 HS No data 2.315 613 850
>> Start of Frame (2) HS 566.0 -> 566.1 2.315 716 483
>> CSPLIT IN transaction 105 1 NAK HS No data 2.315 842 067
>> CSPLIT IN transaction 106 1 NAK HS No data 2.315 843 683
>> CSPLIT IN transaction 107 1 NAK HS No data 2.315 928 750
>> Start of Frame (3) HS 566.2 -> 566.4 2.315 966 517
>
>> In both the cases, CSPLIT of Dev-108 is missing in this portion of the log.
>>
>> So, Does this test log gives some conclusion?
>
> It indicates that the EHCI host controller hardware isn't working
> right. Every now and then it skips sending CSPLIT packets when it
> should send them.
>
> I suppose it's possible that the host controller is okay and the
> problem is a bad memory chip. That could also cause this sort of
> error. Regardless, it has to be a hardware problem.
Is there any test I can run to prove that memory chip is bad?
>
> Now, this doesn't explain why you get the -32 status code. Maybe the
> patch below will provide more information. Try running your test with
> this patch installed and see what shows up in the dmesg log.
>
> Alan Stern
>
>
>
> Index: usb-3.18/drivers/usb/host/ehci-q.c
> ===================================================================
> --- usb-3.18.orig/drivers/usb/host/ehci-q.c
> +++ usb-3.18/drivers/usb/host/ehci-q.c
> @@ -346,6 +346,12 @@ qh_completions (struct ehci_hcd *ehci, s
> /* always clean up qtds the hc de-activated */
> retry_xacterr:
> if ((token & QTD_STS_ACTIVE) == 0) {
> + u32 info2 = hc32_to_cpu(ehci, hw->hw_info2);
> +
> + if ((info2 & QH_SMASK) && (token & 0x7e))
> + ehci_info(ehci, "split intr info2 %x token %x overlay token %x\n",
> + info2, token, hc32_to_cpu(ehci,
> + hw->hw_token));
>
> /* Report Data Buffer Error: non-fatal but useful */
> if (token & QTD_STS_DBE)
>
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
[ 713.126801] hci4
[ 713.127003] hci3
[ 3046.032153] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 3046.032227] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 3046.032272] hci3 urb ffff8800b30f5a80 status -32 count 0
[ 3046.032278] hci4 urb ffff8800b30f53c0 status -32 count 0
[ 3046.033326] hci4
[ 3046.033344] hci3
[ 3586.175590] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 3586.175698] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 3586.175759] hci4 urb ffff8800b8a64a80 status -32 count 0
[ 3586.175766] hci3 urb ffff8800b8a64cc0 status -32 count 0
[ 3586.176625] hci4
[ 3586.177000] hci3
[ 4310.473875] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 4310.473972] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 4310.474019] hci3 urb ffff8800b3099c00 status -32 count 0
[ 4310.474023] hci4 urb ffff8800b3099480 status -32 count 0
[ 4310.474912] hci3
[ 4310.475027] hci4
[ 4313.710199] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 4313.710325] hci4 urb ffff8800b8012a80 status -32 count 0
[ 4313.711207] hci4
[ 4314.722302] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 4314.722359] hci4 urb ffff8800b8012a80 status -32 count 0
[ 4314.723472] hci4
[ 5210.940319] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5210.940423] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5210.940471] hci4 urb ffff8800b8012a80 status -32 count 0
[ 5210.940475] hci3 urb ffff8800b8012180 status -32 count 0
[ 5210.941309] hci4
[ 5210.941703] hci3
[ 5211.464329] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5211.464437] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5211.464490] hci3 urb ffff8800b8bb9000 status -32 count 0
[ 5211.464493] hci4 urb ffff8800b8bb90c0 status -32 count 0
[ 5211.465367] hci4
[ 5211.465383] hci3
[ 5211.508336] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5211.508426] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5211.508469] hci4 urb ffff8800b8bb9000 status -32 count 0
[ 5211.508472] hci3 urb ffff8800b8bb90c0 status -32 count 0
[ 5211.509375] hci3
[ 5211.509390] hci4
[ 5212.144419] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5212.144500] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5212.144539] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
80108d46 overlay token 80108d46
[ 5212.144598] hci3 urb ffff8800b8bb9000 status -32 count 0
[ 5212.144603] hci4 urb ffff8800b8bb90c0 status -32 count 0
[ 5212.144605] hci2 urb ffff8800b7399600 status -32 count 0
[ 5212.145406] hci3
[ 5212.145685] hci4
[ 5212.145697] hci2
[ 5212.284485] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5212.284603] hci2 urb ffff8800b8bb9180 status -32 count 0
[ 5212.285452] hci2
[ 5213.084540] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5213.084660] hci2 urb ffff8800b8bb9180 status -32 count 0
[ 5213.085778] hci2
[ 5213.996615] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5213.996763] hci2 urb ffff8800b8bb9180 status -32 count 0
[ 5214.000391] hci2
[ 5216.156816] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5216.156939] hci2 urb ffff8800b8bb9180 status -32 count 0
[ 5216.157807] hci2
[ 5741.146808] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5741.146906] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5741.146946] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 5741.146994] hci2 urb ffff8800b8bb9180 status -32 count 0
[ 5741.146998] hci4 urb ffff8800b8bb9000 status -32 count 0
[ 5741.147001] hci3 urb ffff8800b8bb90c0 status -32 count 0
[ 5741.147807] hci2
[ 5741.148068] hci3
[ 5741.148204] hci4
[ 8327.577511] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 8327.577600] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 8327.577639] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 8327.577690] hci3 urb ffff8800b8bb9d80 status -32 count 0
[ 8327.577695] hci4 urb ffff8800b8bb9180 status -32 count 0
[ 8327.577697] hci2 urb ffff8800b8bb90c0 status -32 count 0
[ 8327.578683] hci4
[ 8327.578698] hci2
[ 8327.581162] hci3
[ 9347.950892] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 9347.951007] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 9347.951046] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[ 9347.951108] hci2 urb ffff8801399bf600 status -32 count 0
[ 9347.951113] hci4 urb ffff8801399bff00 status -32 count 0
[ 9347.951115] hci3 urb ffff8801399bf6c0 status -32 count 0
[ 9347.952070] hci2
[ 9347.952307] hci4
[ 9347.952422] hci3
[10016.619096] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[10016.619188] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[10016.619227] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[10016.619288] hci3 urb ffff8800b4097000 status -32 count 0
[10016.619293] hci4 urb ffff8800b4097240 status -32 count 0
[10016.619295] hci2 urb ffff8800b4097480 status -32 count 0
[10016.620257] hci4
[10016.620273] hci2
[10016.625393] hci3
[10016.663094] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[10016.663178] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[10016.663228] hci3 urb ffff8800371c1900 status -32 count 0
[10016.663233] hci2 urb ffff8800371c1cc0 status -32 count 0
[10016.664152] hci3
[10016.664162] hci2
[10016.683124] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[10016.683200] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[10016.683239] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[10016.683289] hci2 urb ffff8800371c1900 status -32 count 0
[10016.683293] hci3 urb ffff8800371c1cc0 status -32 count 0
[10016.683295] hci4 urb ffff8800371c1000 status -32 count 0
[10016.684132] hci4
[10016.684139] hci3
[10016.684144] hci2
[10366.025162] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[10366.025240] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[10366.025280] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[10366.025332] hci4 urb ffff8800371c1900 status -32 count 0
[10366.025336] hci3 urb ffff8800371c1cc0 status -32 count 0
[10366.025339] hci2 urb ffff8800371c1000 status -32 count 0
[10366.026485] hci3
[10366.026502] hci4
[10366.026565] hci2
[11095.765903] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11095.765981] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11095.766021] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11095.766085] hci2 urb ffff8800372ad9c0 status -32 count 0
[11095.766090] hci3 urb ffff8800372ad6c0 status -32 count 0
[11095.766092] hci4 urb ffff8800372ad240 status -32 count 0
[11095.767016] hci2
[11095.767032] hci3
[11095.767043] hci4
[11527.042340] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11527.042425] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11527.042464] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11527.042516] hci4 urb ffff8800aed34780 status -32 count 0
[11527.042520] hci3 urb ffff8800aed34c00 status -32 count 0
[11527.042522] hci2 urb ffff8800aed343c0 status -32 count 0
[11527.043377] hci4
[11527.043479] hci3
[11527.043983] hci2
[11716.767697] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11716.767769] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11716.767816] hci2 urb ffff8800b88be840 status -32 count 0
[11716.767820] hci3 urb ffff8800b88bed80 status -32 count 0
[11716.768712] hci3
[11716.768721] hci2
[11816.865884] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11816.865964] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11816.866003] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11816.866058] hci3 urb ffff8800b88be840 status -32 count 0
[11816.866063] hci2 urb ffff8800b88bed80 status -32 count 0
[11816.866065] hci4 urb ffff8800b88bea80 status -32 count 0
[11816.867026] hci2
[11816.867112] hci3
[11816.869653] hci4
[11816.877845] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11816.877950] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11816.877994] ehci-pci 0000:00:1a.0: split intr info2 42821c01 token
108d46 overlay token 108d46
[11816.878058] hci4 urb ffff8800b88be840 status -32 count 0
[11816.878062] hci2 urb ffff8800b88bed80 status -32 count 0
[11816.878064] hci3 urb ffff8800b88bea80 status -32 count 0
[11816.878885] hci2
[11816.878901] hci4
[11816.878910] hci3
Thanks,
Naveen
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-11-10 6:38 ` Naveen Kumar Parna
@ 2014-11-10 16:56 ` Alan Stern
2014-11-11 9:53 ` Naveen Kumar Parna
0 siblings, 1 reply; 45+ messages in thread
From: Alan Stern @ 2014-11-10 16:56 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
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
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-11-10 16:56 ` Alan Stern
@ 2014-11-11 9:53 ` Naveen Kumar Parna
2014-11-11 15:56 ` Alan Stern
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-11-11 9:53 UTC (permalink / raw)
To: Alan Stern; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Mon, Nov 10, 2014 at 10:26 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> 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
>
I am really glad we reached to a conclusion on this.
Thanks for all your help, without which I could not have seen this through.
Now I am confronted with many of these controllers in my lab, with
this hardware issue.
I am not sure I can find a better way than just to tell people to replace them.
Thanks,
Naveen
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-11-11 9:53 ` Naveen Kumar Parna
@ 2014-11-11 15:56 ` Alan Stern
0 siblings, 0 replies; 45+ messages in thread
From: Alan Stern @ 2014-11-11 15:56 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Tue, 11 Nov 2014, Naveen Kumar Parna wrote:
> I am really glad we reached to a conclusion on this.
> Thanks for all your help, without which I could not have seen this through.
You're welcome.
> Now I am confronted with many of these controllers in my lab, with
> this hardware issue.
> I am not sure I can find a better way than just to tell people to replace them.
You could try contacting the manufacturer to see if they are aware of
this problem and have any suggestions.
Alan Stern
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-11-05 6:58 ` Naveen Kumar Parna
@ 2014-11-05 21:09 ` Alan Stern
0 siblings, 0 replies; 45+ messages in thread
From: Alan Stern @ 2014-11-05 21:09 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Wed, 5 Nov 2014, Naveen Kumar Parna wrote:
> > Can you do it again, but this time keep the SOF packets?
> >
> > You don't have to post the entire analyzer log. Just extract 3 or 4 ms
> > from the middle, where it shows the SSPLITS but no CSPLITS for the
> > interrupt endpoints, and post only that portion.
> >
>
> I tried again, I keep getting STALL's but this time I see CSPLITS for
> the interrupt end points.
Any idea why you see the CSPLITs now but didn't see them before?
> usbmon log:
> ffff8800b2cce6c0 1558099725 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 1558099740 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 1558435684 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 1558435700 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 1558447773 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 1558447790 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 1562003759 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 1562003777 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 1835091798 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 1835091818 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 2360295770 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 2360295785 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 2360307814 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 2360307827 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 2746327776 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 2746327796 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 2750455832 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 2750455844 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 2751751777 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 2751751788 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 2752707689 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 2752707707 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 2762271761 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 2762271776 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 2977131824 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 2977131835 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 3602679779 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 3602679798 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 456023739 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 456023758 S Ii:1:055:1 -115:1 16 <
> ffff8800b2cce6c0 456231695 C Ii:1:055:1 -32:1 0
> ffff8800b2cce6c0 456231712 S Ii:1:055:1 -115:1 16 <
Notice that the problem seems to occur very rarely. There are often
many seconds between the -32 status values, whereas the interrupt
endpoint gets polled 1000 times per second.
Inconsistent behavior like that tends to indicate a hardware problem.
Software would behave the same way every time, unless there was some
sort of race.
> Dev 55 usb log:
>
> SSPLIT IN transaction 55 1 HS No data 0.000 238 117
> Start of Frame (2) HS 228.0 -> 228.1 0.000 340 583
> CSPLIT IN transaction 55 1 NAK HS No data 0.000 489 817
> Start of Frame (6) HS 228.2 -> 228.7 0.000 590 617
> SSPLIT IN transaction 55 1 HS No data 0.001 238 117
> Start of Frame (2) HS 229.0 -> 229.1 0.001 340 733
> CSPLIT IN transaction 55 1 NAK HS No data 0.001 489 850
> Start of Frame (6) HS 229.2 -> 229.7 0.001 590 767
> SSPLIT IN transaction 55 1 HS No data 0.002 238 933
> Start of Frame (2) HS 230.0 -> 230.1 0.002 340 867
> CSPLIT IN transaction 55 1 NAK HS No data 0.002 489 933
> Start of Frame (6) HS 230.2 -> 230.7 0.002 590 900
> SSPLIT IN transaction 55 1 HS No data 0.003 238 967
> Start of Frame (2) HS 231.0 -> 231.1 0.003 341 017
> CSPLIT IN transaction 55 1 NAK HS No data 0.003 489 900
> Start of Frame (6) HS 231.2 -> 231.7 0.003 591 050
> SSPLIT IN transaction 55 1 HS No data 0.004 238 950
> Start of Frame (2) HS 232.0 -> 232.1 0.004 341 150
> CSPLIT IN transaction 55 1 NAK HS No data 0.004 489 950
> Start of Frame (6) HS 232.2 -> 232.7 0.004 591 183
> SSPLIT IN transaction 55 1 HS No data 0.005 239 000
> Start of Frame (2) HS 233.0 -> 233.1 0.005 341 283
> CSPLIT IN transaction 55 1 NAK HS No data 0.005 490 000
This looks right. The SSPLIT packets get sent in microframe 7 of each
frame and the CSPLIT packets get sent in microframe 1. (The full-speed
bus transaction occurs during microframe 0, in between.)
Also, a NAK response to a CSPLIT is correct when the device has no data
to send. It wouldn't cause you to get a STALL indication.
I need to see the portion of the analyzer log that corresponds to one
of those -32 events in the usbmon log. It ought to show something
different, something that would cause the -32 status.
> External USB-2 hub (Dev 51) log:
> Start of Frame (570) HS 258.7 -> 330.0 0.000 090 550
> IN transaction 51 1 NAK HS No data 0.071 226 050
> Start of Frame (2,048) HS 299.0 -> 554.7 0.071 350 517
> IN transaction 51 1 NAK HS No data 0.327 261 817
> Start of Frame (2,048) HS 555.0 -> 810.7 0.327 386 250
> IN transaction 51 1 NAK HS No data 0.583 297 550
> Start of Frame (2,048) HS 811.0 -> 1,066.7 0.583 422 000
> IN transaction 51 1 NAK HS No data 0.839 333 283
> Start of Frame (2,048) HS 1,067.0 -> 1,322.7 0.839 457 733
> IN transaction 51 1 NAK HS No data 1.095 369 050
> Start of Frame (2,048) HS 1,323.0 -> 1,578.7 1.095 493 483
> IN transaction 51 1 NAK HS No data 1.351 404 767
> Start of Frame (2,048) HS 1,579.0 -> 1,834.7 1.351 529 233
> IN transaction 51 1 NAK HS No data 1.607 440 517
This also looks right. The hub won't have any data to send until you
plug in or unplug a device from one of its ports.
> Internal USB-2 hub (Dev 2) log:
> Start of Frame (266) HS 258.7 -> 292.0 0.000 090 550
> Incomplete IN transaction 2 1 INCOMPLETE HS No data 0.033 220 750
> Start of Frame (2,048) HS 261.0 -> 516.7 0.033 345 200
> Incomplete IN transaction 2 1 INCOMPLETE HS No data 0.289 256 517
> Start of Frame (2,048) HS 517.0 -> 772.7 0.289 380 950
> Incomplete IN transaction 2 1 INCOMPLETE HS No data 0.545 292 233
> Start of Frame (2,048) HS 773.0 -> 1,028.7 0.545 416 683
> Incomplete IN transaction 2 1 INCOMPLETE HS No data 0.801 328 000
And this looks right too. The analyzer was unable to record the
responses to the IN transactions because the response packets were sent
directly back to the host controller -- they don't get sent to the
external port where the analyzer is attached.
Alan Stern
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-11-03 16:19 ` Alan Stern
@ 2014-11-05 6:58 ` Naveen Kumar Parna
2014-11-05 21:09 ` Alan Stern
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-11-05 6:58 UTC (permalink / raw)
To: Alan Stern; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
[-- Attachment #1: Type: text/plain, Size: 7009 bytes --]
>> >> Split packet transactions are hidden. I could see them by clicking on
>> >> the (Show/Hide Split transactions) button. For INT IN, I could see
>> >> only Start Split packet.
>> >>
>> >> I attached([2014-10-28 session 144012] Trace0003.rar) complete log for
>> >> this scenario.
>> >
>> > How come the log doesn't contain any SOF packets?
>>
>>
>> To avoid recording a huge quantity of data , I enabled the "Drop Start
>> of Frames" filter in the recording options.
>
> Can you do it again, but this time keep the SOF packets?
>
> You don't have to post the entire analyzer log. Just extract 3 or 4 ms
> from the middle, where it shows the SSPLITS but no CSPLITS for the
> interrupt endpoints, and post only that portion.
>
I tried again, I keep getting STALL's but this time I see CSPLITS for
the interrupt end points.
[root@banunxcas29 ns06]# lsusb -t
1-1.5.1:1.2: No such file or directory
1-1.5.2:1.2: No such file or directory
1-1.5.3:1.2: No such file or directory
1-1.5.4:1.2: No such file or directory
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
|__ Port 5: Dev 51, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 1: Dev 52, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 1: Dev 52, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 1: Dev 52, If 2, Class=app., Driver=, 12M
|__ Port 2: Dev 53, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 2: Dev 53, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 2: Dev 53, If 2, Class=app., Driver=, 12M
|__ Port 3: Dev 56, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 3: Dev 56, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 3: Dev 56, If 2, Class=app., Driver=, 12M
|__ Port 4: Dev 55, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 4: Dev 55, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 4: Dev 55, If 2, Class=app., Driver=, 12M
Here Dev 51 is external USB-2 hub.
usbmon log:
ffff8800b2cce6c0 1558099725 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 1558099740 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 1558435684 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 1558435700 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 1558447773 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 1558447790 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 1562003759 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 1562003777 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 1835091798 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 1835091818 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 2360295770 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 2360295785 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 2360307814 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 2360307827 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 2746327776 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 2746327796 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 2750455832 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 2750455844 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 2751751777 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 2751751788 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 2752707689 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 2752707707 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 2762271761 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 2762271776 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 2977131824 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 2977131835 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 3602679779 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 3602679798 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 456023739 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 456023758 S Ii:1:055:1 -115:1 16 <
ffff8800b2cce6c0 456231695 C Ii:1:055:1 -32:1 0
ffff8800b2cce6c0 456231712 S Ii:1:055:1 -115:1 16 <
Dev 55 usb log:
SSPLIT IN transaction 55 1 HS No data 0.000 238 117
Start of Frame (2) HS 228.0 -> 228.1 0.000 340 583
CSPLIT IN transaction 55 1 NAK HS No data 0.000 489 817
Start of Frame (6) HS 228.2 -> 228.7 0.000 590 617
SSPLIT IN transaction 55 1 HS No data 0.001 238 117
Start of Frame (2) HS 229.0 -> 229.1 0.001 340 733
CSPLIT IN transaction 55 1 NAK HS No data 0.001 489 850
Start of Frame (6) HS 229.2 -> 229.7 0.001 590 767
SSPLIT IN transaction 55 1 HS No data 0.002 238 933
Start of Frame (2) HS 230.0 -> 230.1 0.002 340 867
CSPLIT IN transaction 55 1 NAK HS No data 0.002 489 933
Start of Frame (6) HS 230.2 -> 230.7 0.002 590 900
SSPLIT IN transaction 55 1 HS No data 0.003 238 967
Start of Frame (2) HS 231.0 -> 231.1 0.003 341 017
CSPLIT IN transaction 55 1 NAK HS No data 0.003 489 900
Start of Frame (6) HS 231.2 -> 231.7 0.003 591 050
SSPLIT IN transaction 55 1 HS No data 0.004 238 950
Start of Frame (2) HS 232.0 -> 232.1 0.004 341 150
CSPLIT IN transaction 55 1 NAK HS No data 0.004 489 950
Start of Frame (6) HS 232.2 -> 232.7 0.004 591 183
SSPLIT IN transaction 55 1 HS No data 0.005 239 000
Start of Frame (2) HS 233.0 -> 233.1 0.005 341 283
CSPLIT IN transaction 55 1 NAK HS No data 0.005 490 000
External USB-2 hub (Dev 51) log:
Start of Frame (570) HS 258.7 -> 330.0 0.000 090 550
IN transaction 51 1 NAK HS No data 0.071 226 050
Start of Frame (2,048) HS 299.0 -> 554.7 0.071 350 517
IN transaction 51 1 NAK HS No data 0.327 261 817
Start of Frame (2,048) HS 555.0 -> 810.7 0.327 386 250
IN transaction 51 1 NAK HS No data 0.583 297 550
Start of Frame (2,048) HS 811.0 -> 1,066.7 0.583 422 000
IN transaction 51 1 NAK HS No data 0.839 333 283
Start of Frame (2,048) HS 1,067.0 -> 1,322.7 0.839 457 733
IN transaction 51 1 NAK HS No data 1.095 369 050
Start of Frame (2,048) HS 1,323.0 -> 1,578.7 1.095 493 483
IN transaction 51 1 NAK HS No data 1.351 404 767
Start of Frame (2,048) HS 1,579.0 -> 1,834.7 1.351 529 233
IN transaction 51 1 NAK HS No data 1.607 440 517
Internal USB-2 hub (Dev 2) log:
Start of Frame (266) HS 258.7 -> 292.0 0.000 090 550
Incomplete IN transaction 2 1 INCOMPLETE HS No data 0.033 220 750
Start of Frame (2,048) HS 261.0 -> 516.7 0.033 345 200
Incomplete IN transaction 2 1 INCOMPLETE HS No data 0.289 256 517
Start of Frame (2,048) HS 517.0 -> 772.7 0.289 380 950
Incomplete IN transaction 2 1 INCOMPLETE HS No data 0.545 292 233
Start of Frame (2,048) HS 773.0 -> 1,028.7 0.545 416 683
Incomplete IN transaction 2 1 INCOMPLETE HS No data 0.801 328 000
[root@banunxcas29 ns06]# lspci | grep -i usb
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 05)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 05)
[root@banunxcas29 ns06]# lsusb -v -s 1:1 | grep iSerial
iSerial 1 0000:00:1a.0
Attached the files present under /sys/kernel/debug/usb/ehci/0000\:00\:1a.0/.
Thanks,
Naveen
[-- Attachment #2: async --]
[-- Type: application/octet-stream, Size: 776 bytes --]
qh/ffff8800372edd80 dev56 fs ep2 00400238 41b30000 (04048d80* data0 nak0)
ffff8800b3b8bf00*in len=1028 04048d80 urb ffff8800372ed600
ffff8800b3b8b180+in len=1028 04048d80 urb ffff8800372edf00
qh/ffff8800373990c0 dev55 fs ep2 00400237 42330000 (04048d8a* data0 nak0)
ffff8800b3b8b300*in len=1028 04048d80 urb ffff880137949300
ffff8800b3b8b060+in len=1028 04048d80 urb ffff880037399300
qh/ffff8800b3957d80 dev53 fs ep2 00400235 41330000 (04048d8a* data0 nak0)
ffff8800b3b8b840*in len=1028 04048d80 urb ffff8800b3957780
ffff8800b3b8b000+in len=1028 04048d80 urb ffff8800b3957300
qh/ffff8800b2cce780 dev52 fs ep2 00400234 40b30000 (04048d88* data0 nak0)
ffff8800b3b8b7e0*in len=1028 04048d80 urb ffff8800b2cce180
ffff8800b3b8b9c0+in len=1028 04048d80 urb ffff8800b2cce0c0
[-- Attachment #3: bandwidth --]
[-- Type: application/octet-stream, Size: 932 bytes --]
HS bandwidth allocation (us per microframe)
0: 4 0 12 12 12 0 0 0
8: 4 0 12 12 12 0 0 0
16: 4 0 12 12 12 0 0 0
24: 5 0 12 12 12 0 0 0
32: 4 0 12 12 12 0 0 0
40: 5 0 12 12 12 0 0 0
48: 4 0 12 12 12 0 0 0
56: 4 0 12 12 12 0 0 0
TT 1-1.5 port 0 FS/LS bandwidth allocation (us per frame)
96 96 96 96 96 96 96 96
FS/LS budget (us per microframe)
0: 96 0 0 0 0 0 0 0
8: 96 0 0 0 0 0 0 0
16: 96 0 0 0 0 0 0 0
24: 96 0 0 0 0 0 0 0
32: 96 0 0 0 0 0 0 0
40: 96 0 0 0 0 0 0 0
48: 96 0 0 0 0 0 0 0
56: 96 0 0 0 0 0 0 0
1-1.5.1 ep 81: 24 @ 0.0+1 mask 1c01
1-1.5.2 ep 81: 24 @ 0.0+1 mask 1c01
1-1.5.4 ep 81: 24 @ 0.0+1 mask 1c01
1-1.5.3 ep 81: 24 @ 0.0+1 mask 1c01
[-- Attachment #4: periodic --]
[-- Type: application/octet-stream, Size: 32767 bytes --]
size = 1024
0: qh1-1c01/ffff8800b2cce3c0 (f52 ep1in [1/3] q1 p16) qh1-1c01/ffff8800b3957900 (f53 ep1in [1/3] q1 p16) qh1-1c01/ffff8800372ed900 (f56 ep1in [1/3] q1 p16) qh1-1c01/ffff8800b2cceb40 (f55 ep1in [1/3] q1 p16)
1: qh1-1c01/ffff8800b2cce3c0 ... (f52 ep1in [1/3] q1 p16) qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
2: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
3: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
4: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
5: qh256-0001/ffff8800b39889c0 (h2 ep1in [1/0] q1 p1) qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
6: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
7: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
8: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
9: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
10: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
11: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
12: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
13: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
14: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
15: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
16: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
17: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
18: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
19: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
20: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
21: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
22: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
23: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
24: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
25: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
26: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
27: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
28: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
29: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
30: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
31: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
32: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
33: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
34: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
35: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
36: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
37: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
38: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
39: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
40: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
41: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
42: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
43: qh256-0001/ffff8800b3b79900 (h51 ep1in [1/0] q1 p1) qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
44: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
45: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
46: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
47: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
48: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
49: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
50: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
51: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
52: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
53: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
54: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
55: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
56: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
57: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
58: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
59: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
60: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
61: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
62: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
63: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
64: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
65: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
66: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
67: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
68: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
69: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
70: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
71: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
72: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
73: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
74: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
75: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
76: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
77: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
78: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
79: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
80: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
81: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
82: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
83: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
84: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
85: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
86: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
87: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
88: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
89: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
90: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
91: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
92: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
93: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
94: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
95: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
96: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
97: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
98: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
99: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
100: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
101: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
102: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
103: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
104: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
105: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
106: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
107: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
108: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
109: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
110: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
111: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
112: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
113: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
114: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
115: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
116: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
117: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
118: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
119: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
120: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
121: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
122: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
123: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
124: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
125: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
126: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
127: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
128: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
129: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
130: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
131: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
132: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
133: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
134: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
135: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
136: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
137: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
138: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
139: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
140: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
141: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
142: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
143: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
144: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
145: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
146: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
147: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
148: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
149: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
150: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
151: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
152: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
153: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
154: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
155: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
156: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
157: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
158: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
159: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
160: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
161: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
162: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
163: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
164: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
165: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
166: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
167: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
168: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
169: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
170: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
171: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
172: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
173: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
174: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
175: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
176: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
177: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
178: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
179: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
180: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
181: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
182: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
183: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
184: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
185: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
186: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
187: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
188: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
189: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
190: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
191: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
192: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
193: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
194: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
195: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
196: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
197: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
198: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
199: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
200: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
201: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
202: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
203: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
204: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
205: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
206: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
207: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
208: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
209: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
210: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
211: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
212: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
213: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
214: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
215: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
216: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
217: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
218: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
219: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
220: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
221: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
222: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
223: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
224: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
225: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
226: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
227: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
228: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
229: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
230: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
231: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
232: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
233: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
234: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
235: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
236: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
237: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
238: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
239: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
240: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
241: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
242: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
243: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
244: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
245: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
246: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
247: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
248: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
249: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
250: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
251: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
252: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
253: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
254: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
255: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
256: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
257: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
258: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
259: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
260: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
261: qh256-0001/ffff8800b39889c0 ... qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
262: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
263: qh1-1c01/ffff8800b2cce3c0 ... qh1-1c01/ffff8800b3957900 ... qh1-1c01/ffff8800372ed900 ... qh1-1c01/ffff8800b2cceb40
264: qh1-1c01/ffff8800b2cce3c0 ..
[-- Attachment #5: registers --]
[-- Type: application/octet-stream, Size: 503 bytes --]
bus pci, device 0000:00:1a.0
EHCI Host Controller
EHCI 1.00, rh state running
ownership 01000001 linux
SMI sts/enable 0xc0080000
structural params 0x00200002
capability params 0x00036881
status e008 Async Periodic Recl FLR
command 0010031 (park)=0 ithresh=1 Async Periodic period=1024 RUN
intrenable 37 IAA FATAL PCD ERR INT
uframe 0d58
port:1 status 001005 0 ACK POWER sig=se0 PE CONNECT
port:2 status 001000 0 ACK POWER sig=se0
irq normal 70458 err 22167 iaa 95150 (lost 0)
complete 92765 unlink 43
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
[not found] <CAG0bkv+YY90Tq1aTw1Dbg-RSVadoP2U6tyVpW1bZSxBfQ=3Y4g@mail.gmail.com>
@ 2014-11-03 16:19 ` Alan Stern
2014-11-05 6:58 ` Naveen Kumar Parna
0 siblings, 1 reply; 45+ messages in thread
From: Alan Stern @ 2014-11-03 16:19 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Mon, 3 Nov 2014, Naveen Kumar Parna wrote:
> On Sat, Nov 1, 2014 at 2:21 AM, Alan Stern <stern@rowland.harvard.edu> wrote:
> > On Wed, 29 Oct 2014, Naveen Kumar Parna wrote:
> >
> >> Split packet transactions are hidden. I could see them by clicking on
> >> the (Show/Hide Split transactions) button. For INT IN, I could see
> >> only Start Split packet.
> >>
> >> I attached([2014-10-28 session 144012] Trace0003.rar) complete log for
> >> this scenario.
> >
> > How come the log doesn't contain any SOF packets?
>
>
> To avoid recording a huge quantity of data , I enabled the "Drop Start
> of Frames" filter in the recording options.
Can you do it again, but this time keep the SOF packets?
You don't have to post the entire analyzer log. Just extract 3 or 4 ms
from the middle, where it shows the SSPLITS but no CSPLITS for the
interrupt endpoints, and post only that portion.
> > I see what you mean -- the log doesn't contain any CSPLIT transactions
> > for the interrupt endpoints. Only SSPLIT.
> >
> > I'll need to see the scheduling information for these endpoints.
> > You'll have to run a 3.13 or later kernel; then the important files
> > will be under /sys/kernel/debug/usb/ehci/X/, where X is the PCI address
> > of the EHCI controller you are using.
> >
> > Copy the files in that directory while the test is running.
> >
>
>
> I attached all the files. Please let me know if I miss anything?
All the information in the files looks correct, as far as I can see. I
have no idea why the CSPLIT packets are missing.
Alan Stern
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
[not found] ` <CAG0bkvL-qy+Wvp7q39TOaQ1dZDd0PKyoXHjO=5TrJvdC8byr8A@mail.gmail.com>
2014-10-31 11:27 ` Naveen Kumar Parna
@ 2014-10-31 20:51 ` Alan Stern
1 sibling, 0 replies; 45+ messages in thread
From: Alan Stern @ 2014-10-31 20:51 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Wed, 29 Oct 2014, Naveen Kumar Parna wrote:
> Split packet transactions are hidden. I could see them by clicking on
> the (Show/Hide Split transactions) button. For INT IN, I could see
> only Start Split packet.
>
> I attached([2014-10-28 session 144012] Trace0003.rar) complete log for
> this scenario.
How come the log doesn't contain any SOF packets?
> SSPLIT IN transaction 114 1
> HS No data 884.562 264 267
>
> SSPLIT IN transaction 115 1
> HS No data 884.562 265 217
>
> SSPLIT IN transaction 116 1
> HS No data 884.562 285 417
>
> SSPLIT IN transaction 117 1
> HS No data 884.562 286 467
I see what you mean -- the log doesn't contain any CSPLIT transactions
for the interrupt endpoints. Only SSPLIT.
I'll need to see the scheduling information for these endpoints.
You'll have to run a 3.13 or later kernel; then the important files
will be under /sys/kernel/debug/usb/ehci/X/, where X is the PCI address
of the EHCI controller you are using.
Copy the files in that directory while the test is running.
Alan Stern
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
[not found] ` <CAG0bkvL-qy+Wvp7q39TOaQ1dZDd0PKyoXHjO=5TrJvdC8byr8A@mail.gmail.com>
@ 2014-10-31 11:27 ` Naveen Kumar Parna
2014-10-31 20:51 ` Alan Stern
1 sibling, 0 replies; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-31 11:27 UTC (permalink / raw)
To: Alan Stern; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
[-- Attachment #1: Type: text/plain, Size: 4402 bytes --]
Hi ,
I tried on plenty of test servers(Fedora distribution) with USB-EHCI
and all these are having spurious STALL packets issue.
Today I got a test laptop(Ubuntu distribution) with USB-EHCI and
interestingly it does not report STALL packets. The only difference I
observed from lsusb is, Fedora test servers shows “Driver=ehci-pci/2p”
but Ubuntu Laptop shows “Driver=ehci-pci/3p”, but both has same EHCI
controller.
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 05)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 05)
Fedora test server:
[lowerlayers@banunxcas29 epipe_debug]$ lsusb -t
1-1.5.1:1.2: No such file or directory
1-1.5.2:1.2: No such file or directory
1-1.5.3:1.2: No such file or directory
1-1.5.4:1.2: No such file or directory
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
|__ Port 1: Dev 3, If 0, Class=HID, Driver=usbhid, 12M
|__ Port 1: Dev 3, If 1, Class=HID, Driver=usbhid, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
|__ Port 5: Dev 112, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 1: Dev 113, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 1: Dev 113, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 1: Dev 113, If 2, Class=app., Driver=, 12M
|__ Port 2: Dev 114, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 2: Dev 114, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 2: Dev 114, If 2, Class=app., Driver=, 12M
|__ Port 3: Dev 115, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 3: Dev 115, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 3: Dev 115, If 2, Class=app., Driver=, 12M
|__ Port 4: Dev 116, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 4: Dev 116, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 4: Dev 116, If 2, Class=app., Driver=, 12M
Ubuntu Laptop:
root@sandeep-E6410:/home/sandeep# lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
|__ Port 3: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 1: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 1: Dev 5, If 2, Class=Application Specific
Interface, Driver=, 12M
|__ Port 2: Dev 6, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 2: Dev 6, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 2: Dev 6, If 2, Class=Application Specific
Interface, Driver=, 12M
|__ Port 3: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 7, If 2, Class=Application Specific
Interface, Driver=, 12M
|__ Port 4: Dev 8, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 4: Dev 8, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 4: Dev 8, If 2, Class=Application Specific
Interface, Driver=, 12M
|__ Port 8: Dev 3, If 0, Class=Application Specific Interface,
Driver=, 12M
|__ Port 8: Dev 3, If 1, Class=Chip/SmartCard, Driver=, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
|__ Port 4: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 4: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
And in Fedora test servers Bluetooth devices are getting connected to
root_hub on the Bus-1, where as in Ubuntu Laptop these are getting
connected to root_hub on the Bus-2.
Does it gives any clue for the stall packet issue?
Thanks,
Naveen
[-- Attachment #2: lspci_nv_ubuntu --]
[-- Type: application/octet-stream, Size: 9519 bytes --]
00:00.0 0600: 8086:0044 (rev 02)
Subsystem: 1028:040a
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c <?>
Kernel driver in use: agpgart-intel
00:02.0 0300: 8086:0046 (rev 02) (prog-if 00 [VGA controller])
Subsystem: 1028:040a
Flags: bus master, fast devsel, latency 0, IRQ 42
Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 7110 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
00:19.0 0200: 8086:10ea (rev 05)
Subsystem: 1028:040a
Flags: bus master, fast devsel, latency 0, IRQ 40
Memory at f6900000 (32-bit, non-prefetchable) [size=128K]
Memory at f6970000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 7020 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
00:1a.0 0c03: 8086:3b3c (rev 05) (prog-if 20 [EHCI])
Subsystem: 1028:040a
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at f6960000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci-pci
00:1b.0 0403: 8086:3b56 (rev 05)
Subsystem: 1028:040a
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at f6950000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: snd_hda_intel
00:1c.0 0604: 8086:3b42 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00006000-00006fff
Memory behind bridge: f5500000-f68fffff
Prefetchable memory behind bridge: 00000000f6a00000-00000000f6bfffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 1028:040a
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
00:1c.1 0604: 8086:3b44 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 00005000-00005fff
Memory behind bridge: f4100000-f54fffff
Prefetchable memory behind bridge: 00000000f6c00000-00000000f6dfffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 1028:040a
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
00:1c.2 0604: 8086:3b46 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=04, sec-latency=0
I/O behind bridge: 00002000-00003fff
Memory behind bridge: f0400000-f2cfffff
Prefetchable memory behind bridge: 00000000f6e00000-00000000f6ffffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 1028:040a
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
00:1c.3 0604: 8086:3b48 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=05, subordinate=0a, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: f2d00000-f40fffff
Prefetchable memory behind bridge: 00000000f7000000-00000000f71fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 1028:040a
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
00:1d.0 0c03: 8086:3b34 (rev 05) (prog-if 20 [EHCI])
Subsystem: 1028:040a
Flags: bus master, medium devsel, latency 0, IRQ 17
Memory at f6940000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci-pci
00:1e.0 0604: 8086:2448 (rev a5) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0
Capabilities: [50] Subsystem: 1028:040a
00:1f.0 0601: 8086:3b07 (rev 05)
Subsystem: 1028:040a
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=10 <?>
Kernel driver in use: lpc_ich
00:1f.2 0101: 8086:3b2e (rev 05) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: 1028:040a
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 18
I/O ports at 70f0 [size=8]
I/O ports at 70e0 [size=4]
I/O ports at 70d0 [size=8]
I/O ports at 70c0 [size=4]
I/O ports at 70b0 [size=16]
I/O ports at 70a0 [size=16]
Capabilities: [70] Power Management version 3
Capabilities: [b0] PCI Advanced Features
Kernel driver in use: ata_piix
00:1f.3 0c05: 8086:3b30 (rev 05)
Subsystem: 1028:040a
Flags: medium devsel, IRQ 10
Memory at f6930000 (64-bit, non-prefetchable) [size=256]
I/O ports at 7000 [size=32]
00:1f.5 0101: 8086:3b2d (rev 05) (prog-if 85 [Master SecO PriO])
Subsystem: 1028:040a
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 18
I/O ports at 7090 [size=8]
I/O ports at 7080 [size=4]
I/O ports at 7070 [size=8]
I/O ports at 7060 [size=4]
I/O ports at 7050 [size=16]
I/O ports at 7040 [size=16]
Capabilities: [70] Power Management version 3
Capabilities: [b0] PCI Advanced Features
Kernel driver in use: ata_piix
00:1f.6 1180: 8086:3b32 (rev 05)
Subsystem: 1028:040a
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at f6920000 (64-bit, non-prefetchable) [size=4K]
Capabilities: [50] Power Management version 3
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Kernel driver in use: intel ips
02:00.0 0280: 8086:422c (rev 35)
Subsystem: 8086:1321
Flags: bus master, fast devsel, latency 0, IRQ 41
Memory at f4100000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 58-94-6b-ff-ff-5d-25-2c
Kernel driver in use: iwlwifi
03:00.0 0805: 1180:e822 (rev 03) (prog-if 01)
Subsystem: 1028:040a
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at f2c40000 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Power Management version 3
Capabilities: [80] Express Endpoint, MSI 00
Kernel driver in use: sdhci-pci
03:00.4 0c00: 1180:e832 (rev 03) (prog-if 10 [OHCI])
Subsystem: 1028:040a
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f2c00000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Power Management version 3
Capabilities: [80] Express Endpoint, MSI 00
Kernel driver in use: firewire_ohci
05:00.0 0880: 197b:2382
Subsystem: 197b:2382
Physical Slot: 1
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at f2d40000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at f2d30000 [disabled] [size=64K]
Capabilities: [a4] Power Management version 3
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [94] MSI: Enable- Count=1/1 Maskable- 64bit-
Kernel driver in use: sdhci-pci
05:00.2 0805: 197b:2381 (prog-if 01)
Subsystem: 197b:2381
Physical Slot: 1
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at f2d20000 (32-bit, non-prefetchable) [size=256]
Capabilities: [a4] Power Management version 3
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [94] MSI: Enable- Count=1/1 Maskable- 64bit-
Kernel driver in use: slot_shc
05:00.3 0880: 197b:2383
Subsystem: 197b:2383
Physical Slot: 1
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at f2d10000 (32-bit, non-prefetchable) [size=256]
Capabilities: [a4] Power Management version 3
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [94] MSI: Enable- Count=1/1 Maskable- 64bit-
Kernel driver in use: jmb38x_ms
05:00.4 0880: 197b:2384
Subsystem: 197b:2384
Physical Slot: 1
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at f2d00000 (32-bit, non-prefetchable) [size=256]
Capabilities: [a4] Power Management version 3
Capabilities: [80] Express Endpoint, MSI 00
Capabilities: [94] MSI: Enable- Count=1/1 Maskable- 64bit-
3f:00.0 0600: 8086:2c62 (rev 02)
Subsystem: 8086:8086
Flags: bus master, fast devsel, latency 0
3f:00.1 0600: 8086:2d01 (rev 02)
Subsystem: 8086:8086
Flags: bus master, fast devsel, latency 0
3f:02.0 0600: 8086:2d10 (rev 02)
Subsystem: 8086:8086
Flags: bus master, fast devsel, latency 0
3f:02.1 0600: 8086:2d11 (rev 02)
Subsystem: 8086:8086
Flags: bus master, fast devsel, latency 0
3f:02.2 0600: 8086:2d12 (rev 02)
Subsystem: 8086:8086
Flags: bus master, fast devsel, latency 0
3f:02.3 0600: 8086:2d13 (rev 02)
Subsystem: 8086:8086
Flags: bus master, fast devsel, latency 0
[-- Attachment #3: lspci_nv_fedora --]
[-- Type: application/octet-stream, Size: 8908 bytes --]
00:00.0 0600: 8086:d130 (rev 11)
Subsystem: 103c:3318
Flags: fast devsel
Capabilities: [40] #00 [0000]
00:03.0 0604: 8086:d138 (rev 11) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 00002000-00002fff
Memory behind bridge: de900000-deffffff
Capabilities: [40] Subsystem: 103c:3318
Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit-
Capabilities: [90] Express Root Port (Slot-), MSI 00
Capabilities: [e0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [150] Access Control Services
Capabilities: [160] Vendor Specific Information: ID=0002 Rev=0 Len=00c <?>
Kernel driver in use: pcieport
00:08.0 0880: 8086:d155 (rev 11)
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Vendor Specific Information: ID=0000 Rev=0 Len=000 <?>
00:08.1 0880: 8086:d156 (rev 11)
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Vendor Specific Information: ID=0000 Rev=0 Len=000 <?>
00:08.2 0880: 8086:d157 (rev 11)
Flags: fast devsel
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Vendor Specific Information: ID=0000 Rev=0 Len=000 <?>
00:08.3 0880: 8086:d158 (rev 11)
Flags: fast devsel
00:10.0 0880: 8086:d150 (rev 11)
Flags: fast devsel
00:10.1 0880: 8086:d151 (rev 11)
Flags: fast devsel
00:1a.0 0c03: 8086:3b3c (rev 05) (prog-if 20 [EHCI])
Subsystem: 103c:3118
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at df401800 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci-pci
00:1c.0 0604: 8086:3b42 (rev 05) (prog-if 00 [Normal decode])
Physical Slot: 2
Flags: fast devsel
Bus: primary=00, secondary=10, subordinate=10, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: c0000000-c01fffff
Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 103c:3318
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
00:1c.4 0604: 8086:3b4a (rev 05) (prog-if 00 [Normal decode])
Physical Slot: 2
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=20, subordinate=20, sec-latency=0
I/O behind bridge: 00004000-00004fff
Memory behind bridge: df000000-df0fffff
Prefetchable memory behind bridge: 00000000c0400000-00000000c05fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 103c:3318
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
00:1c.5 0604: 8086:3b4c (rev 05) (prog-if 00 [Normal decode])
Physical Slot: 2
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=22, subordinate=22, sec-latency=0
I/O behind bridge: 00005000-00005fff
Memory behind bridge: df100000-df1fffff
Prefetchable memory behind bridge: 00000000c0600000-00000000c07fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 103c:3318
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
00:1c.6 0604: 8086:3b4e (rev 05) (prog-if 00 [Normal decode])
Physical Slot: 2
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=24, subordinate=24, sec-latency=0
I/O behind bridge: 00006000-00006fff
Memory behind bridge: de000000-de8fffff
Prefetchable memory behind bridge: 00000000dd000000-00000000ddffffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 103c:3318
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
00:1c.7 0604: 8086:3b50 (rev 05) (prog-if 00 [Normal decode])
Physical Slot: 2
Flags: fast devsel
Bus: primary=00, secondary=26, subordinate=26, sec-latency=0
I/O behind bridge: 00007000-00007fff
Memory behind bridge: c0800000-c09fffff
Prefetchable memory behind bridge: 00000000c0a00000-00000000c0bfffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 103c:3318
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport
00:1d.0 0c03: 8086:3b34 (rev 05) (prog-if 20 [EHCI])
Subsystem: 103c:3118
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at df401c00 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci-pci
00:1e.0 0604: 8086:244e (rev a5) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=30, subordinate=30, sec-latency=32
Capabilities: [50] Subsystem: 103c:3318
00:1f.0 0601: 8086:3b14 (rev 05)
Subsystem: 103c:3118
Flags: bus master, medium devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=10 <?>
Kernel driver in use: lpc_ich
00:1f.2 0101: 8086:3b20 (rev 05) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: 103c:3118
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 18
I/O ports at 1830 [size=8]
I/O ports at 1824 [size=4]
I/O ports at 1828 [size=8]
I/O ports at 1820 [size=4]
I/O ports at 1810 [size=16]
I/O ports at 1800 [size=16]
Capabilities: [70] Power Management version 3
Capabilities: [b0] PCI Advanced Features
Kernel driver in use: ata_piix
00:1f.3 0c05: 8086:3b30 (rev 05)
Subsystem: 103c:3318
Flags: medium devsel, IRQ 18
Memory at df402000 (64-bit, non-prefetchable) [size=256]
I/O ports at 1840 [size=32]
Kernel driver in use: i801_smbus
00:1f.5 0101: 8086:3b26 (rev 05) (prog-if 85 [Master SecO PriO])
Subsystem: 103c:3118
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 17
I/O ports at 1888 [size=8]
I/O ports at 183c [size=4]
I/O ports at 1880 [size=8]
I/O ports at 1838 [size=4]
I/O ports at 1870 [size=16]
I/O ports at 1860 [size=16]
Capabilities: [70] Power Management version 3
Capabilities: [b0] PCI Advanced Features
Kernel driver in use: ata_piix
01:00.0 0104: 103c:323a (rev 01)
Subsystem: 103c:3241
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at dec00000 (64-bit, non-prefetchable) [size=4M]
Memory at de900000 (64-bit, non-prefetchable) [size=4K]
I/O ports at 2000 [size=256]
[virtual] Expansion ROM at de980000 [disabled] [size=512K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [ac] MSI-X: Enable+ Count=16 Masked-
Capabilities: [100] Advanced Error Reporting
Kernel driver in use: hpsa
20:00.0 0200: 14e4:165b (rev 10)
Subsystem: 103c:705d
Flags: bus master, fast devsel, latency 0, IRQ 37
Memory at df000000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [48] Power Management version 3
Capabilities: [40] Vital Product Data
Capabilities: [60] Vendor Specific Information: Len=6c <?>
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [cc] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 2c-41-38-ff-fe-88-24-04
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: tg3
22:00.0 0200: 14e4:165b (rev 10)
Subsystem: 103c:705d
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at df100000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [48] Power Management version 3
Capabilities: [40] Vital Product Data
Capabilities: [60] Vendor Specific Information: Len=6c <?>
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [cc] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [13c] Virtual Channel
Capabilities: [160] Device Serial Number 2c-41-38-ff-fe-88-24-05
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: tg3
24:00.0 0300: 102b:0522 (rev 02) (prog-if 00 [VGA controller])
Subsystem: 103c:31fa
Flags: bus master, fast devsel, latency 0, IRQ 10
Memory at dd000000 (32-bit, prefetchable) [size=16M]
Memory at de800000 (32-bit, non-prefetchable) [size=16K]
Memory at de000000 (32-bit, non-prefetchable) [size=8M]
[virtual] Expansion ROM at de810000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
Capabilities: [e4] Express Legacy Endpoint, MSI 00
Capabilities: [54] MSI: Enable- Count=1/1 Maskable- 64bit-
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-28 12:40 ` Naveen Kumar Parna
@ 2014-10-28 17:27 ` Alan Stern
[not found] ` <CAG0bkvL-qy+Wvp7q39TOaQ1dZDd0PKyoXHjO=5TrJvdC8byr8A@mail.gmail.com>
0 siblings, 1 reply; 45+ messages in thread
From: Alan Stern @ 2014-10-28 17:27 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Tue, 28 Oct 2014, Naveen Kumar Parna wrote:
> >> You should also run a similar test when you connect the device through
> >> a USB-2 hub. In fact, you should run two tests. In one test, connect
> >> the analyzer to the cable segment between the computer and the hub; in
> >> the other test, connect the analyzer to the cable segment between the
> >> hub and the device.
> >>
> >
>
> I connected the USB analyzer to the cable segment between the computer
> and the external USB-2 hub(devices are attached to this external USB-2
> hub). In this scenario , got the stall in usbmon trace, but not in
> analyzer log. But USB analyzer log shows “Incomplete IN transaction”.
> Please check the attached "Elisys_Usb_log.png".
>
>
>
> Incomplete IN transaction 2 1
> INCOMPLETE HS No data 884.626 273 217
> Does it gives any clue?
Not really. I think your analyzer output is incomplete. For example,
a high-speed Interrupt transaction to a full-speed device should have a
Start Split packet and a Complete Split packet. I don't see either of
those in your picture.
> For the second test(connect the analyzer to the cable segment between
> the hub and the device): Is it possible with single external USB hub?
Of course it is. What's the difficulty?
Alan Stern
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-16 15:32 ` Naveen Kumar Parna
@ 2014-10-28 12:40 ` Naveen Kumar Parna
2014-10-28 17:27 ` Alan Stern
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-28 12:40 UTC (permalink / raw)
To: Alan Stern; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
[-- Attachment #1: Type: text/plain, Size: 2485 bytes --]
>
>> You should also run a similar test when you connect the device through
>> a USB-2 hub. In fact, you should run two tests. In one test, connect
>> the analyzer to the cable segment between the computer and the hub; in
>> the other test, connect the analyzer to the cable segment between the
>> hub and the device.
>>
>
I connected the USB analyzer to the cable segment between the computer
and the external USB-2 hub(devices are attached to this external USB-2
hub). In this scenario , got the stall in usbmon trace, but not in
analyzer log. But USB analyzer log shows “Incomplete IN transaction”.
Please check the attached "Elisys_Usb_log.png".
Incomplete IN transaction 2 1
INCOMPLETE HS No data 884.626 273 217
Incomplete IN transaction 2 1
INCOMPLETE HS No data 884.882 309 000
Incomplete IN transaction 2 1
INCOMPLETE HS No data 885.138 344 750
Incomplete IN transaction 2 1
INCOMPLETE HS No data 885.394 380 533
Incomplete IN transaction 2 1
INCOMPLETE HS No data 885.650 416 300
Incomplete IN transaction 2 1
INCOMPLETE HS No data 885.906 452 050
Incomplete IN transaction 2 1
INCOMPLETE HS No data 886.162 487 833
Incomplete IN transaction 2 1
INCOMPLETE HS No data 886.418 523 583
Incomplete IN transaction 2 1
INCOMPLETE HS No data 886.674 559 367
Incomplete IN transaction 2 1
INCOMPLETE HS No data 886.930 595 117
Incomplete IN transaction 2 1
INCOMPLETE HS No data 887.186 630 883
Incomplete IN transaction 2 1
INCOMPLETE HS No data 887.442 666 667
Incomplete IN transaction 2 1
INCOMPLETE HS No data 887.698 702 417
Does it gives any clue?
For the second test(connect the analyzer to the cable segment between
the hub and the device): Is it possible with single external USB hub?
Thanks,
Naveen
[-- Attachment #2: Elisys_Usb_log.png --]
[-- Type: image/png, Size: 212397 bytes --]
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-16 14:09 ` Alan Stern
2014-10-16 15:05 ` Naveen Kumar Parna
@ 2014-10-27 9:19 ` Naveen Kumar Parna
1 sibling, 0 replies; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-27 9:19 UTC (permalink / raw)
To: Alan Stern; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Thu, Oct 16, 2014 at 7:39 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Thu, 16 Oct 2014, Naveen Kumar Parna wrote:
>
>> > Indeed. However, it is possible to use an additional in between your
>> > devices and the internal hub.
>> >
>> > Regards
>> > Oliver
>> >
>> >
>>
>>
>> Tested with this configuration(external hubs Dev 3, Dev 4, Dev 17, Dev
>> 10) and got the same result.
>>
>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
>>
>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
>>
>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>
>> |__ Port 5: Dev 3, If 0, Class=hub, Driver=hub/7p, 12M
>>
>> |__ Port 1: Dev 4, If 0, Class=hub, Driver=hub/7p, 12M
>
> This is not what Oliver meant. You have to use a USB-2 hub. And
> having one of them is enough; you don't need two.
>
> Alan Stern
>
As suggested, I connected USB-2 hub(Dev 87) in between my devices and
the internal hub. In this scenario also observed the STALL packets.
I am interested in understanding the objective of this test, can you
please help me?
[lowerlayers@banunxcas29 ~]$ lsusb -t
1-1.5.1:1.2: No such file or directory
1-1.5.3:1.2: No such file or directory
1-1.5.4:1.2: No such file or directory
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
|__ Port 5: Dev 87, If 0, Class=hub, Driver=hub/4p, 480M
|__ Port 1: Dev 88, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 1: Dev 88, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 1: Dev 88, If 2, Class=app., Driver=, 12M
|__ Port 3: Dev 90, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 3: Dev 90, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 3: Dev 90, If 2, Class=app., Driver=, 12M
|__ Port 4: Dev 89, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 4: Dev 89, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 4: Dev 89, If 2, Class=app., Driver=, 12M
[root@banunxcas29 ~]# cat /sys/kernel/debug/usb/usbmon/1u
ffff8800b2036540 2419900733 C Ii:1:090:1 -32:1 0
ffff8800b2036540 2419900753 S Ii:1:090:1 -115:1 16 <
ffff8800b2036540 963424773 C Ii:1:090:1 -32:1 0
ffff8800b2036540 963424792 S Ii:1:090:1 -115:1 16 <
ffff8800b2036540 963448864 C Ii:1:090:1 -32:1 0
ffff8800b2036540 963448880 S Ii:1:090:1 -115:1 16 <
/var/log/kernel
Oct 27 13:21:15 banunxcas29 kernel: [1017571.251514] hci2 urb
ffff8800b2036540 status -32 count 0
Oct 27 14:05:15 banunxcas29 kernel: [1020211.003086] hci2 urb
ffff8800b2036540 status -32 count 0
Oct 27 14:05:15 banunxcas29 kernel: [1020211.027178] hci2 urb
ffff8800b2036540 status -32 count 0
Thanks,
Naveen
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-16 14:16 ` Alan Stern
@ 2014-10-16 15:32 ` Naveen Kumar Parna
2014-10-28 12:40 ` Naveen Kumar Parna
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-16 15:32 UTC (permalink / raw)
To: Alan Stern; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Thu, Oct 16, 2014 at 7:46 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Thu, 16 Oct 2014, Naveen Kumar Parna wrote:
>
>> > It's entirely possible that the stall packets are created by the hub.
>> > When a full-speed device is connected to a USB-2 hub, and the device
>> > fails to respond to a packet sent by the host, the hub reports this
>> > failure as a stall.
>>
>> Here I don’t think device fails to respond to a packet sent by the
>> host. I verified this by connecting Ellisys USB analyser in between
>> host and devices.
>>
>> For example Look at the attached(Sample_HciEvt.png) HCI event captured
>> by Ellisys USB analyser. It is a valid HCI event from device to Host.
>> IN transaction 96 1 ACK FS 16 bytes (FF 2F C2 01 00 17 00 DF 00 01 10
>> 00 00 A9 EE 0F)
>> IN transaction 96 1 ACK FS 16 bytes (00 00 00 5A 06 9D 39 00 00 66 00
>> 00 00 00 00 00)
>> IN transaction 96 1 ACK FS 16 bytes (00 00 00 00 00 00 00 00 00 00 00
>> 8E 05 28 00 01)
>> IN transaction 96 1 ACK FS 1 byte (00)
>
> This doesn't prove anything. All it means is that the device responded
> properly on these four occasions. What if the device failed to respond
> on some other occasion? You have to compare the output of the analyzer
> with the output from usbmon. If usbmon shows a STALL and the analyzer
> shows a valid reply for the very same packet, then you'll know the
> device isn't at fault.
>
I forgot to post usbmon log, but usbmon shows a STALL and the analyser
shows a valid reply for the very same packet.
I tried this many number of times and always got same result.
But did not get STALL on OHCI-USB host controller on PCI card with
internal USB 1.1 hub. In both the scenario’s I used same devices.
> You should also run a similar test when you connect the device through
> a USB-2 hub. In fact, you should run two tests. In one test, connect
> the analyzer to the cable segment between the computer and the hub; in
> the other test, connect the analyzer to the cable segment between the
> hub and the device.
>
Ok, I will try and update you on this.
Thanks,
Naveen
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-16 14:09 ` Alan Stern
@ 2014-10-16 15:05 ` Naveen Kumar Parna
2014-10-27 9:19 ` Naveen Kumar Parna
1 sibling, 0 replies; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-16 15:05 UTC (permalink / raw)
To: Alan Stern; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
Ok, I will do this and update you.
But Currently I am on long leave and I can update you on 27th Oct.
Thanks,
Naveen
On Thu, Oct 16, 2014 at 7:39 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Thu, 16 Oct 2014, Naveen Kumar Parna wrote:
>
>> > Indeed. However, it is possible to use an additional in between your
>> > devices and the internal hub.
>> >
>> > Regards
>> > Oliver
>> >
>> >
>>
>>
>> Tested with this configuration(external hubs Dev 3, Dev 4, Dev 17, Dev
>> 10) and got the same result.
>>
>> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
>>
>> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
>>
>> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>>
>> |__ Port 5: Dev 3, If 0, Class=hub, Driver=hub/7p, 12M
>>
>> |__ Port 1: Dev 4, If 0, Class=hub, Driver=hub/7p, 12M
>
> This is not what Oliver meant. You have to use a USB-2 hub. And
> having one of them is enough; you don't need two.
>
> Alan Stern
>
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-16 7:13 ` Naveen Kumar Parna
@ 2014-10-16 14:16 ` Alan Stern
2014-10-16 15:32 ` Naveen Kumar Parna
0 siblings, 1 reply; 45+ messages in thread
From: Alan Stern @ 2014-10-16 14:16 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Thu, 16 Oct 2014, Naveen Kumar Parna wrote:
> > It's entirely possible that the stall packets are created by the hub.
> > When a full-speed device is connected to a USB-2 hub, and the device
> > fails to respond to a packet sent by the host, the hub reports this
> > failure as a stall.
>
> Here I don’t think device fails to respond to a packet sent by the
> host. I verified this by connecting Ellisys USB analyser in between
> host and devices.
>
> For example Look at the attached(Sample_HciEvt.png) HCI event captured
> by Ellisys USB analyser. It is a valid HCI event from device to Host.
> IN transaction 96 1 ACK FS 16 bytes (FF 2F C2 01 00 17 00 DF 00 01 10
> 00 00 A9 EE 0F)
> IN transaction 96 1 ACK FS 16 bytes (00 00 00 5A 06 9D 39 00 00 66 00
> 00 00 00 00 00)
> IN transaction 96 1 ACK FS 16 bytes (00 00 00 00 00 00 00 00 00 00 00
> 8E 05 28 00 01)
> IN transaction 96 1 ACK FS 1 byte (00)
This doesn't prove anything. All it means is that the device responded
properly on these four occasions. What if the device failed to respond
on some other occasion? You have to compare the output of the analyzer
with the output from usbmon. If usbmon shows a STALL and the analyzer
shows a valid reply for the very same packet, then you'll know the
device isn't at fault.
You should also run a similar test when you connect the device through
a USB-2 hub. In fact, you should run two tests. In one test, connect
the analyzer to the cable segment between the computer and the hub; in
the other test, connect the analyzer to the cable segment between the
hub and the device.
Alan Stern
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-16 10:54 ` Naveen Kumar Parna
@ 2014-10-16 14:09 ` Alan Stern
2014-10-16 15:05 ` Naveen Kumar Parna
2014-10-27 9:19 ` Naveen Kumar Parna
0 siblings, 2 replies; 45+ messages in thread
From: Alan Stern @ 2014-10-16 14:09 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Thu, 16 Oct 2014, Naveen Kumar Parna wrote:
> > Indeed. However, it is possible to use an additional in between your
> > devices and the internal hub.
> >
> > Regards
> > Oliver
> >
> >
>
>
> Tested with this configuration(external hubs Dev 3, Dev 4, Dev 17, Dev
> 10) and got the same result.
>
> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
>
> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
>
> |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
>
> |__ Port 5: Dev 3, If 0, Class=hub, Driver=hub/7p, 12M
>
> |__ Port 1: Dev 4, If 0, Class=hub, Driver=hub/7p, 12M
This is not what Oliver meant. You have to use a USB-2 hub. And
having one of them is enough; you don't need two.
Alan Stern
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-16 9:15 ` Oliver Neukum
@ 2014-10-16 10:54 ` Naveen Kumar Parna
2014-10-16 14:09 ` Alan Stern
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-16 10:54 UTC (permalink / raw)
To: Oliver Neukum; +Cc: Alan Stern, linux-bluetooth, linux-usb, acho
On Thu, Oct 16, 2014 at 2:45 PM, Oliver Neukum <oneukum@suse.de> wrote:
>
> On Wed, 2014-10-15 at 12:11 -0400, Alan Stern wrote:
> > > If the hub is the problem… what will be the better solution? Is it
> > > possible to change internal hub?
> >
> > No, it is not possible.
>
> Indeed. However, it is possible to use an additional in between your
> devices and the internal hub.
>
> Regards
> Oliver
>
>
Tested with this configuration(external hubs Dev 3, Dev 4, Dev 17, Dev
10) and got the same result.
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/6p, 480M
|__ Port 5: Dev 3, If 0, Class=hub, Driver=hub/7p, 12M
|__ Port 1: Dev 4, If 0, Class=hub, Driver=hub/7p, 12M
|__ Port 1: Dev 11, If 0, Class=vend., Driver=, 12M
|__ Port 2: Dev 12, If 0, Class=vend., Driver=, 12M
|__ Port 3: Dev 13, If 0, Class=vend., Driver=, 12M
|__ Port 4: Dev 14, If 0, Class=vend., Driver=, 12M
|__ Port 5: Dev 15, If 0, Class=vend., Driver=, 12M
|__ Port 6: Dev 16, If 0, Class=vend., Driver=, 12M
|__ Port 7: Dev 17, If 0, Class=hub, Driver=hub/2p, 12M
|__ Port 1: Dev 21, If 0, Class=vend., Driver=, 12M
|__ Port 2: Dev 22, If 0, Class=vend., Driver=, 12M
|__ Port 2: Dev 5, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 2: Dev 5, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 2: Dev 5, If 2, Class=app., Driver=, 12M
|__ Port 3: Dev 6, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 3: Dev 6, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 3: Dev 6, If 2, Class=app., Driver=, 12M
|__ Port 4: Dev 7, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 4: Dev 7, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 4: Dev 7, If 2, Class=app., Driver=, 12M
|__ Port 5: Dev 8, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 5: Dev 8, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 5: Dev 8, If 2, Class=app., Driver=, 12M
|__ Port 6: Dev 9, If 0, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 6: Dev 9, If 1, Class='bInterfaceClass 0xe0 not
yet handled', Driver=btusb, 12M
|__ Port 6: Dev 9, If 2, Class=app., Driver=, 12M
|__ Port 7: Dev 10, If 0, Class=hub, Driver=hub/3p, 12M
|__ Port 1: Dev 18, If 0, Class='bInterfaceClass 0xe0
not yet handled', Driver=btusb, 12M
|__ Port 1: Dev 18, If 1, Class='bInterfaceClass 0xe0
not yet handled', Driver=btusb, 12M
|__ Port 1: Dev 18, If 2, Class=app., Driver=, 12M
|__ Port 2: Dev 19, If 0, Class='bInterfaceClass 0xe0
not yet handled', Driver=btusb, 12M
|__ Port 2: Dev 19, If 1, Class='bInterfaceClass 0xe0
not yet handled', Driver=btusb, 12M
|__ Port 2: Dev 19, If 2, Class=app., Driver=, 12M
|__ Port 3: Dev 20, If 0, Class='bInterfaceClass 0xe0
not yet handled', Driver=btusb, 12M
|__ Port 3: Dev 20, If 1, Class='bInterfaceClass 0xe0
not yet handled', Driver=btusb, 12M
|__ Port 3: Dev 20, If 2, Class=app., Driver=, 12M
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-15 16:11 ` Alan Stern
2014-10-16 7:13 ` Naveen Kumar Parna
@ 2014-10-16 9:15 ` Oliver Neukum
2014-10-16 10:54 ` Naveen Kumar Parna
1 sibling, 1 reply; 45+ messages in thread
From: Oliver Neukum @ 2014-10-16 9:15 UTC (permalink / raw)
To: Alan Stern; +Cc: Naveen Kumar Parna, linux-bluetooth, linux-usb, acho
On Wed, 2014-10-15 at 12:11 -0400, Alan Stern wrote:
> > If the hub is the problem… what will be the better solution? Is it
> > possible to change internal hub?
>
> No, it is not possible.
Indeed. However, it is possible to use an additional in between your
devices and the internal hub.
Regards
Oliver
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-15 16:11 ` Alan Stern
@ 2014-10-16 7:13 ` Naveen Kumar Parna
2014-10-16 14:16 ` Alan Stern
2014-10-16 9:15 ` Oliver Neukum
1 sibling, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-16 7:13 UTC (permalink / raw)
To: Alan Stern; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]
> It's entirely possible that the stall packets are created by the hub.
> When a full-speed device is connected to a USB-2 hub, and the device
> fails to respond to a packet sent by the host, the hub reports this
> failure as a stall.
Here I don’t think device fails to respond to a packet sent by the
host. I verified this by connecting Ellisys USB analyser in between
host and devices.
For example Look at the attached(Sample_HciEvt.png) HCI event captured
by Ellisys USB analyser. It is a valid HCI event from device to Host.
IN transaction 96 1 ACK FS 16 bytes (FF 2F C2 01 00 17 00 DF 00 01 10
00 00 A9 EE 0F)
IN transaction 96 1 ACK FS 16 bytes (00 00 00 5A 06 9D 39 00 00 66 00
00 00 00 00 00)
IN transaction 96 1 ACK FS 16 bytes (00 00 00 00 00 00 00 00 00 00 00
8E 05 28 00 01)
IN transaction 96 1 ACK FS 1 byte (00)
Due to spurious stall packets , sometimes btusb driver is not
receiving this full event , instead it got STALL packet instead of
first 16 bytes plus rest of other 33 bytes.
> When the device is connected to an OHCI controller, such failures would
> be reported in a different way, such as a -EPROTO or -EILSEQ status.
>
I did not observed -EPROTO or -EILSEQ status in OHCI controller scenario.
Thanks,
Naveen
[-- Attachment #2: Sample_HciEvt.png --]
[-- Type: image/png, Size: 7343 bytes --]
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-15 13:46 ` Naveen Kumar Parna
@ 2014-10-15 16:11 ` Alan Stern
2014-10-16 7:13 ` Naveen Kumar Parna
2014-10-16 9:15 ` Oliver Neukum
0 siblings, 2 replies; 45+ messages in thread
From: Alan Stern @ 2014-10-15 16:11 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Wed, 15 Oct 2014, Naveen Kumar Parna wrote:
> Hi Oliver,
>
> I tried this test in two different set of hardware configurations.
>
>
>
> i) I tried in multiple test systems which has
> EHCI-USB host controller on PCI card and internal USB 2.0
> hub("rate-matching" hub). All the test systems with this configuration
> gives spurious stall packets.
>
> [lowerlayers@banunxcas29 ~]$ lspci | grep -i usb
>
> 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
> USB2 Enhanced Host Controller (rev 05)
>
> 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
> USB2 Enhanced Host Controller (rev 05)
>
>
> lsusb:
>
> Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
>
> Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
>
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
>
>
>
>
> ii) I found different test systems which has
> OHCI-USB host controller on PCI card and internal USB 1.1 hub. All the
> test systems with this configuration are not producing stall packets.
>
> [lowerlayers@camunxcas11 ~]$ lspci | grep -i usb
>
> 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
>
> 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
>
>
> lsusb:
>
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> Bus 002 Device 002: ID 0451:2077 Texas Instruments, Inc. TUSB2077 Hub
>
>
>
>
> My device is a full-speed device. So , stall packets are due to buggy
> USB 2.0 hub?
It's entirely possible that the stall packets are created by the hub.
When a full-speed device is connected to a USB-2 hub, and the device
fails to respond to a packet sent by the host, the hub reports this
failure as a stall.
When the device is connected to an OHCI controller, such failures would
be reported in a different way, such as a -EPROTO or -EILSEQ status.
> Is there a chance of getting stall packets “If the device runs at low
> speed or full speed and is connected through a USB-2.0 hub”? If so it
> looks like hub driver issue right?
If the problem is that the device fails to respond to a packet then it
is an issue with the device.
> If the hub is the problem… what will be the better solution? Is it
> possible to change internal hub?
No, it is not possible.
Alan Stern
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-15 13:09 ` Naveen Kumar Parna
@ 2014-10-15 13:46 ` Naveen Kumar Parna
2014-10-15 16:11 ` Alan Stern
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-15 13:46 UTC (permalink / raw)
To: Oliver Neukum; +Cc: Alan Stern, linux-bluetooth, linux-usb, acho
Hi Oliver,
I tried this test in two different set of hardware configurations.
i) I tried in multiple test systems which has
EHCI-USB host controller on PCI card and internal USB 2.0
hub("rate-matching" hub). All the test systems with this configuration
gives spurious stall packets.
[lowerlayers@banunxcas29 ~]$ lspci | grep -i usb
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 05)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset
USB2 Enhanced Host Controller (rev 05)
lsusb:
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ii) I found different test systems which has
OHCI-USB host controller on PCI card and internal USB 1.1 hub. All the
test systems with this configuration are not producing stall packets.
[lowerlayers@camunxcas11 ~]$ lspci | grep -i usb
00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
lsusb:
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0451:2077 Texas Instruments, Inc. TUSB2077 Hub
My device is a full-speed device. So , stall packets are due to buggy
USB 2.0 hub?
Is there a chance of getting stall packets “If the device runs at low
speed or full speed and is connected through a USB-2.0 hub”? If so it
looks like hub driver issue right?
If the hub is the problem… what will be the better solution? Is it
possible to change internal hub?
Thanks,
Naveen
On Wed, Oct 15, 2014 at 6:39 PM, Naveen Kumar Parna
<pnaveenkos@gmail.com> wrote:
> EHCI controller on PCI card and hub("rate-matching" hub) also internal.
>
> Is it possible to change the internal hub?
>
>
>
> Thanks,
> Naveen
>
> On Wed, Oct 15, 2014 at 3:41 PM, Oliver Neukum <oneukum@suse.de> wrote:
>> On Thu, 2014-10-09 at 10:31 -0400, Alan Stern wrote:
>>> On Thu, 9 Oct 2014, Naveen Kumar Parna wrote:
>>>
>>> > Hi Oliver & Alan,
>>> >
>>> >
>>> >
>>> > Thanks for your inputs.
>>> >
>>> >
>>> >
>>> > I enabled the dynamic debugging for USB HC driver. Please correct me
>>> > if I am wrong.
>>>
>>> Debugging the kernel (or doing anything else to the kernel, for that
>>> matter) won't solve the problem if it is caused by a buggy hub.
>>
>> Indeed. Could you just try a different hub?
>>
>> Regards
>> Oliver
>>
>>
>>
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-15 10:11 ` Oliver Neukum
@ 2014-10-15 13:09 ` Naveen Kumar Parna
2014-10-15 13:46 ` Naveen Kumar Parna
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-15 13:09 UTC (permalink / raw)
To: Oliver Neukum; +Cc: Alan Stern, linux-bluetooth, linux-usb, acho
EHCI controller on PCI card and hub("rate-matching" hub) also internal.
Is it possible to change the internal hub?
Thanks,
Naveen
On Wed, Oct 15, 2014 at 3:41 PM, Oliver Neukum <oneukum@suse.de> wrote:
> On Thu, 2014-10-09 at 10:31 -0400, Alan Stern wrote:
>> On Thu, 9 Oct 2014, Naveen Kumar Parna wrote:
>>
>> > Hi Oliver & Alan,
>> >
>> >
>> >
>> > Thanks for your inputs.
>> >
>> >
>> >
>> > I enabled the dynamic debugging for USB HC driver. Please correct me
>> > if I am wrong.
>>
>> Debugging the kernel (or doing anything else to the kernel, for that
>> matter) won't solve the problem if it is caused by a buggy hub.
>
> Indeed. Could you just try a different hub?
>
> Regards
> Oliver
>
>
>
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-09 14:31 ` Alan Stern
@ 2014-10-15 10:11 ` Oliver Neukum
2014-10-15 13:09 ` Naveen Kumar Parna
0 siblings, 1 reply; 45+ messages in thread
From: Oliver Neukum @ 2014-10-15 10:11 UTC (permalink / raw)
To: Alan Stern; +Cc: Naveen Kumar Parna, linux-bluetooth, linux-usb, acho
On Thu, 2014-10-09 at 10:31 -0400, Alan Stern wrote:
> On Thu, 9 Oct 2014, Naveen Kumar Parna wrote:
>
> > Hi Oliver & Alan,
> >
> >
> >
> > Thanks for your inputs.
> >
> >
> >
> > I enabled the dynamic debugging for USB HC driver. Please correct me
> > if I am wrong.
>
> Debugging the kernel (or doing anything else to the kernel, for that
> matter) won't solve the problem if it is caused by a buggy hub.
Indeed. Could you just try a different hub?
Regards
Oliver
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
[not found] <CAG0bkvJDLP2tgnzu7H_ZCRCnZwkw1zUd1uqWwoDkmrU_FLts7w@mail.gmail.com>
@ 2014-10-09 14:31 ` Alan Stern
2014-10-15 10:11 ` Oliver Neukum
0 siblings, 1 reply; 45+ messages in thread
From: Alan Stern @ 2014-10-09 14:31 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: Oliver Neukum, linux-bluetooth, linux-usb, acho
On Thu, 9 Oct 2014, Naveen Kumar Parna wrote:
> Hi Oliver & Alan,
>
>
>
> Thanks for your inputs.
>
>
>
> I enabled the dynamic debugging for USB HC driver. Please correct me
> if I am wrong.
Debugging the kernel (or doing anything else to the kernel, for that
matter) won't solve the problem if it is caused by a buggy hub.
Alan Stern
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-08 13:17 ` Oliver Neukum
2014-10-08 14:10 ` Naveen Kumar Parna
@ 2014-10-08 14:46 ` Alan Stern
1 sibling, 0 replies; 45+ messages in thread
From: Alan Stern @ 2014-10-08 14:46 UTC (permalink / raw)
To: Oliver Neukum; +Cc: Naveen Kumar Parna, linux-bluetooth, linux-usb, acho
On Wed, 8 Oct 2014, Oliver Neukum wrote:
> On Wed, 2014-10-08 at 18:31 +0530, Naveen Kumar Parna wrote:
> > Later connected third device(hci2) and after 2mins observed –EPIPE for
> > hci2(hci2 urb ffff880124f11cc0 status -32 count 0)
>
> This points to a problem in the USB HC driver.
> Can you enable debugging in that driver.
It could also be a bug in the hub that the BT devices are plugged into.
I have seen a report of a hub that sends STALL when a bunch of devices
are plugged in, even though the devices themselves did not send a
STALL.
Alan Stern
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-08 13:17 ` Oliver Neukum
@ 2014-10-08 14:10 ` Naveen Kumar Parna
2014-10-08 14:46 ` Alan Stern
1 sibling, 0 replies; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-08 14:10 UTC (permalink / raw)
To: Oliver Neukum; +Cc: linux-bluetooth, linux-usb, acho
> This points to a problem in the USB HC driver.
> Can you enable debugging in that driver.
Is it enabling dynamic debugging?
Could you please point me the steps to enable debugging in USB HC driver?
Thanks,
Naveen
On Wed, Oct 8, 2014 at 6:47 PM, Oliver Neukum <oneukum@suse.de> wrote:
> On Wed, 2014-10-08 at 18:31 +0530, Naveen Kumar Parna wrote:
>> Later connected third device(hci2) and after 2mins observed –EPIPE for
>> hci2(hci2 urb ffff880124f11cc0 status -32 count 0)
>
> This points to a problem in the USB HC driver.
> Can you enable debugging in that driver.
>
> Regards
> Oliver
>
>
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-08 13:01 ` Naveen Kumar Parna
@ 2014-10-08 13:17 ` Oliver Neukum
2014-10-08 14:10 ` Naveen Kumar Parna
2014-10-08 14:46 ` Alan Stern
0 siblings, 2 replies; 45+ messages in thread
From: Oliver Neukum @ 2014-10-08 13:17 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: linux-bluetooth, linux-usb, acho
On Wed, 2014-10-08 at 18:31 +0530, Naveen Kumar Parna wrote:
> Later connected third device(hci2) and after 2mins observed –EPIPE for
> hci2(hci2 urb ffff880124f11cc0 status -32 count 0)
This points to a problem in the USB HC driver.
Can you enable debugging in that driver.
Regards
Oliver
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-08 10:44 ` Oliver Neukum
@ 2014-10-08 13:01 ` Naveen Kumar Parna
2014-10-08 13:17 ` Oliver Neukum
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-08 13:01 UTC (permalink / raw)
To: Oliver Neukum; +Cc: linux-bluetooth, linux-usb, acho
> Do you see the problem with single devices?
If I connect only one device to system then I did not see this issue.
Usually I will use 8 devices(all with the same firmware) for testing.
I tried different method to get some clue. First I disconnected all
the devices and rebooted the system and later connected only one
device and observed hci0 related debug print statements in the kernel
log. Waited for 16mins idle, but did not get –EPIPE.
Oct 8 16:41:46 banunxcas29 kernel: [ 488.018751] usb 1-1.5.1.7: new
full speed USB device number 13 using ehci_hcd
Oct 8 16:41:46 banunxcas29 kernel: [ 488.093487] usb 1-1.5.1.7: New
USB device found, idVendor=0451, idProduct=2036
Oct 8 16:41:46 banunxcas29 kernel: [ 488.093494] usb 1-1.5.1.7: New
USB device strings: Mfr=0, Product=1, SerialNumber=0
Oct 8 16:41:46 banunxcas29 kernel: [ 488.093499] usb 1-1.5.1.7:
Product: General Purpose USB Hub
Oct 8 16:41:46 banunxcas29 kernel: [ 488.094581] hub 1-1.5.1.7:1.0:
USB hub found
Oct 8 16:41:46 banunxcas29 kernel: [ 488.094811] hub 1-1.5.1.7:1.0:
2 ports detected
Oct 8 16:41:46 banunxcas29 kernel: [ 488.261141] usb 1-1.5.2: new
full speed USB device number 14 using ehci_hcd
Oct 8 16:41:46 banunxcas29 kernel: [ 488.323983] usb 1-1.5.2: device
descriptor read/64, error -32
Oct 8 16:41:47 banunxcas29 kernel: [ 488.518202] usb 1-1.5.2: New
USB device found, idVendor=0a12, idProduct=0001
Oct 8 16:41:47 banunxcas29 kernel: [ 488.518208] usb 1-1.5.2: New
USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 8 16:41:47 banunxcas29 kernel: [ 488.551389] Bluetooth: Core ver 2.16
Oct 8 16:41:47 banunxcas29 kernel: [ 488.551402] NET: Registered
protocol family 31
Oct 8 16:41:47 banunxcas29 kernel: [ 488.551404] Bluetooth: HCI
device and connection manager initialized
Oct 8 16:41:47 banunxcas29 kernel: [ 488.551406] Bluetooth: HCI
socket layer initialized
Oct 8 16:41:47 banunxcas29 kernel: [ 488.551408] Bluetooth: L2CAP
socket layer initialized
Oct 8 16:41:47 banunxcas29 kernel: [ 488.551411] Bluetooth: SCO
socket layer initialized
Oct 8 16:41:47 banunxcas29 kernel: [ 488.565663] Bluetooth: Generic
Bluetooth USB driver ver 0.6
Oct 8 16:41:47 banunxcas29 kernel: [ 488.565693] intf
ffff880128640800 id ffffffffa0197f00
Oct 8 16:41:47 banunxcas29 kernel: [ 488.580231] hci0
Oct 8 16:41:47 banunxcas29 kernel: [ 488.580236] hci0
Oct 8 16:41:47 banunxcas29 kernel: [ 488.580258] intf
ffff880128641000 id ffffffffa0197f00
Oct 8 16:41:47 banunxcas29 kernel: [ 488.580296] usbcore: registered
new interface driver btusb
Oct 8 16:41:47 banunxcas29 kernel: [ 488.580480] hci0
Oct 8 16:41:47 banunxcas29 kernel: [ 488.580486] hci0
Oct 8 16:41:47 banunxcas29 kernel: [ 488.580503] hci0
Oct 8 16:41:47 banunxcas29 kernel: [ 488.581314] hci0 urb
ffff880131dbe3c0 status 0 count 6
Later connected one more device to system and noticed hci1 related
debug print statements in the kernel log. Waited for 20mins idle and
now also not received –EPIPE.
Oct 8 16:57:44 banunxcas29 kernel: [ 1443.815276] usb 1-1.5.3: new
full speed USB device number 17 using ehci_hcd
Oct 8 16:57:45 banunxcas29 kernel: [ 1444.400987] usb 1-1.5.3: New
USB device found, idVendor=0a12, idProduct=0001
Oct 8 16:57:45 banunxcas29 kernel: [ 1444.400993] usb 1-1.5.3: New
USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 8 16:57:45 banunxcas29 kernel: [ 1444.403218] intf
ffff880124c45800 id ffffffffa0197f00
Oct 8 16:57:45 banunxcas29 kernel: [ 1444.403360] hci1
Oct 8 16:57:45 banunxcas29 kernel: [ 1444.403364] hci1
Oct 8 16:57:45 banunxcas29 kernel: [ 1444.403500] intf
ffff880124c44c00 id ffffffffa0197f00
Oct 8 16:57:45 banunxcas29 kernel: [ 1444.403511] hci1
Oct 8 16:57:45 banunxcas29 kernel: [ 1444.403515] hci1
Oct 8 16:57:45 banunxcas29 kernel: [ 1444.403529] hci1
Oct 8 16:57:45 banunxcas29 kernel: [ 1444.404872] hci1 urb
ffff880129162840 status 0 count 6
Later connected third device(hci2) and after 2mins observed –EPIPE for
hci2(hci2 urb ffff880124f11cc0 status -32 count 0)
Oct 8 17:18:21 banunxcas29 kernel: [ 2677.069853] usb 1-1.5.4: new
full speed USB device number 18 using ehci_hcd
Oct 8 17:18:21 banunxcas29 kernel: [ 2677.681729] usb 1-1.5.4: New
USB device found, idVendor=0a12, idProduct=0001
Oct 8 17:18:21 banunxcas29 kernel: [ 2677.681735] usb 1-1.5.4: New
USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 8 17:18:21 banunxcas29 kernel: [ 2677.683689] intf
ffff880119c3b400 id ffffffffa0197f00
Oct 8 17:18:21 banunxcas29 kernel: [ 2677.683886] hci2
Oct 8 17:18:21 banunxcas29 kernel: [ 2677.683889] hci2
Oct 8 17:18:21 banunxcas29 kernel: [ 2677.684083] intf
ffff880119c3a800 id ffffffffa0197f00
Oct 8 17:18:21 banunxcas29 kernel: [ 2677.684161] hci2
Oct 8 17:18:21 banunxcas29 kernel: [ 2677.684166] hci2
Oct 8 17:18:21 banunxcas29 kernel: [ 2677.684184] hci2
Oct 8 17:18:21 banunxcas29 kernel: [ 2677.685364] hci2 urb
ffff880124f11cc0 status 0 count 6
Oct 8 17:18:22 banunxcas29 kernel: [ 2678.126333] hci2 urb
ffff880124f11cc0 status 0 count 6
Oct 8 17:20:20 banunxcas29 kernel: [ 2795.645039] hci2 urb
ffff880124f11cc0 status -32 count 0
Oct 8 17:20:20 banunxcas29 kernel: [ 2795.646013] hci2
Later connected 4th device(hci3) and now repeatedly getting –EPIPE for
hci3 and hci2
Oct 8 17:44:14 banunxcas29 kernel: [ 4226.073252] usb 1-1.5.5: new
full speed USB device number 19 using ehci_hcd
Oct 8 17:44:14 banunxcas29 kernel: [ 4226.746971] usb 1-1.5.5: New
USB device found, idVendor=0a12, idProduct=0001
Oct 8 17:44:14 banunxcas29 kernel: [ 4226.746977] usb 1-1.5.5: New
USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 8 17:44:14 banunxcas29 kernel: [ 4226.749042] intf
ffff880124c47400 id ffffffffa0197f00
Oct 8 17:44:14 banunxcas29 kernel: [ 4226.749403] hci3
Oct 8 17:44:14 banunxcas29 kernel: [ 4226.749407] hci3
Oct 8 17:44:14 banunxcas29 kernel: [ 4226.749526] intf
ffff880124c47000 id ffffffffa0197f00
Oct 8 17:44:14 banunxcas29 kernel: [ 4226.749679] hci3
Oct 8 17:44:14 banunxcas29 kernel: [ 4226.749684] hci3
Oct 8 17:44:14 banunxcas29 kernel: [ 4226.749700] hci3
Oct 8 17:44:14 banunxcas29 kernel: [ 4226.750520] hci3 urb
ffff8801344e6a80 status 0 count 6
Oct 8 17:49:45 banunxcas29 kernel: [ 4556.495180] hci3 urb
ffff8801344e6a80 status -32 count 0
Oct 8 17:49:45 banunxcas29 kernel: [ 4556.496341] hci3
Oct 8 17:51:24 banunxcas29 kernel: [ 4655.170274] hci2 urb
ffff880131c6ea80 status -32 count 0
Oct 8 17:51:24 banunxcas29 kernel: [ 4655.170345] hci3 urb
ffff880124dfb480 status -32 count 0
Oct 8 17:51:24 banunxcas29 kernel: [ 4655.171381] hci2
Oct 8 17:51:24 banunxcas29 kernel: [ 4655.171759] hci3
Oct 8 18:00:24 banunxcas29 kernel: [ 5193.920586] hci3 urb
ffff880124f11d80 status -32 count 0
Oct 8 18:00:24 banunxcas29 kernel: [ 5193.921890] hci3
Oct 8 18:00:24 banunxcas29 kernel: [ 5193.928470] hci3 urb
ffff880124f11d80 status -32 count 0
Oct 8 18:00:24 banunxcas29 kernel: [ 5193.929511] hci3
Oct 8 18:00:24 banunxcas29 kernel: [ 5193.933570] hci3 urb
ffff880124f11d80 status -32 count 0
Oct 8 18:00:24 banunxcas29 kernel: [ 5193.934402] hci3
Oct 8 18:00:24 banunxcas29 kernel: [ 5193.940425] hci3 urb
ffff880124f11d80 status -32 count 0
Oct 8 18:00:24 banunxcas29 kernel: [ 5193.941531] hci3
Oct 8 18:05:18 banunxcas29 kernel: [ 5487.003279] hci3 urb
ffff880124f11d80 status -32 count 0
Oct 8 18:05:18 banunxcas29 kernel: [ 5487.004528] hci3
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.844852] hci3 urb
ffff880124f11d80 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.846068] hci3
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.860809] hci3 urb
ffff880124f11d80 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.861776] hci3
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.867701] hci3 urb
ffff880124f11d80 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.868651] hci3
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.874669] hci2 urb
ffff880124f11cc0 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.874738] hci3 urb
ffff880124f183c0 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.875772] hci2
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.875949] hci3
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.877734] hci2 urb
ffff880124f11cc0 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.877800] hci3 urb
ffff880124f11e40 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.878720] hci3
Oct 8 18:06:24 banunxcas29 kernel: [ 5552.878922] hci2
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.098220] hci3 urb
ffff880124f11cc0 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.098291] hci2 urb
ffff880124f11e40 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.099158] hci2
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.099339] hci3
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.101145] hci3 urb
ffff880124f11e40 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.102165] hci3
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.107198] hci3 urb
ffff880124f11e40 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.108141] hci3
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.121160] hci3 urb
ffff880124f11e40 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.122130] hci3
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.133127] hci2 urb
ffff880124f11cc0 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.133196] hci3 urb
ffff880124f11e40 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.134075] hci3
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.134300] hci2
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.136143] hci3 urb
ffff880124f11cc0 status -32 count 0
Oct 8 18:06:24 banunxcas29 kernel: [ 5553.136176] hci2 urb
ffff880124f11e40 status -32 count 0
I ran hcidump for each hci device separately, but it does not show any
activity during EPIPE occurrence.
It clearly tells that device not producing stalls , looks like issue
might be in between btusb and ehci_hcd\hub.
What might the best way to recover and avoid spurious stalls?
Thanks,
Naveen
On Wed, Oct 8, 2014 at 4:14 PM, Oliver Neukum <oneukum@suse.de> wrote:
> On Wed, 2014-10-08 at 15:51 +0530, Naveen Kumar Parna wrote:
>> hcidump does not show anything when the stalls happen.
>
> There is nothing in all logs. Do you see the problem
> with single devices?
>
> Regards
> Oliver
>
>
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-08 10:21 ` Naveen Kumar Parna
@ 2014-10-08 10:44 ` Oliver Neukum
2014-10-08 13:01 ` Naveen Kumar Parna
0 siblings, 1 reply; 45+ messages in thread
From: Oliver Neukum @ 2014-10-08 10:44 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: linux-bluetooth, linux-usb, acho
On Wed, 2014-10-08 at 15:51 +0530, Naveen Kumar Parna wrote:
> hcidump does not show anything when the stalls happen.
There is nothing in all logs. Do you see the problem
with single devices?
Regards
Oliver
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-08 9:09 ` Oliver Neukum
@ 2014-10-08 10:21 ` Naveen Kumar Parna
2014-10-08 10:44 ` Oliver Neukum
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-08 10:21 UTC (permalink / raw)
To: Oliver Neukum; +Cc: linux-bluetooth, linux-usb, acho
hcidump does not show anything when the stalls happen.
Here is the hcidump log:
[root@banunxcas29 np03]# hcidump -x -t
HCI sniffer - Bluetooth packet analyzer ver 2.1
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
Corresponding usbmon log
ffff8801265343c0 2826295762 C Ii:1:021:1 -32:1 0
ffff880126418840 2826297275 S Ii:1:021:1 -115:1 16 <
ffff880126534240 2826298730 C Ii:1:020:1 -32:1 0
ffff880126418840 2826298856 C Ii:1:021:1 -32:1 0
ffff880126418840 2826299789 S Ii:1:020:1 -115:1 16 <
ffff880126418900 2826300154 S Ii:1:021:1 -115:1 16 <
ffff8801266329c0 2837941755 C Ii:1:018:1 -32:1 0
ffff880126632c00 2837941884 C Ii:1:016:1 -32:1 0
ffff880126418b40 2837942862 S Ii:1:016:1 -115:1 16 <
ffff880126418300 2837943184 S Ii:1:018:1 -115:1 16 <
ffff880126418300 2897160790 C Ii:1:018:1 -32:1 0
ffff880126418300 2897162701 S Ii:1:018:1 -115:1 16 <
ffff880126632cc0 2897332778 C Ii:1:019:1 -32:1 0
ffff880126418840 2897332909 C Ii:1:020:1 -32:1 0
ffff880126418900 2897332959 C Ii:1:021:1 -32:1 0
ffff880126418b40 2897333002 C Ii:1:016:1 -32:1 0
ffff880126418300 2897333035 C Ii:1:018:1 -32:1 0
ffff880126418900 2897334155 S Ii:1:021:1 -115:1 16 <
ffff880126418b40 2897334405 S Ii:1:020:1 -115:1 16 <
ffff880126418300 2897334635 S Ii:1:019:1 -115:1 16 <
ffff880126418f00 2897335015 S Ii:1:018:1 -115:1 16 <
ffff880126418840 2897335367 S Ii:1:016:1 -115:1 16 <
Corresponding kernel log:
Oct 8 15:29:38 banunxcas29 kernel: [ 3244.604776] hci7 urb
ffff8801265343c0 status -32 count 0
Oct 8 15:29:38 banunxcas29 kernel: [ 3244.606273] hci7
Oct 8 15:29:38 banunxcas29 kernel: [ 3244.607741] hci6 urb
ffff880126534240 status -32 count 0
Oct 8 15:29:38 banunxcas29 kernel: [ 3244.607862] hci7 urb
ffff880126418840 status -32 count 0
Oct 8 15:29:38 banunxcas29 kernel: [ 3244.608787] hci6
Oct 8 15:29:38 banunxcas29 kernel: [ 3244.609155] hci7
Oct 8 15:29:49 banunxcas29 kernel: [ 3256.251736] hci4 urb
ffff8801266329c0 status -32 count 0
Oct 8 15:29:49 banunxcas29 kernel: [ 3256.251857] hci2 urb
ffff880126632c00 status -32 count 0
Oct 8 15:29:49 banunxcas29 kernel: [ 3256.252828] hci2
Oct 8 15:29:49 banunxcas29 kernel: [ 3256.253153] hci4
Oct 8 15:30:49 banunxcas29 kernel: [ 3315.476287] hci4 urb
ffff880126418300 status -32 count 0
Oct 8 15:30:49 banunxcas29 kernel: [ 3315.478179] hci4
Oct 8 15:30:49 banunxcas29 kernel: [ 3315.648289] hci5 urb
ffff880126632cc0 status -32 count 0
Oct 8 15:30:49 banunxcas29 kernel: [ 3315.648411] hci6 urb
ffff880126418840 status -32 count 0
Oct 8 15:30:49 banunxcas29 kernel: [ 3315.648461] hci7 urb
ffff880126418900 status -32 count 0
Oct 8 15:30:49 banunxcas29 kernel: [ 3315.648504] hci2 urb
ffff880126418b40 status -32 count 0
Oct 8 15:30:49 banunxcas29 kernel: [ 3315.648537] hci4 urb
ffff880126418300 status -32 count 0
Oct 8 15:30:49 banunxcas29 kernel: [ 3315.649651] hci7
Oct 8 15:30:49 banunxcas29 kernel: [ 3315.649905] hci6
Oct 8 15:30:49 banunxcas29 kernel: [ 3315.650134] hci5
Oct 8 15:30:49 banunxcas29 kernel: [ 3315.650514] hci4
Oct 8 15:30:49 banunxcas29 kernel: [ 3315.650866] hci2
Thanks,
Naveen
On Wed, Oct 8, 2014 at 2:39 PM, Oliver Neukum <oneukum@suse.de> wrote:
> On Tue, 2014-10-07 at 20:01 +0530, Naveen Kumar Parna wrote:
>> > The new patch clears the halt condition.
>>
>> I mean usb_clear_halt( ) returned zero.
>
> That probably means that the device doesn't just
> produce spurious stalls. Does hcidump show anything
> when the stalls happen?
>
> Regards
> Oliver
>
>
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-07 14:31 ` Naveen Kumar Parna
@ 2014-10-08 9:09 ` Oliver Neukum
2014-10-08 10:21 ` Naveen Kumar Parna
0 siblings, 1 reply; 45+ messages in thread
From: Oliver Neukum @ 2014-10-08 9:09 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: linux-bluetooth, linux-usb, acho
On Tue, 2014-10-07 at 20:01 +0530, Naveen Kumar Parna wrote:
> > The new patch clears the halt condition.
>
> I mean usb_clear_halt( ) returned zero.
That probably means that the device doesn't just
produce spurious stalls. Does hcidump show anything
when the stalls happen?
Regards
Oliver
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-07 13:34 ` Naveen Kumar Parna
@ 2014-10-07 14:31 ` Naveen Kumar Parna
2014-10-08 9:09 ` Oliver Neukum
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-07 14:31 UTC (permalink / raw)
To: Oliver Neukum; +Cc: linux-bluetooth, linux-usb, acho
> The new patch clears the halt condition.
I mean usb_clear_halt( ) returned zero.
Thanks,
Naveen
On Tue, Oct 7, 2014 at 7:04 PM, Naveen Kumar Parna <pnaveenkos@gmail.com> wrote:
> Thanks for the new patch.
>
>
>
> The new patch clears the halt condition. But after submitting the urb
> again the INT in endpoint returns EPIPE, this behavior continues
> infinitely.
>
>
>
> Corresponding kernel log is here:
>
> Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.311863] hci0 urb
> ffff88012f670b40 status -32 count 0
>
> Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.311988] hci5 urb
> ffff8801379d2180 status -32 count 0
>
> Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.455464] hci4 urb
> ffff88012a4b2e40 status -32 count 0
>
> Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.455586] hci1 urb
> ffff88012a4b2180 status -32 count 0
>
> Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.455691] hci2 urb
> ffff88012f670480 status -32 count 0
>
> Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.455784] hci3 urb
> ffff88012f670e40 status -32 count 0
>
> Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.455853] hci0 urb
> ffff880131e5ee40 status -32 count 0
>
> Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.455913] hci5 urb
> ffff880131e5e780 status -32 count 0
>
> Oct 7 17:58:44 naveen-OptiPlex-745 kernel: [ 19.690366] hci4 urb
> ffff880131e5e780 status -32 count 0
>
> Oct 7 17:58:44 naveen-OptiPlex-745 kernel: [ 19.690490] hci5 urb
> ffff880131e5e300 status -32 count 0
>
> Oct 7 17:58:47 naveen-OptiPlex-745 kernel: [ 22.163163] hci5 urb
> ffff88012f541540 status -32 count 0
>
> Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.313996] hci1 urb
> ffff880131e5ee40 status -32 count 0
>
> Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.314121] hci0 urb
> ffff880131e5e900 status -32 count 0
>
> Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.314169] hci3 urb
> ffff880131e5e3c0 status -32 count 0
>
> Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.314213] hci2 urb
> ffff880131e5ef00 status -32 count 0
>
> Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.314245] hci4 urb
> ffff88012f541d80 status -32 count 0
>
> Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.314274] hci5 urb
> ffff88012f541540 status -32 count 0
>
> Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.319974] hci2 urb
> ffff8801384dcb40 status -32 count 0
>
> Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.320095] hci0 urb
> ffff8801384dc300 status -32 count 0
>
> Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.320151] hci4 urb
> ffff8801384dc6c0 status -32 count 0
>
> Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.320193] hci5 urb
> ffff8801384dcf00 status -32 count 0
>
>
>
> Thanks,
>
> Naveen
>
> On Tue, Oct 7, 2014 at 3:31 PM, Oliver Neukum <oneukum@suse.de> wrote:
>> On Tue, 2014-10-07 at 12:14 +0530, Naveen Kumar Parna wrote:
>>> > + err = usb_clear_halt(data->udev,
>>> > + usb_rcvbulkpipe(data->udev,
>>> > + data->intr_ep->bEndpointAddress));
>>>
>>> EPIPE occurred for INT in endpoint, so we should use usb_rcvintpipe()
>>> instead of usb_rcvbulkpipe() right?
>>
>> Yes. And I noticed a copy and past error.
>>
>>> Does the “lsusb –v” gives any clue about the reason for getting -EPIPE?
>>
>> No. Could you nevertheless test the attached version?
>>
>> Regards
>> Oliver
>>
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-07 10:01 ` Oliver Neukum
@ 2014-10-07 13:34 ` Naveen Kumar Parna
2014-10-07 14:31 ` Naveen Kumar Parna
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-07 13:34 UTC (permalink / raw)
To: Oliver Neukum; +Cc: linux-bluetooth, linux-usb, acho
Thanks for the new patch.
The new patch clears the halt condition. But after submitting the urb
again the INT in endpoint returns EPIPE, this behavior continues
infinitely.
Corresponding kernel log is here:
Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.311863] hci0 urb
ffff88012f670b40 status -32 count 0
Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.311988] hci5 urb
ffff8801379d2180 status -32 count 0
Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.455464] hci4 urb
ffff88012a4b2e40 status -32 count 0
Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.455586] hci1 urb
ffff88012a4b2180 status -32 count 0
Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.455691] hci2 urb
ffff88012f670480 status -32 count 0
Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.455784] hci3 urb
ffff88012f670e40 status -32 count 0
Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.455853] hci0 urb
ffff880131e5ee40 status -32 count 0
Oct 7 17:58:41 naveen-OptiPlex-745 kernel: [ 16.455913] hci5 urb
ffff880131e5e780 status -32 count 0
Oct 7 17:58:44 naveen-OptiPlex-745 kernel: [ 19.690366] hci4 urb
ffff880131e5e780 status -32 count 0
Oct 7 17:58:44 naveen-OptiPlex-745 kernel: [ 19.690490] hci5 urb
ffff880131e5e300 status -32 count 0
Oct 7 17:58:47 naveen-OptiPlex-745 kernel: [ 22.163163] hci5 urb
ffff88012f541540 status -32 count 0
Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.313996] hci1 urb
ffff880131e5ee40 status -32 count 0
Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.314121] hci0 urb
ffff880131e5e900 status -32 count 0
Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.314169] hci3 urb
ffff880131e5e3c0 status -32 count 0
Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.314213] hci2 urb
ffff880131e5ef00 status -32 count 0
Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.314245] hci4 urb
ffff88012f541d80 status -32 count 0
Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.314274] hci5 urb
ffff88012f541540 status -32 count 0
Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.319974] hci2 urb
ffff8801384dcb40 status -32 count 0
Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.320095] hci0 urb
ffff8801384dc300 status -32 count 0
Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.320151] hci4 urb
ffff8801384dc6c0 status -32 count 0
Oct 7 18:06:01 naveen-OptiPlex-745 kernel: [ 45.320193] hci5 urb
ffff8801384dcf00 status -32 count 0
Thanks,
Naveen
On Tue, Oct 7, 2014 at 3:31 PM, Oliver Neukum <oneukum@suse.de> wrote:
> On Tue, 2014-10-07 at 12:14 +0530, Naveen Kumar Parna wrote:
>> > + err = usb_clear_halt(data->udev,
>> > + usb_rcvbulkpipe(data->udev,
>> > + data->intr_ep->bEndpointAddress));
>>
>> EPIPE occurred for INT in endpoint, so we should use usb_rcvintpipe()
>> instead of usb_rcvbulkpipe() right?
>
> Yes. And I noticed a copy and past error.
>
>> Does the “lsusb –v” gives any clue about the reason for getting -EPIPE?
>
> No. Could you nevertheless test the attached version?
>
> Regards
> Oliver
>
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-07 6:44 ` Naveen Kumar Parna
@ 2014-10-07 10:01 ` Oliver Neukum
2014-10-07 13:34 ` Naveen Kumar Parna
0 siblings, 1 reply; 45+ messages in thread
From: Oliver Neukum @ 2014-10-07 10:01 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: linux-bluetooth, linux-usb, acho
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
On Tue, 2014-10-07 at 12:14 +0530, Naveen Kumar Parna wrote:
> > + err = usb_clear_halt(data->udev,
> > + usb_rcvbulkpipe(data->udev,
> > + data->intr_ep->bEndpointAddress));
>
> EPIPE occurred for INT in endpoint, so we should use usb_rcvintpipe()
> instead of usb_rcvbulkpipe() right?
Yes. And I noticed a copy and past error.
> Does the “lsusb –v” gives any clue about the reason for getting -EPIPE?
No. Could you nevertheless test the attached version?
Regards
Oliver
[-- Attachment #2: 0001-btusb-clear-halt-if-intr-in-stalls.patch --]
[-- Type: text/x-patch, Size: 2656 bytes --]
>From b8109554277bde9da4275e7a9ce1ef76b43ebd59 Mon Sep 17 00:00:00 2001
From: Oliver Neukum <oneukum@suse.de>
Date: Mon, 6 Oct 2014 15:27:54 +0200
Subject: [PATCH] btusb: clear halt if intr in stalls
Use a work queue for clearing a halt.
Signed-off-by: Oliver Neukum <oneukum@suse.de>
---
drivers/bluetooth/btusb.c | 34 ++++++++++++++++++++++++++++++++--
1 file changed, 32 insertions(+), 2 deletions(-)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 292c38e..716c37a 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -273,6 +273,7 @@ struct btusb_data {
struct work_struct work;
struct work_struct waker;
+ struct work_struct intr_in_work;
struct usb_anchor tx_anchor;
struct usb_anchor intr_anchor;
@@ -314,14 +315,15 @@ static void btusb_intr_complete(struct urb *urb)
struct hci_dev *hdev = urb->context;
struct btusb_data *data = hci_get_drvdata(hdev);
int err;
+ int status = urb->status;
BT_DBG("%s urb %p status %d count %d", hdev->name,
- urb, urb->status, urb->actual_length);
+ urb, status, urb->actual_length);
if (!test_bit(HCI_RUNNING, &hdev->flags))
return;
- if (urb->status == 0) {
+ if (status == 0) {
hdev->stat.byte_rx += urb->actual_length;
if (hci_recv_fragment(hdev, HCI_EVENT_PKT,
@@ -330,6 +332,10 @@ static void btusb_intr_complete(struct urb *urb)
BT_ERR("%s corrupted event packet", hdev->name);
hdev->stat.err_rx++;
}
+ } else if (status == -EPIPE) {
+ usb_mark_last_busy(data->udev);
+ schedule_work(&data->intr_in_work);
+ return;
}
if (!test_bit(BTUSB_INTR_RUNNING, &data->flags))
@@ -971,6 +977,29 @@ static void btusb_waker(struct work_struct *work)
usb_autopm_put_interface(data->intf);
}
+static void clear_halt_intr_in(struct work_struct *work)
+{
+ struct btusb_data *data = container_of(work, struct btusb_data, intr_in_work);
+ int err;
+
+ err = usb_autopm_get_interface(data->intf);
+ if (err < 0)
+ return;
+
+ err = usb_clear_halt(data->udev,
+ usb_rcvintpipe(data->udev,
+ data->intr_ep->bEndpointAddress));
+ if (err < 0)
+ return;
+
+ if (!test_bit(BTUSB_INTR_RUNNING, &data->flags))
+ return;
+
+ btusb_submit_intr_urb(data->hdev, GFP_NOIO);
+
+ usb_autopm_put_interface(data->intf);
+}
+
static int btusb_setup_bcm92035(struct hci_dev *hdev)
{
struct sk_buff *skb;
@@ -1759,6 +1788,7 @@ static int btusb_probe(struct usb_interface *intf,
INIT_WORK(&data->work, btusb_work);
INIT_WORK(&data->waker, btusb_waker);
+ INIT_WORK(&data->intr_in_work, clear_halt_intr_in);
spin_lock_init(&data->txlock);
init_usb_anchor(&data->tx_anchor);
--
1.8.4.5
^ permalink raw reply related [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
[not found] ` <CAG0bkvKJZMhurNNpc_2wgaACRzhyEikb0G0YSY7QnxqBe1rnjw@mail.gmail.com>
@ 2014-10-07 6:44 ` Naveen Kumar Parna
2014-10-07 10:01 ` Oliver Neukum
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-07 6:44 UTC (permalink / raw)
To: Oliver Neukum; +Cc: linux-bluetooth, linux-usb, acho
> + err = usb_clear_halt(data->udev,
> + usb_rcvbulkpipe(data->udev,
> + data->intr_ep->bEndpointAddress));
EPIPE occurred for INT in endpoint, so we should use usb_rcvintpipe()
instead of usb_rcvbulkpipe() right?
Does the “lsusb –v” gives any clue about the reason for getting -EPIPE?
Thanks,
Naveen
On Mon, Oct 6, 2014 at 8:42 PM, Naveen Kumar Parna <pnaveenkos@gmail.com> wrote:
> Attached the lsusb -v file.
>
> Captured the usbmon log file for this patch and attached it.
>
>
>
> Thanks,
>
> Naveen
>
> On Mon, Oct 6, 2014 at 8:20 PM, Oliver Neukum <oneukum@suse.de> wrote:
>> On Mon, 2014-10-06 at 20:08 +0530, Naveen Kumar Parna wrote:
>>> Thanks for the patch.
>>>
>>> I tried and It crashed after the first occurrence of EPIPE.
>>>
>>> Crash log is attached.
>>
>> Could you post a full "lsusb -v"?
>>
>> Regards
>> Oliver
>>
>>
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-06 14:38 ` Naveen Kumar Parna
@ 2014-10-06 14:50 ` Oliver Neukum
[not found] ` <CAG0bkvKJZMhurNNpc_2wgaACRzhyEikb0G0YSY7QnxqBe1rnjw@mail.gmail.com>
0 siblings, 1 reply; 45+ messages in thread
From: Oliver Neukum @ 2014-10-06 14:50 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: linux-bluetooth, linux-usb, acho
On Mon, 2014-10-06 at 20:08 +0530, Naveen Kumar Parna wrote:
> Thanks for the patch.
>
> I tried and It crashed after the first occurrence of EPIPE.
>
> Crash log is attached.
Could you post a full "lsusb -v"?
Regards
Oliver
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-06 13:29 ` Oliver Neukum
@ 2014-10-06 14:38 ` Naveen Kumar Parna
2014-10-06 14:50 ` Oliver Neukum
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-06 14:38 UTC (permalink / raw)
To: Oliver Neukum; +Cc: linux-bluetooth, linux-usb, acho
[-- Attachment #1: Type: text/plain, Size: 5945 bytes --]
Thanks for the patch.
I tried and It crashed after the first occurrence of EPIPE.
Crash log is attached.
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.188379] hci4 urb
ffff880127ad9240 status -32 count 0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.188556] BUG: unable
to handle kernel paging request at 00000000000102a0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.189281] IP:
[<ffffffff812e53c9>] atomic_inc+0x9/0xe
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.189634] PGD
127884067 PUD 131fc0067 PMD 0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.189989] Oops: 0002 [#1] SMP
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.190337] CPU 6
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.190344] Modules
linked in: rfcomm bnep btusb bluetooth rfkill babel nfs fscache
auth_rpcgss nfs_acl lockd iTCO_wdt iTCO_vendor_support i2c_i801
i2c_core tg3 joydev sunrpc uinput microcode hpsa usb_storage uas [last
unloaded: scsi_wait_scan]
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.192109]
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.192442] Pid: 53,
comm: kworker/6:1 Not tainted 3.1.0-7.fc16.x86_64 #1 HP ProLiant DL120
G6/ProLiant DL120 G6
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.193151] RIP:
0010:[<ffffffff812e53c9>] [<ffffffff812e53c9>] atomic_inc+0x9/0xe
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.193839] RSP:
0018:ffff88013868ddb0 EFLAGS: 00010202
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.194273] RAX:
ffff880128191c78 RBX: 0000000000010130 RCX: ffff880128191c70
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.194625] RDX:
ffff880128191c70 RSI: 0000000000000004 RDI: 00000000000102a0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.194979] RBP:
ffff88013868ddb0 R08: ffff880128191c78 R09: 0000000000608007
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.195329] R10:
0000000000608007 R11: ffff88013fd92f80 R12: 0000000000010100
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.195680] R13:
0000000000010130 R14: 0000000000000004 R15: ffff88013fd96805
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.196032] FS:
0000000000000000(0000) GS:ffff88013fd80000(0000)
knlGS:0000000000000000
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.196716] CS: 0010
DS: 0000 ES: 0000 CR0: 000000008005003b
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.197063] CR2:
00000000000102a0 CR3: 000000012a613000 CR4: 00000000000006e0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.197422] DR0:
0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.197780] DR3:
0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.198138] Process
kworker/6:1 (pid: 53, threadinfo ffff88013868c000, task
ffff880138690000)
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.198811] Stack:
Message from syslogd@naveen-OptiPlex-745 at Oct 6 19:49:24 ...
kernel:[ 979.189989] Oops: 0002 [#1] SMP
Message from syslogd@naveen-OptiPlex-745 at Oct 6 19:49:24 ...
kernel:[ 979.198811] Stack:
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.199146]
ffff88013868ddf0 ffffffff812e645c ffffffff81605920 ffff88013fd92f80
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.199831]
ffff880128191c70 0000000000010100 0000000000010130 ffffffffa0091b49
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.200525]
ffff88013868de20 ffffffff8133a672 ffff880128191c70 ffff880128191c70
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.201211] Call Trace:
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.201550]
[<ffffffff812e645c>] __pm_runtime_resume+0x2c/0x65
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.201907]
[<ffffffffa0091b49>] ? btusb_submit_intr_urb+0x173/0x173 [btusb]
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.202268]
[<ffffffff8133a672>] usb_autopm_get_interface+0x23/0x52
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.202626]
[<ffffffffa0091b60>] clear_halt_intr_in+0x17/0xac [btusb]
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.202978]
[<ffffffff8106edbc>] process_one_work+0x176/0x2a9
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.203331]
[<ffffffff8106f8ca>] worker_thread+0xda/0x15d
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.203680]
[<ffffffff8106f7f0>] ? manage_workers+0x176/0x176
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.204022]
[<ffffffff81072d17>] kthread+0x84/0x8c
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.204365]
[<ffffffff814be5f4>] kernel_thread_helper+0x4/0x10
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.204711]
[<ffffffff81072c93>] ? kthread_worker_fn+0x148/0x148
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.205058]
[<ffffffff814be5f0>] ? gs_change+0x13/0x13
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.205402] Code: d9 81
e8 07 f6 ff ff 80 3d 24 26 ab 00 00 75 05 e8 da f7 ff ff 8a 05 17 26
ab 00 41 5b 5b 5d c3 90 90 55 48 89 e5 66 66 66 66 90 <f0> ff 07 5d c3
55 48 89 e5 66 66 66 66 90 f0 ff 0f 0f 94 c0 84
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.206652] RIP
[<ffffffff812e53c9>] atomic_inc+0x9/0xe
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.207007] RSP
<ffff88013868ddb0>
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.207354] CR2: 00000000000102a0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208287] ---[ end
trace 0089da2b8191af16 ]---
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208739] BUG: unable
to handle kernel paging request at fffffffffffffff8
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208742] IP:
[<ffffffff81072f65>] kthread_data+0x11/0x16
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208747] PGD 1a07067
PUD 1a08067 PMD 0
Thanks,
Naveen
On Mon, Oct 6, 2014 at 6:59 PM, Oliver Neukum <oneukum@suse.de> wrote:
> On Mon, 2014-10-06 at 18:33 +0530, Naveen Kumar Parna wrote:
>> Thank you very much. I will try that patch.
>
> Then please try.
>
> Regards
> Oliver
>
[-- Attachment #2: 0001-btusb-clear-halt-if-intr-in-stalls.patch.crash.log --]
[-- Type: application/octet-stream, Size: 12596 bytes --]
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.188379] hci4 urb ffff880127ad9240 status -32 count 0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.188556] BUG: unable to handle kernel paging request at 00000000000102a0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.189281] IP: [<ffffffff812e53c9>] atomic_inc+0x9/0xe
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.189634] PGD 127884067 PUD 131fc0067 PMD 0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.189989] Oops: 0002 [#1] SMP
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.190337] CPU 6
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.190344] Modules linked in: rfcomm bnep btusb bluetooth rfkill babel nfs fscache auth_rpcgss nfs_acl lockd iTCO_wdt iTCO_vendor_support i2c_i801 i2c_core tg3 joydev sunrpc uinput microcode hpsa usb_storage uas [last unloaded: scsi_wait_scan]
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.192109]
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.192442] Pid: 53, comm: kworker/6:1 Not tainted 3.1.0-7.fc16.x86_64 #1 HP ProLiant DL120 G6/ProLiant DL120 G6
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.193151] RIP: 0010:[<ffffffff812e53c9>] [<ffffffff812e53c9>] atomic_inc+0x9/0xe
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.193839] RSP: 0018:ffff88013868ddb0 EFLAGS: 00010202
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.194273] RAX: ffff880128191c78 RBX: 0000000000010130 RCX: ffff880128191c70
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.194625] RDX: ffff880128191c70 RSI: 0000000000000004 RDI: 00000000000102a0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.194979] RBP: ffff88013868ddb0 R08: ffff880128191c78 R09: 0000000000608007
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.195329] R10: 0000000000608007 R11: ffff88013fd92f80 R12: 0000000000010100
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.195680] R13: 0000000000010130 R14: 0000000000000004 R15: ffff88013fd96805
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.196032] FS: 0000000000000000(0000) GS:ffff88013fd80000(0000) knlGS:0000000000000000
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.196716] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.197063] CR2: 00000000000102a0 CR3: 000000012a613000 CR4: 00000000000006e0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.197422] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.197780] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.198138] Process kworker/6:1 (pid: 53, threadinfo ffff88013868c000, task ffff880138690000)
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.198811] Stack:
Message from syslogd@naveen-OptiPlex-745 at Oct 6 19:49:24 ...
kernel:[ 979.189989] Oops: 0002 [#1] SMP
Message from syslogd@naveen-OptiPlex-745 at Oct 6 19:49:24 ...
kernel:[ 979.198811] Stack:
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.199146] ffff88013868ddf0 ffffffff812e645c ffffffff81605920 ffff88013fd92f80
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.199831] ffff880128191c70 0000000000010100 0000000000010130 ffffffffa0091b49
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.200525] ffff88013868de20 ffffffff8133a672 ffff880128191c70 ffff880128191c70
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.201211] Call Trace:
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.201550] [<ffffffff812e645c>] __pm_runtime_resume+0x2c/0x65
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.201907] [<ffffffffa0091b49>] ? btusb_submit_intr_urb+0x173/0x173 [btusb]
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.202268] [<ffffffff8133a672>] usb_autopm_get_interface+0x23/0x52
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.202626] [<ffffffffa0091b60>] clear_halt_intr_in+0x17/0xac [btusb]
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.202978] [<ffffffff8106edbc>] process_one_work+0x176/0x2a9
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.203331] [<ffffffff8106f8ca>] worker_thread+0xda/0x15d
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.203680] [<ffffffff8106f7f0>] ? manage_workers+0x176/0x176
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.204022] [<ffffffff81072d17>] kthread+0x84/0x8c
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.204365] [<ffffffff814be5f4>] kernel_thread_helper+0x4/0x10
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.204711] [<ffffffff81072c93>] ? kthread_worker_fn+0x148/0x148
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.205058] [<ffffffff814be5f0>] ? gs_change+0x13/0x13
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.205402] Code: d9 81 e8 07 f6 ff ff 80 3d 24 26 ab 00 00 75 05 e8 da f7 ff ff 8a 05 17 26 ab 00 41 5b 5b 5d c3 90 90 55 48 89 e5 66 66 66 66 90 <f0> ff 07 5d c3 55 48 89 e5 66 66 66 66 90 f0 ff 0f 0f 94 c0 84
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.206652] RIP [<ffffffff812e53c9>] atomic_inc+0x9/0xe
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.207007] RSP <ffff88013868ddb0>
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.207354] CR2: 00000000000102a0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208287] ---[ end trace 0089da2b8191af16 ]---
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208739] BUG: unable to handle kernel paging request at fffffffffffffff8
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208742] IP: [<ffffffff81072f65>] kthread_data+0x11/0x16
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208747] PGD 1a07067 PUD 1a08067 PMD 0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208749] Oops: 0000 [#2] SMP
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208752] CPU 6
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208753] Modules linked in: rfcomm bnep btusb bluetooth rfkill babel nfs fscache auth_rpcgss nfs_acl lockd iTCO_wdt iTCO_vendor_support i2c_i801 i2c_core tg3 joydev sunrpc uinput microcode hpsa usb_storage uas [last unloaded: scsi_wait_scan]
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208765]
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208768] Pid: 53, comm: kworker/6:1 Tainted: G D 3.1.0-7.fc16.x86_64 #1 HP ProLiant DL120 G6/ProLiant DL120 G6
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208772] RIP: 0010:[<ffffffff81072f65>] [<ffffffff81072f65>] kthread_data+0x11/0x16
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208777] RSP: 0018:ffff88013868d990 EFLAGS: 00010002
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208779] RAX: 0000000000000000 RBX: ffff88013fd92f80 RCX: 0000000000000006
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208781] RDX: 0000000000000006 RSI: 0000000000000006 RDI: ffff880138690000
Message from syslogd@naveen-OptiPlex-745 at Oct 6 19:49:24 ...
kernel:[ 979.201211] Call Trace:
Message from syslogd@naveen-OptiPlex-745 at Oct 6 19:49:24 ...
kernel:[ 979.205402] Code: d9 81 e8 07 f6 ff ff 80 3d 24 26 ab 00 00 75 05 e8 da f7 ff ff 8a 05 17 26 ab 00 41 5b 5b 5d c3 90 90 55 48 89 e5 66 66 66 66 90 <f0> ff 07 5d c3 55 48 89 e5 66 66 66 66 90 f0 ff 0f 0f 94 c0 84
Message from syslogd@naveen-OptiPlex-745 at Oct 6 19:49:24 ...
kernel:[ 979.207354] CR2: 00000000000102a0
Message from syslogd@naveen-OptiPlex-745 at Oct 6 19:49:24 ...
kernel:[ 979.208749] Oops: 0000 [#2] SMP
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208784] RBP: ffff88013868d9b8 R08: ffff880138690070 R09: dead000000200200
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208786] R10: dead000000200200 R11: ffff88013fd92f80 R12: 0000000000000006
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208788] R13: ffff88013868daa0 R14: 0000000000000006 R15: ffff8801386903c8
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208791] FS: 0000000000000000(0000) GS:ffff88013fd80000(0000) knlGS:0000000000000000
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208794] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208796] CR2: fffffffffffffff8 CR3: 000000012a613000 CR4: 00000000000006e0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208799] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208801] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208804] Process kworker/6:1 (pid: 53, threadinfo ffff88013868c000, task ffff880138690000)
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208806] Stack:
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208807] ffffffff8106fc19 dead000000200200 ffff88013fd92f80 ffff8801386905e0
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208811] ffff88013868daa0 ffff88013868da48 ffffffff814b4128 ffff88013b006d00
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208814] ffff88013868daa0 ffff880138690000 ffff88013868dfd8 ffff88013868dfd8
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208816] Call Trace:
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208819] [<ffffffff8106fc19>] ? wq_worker_sleeping+0x18/0x82
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208823] [<ffffffff814b4128>] __schedule+0x15d/0x669
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208826] [<ffffffff814b4897>] schedule+0x5a/0x5c
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208829] [<ffffffff8105b4e4>] do_exit+0x74d/0x764
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208832] [<ffffffff814b6eae>] oops_end+0xbc/0xc5
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208835] [<ffffffff814ac438>] no_context+0x203/0x212
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208837] [<ffffffff814ac612>] __bad_area_nosemaphore+0x1cb/0x1ec
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208840] [<ffffffff814ac646>] bad_area_nosemaphore+0x13/0x15
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208842] [<ffffffff814b8e56>] do_page_fault+0x1b8/0x37e
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208845] [<ffffffff814b63b5>] page_fault+0x25/0x30
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208848] [<ffffffff812e53c9>] ? atomic_inc+0x9/0xe
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208850] [<ffffffff812e645c>] __pm_runtime_resume+0x2c/0x65
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208853] [<ffffffffa0091b49>] ? btusb_submit_intr_urb+0x173/0x173 [btusb]
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208856] [<ffffffff8133a672>] usb_autopm_get_interface+0x23/0x52
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208859] [<ffffffffa0091b60>] clear_halt_intr_in+0x17/0xac [btusb]
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208861] [<ffffffff8106edbc>] process_one_work+0x176/0x2a9
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208864] [<ffffffff8106f8ca>] worker_thread+0xda/0x15d
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208866] [<ffffffff8106f7f0>] ? manage_workers+0x176/0x176
Message from syslogd@naveen-OptiPlex-745 at Oct 6 19:49:24 ...
kernel:[ 979.208806] Stack:
Message from syslogd@naveen-OptiPlex-745 at Oct 6 19:49:24 ...
kernel:[ 979.208816] Call Trace:
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208868] [<ffffffff81072d17>] kthread+0x84/0x8c
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208871] [<ffffffff814be5f4>] kernel_thread_helper+0x4/0x10
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208873] [<ffffffff81072c93>] ? kthread_worker_fn+0x148/0x148
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208876] [<ffffffff814be5f0>] ? gs_change+0x13/0x13
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208877] Code: 8d b0 30 64 60 81 4c 29 e6 e8 60 01 fe ff 81 4b 14 00 00 00 04 5b 41 5c 5d c3 55 48 89 e5 66 66 66 66 90 48 8b 87 70 03 00 00 5d
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208890] RIP [<ffffffff81072f65>] kthread_data+0x11/0x16
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208893] RSP <ffff88013868d990>
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208894] CR2: fffffffffffffff8
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208895] ---[ end trace 0089da2b8191af17 ]---
Oct 6 19:49:24 naveen-OptiPlex-745 kernel: [ 979.208897] Fixing recursive fault but reboot is needed!
Message from syslogd@naveen-OptiPlex-745 at Oct 6 19:49:24 ...
kernel:[ 979.208877] Code: 8d b0 30 64 60 81 4c 29 e6 e8 60 01 fe ff 81 4b 14 00 00 00 04 5b 41 5c 5d c3 55 48 89 e5 66 66 66 66 90 48 8b 87 70 03 00 00 5d
Message from syslogd@naveen-OptiPlex-745 at Oct 6 19:49:24 ...
kernel:[ 979.208894] CR2: fffffffffffffff8
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-06 13:03 ` Naveen Kumar Parna
@ 2014-10-06 13:29 ` Oliver Neukum
2014-10-06 14:38 ` Naveen Kumar Parna
0 siblings, 1 reply; 45+ messages in thread
From: Oliver Neukum @ 2014-10-06 13:29 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: linux-bluetooth, linux-usb, acho
[-- Attachment #1: Type: text/plain, Size: 145 bytes --]
On Mon, 2014-10-06 at 18:33 +0530, Naveen Kumar Parna wrote:
> Thank you very much. I will try that patch.
Then please try.
Regards
Oliver
[-- Attachment #2: 0001-btusb-clear-halt-if-intr-in-stalls.patch --]
[-- Type: text/x-patch, Size: 2652 bytes --]
>From f9f74591abed07ee71c46d443dd10176d05096c5 Mon Sep 17 00:00:00 2001
From: Oliver Neukum <oneukum@suse.de>
Date: Mon, 6 Oct 2014 15:27:54 +0200
Subject: [PATCH] btusb: clear halt if intr in stalls
Use a work queue for clearing a halt.
Signed-off-by: Oliver Neukum <oneukum@suse.de>
---
drivers/bluetooth/btusb.c | 34 ++++++++++++++++++++++++++++++++--
1 file changed, 32 insertions(+), 2 deletions(-)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 292c38e..65a2c6b 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -273,6 +273,7 @@ struct btusb_data {
struct work_struct work;
struct work_struct waker;
+ struct work_struct intr_in_work;
struct usb_anchor tx_anchor;
struct usb_anchor intr_anchor;
@@ -314,14 +315,15 @@ static void btusb_intr_complete(struct urb *urb)
struct hci_dev *hdev = urb->context;
struct btusb_data *data = hci_get_drvdata(hdev);
int err;
+ int status = urb->status;
BT_DBG("%s urb %p status %d count %d", hdev->name,
- urb, urb->status, urb->actual_length);
+ urb, status, urb->actual_length);
if (!test_bit(HCI_RUNNING, &hdev->flags))
return;
- if (urb->status == 0) {
+ if (status == 0) {
hdev->stat.byte_rx += urb->actual_length;
if (hci_recv_fragment(hdev, HCI_EVENT_PKT,
@@ -330,6 +332,10 @@ static void btusb_intr_complete(struct urb *urb)
BT_ERR("%s corrupted event packet", hdev->name);
hdev->stat.err_rx++;
}
+ } else if (status == -EPIPE) {
+ usb_mark_last_busy(data->udev);
+ schedule_work(&data->intr_in_work);
+ return;
}
if (!test_bit(BTUSB_INTR_RUNNING, &data->flags))
@@ -971,6 +977,29 @@ static void btusb_waker(struct work_struct *work)
usb_autopm_put_interface(data->intf);
}
+static void clear_halt_intr_in(struct work_struct *work)
+{
+ struct btusb_data *data = container_of(work, struct btusb_data, waker);
+ int err;
+
+ err = usb_autopm_get_interface(data->intf);
+ if (err < 0)
+ return;
+
+ err = usb_clear_halt(data->udev,
+ usb_rcvbulkpipe(data->udev,
+ data->intr_ep->bEndpointAddress));
+ if (err < 0)
+ return;
+
+ if (!test_bit(BTUSB_INTR_RUNNING, &data->flags))
+ return;
+
+ btusb_submit_intr_urb(data->hdev, GFP_ATOMIC);
+
+ usb_autopm_put_interface(data->intf);
+}
+
static int btusb_setup_bcm92035(struct hci_dev *hdev)
{
struct sk_buff *skb;
@@ -1759,6 +1788,7 @@ static int btusb_probe(struct usb_interface *intf,
INIT_WORK(&data->work, btusb_work);
INIT_WORK(&data->waker, btusb_waker);
+ INIT_WORK(&data->intr_in_work, clear_halt_intr_in);
spin_lock_init(&data->txlock);
init_usb_anchor(&data->tx_anchor);
--
1.8.4.5
^ permalink raw reply related [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-06 12:55 ` Oliver Neukum
@ 2014-10-06 13:03 ` Naveen Kumar Parna
2014-10-06 13:29 ` Oliver Neukum
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-06 13:03 UTC (permalink / raw)
To: Oliver Neukum; +Cc: linux-bluetooth, linux-usb
Thank you very much. I will try that patch.
Thanks,
Naveen
On Mon, Oct 6, 2014 at 6:25 PM, Oliver Neukum <oneukum@suse.de> wrote:
> On Mon, 2014-10-06 at 18:18 +0530, Naveen Kumar Parna wrote:
>> Hi,
>>
>> I just collected the usbmon log(1.mon.out) and attached it. It stalls
>> for INT in transfers.
>>
>> Corresponding kernel log is here:
>> Oct 6 18:00:48 naveen-OptiPlex-745 kernel: [ 7528.718473] hci3 urb
>> ffff88012954dd80 status -32 count 0
>> Oct 6 18:05:35 naveen-OptiPlex-745 kernel: [ 7814.688122] hci3 urb
>> ffff88012954dd80 status -32 count 0
>> Oct 6 18:05:35 naveen-OptiPlex-745 kernel: [ 7814.693086] hci3 urb
>> ffff88012954dd80 status -32 count 0
>> Oct 6 18:05:35 naveen-OptiPlex-745 kernel: [ 7814.695058] hci3 urb
>> ffff88012954dd80 status -32 count 0
>> Oct 6 18:05:35 naveen-OptiPlex-745 kernel: [ 7814.703073] hci3 urb
>> ffff88012954dd80 status -32 count 0
>> Oct 6 18:05:35 naveen-OptiPlex-745 kernel: [ 7814.717038] hci5 urb
>> ffff88012954de40 status -32 count 0
>> Oct 6 18:05:35 naveen-OptiPlex-745 kernel: [ 7814.717496] hci3 urb
>> ffff88012954dd80 status -32 count 0
>>
>> Corresponding Usbmon trace:
>> ffff88012954dd80 2936526502 C Ii:1:009:1 -32:1 0
>> ffff88012954dd80 3223215374 C Ii:1:009:1 -32:1 0
>> ffff88012954dd80 3223220352 C Ii:1:009:1 -32:1 0
>> ffff88012954dd80 3223222332 C Ii:1:009:1 -32:1 0
>> ffff88012954dd80 3223230362 C Ii:1:009:1 -32:1 0
>> ffff88012954de40 3223244362 C Ii:1:019:1 -32:1 0
>> ffff88012954dd80 3223244830 C Ii:1:009:1 -32:1 0
>>
>> Does it gives any clue?
>
> Not really. I'll make a patch to clear the condition.
> Let's see what happens then.
>
> Regards
> Oliver
>
>
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
[not found] ` <CAG0bkv+nKt-TgONDLENNUncz9NScdJGcYR+J2Z6b=wg2grvqhg@mail.gmail.com>
@ 2014-10-06 12:55 ` Oliver Neukum
2014-10-06 13:03 ` Naveen Kumar Parna
0 siblings, 1 reply; 45+ messages in thread
From: Oliver Neukum @ 2014-10-06 12:55 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: linux-bluetooth, linux-usb
On Mon, 2014-10-06 at 18:18 +0530, Naveen Kumar Parna wrote:
> Hi,
>
> I just collected the usbmon log(1.mon.out) and attached it. It stalls
> for INT in transfers.
>
> Corresponding kernel log is here:
> Oct 6 18:00:48 naveen-OptiPlex-745 kernel: [ 7528.718473] hci3 urb
> ffff88012954dd80 status -32 count 0
> Oct 6 18:05:35 naveen-OptiPlex-745 kernel: [ 7814.688122] hci3 urb
> ffff88012954dd80 status -32 count 0
> Oct 6 18:05:35 naveen-OptiPlex-745 kernel: [ 7814.693086] hci3 urb
> ffff88012954dd80 status -32 count 0
> Oct 6 18:05:35 naveen-OptiPlex-745 kernel: [ 7814.695058] hci3 urb
> ffff88012954dd80 status -32 count 0
> Oct 6 18:05:35 naveen-OptiPlex-745 kernel: [ 7814.703073] hci3 urb
> ffff88012954dd80 status -32 count 0
> Oct 6 18:05:35 naveen-OptiPlex-745 kernel: [ 7814.717038] hci5 urb
> ffff88012954de40 status -32 count 0
> Oct 6 18:05:35 naveen-OptiPlex-745 kernel: [ 7814.717496] hci3 urb
> ffff88012954dd80 status -32 count 0
>
> Corresponding Usbmon trace:
> ffff88012954dd80 2936526502 C Ii:1:009:1 -32:1 0
> ffff88012954dd80 3223215374 C Ii:1:009:1 -32:1 0
> ffff88012954dd80 3223220352 C Ii:1:009:1 -32:1 0
> ffff88012954dd80 3223222332 C Ii:1:009:1 -32:1 0
> ffff88012954dd80 3223230362 C Ii:1:009:1 -32:1 0
> ffff88012954de40 3223244362 C Ii:1:019:1 -32:1 0
> ffff88012954dd80 3223244830 C Ii:1:009:1 -32:1 0
>
> Does it gives any clue?
Not really. I'll make a patch to clear the condition.
Let's see what happens then.
Regards
Oliver
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: btusb_intr_complete returns -EPIPE
2014-10-06 11:35 Naveen Kumar Parna
@ 2014-10-06 12:24 ` Oliver Neukum
[not found] ` <CAG0bkv+nKt-TgONDLENNUncz9NScdJGcYR+J2Z6b=wg2grvqhg@mail.gmail.com>
0 siblings, 1 reply; 45+ messages in thread
From: Oliver Neukum @ 2014-10-06 12:24 UTC (permalink / raw)
To: Naveen Kumar Parna; +Cc: linux-bluetooth, linux-usb
On Mon, 2014-10-06 at 17:05 +0530, Naveen Kumar Parna wrote:
> These errors will repeat until sending a proper HCI command on the USB
> bus. Again after some time duration same error will repeats.
>
> The error -32(-EPIPE) says , Endpoint stalled. For non-control
> endpoints, reset this status with usb_clear_halt().
>
> But I don’t see the error(-EPIPE) handling code in btusb module. Does
> anyone has the patch for this scenario?
It really shouldn't stall without reason. We need to know which
transfers stall. A usbmon trace would show you.
Regards
Oliver
^ permalink raw reply [flat|nested] 45+ messages in thread
* btusb_intr_complete returns -EPIPE
@ 2014-10-06 12:23 Naveen Kumar Parna
0 siblings, 0 replies; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-06 12:23 UTC (permalink / raw)
To: linux-usb; +Cc: linux-bluetooth
Hi,
I am using “3.1.0-7.fc16.x86_64” kernel and testing eight USB
Bluetooth dongles using btusb.ko module.
Once I power-on the system and loading the btusb.ko driver immediately
results the below mentioned errors:
[ 1389.410907] hci3 urb ffff88012954dd80 status -32 count 0
[ 1389.411367] hci4 urb ffff88012954d3c0 status -32 count 0
[ 1389.411845] hci1 urb ffff88012b4b6b40 status -32 count 0
[ 1389.412238] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 1518.647255] hci3 urb ffff88012954dd80 status -32 count 0
[ 1518.647722] hci4 urb ffff88012954d3c0 status -32 count 0
[ 1518.648120] hci1 urb ffff88012b4b6b40 status -32 count 0
[ 1518.648514] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 1518.722033] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 2191.964545] hci4 urb ffff88012954d3c0 status -32 count 0
[ 2191.965001] hci1 urb ffff88012b4b6b40 status -32 count 0
[ 2191.965396] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 2191.966530] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 2191.975514] hci4 urb ffff88012954d3c0 status -32 count 0
[ 2191.975936] hci1 urb ffff88012b4b6b40 status -32 count 0
[ 2191.976330] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 2191.977503] hci4 urb ffff88012954d3c0 status -32 count 0
[ 2191.977929] hci1 urb ffff88012b4b6b40 status -32 count 0
[ 2191.978325] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 2560.132682] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 2569.160895] hci4 urb ffff88012954d3c0 status -32 count 0
[ 2569.161367] hci1 urb ffff88012b4b6b40 status -32 count 0
[ 2569.161827] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 3022.252541] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 3022.254504] hci2 urb ffff8801347ee0c0 status -32 count 0
These errors will repeat until sending a proper HCI command on the USB
bus. Again after some time duration same error will repeats.
The error -32(-EPIPE) says , Endpoint stalled. For non-control
endpoints, reset this status with usb_clear_halt().
But I don’t see the error(-EPIPE) handling code in btusb module. Does
anyone has the patch for this scenario?
Thanks,
Naveen
^ permalink raw reply [flat|nested] 45+ messages in thread
* btusb_intr_complete returns -EPIPE
@ 2014-10-06 11:35 Naveen Kumar Parna
2014-10-06 12:24 ` Oliver Neukum
0 siblings, 1 reply; 45+ messages in thread
From: Naveen Kumar Parna @ 2014-10-06 11:35 UTC (permalink / raw)
To: linux-bluetooth, linux-usb
Hi,
I am using “3.1.0-7.fc16.x86_64” kernel and testing eight USB
Bluetooth dongles using btusb.ko module.
Once I power-on the system and loading the btusb.ko driver immediately
results the below mentioned errors:
[ 1389.410907] hci3 urb ffff88012954dd80 status -32 count 0
[ 1389.411367] hci4 urb ffff88012954d3c0 status -32 count 0
[ 1389.411845] hci1 urb ffff88012b4b6b40 status -32 count 0
[ 1389.412238] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 1518.647255] hci3 urb ffff88012954dd80 status -32 count 0
[ 1518.647722] hci4 urb ffff88012954d3c0 status -32 count 0
[ 1518.648120] hci1 urb ffff88012b4b6b40 status -32 count 0
[ 1518.648514] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 1518.722033] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 2191.964545] hci4 urb ffff88012954d3c0 status -32 count 0
[ 2191.965001] hci1 urb ffff88012b4b6b40 status -32 count 0
[ 2191.965396] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 2191.966530] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 2191.975514] hci4 urb ffff88012954d3c0 status -32 count 0
[ 2191.975936] hci1 urb ffff88012b4b6b40 status -32 count 0
[ 2191.976330] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 2191.977503] hci4 urb ffff88012954d3c0 status -32 count 0
[ 2191.977929] hci1 urb ffff88012b4b6b40 status -32 count 0
[ 2191.978325] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 2560.132682] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 2569.160895] hci4 urb ffff88012954d3c0 status -32 count 0
[ 2569.161367] hci1 urb ffff88012b4b6b40 status -32 count 0
[ 2569.161827] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 3022.252541] hci2 urb ffff8801347ee0c0 status -32 count 0
[ 3022.254504] hci2 urb ffff8801347ee0c0 status -32 count 0
These errors will repeat until sending a proper HCI command on the USB
bus. Again after some time duration same error will repeats.
The error -32(-EPIPE) says , Endpoint stalled. For non-control
endpoints, reset this status with usb_clear_halt().
But I don’t see the error(-EPIPE) handling code in btusb module. Does
anyone has the patch for this scenario?
Thanks,
Naveen
^ permalink raw reply [flat|nested] 45+ messages in thread
end of thread, other threads:[~2014-11-11 15:56 UTC | newest]
Thread overview: 45+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CAG0bkv+DL0bVs9irE7eUB3rC-J16Ue=b9+_TqeuTHJYMJDkC0g@mail.gmail.com>
2014-11-06 16:44 ` btusb_intr_complete returns -EPIPE Alan Stern
2014-11-10 6:38 ` Naveen Kumar Parna
2014-11-10 16:56 ` Alan Stern
2014-11-11 9:53 ` Naveen Kumar Parna
2014-11-11 15:56 ` Alan Stern
2014-11-10 9:29 ` Naveen Kumar Parna
[not found] <CAG0bkv+YY90Tq1aTw1Dbg-RSVadoP2U6tyVpW1bZSxBfQ=3Y4g@mail.gmail.com>
2014-11-03 16:19 ` Alan Stern
2014-11-05 6:58 ` Naveen Kumar Parna
2014-11-05 21:09 ` Alan Stern
[not found] <CAG0bkvJDLP2tgnzu7H_ZCRCnZwkw1zUd1uqWwoDkmrU_FLts7w@mail.gmail.com>
2014-10-09 14:31 ` Alan Stern
2014-10-15 10:11 ` Oliver Neukum
2014-10-15 13:09 ` Naveen Kumar Parna
2014-10-15 13:46 ` Naveen Kumar Parna
2014-10-15 16:11 ` Alan Stern
2014-10-16 7:13 ` Naveen Kumar Parna
2014-10-16 14:16 ` Alan Stern
2014-10-16 15:32 ` Naveen Kumar Parna
2014-10-28 12:40 ` Naveen Kumar Parna
2014-10-28 17:27 ` Alan Stern
[not found] ` <CAG0bkvL-qy+Wvp7q39TOaQ1dZDd0PKyoXHjO=5TrJvdC8byr8A@mail.gmail.com>
2014-10-31 11:27 ` Naveen Kumar Parna
2014-10-31 20:51 ` Alan Stern
2014-10-16 9:15 ` Oliver Neukum
2014-10-16 10:54 ` Naveen Kumar Parna
2014-10-16 14:09 ` Alan Stern
2014-10-16 15:05 ` Naveen Kumar Parna
2014-10-27 9:19 ` Naveen Kumar Parna
2014-10-06 12:23 Naveen Kumar Parna
-- strict thread matches above, loose matches on Subject: below --
2014-10-06 11:35 Naveen Kumar Parna
2014-10-06 12:24 ` Oliver Neukum
[not found] ` <CAG0bkv+nKt-TgONDLENNUncz9NScdJGcYR+J2Z6b=wg2grvqhg@mail.gmail.com>
2014-10-06 12:55 ` Oliver Neukum
2014-10-06 13:03 ` Naveen Kumar Parna
2014-10-06 13:29 ` Oliver Neukum
2014-10-06 14:38 ` Naveen Kumar Parna
2014-10-06 14:50 ` Oliver Neukum
[not found] ` <CAG0bkvKJZMhurNNpc_2wgaACRzhyEikb0G0YSY7QnxqBe1rnjw@mail.gmail.com>
2014-10-07 6:44 ` Naveen Kumar Parna
2014-10-07 10:01 ` Oliver Neukum
2014-10-07 13:34 ` Naveen Kumar Parna
2014-10-07 14:31 ` Naveen Kumar Parna
2014-10-08 9:09 ` Oliver Neukum
2014-10-08 10:21 ` Naveen Kumar Parna
2014-10-08 10:44 ` Oliver Neukum
2014-10-08 13:01 ` Naveen Kumar Parna
2014-10-08 13:17 ` Oliver Neukum
2014-10-08 14:10 ` Naveen Kumar Parna
2014-10-08 14:46 ` Alan Stern
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.