From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
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: Wed, 22 Jul 2015 16:12:58 +0200 [thread overview]
Message-ID: <201507221612.58846.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <55AE5B02.1000908@linux.intel.com>
[sorry, resend from different email - vger postmaster team has stupid filters
in place]
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
>
> Looks like we get an event for a really old transfer for some reason, it
> should probably be handled already.
>
> I got a patch that adds more paranoid checks for TRB cancel, which has been
> one major reasons for the "Transfer event TRB DMA ptr not part of current
> TD" Errors. It also adds some logging to show what's went wrong. (patch
> attached, applies on 4.2-rc3) Can you see if it helps?
It doesn't unfortunately. 4.2.0-rc3-00017-gd725e66 + that patch
-> dmesg http://sprunge.us/PDIE
around 91s - after resume from ram bluetooth driver reloads
around 754s - tried to copy data from external usb disk
> If it doesn't, then adding xhci debugging could give us some clue:
> echo -n 'module xhci_hcd =p' > /sys/kernel/debug/dynamic_debug/control
Ok, http://sprunge.us/GiHX
mounted fs around 1347s and started copying; TRB problems were still there but
file was being copied (in bursts)
> You said 3.19.3 works fine, but 4.0.8 and 4.2-rc2 fail, any chance you
> could bisect it?
Unfortunately some kernels around 3.19 don't even boot (grub says it loads
initrd and no progress from that) - some commit fixed that but no idea which
one.
> Thanks
> -Mathias
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
next prev parent reply other threads:[~2015-07-22 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 14:49 Arkadiusz Miskiewicz
2015-07-20 20:13 ` Arkadiusz Miskiewicz
2015-07-21 14:45 ` Mathias Nyman
2015-07-22 14:12 ` Arkadiusz Miskiewicz [this message]
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
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=201507221612.58846.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=arekm@maven.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.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
Powered by JetHome