linux-kernel - RE: [BUGREPORT] Linux USB 3.0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <063D6719AE5E284EB5DD2968C1650D6D0F6B8058@AcuExch.aculab.com>
Date:	Tue, 4 Feb 2014 09:31:52 +0000
From:	David Laight <David.Laight@...LAB.COM>
To:	'Markus Rechberger' <mrechberger@...il.com>,
	Sarah Sharp <sarah.a.sharp@...ux.intel.com>
CC:	LKML <linux-kernel@...r.kernel.org>,
	USB list <linux-usb@...r.kernel.org>,
	Alan Stern <stern@...land.harvard.edu>,
	Greg KH <gregkh@...uxfoundation.org>
Subject: RE: [BUGREPORT] Linux USB 3.0

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.

	David



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/