linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: Problem with rtl8187
Date: Mon, 05 Jan 2009 22:01:42 +0100	[thread overview]
Message-ID: <1231189302.3697.25.camel@johannes> (raw)
In-Reply-To: <496273D4.6020600@lwfinger.net>

[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]

Larry,

> I'm chasing a problem with suspend/resume on rtl8187; however, in my testing, I
> found that a simple "modprobe -r/modprobe" sequence fails, even though
> unplugging/replugging the stick with or without a "modprobe -r" works just fine.

Strange, since modprobe -r/rmmod should unregister the driver just as
though it was unplugged, afaik.

> I'm running into the WARN-ON at net/mac80211/tx.c:1184. The start of the
> traceback is as follows:
> 
>  [<ffffffff8023afce>] warn_on_slowpath+0x58/0x7d
>  [<ffffffff803c8c3c>] ? pskb_expand_head+0xe6/0x156
>  [<ffffffffa029dbff>] ? __ieee80211_tx+0x40/0x12a [mac80211]
>  [<ffffffffa029e98b>] ieee80211_master_start_xmit+0x41c/0x50d [mac80211]
>  [<ffffffffa029e8c5>] ? ieee80211_master_start_xmit+0x356/0x50d [mac80211]
>  [<ffffffff803cf0a4>] dev_hard_start_xmit+0x214/0x28f
>  [<ffffffff803dfb9b>] __qdisc_run+0xf3/0x1fe
>  [<ffffffff803cf584>] dev_queue_xmit+0x357/0x48f
> 
> The last rtl8187 routine that was started was rtl8187_add_interface. From a
> debugging message, I see that info->flags = 0x6B6B6B6B - the SLUB debugging
> poison value. 

The WARN_ON then triggers because IEEE80211_TX_CTL_AMPDU is 0x40 which
is set in 0x6b. The question is ... why are we trying to send a freed
skb??

>  If I interpret the traceback correctly, a workqueue has been
> restarted without being properly initialized.

Does the backtrace continue beyond what you pasted?

> Is there any routine that needs to be called when shutting down that has been
> missed?

Just unregister_hw/free_hw ought to be fine, very strange.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-01-05 21:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 20:55 Problem with rtl8187 Larry Finger
2009-01-05 21:01 ` Johannes Berg [this message]
2009-01-05 21:10   ` Larry Finger
2009-01-05 21:23     ` Johannes Berg
2009-01-05 22:04       ` Larry Finger
2009-01-05 22:09         ` Johannes Berg
2009-01-05 22:15           ` Larry Finger
2009-01-05 21:20 ` Bob Copeland
  -- strict thread matches above, loose matches on Subject: below --
2008-12-01 14:03 Martín Ernesto Barreyro
2008-12-01 23:20 ` Larry Finger

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=1231189302.3697.25.camel@johannes \
    --to=johannes@sipsolutions.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    /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).