From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Greear Date: Sun, 22 Apr 2012 20:07:08 -0700 Subject: [ath9k-devel] Card AR928X very slow with new kernels In-Reply-To: References: <20120422005427.GA7640@nil> <20120423013957.5007.qmail@stuge.se> Message-ID: <4F94C75C.2070706@candelatech.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On 04/22/2012 07:35 PM, Mitch Davis wrote: > On Mon, Apr 23, 2012 at 11:39 AM, Peter Stuge wrote: >> Mitch Davis wrote: >>> I'd love to investigate what's happening but I have no idea where >>> to start. Is this page what I'm after: >>> >>> http://linuxwireless.org/en/users/Drivers/ath9k/debug >>> >>> That page tells me about all the cool things for debugging, but >>> doesn't give me an idea of how to methodically go about finding the >>> right info. Any suggestions for values of debug? Any suggestions >>> for the right place to look in /sys/kernel/debug/ath9k? >> >> I was in your situation some years ago. Unfortunately what you hope >> for is nowhere to be found. :\ > > Sigh. I'm confronted with a wall of possibilities, and no idea of > where to start. If you have a kernel that works, and one that doesn't, you can try to bisect and figure out what commit caused it to go bad. I must have deleted your first email..but can you be more specific about what kernel(s) work for you and which ones fail? Try looking at the xmit, interrupt, and recv ath9k debugfs files. With the very latest wireless-testing tree, there are some extended interrupt errors in the interrupt debugfs file that might shed some light. Let us know what AP you are using, if you know. Feel free to post a set of these to the list (ie, with some specific amount of time between them so we can see the rate of change). Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com