From mboxrd@z Thu Jan  1 00:00:00 1970
From: Luis R. Rodriguez <lrodriguez@atheros.com>
Date: Mon, 2 Feb 2009 21:04:20 -0800
Subject: [ath9k-devel] modprobe ath9k == BUG: unable to handle
	kernel	NULL pointer dereference at 000001dc
In-Reply-To: <4987C187.9090904@cheek.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>
	<4987C187.9090904@cheek.com>
Message-ID: <20090203050420.GA16853@tesla>
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

On Mon, Feb 02, 2009 at 08:01:11PM -0800, Joseph Cheek wrote:
> 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?

Yeah that's what I would think, can you reproduce? If so
please enable debugging and see if you can find something
a bit more indicative of what happened.

modprobe ath9k debug=0xfffffffff

  Luis