From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-qa0-f46.google.com ([209.85.216.46]:52297 "EHLO mail-qa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751766Ab2CXCPh (ORCPT ); Fri, 23 Mar 2012 22:15:37 -0400 Message-ID: <4F6D2E76.90204@gmail.com> (sfid-20120324_031548_768085_9A1E9039) Date: Fri, 23 Mar 2012 22:16:22 -0400 From: Richard Farina MIME-Version: 1.0 To: Sarah Sharp CC: Larry Finger , jerome huang , "Xu, Andiry" , linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org Subject: Re: rt8192cu on USB3 References: <4F585BA9.6020903@amd.com> <2A76B9D36150BE4293842BC2FE8FF165016A31@SCYBEXDAG04.amd.com> <4F58F2D0.5060805@lwfinger.net> <4F59800B.80407@lwfinger.net> <20120322223107.GA8877@xanatos> <4F6BDEDF.2020907@lwfinger.net> <20120323203404.GD5207@xanatos> In-Reply-To: <20120323203404.GD5207@xanatos> Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 03/23/12 16:34, Sarah Sharp wrote: > On Thu, Mar 22, 2012 at 09:24:31PM -0500, Larry Finger wrote: >> On 03/22/2012 05:31 PM, Sarah Sharp wrote: >> >>> Larry, if the driver doesn't cancel an URB that the device doesn't >>> respond to, then it will just be left on the endpoint ring. If the >>> driver then tries to queue new transfers to that same endpoint, but the >>> device keeps NAKing the uncancelled transfer, then the endpoint ring >>> would fill up with unanswered transfers. >>> >>> Perhaps some userspace or kernel portion is forgetting to cancel URBs >>> before moving onto the next thing? You said you moved to asynchronous >>> transfers, so maybe the problem lies there? >> The writes have always been asynchronous and reads are synchronous. >> The only change was to convert the firmware uploading writes from >> 32-bits at a time into block writes of 1000+ 32-bit words. > Yeah, that's going to cause the out-of-room warning under xHCI. That > should be fixed in the 3.4-rc1 kernel though. Given that I can replicate this issue using several different drivers, should I test using 3.4_rc1 kernel to see if the usb is fixed or using compat-wireless based on 3.4_rc1 to see if the drivers are fixed? Or both? Thanks, Rick > >> Would xhci be worse that ohci or ehci in terms of the device not >> responding to URBs? We only see problems with USB3.0 hubs, never >> with 2.0 or 1.1. > That's because EHCI handles arbitrarily large transfers, and xHCI didn't > until now. > >> I am looking into changing the writes to be synchronous. That should >> clear up any problems. > Yeah, your problem probably was in the bulk large transfer, not the > unfinished canceled URBs. I would suggest getting your reporters to > just try 3.4-rc1 and see if it helps before doing too much work to debug > this. > > Sarah Sharp > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >