From: Felix Fietkau <nbd@openwrt.org>
To: Russell Senior <seniorr@aracnet.com>
Cc: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org
Subject: Re: [ath5k-devel] kernel panic on MIPS + ath5k + Wistron CM9 radio
Date: Wed, 04 May 2011 16:47:56 +0200 [thread overview]
Message-ID: <4DC1671C.9040906@openwrt.org> (raw)
In-Reply-To: <86iptq8r8w.fsf@coulee.tdb.com>
On 2011-05-04 4:39 PM, Russell Senior wrote:
>>>>>> "Russell" == Russell Senior<seniorr@aracnet.com> writes:
>
> Russell> Recently trying to abandon madwifi for good on some embedded
> Russell> devices with OpenWrt, encountered kernel panics. Same radio
> Russell> on an x86 platform (Soekris net4826), no kernel panic.
> Russell> Different atheros radio, no kernel panic. Tried two
> Russell> different MIPS boards (Netgear WGT634U and Ubiquiti
> Russell> RouterStation), both panic'd.
>
> Russell> Netgear WGT634U: http://pastebin.ca/2051127 Ubiquiti
> Russell> RouterStation: http://pastebin.ca/2052610
>
> Here is another panic, this time not resulting from hostapd, but from
> an adhoc vif:
>
> http://pastebin.ca/2053827
>
> The initial panic appears to occur in a different function from the
> hostapd initiated panics:
Again a beacon related register, this time AR5K_BEACON
- Felix
next prev parent reply other threads:[~2011-05-04 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 19:39 kernel panic on MIPS + ath5k + Wistron CM9 radio Russell Senior
2011-05-03 6:18 ` 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 [this message]
[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=4DC1671C.9040906@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=seniorr@aracnet.com \
/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.