From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: "Jörg Otte" <jrg.otte@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"USB list" <linux-usb@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Subject: Re: [V4.0.0-rc3] Xhci Regression: ERROR Transfer event TRB DMA ptr not part of current TD
Date: Tue, 10 Mar 2015 15:06:26 +0200 [thread overview]
Message-ID: <54FEEC52.8080308@linux.intel.com> (raw)
In-Reply-To: <CADDKRnDPYxj8_iRd=S_Z4308v360nH41o24gHwB33TQsf-12mQ@mail.gmail.com>
On 10.03.2015 11:40, Jörg Otte wrote:
> If I plug in my USB DVB-T stick I get the following in dmesg:
>
> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm state.
> dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
> DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T Receiver)
> usb 1-1: DVB: registering adapter 0 frontend 0 (TerraTec/qanu USB2.0
> Highspeed DVB-T Receiver)...
> input: IR-receiver inside an USB DVB receiver as
> /devices/pci0000:00/0000:00:14.0/usb1/1-1/input/input17
> dvb-usb: schedule remote query interval to 50 msecs.
> xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of
> current TD ep_index 1 comp_code 1
> xhci_hcd 0000:00:14.0: Looking for event-dma 0000000207540400
> trb-start 0000000207540420 trb-end 0000000207540420 seg-start
> 00000002075404
> xhci_hcd 0000:00:14.0: ERROR Transfer event TRB DMA ptr not part of
> current TD ep_index 1 comp_code 1
> xhci_hcd 0000:00:14.0: Looking for event-dma 0000000207540410
> trb-start 0000000207540420 trb-end 0000000207540420 seg-start
> 00000002075404
> dvb-usb: bulk message failed: -110 (2/0)
>
> and DVB-T is not functional. The problem came in with:
>
> 1163d50 Merge tag 'usb-4.0-rc3' of
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb
>
> I never had this xhci_hcd error before so this is a regression.
>
>
> Thanks, Jörg
Oh, thanks.
Looks like we get an event for a TRB we just moved past.
Any chance you could take a log with xhci debugging enabled before attaching the DVB-T
stick?
echo -n 'module xhci_hcd =p' > /sys/kernel/debug/dynamic_debug/control
I'd suspect one of these two patches:
commit 45ba2154d12fc43b70312198ec47085f10be801a
xhci: fix reporting of 0-sized URBs in control endpoint
commit 27082e2654dc148078b0abdfc3c8e5ccbde0ebfa
xhci: Clear the host side toggle manually when endpoint is 'soft reset'
-Mathias
next prev parent reply other threads:[~2015-03-10 13:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 9:40 [V4.0.0-rc3] Xhci Regression: ERROR Transfer event TRB DMA ptr not part of current TD Jörg Otte
2015-03-10 13:06 ` Mathias Nyman [this message]
2015-03-10 14:03 ` Jörg Otte
2015-03-10 15:36 ` Jörg Otte
2015-03-10 17:04 ` Mathias Nyman
2015-03-10 17:29 ` Alan Stern
2015-03-10 18:21 ` Mathias Nyman
2015-03-10 18:49 ` Alan Stern
2015-03-11 7:04 ` Lu, Baolu
2015-03-11 14:03 ` Alan Stern
2015-03-11 15:48 ` Mathias Nyman
2015-03-11 9:00 ` Mathias Nyman
2015-03-11 11:01 ` Jörg Otte
2015-03-11 16:16 ` Jörg Otte
2015-03-12 8:32 ` 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=54FEEC52.8080308@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jrg.otte@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=torvalds@linux-foundation.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 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.