linux-kernel - Re: Question about error from xhci-hcd

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] [day] [month] [year] [list]

Message-ID: <4EFC9A1D.4000601@lwfinger.net>
Date:	Thu, 29 Dec 2011 10:49:33 -0600
From:	Larry Finger <Larry.Finger@...inger.net>
To:	Andiry Xu <andiry.xu@....com>
CC:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
	USB list <linux-usb@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>, v4mp <gaigo88@...mail.it>
Subject: Re: Question about error from xhci-hcd

On 12/28/2011 10:30 PM, Andiry Xu wrote:
>
> That's the error I want to see, but I didn't find it in the dmesg you
> posted. is it wrapped?
>
> Anyway, please post the full dmesg with no room on ring error and the
> dump of the ep ring and event ring (so the xhci_debug_ring() is
> triggered in the patch), so we can see if the ring is mangled or there
> is just too many transfers.
>
> Another thing you can try is the andiry-ring-expansion branch on Sarah's
> xhci git tree, check if there is still no room on ring error.

No, the ring is not wrapped. I seems that my anti-spam mechanism kicked in too 
soon. or the run stopped too soon.

I'll have the OP do another run and see if we can get the right information.

Larry
--
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/