From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joseph Cheek <joseph@cheek.com>
Date: Mon, 02 Feb 2009 23:01:11 -0500
Subject: [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel
 NULL pointer dereference at 000001dc
In-Reply-To: <43e72e890902021550q60103e5an2a56d3cc4cd8f4dd@mail.gmail.com>
References: <4976BD2E.3070807@cheek.com>	
	<43e72e890901211049k1d222dcfqe9a530b26ccd4ca8@mail.gmail.com>	
	<49777D8B.10802@cheek.com> <49779F1D.2090800@cheek.com>	
	<4978C6A4.4050709@cheek.com> <20090122194435.GA14561@tesla>	
	<497BB336.1040505@cheek.com> <49877200.2070009@cheek.com>
	<43e72e890902021550q60103e5an2a56d3cc4cd8f4dd@mail.gmail.com>
Message-ID: <4987C187.9090904@cheek.com>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

looks like i was a little hasty.  checking syslog I see:

Feb  2 22:49:31 harrisburg ath9k: received PCI FATAL interrupt
Feb  2 22:49:36 harrisburg wlan0: No ProbeResp from current AP
00:21:91:df:00:29
 - assume out of range

can I assume that the lack of a ProbeResp is because of the fatal
interrupt 5 seconds earlier?

Joseph Cheek

Luis R. Rodriguez wrote:
> On Mon, Feb 2, 2009 at 2:21 PM, Joseph Cheek <joseph@cheek.com> wrote:
>   
>> I've been trying git tip for a week and no more kernel OOPS!  great job,
>> thanks!
>>     
>
> Good to hear :)
>
>   
>> I also did NOT have to change IEEE_MONITORING_INTERVAL to stay
>> connected.  *But* I still lose connectivity for several seconds during a
>> large file transfer (most often transferring 50M or more via scp or
>> rsync -e ssh).
>>     
>
> Check the logs for reason given for the disassociation, see another
> thread recently where I posted the reason number to reason
> description.
>
>   Luis
>
>