From: Greg KH <gregkh@linuxfoundation.org>
To: Markus Rechberger <mrechberger@gmail.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
David Laight <David.Laight@aculab.com>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [BUGREPORT] Linux USB 3.0
Date: Tue, 11 Feb 2014 10:45:11 -0800 [thread overview]
Message-ID: <20140211184511.GA32425@kroah.com> (raw)
In-Reply-To: <CA+O4pCL8gUqFs7zTJZ+0UftOq_jALpg=rsmz3hSypOPr2qZg7Q@mail.gmail.com>
On Tue, Feb 11, 2014 at 07:29:47PM +0100, Markus Rechberger wrote:
> On Mon, Feb 10, 2014 at 12:15 AM, Robert Hancock <hancockrwd@gmail.com> wrote:
> > On 08/02/14 03:00 AM, Markus Rechberger wrote:
> >>
> >> On Tue, Feb 4, 2014 at 10:31 AM, David Laight <David.Laight@aculab.com>
> >> wrote:
> >>>
> >>> From: Markus Rechberger
> >>>>>>
> >>>>>> Dec 27 23:23:50 solist kernel: [ 36.118245] xhci_hcd 0000:00:14.0:
> >>>>>> ERROR Transfer event TRB DMA
> >>>>
> >>>> ptr
> >>>>>
> >>>>>
> >>>>> These messages might be harmless. The 3.0 kernel contains a fix for
> >>>>> Intel Panther Point xHCI hosts that suppresses those messages, commit
> >>>>> ad808333d8201d53075a11bc8dd83b81f3d68f0b "Intel xhci: Ignore spurious
> >>>>> successful event."
> >>>>>
> >>>>> A later commit extends that to all xHCI 1.0 hosts, commit
> >>>>> 07f3cb7c28bf3f4dd80bfb136cf45810c46ac474 "usb: host: xhci: Enable
> >>>>> XHCI_SPURIOUS_SUCCESS for all controllers with xhci 1.0" That was
> >>>>> queued for 3.11 and marked to be backported into stable kernels as old
> >>>>> as 3.0.
> >>>
> >>>
> >>> I see the same error message on the 0.96 ASMedia controller when
> >>> the rx buffers for the ax88179_178a driver cross 64k boundaries.
> >>>
> >>> So this isn't confined to 1.0 controllers.
> >>>
> >>
> >> Sarah,
> >>
> >> since there is no response yet, is there anyone at Intel dedicated at
> >> working on USB 3.0?
> >> We are also getting more and more negative USB 3.0 feedback with Linux
> >
> >
> > Still nobody appears to have provided the requested debugging information
> > that was requested. So there is not much that can be done upstream to debug
> > things based only on vague reports, especially when not using current kernel
> > versions.
> >
>
> Next kernel crash report, this time a Synology NAS System:
> http://support.sundtek.com/index.php/topic,1511.0.html
That kernel has a closed source kernel module loaded, no community
member can look at it, sorry, please get support from the company that
wrote that module.
greg k-h
next prev parent reply other threads:[~2014-02-11 18:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-25 7:18 [BUGREPORT] Linux USB 3.0 Markus Rechberger
2013-12-27 17:18 ` Markus Rechberger
2013-12-27 19:59 ` Markus Rechberger
2013-12-28 6:24 ` Markus Rechberger
2014-01-20 19:35 ` Sarah Sharp
2014-02-03 23:08 ` Markus Rechberger
2014-02-04 9:31 ` David Laight
2014-02-08 9:00 ` Markus Rechberger
2014-02-08 13:06 ` Markus Rechberger
2014-02-09 23:15 ` Robert Hancock
2014-02-11 18:29 ` Markus Rechberger
2014-02-11 18:43 ` Bjørn Mork
2014-02-11 18:45 ` Greg KH [this message]
2014-02-11 19:32 ` Markus Rechberger
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=20140211184511.GA32425@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=David.Laight@aculab.com \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mrechberger@gmail.com \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stern@rowland.harvard.edu \
/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