Return-path: <linux-wireless-owner@vger.kernel.org>
Received: from mail-iw0-f174.google.com ([209.85.214.174]:62335 "EHLO
	mail-iw0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751129Ab0JERQu (ORCPT
	<rfc822;linux-wireless@vger.kernel.org>);
	Tue, 5 Oct 2010 13:16:50 -0400
Received: by iwn5 with SMTP id 5so8558610iwn.19
        for <linux-wireless@vger.kernel.org>; Tue, 05 Oct 2010 10:16:49 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <4CAB59B2.5050106@candelatech.com>
References: <4CAB59B2.5050106@candelatech.com>
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
Date: Tue, 5 Oct 2010 10:16:29 -0700
Message-ID: <AANLkTikhGCTS8kJgpDzjudyBTk-rkyXY33UO7kB0+Cc-@mail.gmail.com>
Subject: Re: memory clobber in rx path, maybe related to ath9k.
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-wireless-owner@vger.kernel.org
List-ID: <linux-wireless.vger.kernel.org>

On Tue, Oct 5, 2010 at 10:00 AM, Ben Greear <greearb@candelatech.com> wrote:
> I started seeing this very soon after creating interfaces.

Can you be more specific how one can reproduce?

  Luis