From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
Date: Mon, 2 Feb 2009 21:04:20 -0800 [thread overview]
Message-ID: <20090203050420.GA16853@tesla> (raw)
In-Reply-To: <4987C187.9090904@cheek.com>
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
next prev parent reply other threads:[~2009-02-03 5:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 6:14 [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc Joseph Cheek
2009-01-21 18:49 ` Luis R. Rodriguez
2009-01-21 19:54 ` Joseph Cheek
2009-01-21 22:18 ` Joseph Cheek
2009-01-22 19:19 ` Joseph Cheek
2009-01-22 19:44 ` Luis R. Rodriguez
2009-01-25 0:32 ` Joseph Cheek
2009-01-25 2:23 ` Luis R. Rodriguez
2009-01-25 2:27 ` Stephen Gutknecht
2009-02-02 22:21 ` Joseph Cheek
2009-02-02 23:50 ` Luis R. Rodriguez
2009-02-03 4:01 ` Joseph Cheek
2009-02-03 5:04 ` Luis R. Rodriguez [this message]
2009-02-03 11:11 ` [ath9k-devel] Problem with 80211n Speed and packet drop Amit Sood
2009-02-04 20:58 ` Pavel Roskin
2009-02-04 23:21 ` Amit Sood
2009-02-05 4:37 ` Pavel Roskin
2009-02-08 3:14 ` [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc Joseph Cheek
-- strict thread matches above, loose matches on Subject: below --
2009-04-06 7:36 Masashi Honma
2009-04-06 7:43 Masashi Honma
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090203050420.GA16853@tesla \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.