linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Kernel splats in 3.3.6+, drv_finish_tx_sync
Date: Wed, 23 May 2012 09:28:26 -0700	[thread overview]
Message-ID: <4FBD102A.3060906@candelatech.com> (raw)

NOTE:  These are against 3.3.6+, not 3.3.7+ as I posted earlier.

We ran a torture test where we try to associate 130 stations against an AP
that can only do 128.  The end result is constant resetting of many of the
virtual station interfaces.

It ran overnight w/out crashing, but spewed quite a few warnings.

I will be happy to test patches or attempt fixes if anyone has suggestions
for what the cause might be....

------------[ cut here ]------------
WARNING: at /home/greearb/git/linux-3.3.dev.y/net/mac80211/driver-ops.h:12 drv_finish_tx_sync+0x45/0x6e [mac80211]()
Hardware name: To be filled by O.E.M.
sta20:  Failed check-sdata-in-driver check, flags: 0x4
Modules linked in: aesni_intel cryptd aes_x86_64 aes_generic 8021q garp stp llc fuse macvlan wanlink(PO) pktgen coretemp hwmon sunrpc ipv6 uinput arc4 ath9k 
snd_hda_codec_realtek mac80211 snd_hda_intel snd_hda_codec snd_hwdep snd_seq ath9k_common ath9k_hw snd_seq_device snd_pcm ath snd_timer e1000e cfg80211 snd 
microcode ppdev iTCO_wdt soundcore pcspkr mei(C) serio_raw i2c_i801 snd_page_alloc iTCO_vendor_support parport_pc parport i915 drm_kms_helper drm i2c_algo_bit 
i2c_core video [last unloaded: nf_nat]
Pid: 31420, comm: kworker/u:0 Tainted: P        WC O 3.3.6+ #43
Call Trace:
  [<ffffffff81036ef9>] warn_slowpath_common+0x80/0x98
  [<ffffffff81036fa5>] warn_slowpath_fmt+0x41/0x43
  [<ffffffffa023d8ad>] drv_finish_tx_sync+0x45/0x6e [mac80211]
  [<ffffffffa023f9d9>] ieee80211_assoc_done+0x1b0/0x1c4 [mac80211]
  [<ffffffff8105d28f>] ? enqueue_task_fair+0x136/0x294
  [<ffffffff81055cd8>] ? resched_task+0x47/0x67
  [<ffffffff810e03e3>] ? __slab_free+0xe1/0x22d
  [<ffffffff8144a718>] ? _raw_spin_unlock_irqrestore+0x3a/0x47
  [<ffffffffa0242410>] ieee80211_work_work+0xf6f/0xfd9 [mac80211]
  [<ffffffff81449a93>] ? __schedule+0x499/0x4c8
  [<ffffffff81057b87>] ? get_parent_ip+0x11/0x41
  [<ffffffffa02414a1>] ? free_work+0x14/0x14 [mac80211]
  [<ffffffff810496b5>] process_one_work+0x1a6/0x278
  [<ffffffff8104b708>] worker_thread+0x136/0x255
  [<ffffffff8104b5d2>] ? manage_workers+0x190/0x190
  [<ffffffff8104ed09>] kthread+0x84/0x8c
  [<ffffffff81450924>] kernel_thread_helper+0x4/0x10
  [<ffffffff8104ec85>] ? __init_kthread_worker+0x37/0x37
  [<ffffffff81450920>] ? gs_change+0x13/0x13
---[ end trace d1b4803845952d45 ]---



static inline void check_sdata_in_driver(struct ieee80211_sub_if_data *sdata)
{
	WARN(!(sdata->flags & IEEE80211_SDATA_IN_DRIVER),
	     "%s:  Failed check-sdata-in-driver check, flags: 0x%x\n",
	     sdata->dev->name, sdata->flags);
}


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


             reply	other threads:[~2012-05-23 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 16:28 Ben Greear [this message]
2012-05-29  6:49 ` Kernel splats in 3.3.6+, drv_finish_tx_sync 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=4FBD102A.3060906@candelatech.com \
    --to=greearb@candelatech.com \
    --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).