From: Pavel Roskin <proski@gnu.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Krzysztof Halasa <khc@pm.waw.pl>, linux-wireless@vger.kernel.org
Subject: Re: ath5k WARNING: at ieee80211_rate.h:149
Date: Tue, 26 Feb 2008 18:02:51 -0500 [thread overview]
Message-ID: <1204066971.19041.16.camel@dv> (raw)
In-Reply-To: <20080226193326.GC3013@tuxdriver.com>
On Tue, 2008-02-26 at 14:33 -0500, John W. Linville wrote:
> On Tue, Feb 26, 2008 at 06:29:11PM +0100, Krzysztof Halasa wrote:
> > Is this normal as well?
> >
> > phy0: Selected rate control algorithm 'pid'
> > ath5k phy0: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61)
> > phy0: Adding new IBSS station XXX (dev=wlan0)
> > ------------[ cut here ]------------
> > WARNING: at net/mac80211/ieee80211_rate.h:149 rate_control_pid_rate_init+0x6c/0x7c()
> > Modules linked in: ixp4xx_eth ixp4xx_hss ixp4xx_qmgr ixp4xx_npe ath5k
> > [<c00c1b3c>] (dump_stack+0x0/0x14) from [<c00d463c>] (warn_on_slowpath+0x4c/0x60)
> > [<c00d45f0>] (warn_on_slowpath+0x0/0x60) from [<c032a50c>] (rate_control_pid_rate_init+0x6c/0x7c)
> > r6:c689e800 r5:c7cace18 r4:c68ab000
> > [<c032a4a0>] (rate_control_pid_rate_init+0x0/0x7c) from [<c031e56c>] (ieee80211_ibss_add_sta+0xb0/0x114)
> > r5:c7cac160 r4:c68ab000
>
> <snip>
>
> Looks like you are hitting the WARN_ON in rate_lowest_index (called
> from rate_control_pid_rate_init). Perhaps your supported band
> information is not being setup correctly? Possibly an endian problem?
> Just speculating, really...
There are indeed endian issues reported by sparse in the IBSS code.
I've just submitted a patch. Not sure if they are relevant to the
issue, but I think it's worth trying.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-02-26 23:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 17:29 ath5k WARNING: at ieee80211_rate.h:149 Krzysztof Halasa
2008-02-26 19:33 ` John W. Linville
2008-02-26 23:02 ` Pavel Roskin [this message]
2008-02-26 23:33 ` Krzysztof Halasa
2008-02-27 21:42 ` Krzysztof Halasa
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=1204066971.19041.16.camel@dv \
--to=proski@gnu.org \
--cc=khc@pm.waw.pl \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 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).