From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: arekm@maven.pl
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 1
Date: Mon, 03 Aug 2015 16:12:23 +0300 [thread overview]
Message-ID: <55BF68B7.5040804@linux.intel.com> (raw)
In-Reply-To: <201507241733.18308.a.miskiewicz@gmail.com>
On 24.07.2015 18:33, Arkadiusz Miskiewicz wrote:
> On Friday 24 of July 2015, Mathias Nyman wrote:
>> On 24.07.2015 14:59, Mathias Nyman wrote:
>>> On 22.07.2015 17:12, Arkadiusz Miskiewicz wrote:
>>>> On Tuesday 21 of July 2015, Mathias Nyman wrote:
>>>>> On 20.07.2015 23:13, Arkadiusz Miskiewicz wrote:
>>>>>> On Saturday 18 of July 2015, Arkadiusz Miskiewicz wrote:
>>>>>>> Hi.
>>>>>>>
>>>>>>> I'm on 4.2.0-rc2-00077-gf760b87 kernel and while trying to copy some
>>>>>>> file from usb storage (sata disk behind sata-usb bridge or pendrive;
>>>>>>> hapens in
>>>>>>
>>>>>>> both cases) copying process hangs just early after start with:
>>>>>> Looks like suspend & resume is enough. Reloading bluetooth firmware
>>>>>> done by kernel triggers problem:
>>>>>>
>>>>>> [ 106.302783] rtc_cmos 00:02: System wakeup disabled by ACPI
>>>>>> [ 106.313280] PM: resume of devices complete after 3003.032 msecs
>>>>>> [ 106.314079] Restarting tasks ... done.
>>>>>> [ 106.326434] Bluetooth: hci0: read Intel version: 370710018002030d00
>>>>>> [ 106.330422] Bluetooth: hci0: Intel Bluetooth firmware file:
>>>>>> intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq [ 106.398223] xhci_hcd
>>>>>> 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD
>>>>>> ep_index 0 comp_code 1
>>>
>>> Thanks for the logs, They show that the error is related to transfer
>>> descriptors that wrap around on the endpoint ring buffer by exactly one
>>> transfer block.
>>>
>>> I don't know yet why this happens, and I might need some help running
>>> additional debug patches to solve this. I'll take a more in depth look
>>> at the code one more time first.
>>
>> I think I found something, The recent ring segment size increase exposed an
>> off by one error that has been in the driver for a long time. But you need
>> to be unlucky and have your memory pages allocated in a specific order to
>> trigger it.
>>
>> small fix, looks like this:
>>
>> diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
>> index 94416ff..77da8fe 100644
>> --- a/drivers/usb/host/xhci-ring.c
>> +++ b/drivers/usb/host/xhci-ring.c
>> @@ -82,7 +82,7 @@ dma_addr_t xhci_trb_virt_to_dma(struct xhci_segment *seg,
>> return 0;
>> /* offset in TRBs */
>> segment_offset = trb - seg->trbs;
>> - if (segment_offset > TRBS_PER_SEGMENT)
>> + if (segment_offset > TRBS_PER_SEGMENT - 1)
>> return 0;
>> return seg->dma + (segment_offset * sizeof(*trb));
>> }
>>
>>
>> Patch attached, could you try it out?
>
> Works fine with this patch, so:
>
> Tested-by: Arkadiusz Miśkiewicz <arekm@maven.pl>
>
> Thanks!
>
> ps. please push to stable@, too
>
Patch sent forward, added Tested-by and stable tags
Thanks
- Mathias
prev parent reply other threads:[~2015-08-03 13:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 14:49 xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 1 Arkadiusz Miskiewicz
2015-07-20 20:13 ` Arkadiusz Miskiewicz
2015-07-21 14:45 ` Mathias Nyman
2015-07-22 14:12 ` Arkadiusz Miskiewicz
2015-07-24 11:59 ` Mathias Nyman
2015-07-24 13:39 ` Mathias Nyman
2015-07-24 13:53 ` Peter Stuge
2015-07-24 14:37 ` Mathias Nyman
2015-07-24 15:33 ` Arkadiusz Miskiewicz
2015-08-03 13:12 ` Mathias Nyman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55BF68B7.5040804@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=arekm@maven.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).