From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>, Chr <chunkeey@web.de>
Cc: wireless <linux-wireless@vger.kernel.org>,
John Linville <linville@tuxdriver.com>
Subject: Kernel Panic in __ieee80211_tx with p43usb as AP
Date: Mon, 24 Aug 2009 15:07:17 -0500 [thread overview]
Message-ID: <4A92F2F5.6000909@lwfinger.net> (raw)
In trying to track down a WARNING reported while using p54usb as the
basis for an AP (http://bugzilla.kernel.org/show_bug.cgi?id=13725), I
created an AP using hostapd 0.6.8. It worked fine as long as I used a
Linux client. I ran repeated tcpperf runs through it to my server, and
repeated installations of b43 firmware. That routine uses wget to pull
the driver files. The only machine I had available as a client does
not include X, so I could not run a browser.
All went well until I had a Windows Vista client connect to the
network. As soon as I launched a browser, the kernel on the AP crashed.
The kernel in question is 2.6.31-rc7-Linus-00012-g3edf2fb from the
mainline tree. I do not know the reported reason for the panic, as
that scrolls off the screen. The traceback shows the error to be in
__ieee80211_tx in this statement: ret = drv_tx(local, skb), which
makes the problem be here:
static inline int drv_tx(struct ieee80211_local *local, struct sk_buff
*skb)
{
return local->ops->tx(&local->hw, skb);
}
Are there any suggest changes that would let me debug this problem
without crashing the kernel?
Thanks,
Larry
next reply other threads:[~2009-08-24 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 20:07 Larry Finger [this message]
2009-08-24 20:16 ` Kernel Panic in __ieee80211_tx with p43usb as AP Johannes Berg
2009-08-24 20:19 ` Bob Copeland
-- strict thread matches above, loose matches on Subject: below --
2009-08-24 20:33 Chunkeey
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=4A92F2F5.6000909@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chunkeey@web.de \
--cc=johannes@sipsolutions.net \
--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).