From: Michael Buesch <mb@bu3sch.de>
To: Bob Copeland <me@bobcopeland.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"Alexander E. Patrakov" <patrakov@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: Kernel panic with zd1211rw and today's compat-wireless
Date: Sun, 22 Mar 2009 23:12:07 +0100 [thread overview]
Message-ID: <200903222312.07360.mb@bu3sch.de> (raw)
In-Reply-To: <20090322220421.GG18141@hash.localnet>
On Sunday 22 March 2009 23:04:21 Bob Copeland wrote:
> On Sun, Mar 22, 2009 at 04:09:26PM +0100, Michael Buesch wrote:
> > Is it possible that the skb->cb (where I guess the RX status and TX status
> > are stored) is getting corrupted after the skb got queued by the driver for
> > processing in the RX or TX status tasklet?
>
> Hmm, that's an interesting possibility, and yeah that is stored in cb, for
> TX at least:
Ok, at least for the RX path the corruption was in the b43 driver.
See "[PATCH] b43: fix b43_plcp_get_bitrate_idx_ofdm return type".
So there's probably no cb corruption going on...
> > struct ieee80211_tx_info *info = IEEE80211_SKB_CB(skb);
>
> I did debug it on the driver side and the rates I was sending back to the
> RC were fine.
>
--
Greetings, Michael.
next prev parent reply other threads:[~2009-03-22 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 12:45 Kernel panic with zd1211rw and today's compat-wireless Alexander E. Patrakov
2009-03-22 12:56 ` Johannes Berg
2009-03-22 13:15 ` Michael Buesch
2009-03-22 14:49 ` Bob Copeland
2009-03-22 15:09 ` Michael Buesch
2009-03-22 22:04 ` Bob Copeland
2009-03-22 22:12 ` Michael Buesch [this message]
2009-03-23 15:08 ` Kalle Valo
2009-03-23 19:36 ` Johannes Berg
2009-03-23 19:52 ` Bob Copeland
2009-03-23 19:56 ` Johannes Berg
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=200903222312.07360.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=patrakov@gmail.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.