From: Masashi Honma <honma@ictec.co.jp>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc
Date: Mon, 06 Apr 2009 16:36:29 +0900 [thread overview]
Message-ID: <49D9B0FD.4040302@ictec.co.jp> (raw)
> On Sun Feb 8 04:14:02 CET 2009, Joseph Cheek wrote:
> # egrep '(No.Probe|PCI.FATAL)' /var/log/messages
> Feb 7 15:12:50 harrisburg ath9k: received PCI FATAL interrupt
Hello.
I encountered identical error on Debian sid.
[ 467.614789] ath9k: received PCI FATAL interrupt
[ 714.384969] ath9k: received PCI FATAL interrupt
[ 729.166142] ath9k: received PCI FATAL interrupt
[ 774.222352] ath9k: received PCI FATAL interrupt
[ 819.272511] ath9k: received PCI FATAL interrupt
I can't ping with wpa_supplicant + ath9k driver.
WPA2-PSK connection is ok (GTK exchange succeeded).
But wpa_supplicant doesn't sends ping request.
I'm capturing wpa_supplicant wireless frame, but it doesn't
send any frame.
After that, I changed the card to ath5k device.
Then I can ping with same settings.
But I need to use ath9k, because I wnat 802.11w support.
My environment is these.
[uname -a]
Linux debian 2.6.29 #1 SMP Mon Apr 6 10:56:46 JST 2009 i686 GNU/Linux
[wireless card]
WL300NC (AR5416+AR5133)
[compat-wireless]
compat-wireless-2009-04-05
[CRDA]
crda-1.0.1
[CRDA-rule]
/etc/udev/rules.d/91-regulatory.rules
KERNEL=="regulatory*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/sbin/crda"
[CRDA log]
debian:~# dmesg | grep CRDA
[ 6.669048] cfg80211: Calling CRDA for country: US
[ 7.377956] cfg80211: Calling CRDA for country: JP
debian:~#
[wireless-regdb]
wireless-regdb-2009.03.09
[wpa_supplicant]
newest on git snapshot
http://hostap.epitest.fi/gitweb/gitweb.cgi?p=hostap.git;a=snapshot;h=a0b2f99bd7f608236e8a2e650655a79280248740;sf=tgz
[.config]
CONFIG_DRIVER_NL80211=y
CONFIG_DRIVER_WIRED=y
CONFIG_IEEE8021X_EAPOL=y
CONFIG_EAP_MD5=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_EAP_TLS=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_TTLS=y
CONFIG_EAP_GTC=y
CONFIG_EAP_OTP=y
CONFIG_EAP_LEAP=y
CONFIG_EAP_TNC=y
CONFIG_WPS=y
CONFIG_PKCS12=y
CONFIG_SMARTCARD=y
CONFIG_CTRL_IFACE=y
CONFIG_BACKEND=file
CONFIG_PEERKEY=y
CONFIG_IEEE80211W=y
CONFIG_TLS=internal
CONFIG_INTERNAL_LIBTOMMATH=y
CONFIG_IEEE80211R=y
[wpa_supplicant.conf]
ctrl_interface=/var/run/wpa_supplicant
country=JP
network={
ssid="wpa-eap"
key_mgmt=WPA-PSK
proto=WPA2
pairwise=CCMP
group=CCMP
psk="12345678"
}
Is there any idea ?
Regards,
Masashi Honma.
next reply other threads:[~2009-04-06 7:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 7:36 Masashi Honma [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-06 7:43 [ath9k-devel] modprobe ath9k == BUG: unable to handle kernel NULL pointer dereference at 000001dc Masashi Honma
2009-01-21 6:14 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
2009-02-08 3:14 ` Joseph Cheek
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=49D9B0FD.4040302@ictec.co.jp \
--to=honma@ictec.co.jp \
--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.