From: "Ray Lee" <ray-lk@madrabbit.org>
To: "kernel list" <linux-kernel@vger.kernel.org>,
bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Cc: "John Linville" <linville@tuxdriver.com>
Subject: Oops in mac80211:rate_control_pid_tx_status
Date: Sat, 1 Mar 2008 17:05:50 -0800 [thread overview]
Message-ID: <2c0942db0803011705j260186bbgb02dcd8f9842e52b@mail.gmail.com> (raw)
Kernel version 2.6.24+ a little (but pre-rc1).
I have a wireless base station that I switched from B/G mixed mode to
purely B to try to debug a separate issue with a different device on
my network. As soon as I did that (and on every subsequent boot), the
system oopses as soon as it tries to associate. Switching the base
station back to "mixed" avoids the oops.
This is with the b43 driver.
Nothing gets to the logs, but there's a photo at:
http://madrabbit.org/~ray/mac80211-oops.jpg
Ray
next reply other threads:[~2008-03-02 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 1:05 Ray Lee [this message]
2008-03-02 11:04 ` Oops in mac80211:rate_control_pid_tx_status Stefano Brivio
2008-03-02 17:17 ` Ray Lee
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=2c0942db0803011705j260186bbgb02dcd8f9842e52b@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-kernel@vger.kernel.org \
--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