From: Russell Senior <seniorr@aracnet.com>
To: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org
Subject: kernel panic on MIPS + ath5k + Wistron CM9 radio
Date: Sun, 01 May 2011 12:39:16 -0700 [thread overview]
Message-ID: <861v0igqhn.fsf@coulee.tdb.com> (raw)
Recently trying to abandon madwifi for good on some embedded devices
with OpenWrt, encountered kernel panics. Same radio on an x86
platform (Soekris net4826), no kernel panic. Different atheros radio,
no kernel panic. Tried two different MIPS boards (Netgear WGT634U and
Ubiquiti RouterStation), both panic'd.
Netgear WGT634U: http://pastebin.ca/2051127
Ubiquiti RouterStation: http://pastebin.ca/2052610
Both cases were firmwares built from r26771 of OpenWrt, and both seem
to have panic'd from hostapd. While researching this, I encountered a
similar report from last June:
http://www.mail-archive.com/openwrt-users@lists.openwrt.org/msg01001.html
http://www.spinics.net/lists/linux-wireless/msg52502.html
Another person reported some issues with the CM9 earlier this year in
client mode:
http://permalink.gmane.org/gmane.linux.drivers.ath5k.devel/4722
I am happy to do some leg work on getting this fixed, if someone can
provide some guidance. Thanks!
--
Russell Senior ``I have nine fingers; you have ten.''
seniorr@aracnet.com
next reply other threads:[~2011-05-01 19:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 19:39 Russell Senior [this message]
2011-05-03 6:18 ` kernel panic on MIPS + ath5k + Wistron CM9 radio Adrian Chadd
2011-05-03 6:56 ` [ath5k-devel] " Peizhao Hu
2011-05-03 19:19 ` Felix Fietkau
2011-05-04 19:55 ` Russell Senior
2011-05-06 1:57 ` Peizhao Hu
2011-05-04 14:39 ` Russell Senior
2011-05-04 14:47 ` Felix Fietkau
[not found] ` <86liyjjo0a.fsf@coulee.tdb.com>
2011-05-31 17:30 ` Russell Senior
2011-05-31 18:16 ` Sedat Dilek
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=861v0igqhn.fsf@coulee.tdb.com \
--to=seniorr@aracnet.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).