From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: alex zheng <tc0721@gmail.com>
Cc: Felipe Balbi <felipe.balbi@linux.intel.com>,
linux-usb@vger.kernel.org, xiaowei.zheng@dji.com
Subject: Re: BUG report: usb: dwc3: Link TRB triggered an intterupt without IOC being setted
Date: Wed, 25 Sep 2019 17:48:11 +0300 [thread overview]
Message-ID: <5431a9df-3816-b525-c3bc-4e7462d0f38f@linux.intel.com> (raw)
In-Reply-To: <CADGPSwi87a5+3mCGAgptHgpBsQk9STQrEKs-kC6Nw55nPdRtOw@mail.gmail.com>
On 24.9.2019 17.45, alex zheng wrote:
> Hi Mathias,
>
> I try to ignore the DMA errors, then the transfer continues but it
> complete with data lost, it seems like these ERROR Transfer event
> should be right and must not be ignore.
>
> test app show:
> "did not get enough data, received size:14410176/15000000"
>
> kernel log show: (you can see more detail info in the attached log files)
Logs show your transfer ring has four segments, but hardware fails to
jump from the last segment back to first)
Last TRB (LINK TRB) of each segment points to the next segment,
last segments link trb points back to first segment.
In your case:
0x1d117000 -> 0x1eb09000 -> 0x1eb0a000 -> 0x1dbda000 -> (back to 0x1d117000)
For some reason your hardware doesn't treat the last TRB at the last segment
as a LINK TRB, instead it just issues a transfer event for it, and continues to
the next address instead of jumping back to first segment:
Transfer event for last TRB at last segment: 0x1dbda000 (TRB: 0x1dbdaff0):
This is a link TRB and should not generate transfer event:
xhci-hcd.0.auto: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 16 comp_code 1
xhci-hcd xhci-hcd.0.auto: Looking for event-dma 000000001dbdaff0 trb-start 000000001d117000 trb-end 000000001d117000 seg-start 000000001d117000 seg-end 000000001d10
xhci-hcd xhci-hcd.0.auto: Ignoring error
Next transfer event should be for TRB at fisrt segment (0x1d117000)
but event shows its trying to handle a event from TRB at 000000001dbdb000, which isn't even part of the ring.
xhci-hcd xhci-hcd.0.auto: process trans event : ep_index = 16, event_dma = 1dbdb000
xhci-hcd xhci-hcd.0.auto: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 16 comp_code 1
xhci-hcd xhci-hcd.0.auto: Looking for event-dma 000000001dbdb000 trb-start 000000001d117000 trb-end 000000001d117000 seg-start 000000001d117000 seg-end 000000001d10
xhci-hcd xhci-hcd.0.auto: Ignoring error
-Mathias
next prev parent reply other threads:[~2019-09-25 14:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 8:34 BUG report: usb: dwc3: Link TRB triggered an intterupt without IOC being setted alex zheng
2019-09-23 5:36 ` Felipe Balbi
2019-09-23 7:08 ` alex zheng
2019-09-23 10:15 ` Mathias Nyman
[not found] ` <CADGPSwi87a5+3mCGAgptHgpBsQk9STQrEKs-kC6Nw55nPdRtOw@mail.gmail.com>
2019-09-25 14:48 ` Mathias Nyman [this message]
2019-09-25 16:22 ` David Laight
2019-09-26 5:45 ` Felipe Balbi
2019-09-26 8:21 ` Mathias Nyman
2019-09-26 10:38 ` alex zheng
[not found] ` <CADGPSwhCPvdu=KmQP6RHMJnh292UO0uBAt+KyJqqOWY5DWDc3w@mail.gmail.com>
2019-10-23 9:52 ` alex zheng
2019-10-23 10:01 ` Felipe Balbi
2019-10-25 8:44 ` alex zheng
2019-09-23 10:45 ` Felipe Balbi
2019-09-24 14:19 ` alex zheng
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=5431a9df-3816-b525-c3bc-4e7462d0f38f@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=felipe.balbi@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=tc0721@gmail.com \
--cc=xiaowei.zheng@dji.com \
/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).