Return-path: Received: from nf-out-0910.google.com ([64.233.182.184]:8209 "EHLO nf-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755581AbYIRXI7 (ORCPT ); Thu, 18 Sep 2008 19:08:59 -0400 Received: by nf-out-0910.google.com with SMTP id d3so70763nfc.21 for ; Thu, 18 Sep 2008 16:08:57 -0700 (PDT) Message-ID: (sfid-20080919_010908_467941_448BEEA2) Date: Thu, 18 Sep 2008 16:08:57 -0700 From: "Steven Noonan" To: "Luis R. Rodriguez" Subject: Re: [ath9k-devel] ath9k: massive unexplained latency in 2.6.27 (rc5, rc6, probably others) Cc: "Luis Rodriguez" , "Ingo Molnar" , "ath9k-devel@lists.ath9k.org" , linux-wireless , LKML In-Reply-To: <20080918220102.GE7408@tesla> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <43e72e890809181134ybbec8fdxcb2a466aa17fe390@mail.gmail.com> <43e72e890809181142n7738cd99g522e6688e68d11ce@mail.gmail.com> <43e72e890809181344q416b5944w3332ee5a33db048c@mail.gmail.com> <20080918220102.GE7408@tesla> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Sep 18, 2008 at 3:01 PM, Luis R. Rodriguez wrote: >> If I do, I'll need to know what precisely to do about it. What debug >> info should I collect before rebooting? > > Sure, OK so in ath9k's core.h we have a macro used to indicate what > type of debugging stuff gets print out. By default we only leave > enabled the fatal stuff. > > #define DBG_DEFAULT (ATH_DBG_FATAL ) > > You want to add to this ATH_DBG_INTERRUPT as follows: > > #define DBG_DEFAULT (ATH_DBG_FATAL | ATH_DBG_INTERRUPT) > > Then since the issue seems to come up when you rmmod, simply try to > download do some large RXing or TXing or both and then rmmod. Capture > the output and send along. Will do! And actually, to be precise, the issue occurred not on the rmmod, but on the following modprobe for ath9k. >> Which is far more important, I agree. It's annoying to get speeds >> <802.11b on my pre-802.11n capable chipset and network. ;) > > Yeah exactly, I hope the work we do will get in for 27. We'll see. Linus has been fairly strict lately, so I am as uncertain as you are. It really should get merged, because having 2.6.27 with [partially] broken wireless networking is kind of stupid. In the worst case, isn't it possible to do a revert to get the old aggregation crap back in?