Return-path: Received: from mail-iw0-f174.google.com ([209.85.214.174]:47309 "EHLO mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753237Ab0JNWfz (ORCPT ); Thu, 14 Oct 2010 18:35:55 -0400 Received: by iwn35 with SMTP id 35so116785iwn.19 for ; Thu, 14 Oct 2010 15:35:54 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <4CAE1DFB.303@candelatech.com> <1286479642.20974.32.camel@jlt3.sipsolutions.net> <4CB378CD.1080800@candelatech.com> <4CB3D598.7050904@candelatech.com> <4CB4AA89.1070009@candelatech.com> <20101013053141.GA15798@vasanth-laptop> <4CB5E0A8.5020502@candelatech.com> <4CB77EA0.1000005@candelatech.com> From: "Luis R. Rodriguez" Date: Thu, 14 Oct 2010 15:35:34 -0700 Message-ID: Subject: Re: memory clobber in rx path, maybe related to ath9k. To: Ben Greear Cc: linux-wireless , "Luis R. Rodriguez" Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Thu, Oct 14, 2010 at 3:29 PM, Luis R. Rodriguez wrote: > Fun enough if I just create one monitor interface and loop quickly > over some 2 GHz channels where I know I have traffic nearby I don't > see the poison. So channel changes don't seem to do much because this > is changing channels as fast as possible from userspace. I also can > confirm that I see frames from the different channels as I move along. Even forcing a band change doesn't help trigger it with just one mon0 and one regular device scanning in a loop; while true; do for i in 2412 5745 2417 5745 2422 5745 2427 5745 2432 5745 2442; do echo $i iw dev mon0 set freq $i; done; done while true; do iw dev wlan0 scan; done Luis