linux-kernel - Re: [ath9k-devel] ath9k: massive unexplained latency in 2.6.27 (rc5, rc6, probably others)

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]

Date:	Thu, 18 Sep 2008 16:08:57 -0700
From:	"Steven Noonan" <steven@...inklabs.net>
To:	"Luis R. Rodriguez" <lrodriguez@...eros.com>
Cc:	"Luis Rodriguez" <Luis.Rodriguez@...eros.com>,
	"Ingo Molnar" <mingo@...e.hu>,
	"ath9k-devel@...ts.ath9k.org" <ath9k-devel@...ts.ath9k.org>,
	linux-wireless <linux-wireless@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [ath9k-devel] ath9k: massive unexplained latency in 2.6.27 (rc5, rc6, probably others)

On Thu, Sep 18, 2008 at 3:01 PM, Luis R. Rodriguez
<lrodriguez@...eros.com> 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?
--
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/