From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k and pktgen generate WARNings.
Date: Thu, 10 Feb 2011 09:31:38 +0100 [thread overview]
Message-ID: <201102100931.38777.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <4D531CA6.8010903@candelatech.com>
Hi Ben,
Am Donnerstag, 10. Februar 2011 schrieb Ben Greear:
> I see this warning when I generate traffic with a hacked version
> of pktgen. This works with various other interfaces w/out problems,
> so I think it's probably an ath9k and/or mac80211 bug.
>
>
> WARNING: at /home/greearb/git/linux.wireless-testing-ct/drivers/net/wireless/ath/ath9k/xmit.c:1735 ath_tx_start+0x43c/0x607 [ath9k]()
> Hardware name: To Be Filled By O.E.M.
> Modules linked in: bridge nfs lockd bluetooth cryptd aes_i586 aes_generic veth 8021q garp stp llc fuse macvlan pktgen coretemp hwmon fscache nfs_acl auth_rpcgss
> sunrpc ipv6 uinput arc4 ecb snd_hda_codec_realtek ath9k snd_hda_intel snd_hda_codec mac80211 snd_hwdep snd_seq snd_seq_device ath9k_common ath9k_hw snd_pcm ath
> cfg80211 microcode snd_timer iTCO_wdt snd iTCO_vendor_support i2c_i801 serio_raw pcspkr soundcore r8169 snd_page_alloc mii i915 drm_kms_helper drm i2c_algo_bit
> video [last unloaded: lockd]
> Pid: 1729, comm: kpktgend_0 Tainted: G W 2.6.38-rc4-wl+ #21
> Call Trace:
> [<c043091b>] ? warn_slowpath_common+0x65/0x7a
> [<f8ded7e8>] ? ath_tx_start+0x43c/0x607 [ath9k]
> [<c043093f>] ? warn_slowpath_null+0xf/0x13
> [<f8ded7e8>] ? ath_tx_start+0x43c/0x607 [ath9k]
> [<f8de74d0>] ? ath9k_tx+0x14f/0x183 [ath9k]
> [<f8d1326d>] ? __ieee80211_tx+0x10c/0x18c [mac80211]
> [<f8d13397>] ? ieee80211_tx+0xaa/0x188 [mac80211]
> [<f8d135f3>] ? ieee80211_xmit+0x17e/0x186 [mac80211]
> [<f8d11cc0>] ? ieee80211_skb_resize+0x8e/0xd2 [mac80211]
> [<f8d1448b>] ? ieee80211_subif_start_xmit+0x643/0x65c [mac80211]
> [<c0440000>] ? rescuer_thread+0x25/0x1c8
> [<f92cd354>] ? pktgen_thread_worker+0x114c/0x1b44 [pktgen]
> [<f8d13e48>] ? ieee80211_subif_start_xmit+0x0/0x65c [mac80211]
> [<c042d612>] ? default_wake_function+0xb/0xd
> [<c04254c7>] ? __wake_up_common+0x34/0x5c
> [<c0443a29>] ? autoremove_wake_function+0x0/0x2f
> [<f92cc208>] ? pktgen_thread_worker+0x0/0x1b44 [pktgen]
> [<c044371a>] ? kthread+0x62/0x67
> [<c04436b8>] ? kthread+0x0/0x67
> [<c04035f6>] ? kernel_thread_helper+0x6/0x10
>
>
> /* FIXME: tx power */
> static void ath_tx_start_dma(struct ath_softc *sc, struct ath_buf *bf,
> struct ath_tx_control *txctl)
> {
> struct sk_buff *skb = bf->bf_mpdu;
> struct ieee80211_tx_info *tx_info = IEEE80211_SKB_CB(skb);
> struct ieee80211_hdr *hdr = (struct ieee80211_hdr *)skb->data;
> struct list_head bf_head;
> struct ath_atx_tid *tid = NULL;
> u8 tidno;
>
> spin_lock_bh(&txctl->txq->axq_lock);
>
> if (ieee80211_is_data_qos(hdr->frame_control) && txctl->an) {
> tidno = ieee80211_get_qos_ctl(hdr)[0] &
> IEEE80211_QOS_CTL_TID_MASK;
> tid = ATH_AN_2_TID(txctl->an, tidno);
>
> WARN_ON(tid->ac->txq != txctl->txq);
> }
>
> Anyone have any ideas on this one?
pktgen seems to directly inject frames via the xmit callback and hence
mac80211's select_queue callback isn't used for proper queue assignment.
However, you should be able to specify the queue manuelly with
"cur_queue_map".
Helmut
next prev parent reply other threads:[~2011-02-10 8:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 23:00 ath9k and pktgen generate WARNings Ben Greear
2011-02-09 23:36 ` Ben Greear
2011-02-10 8:31 ` Helmut Schaa [this message]
2011-02-10 17:19 ` Ben Greear
2011-02-10 17:54 ` Helmut Schaa
2011-02-10 18:00 ` Ben Greear
2011-02-10 19:23 ` Felix Fietkau
2011-02-10 19:43 ` Ben Greear
2011-02-10 20:01 ` Felix Fietkau
2011-02-10 22:11 ` Helmut Schaa
2011-02-10 19:00 ` David Miller
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=201102100931.38777.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=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).