linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chunkeey@web.de
To: Larry Finger <Larry.Finger@lwfinger.net>,
	Bob Copeland <bcopeland@gmail.com>
Cc: Chr <chunkeey@web.de>, Johannes Berg <johannes@sipsolutions.net>,
	wireless <linux-wireless@vger.kernel.org>,
	John Linville <linville@tuxdriver.com>
Subject: Re: Kernel Panic in __ieee80211_tx with p43usb as AP
Date: Mon, 24 Aug 2009 22:33:16 +0200	[thread overview]
Message-ID: <1779655662@web.de> (raw)

> On Mon, Aug 24, 2009 at 4:07 PM, Larry Finger<Larry.Finger@lwfinger.net> wrote:
> > 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?
> 
> Could be a callback into mac80211, e.g. ieee80211_get_tx_rate()
> returning null (I haven't looked at any p54 code, I just know I've hit
> one there before with ath5k).

huu. at this point the frame already has a valid rate.
I guessing the dump is missing some more lines and 
it crashes somewhere deep down in the driver.
But, I'm not yet sure where exactly... do you think
you can capture a full oops?

Regards,
   Chr
________________________________________________________________
Neu: WEB.DE Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate
für nur 19,99 Euro/mtl.!* http://produkte.web.de/go/02/


             reply	other threads:[~2009-08-24 20:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24 20:33 Chunkeey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-24 20:07 Kernel Panic in __ieee80211_tx with p43usb as AP Larry Finger
2009-08-24 20:16 ` Johannes Berg
2009-08-24 20:19 ` Bob Copeland

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=1779655662@web.de \
    --to=chunkeey@web.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bcopeland@gmail.com \
    --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).