From: Jan Kiszka <jan.kiszka@web.de>
To: Jiri Benc <jbenc@suse.cz>
Cc: netdev@vger.kernel.org, Ivo Van Doorn <ivdoorn@gmail.com>,
rt2400-devel@lists.sourceforge.net
Subject: Re: d80211: How does TX flow control work?
Date: Wed, 03 Jan 2007 19:50:45 +0100 [thread overview]
Message-ID: <459BFB05.9040608@web.de> (raw)
In-Reply-To: <20070103191853.4f440b8b@griffin.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]
Jiri Benc wrote:
> On Wed, 03 Jan 2007 19:10:01 +0100, Jan Kiszka wrote:
>> BUG: warning at /usr/src/rt2x00/rt2x00/ieee80211/ieee80211.c:1256/ieee80211_tx()
>> <cfa02245> ieee80211_master_start_xmit+0x105/0x430 [80211] <c024e35d> __ip_ct_refresh_acct+0x4d/0x60
>> <c024fd11> tcp_packet+0x941/0x970 <c0217442> qdisc_restart+0x92/0x100
>> <c020d43d> dev_queue_xmit+0xbd/0x1a0 <cfa050d8> ieee80211_subif_start_xmit+0x468/0x480 [80211]
>> <c0207dca> skb_clone+0x3a/0x1a0 <c021d16d> nf_hook_slow+0x4d/0xc0
>> <c020d495> dev_queue_xmit+0x115/0x1a0 <c0226a63> ip_output+0x1c3/0x200
>> <c0225740> ip_finish_output+0x0/0x180 <c022628b> ip_queue_xmit+0x36b/0x3b0
>> <c0224130> dst_output+0x0/0x10 <ce9bae7d> usb_hcd_giveback_urb+0x2d/0x60 [usbcore]
>> <c0237da2> tcp_v4_send_check+0x82/0xd0 <c0237da2> tcp_v4_send_check+0x82/0xd0
>> <c0233244> tcp_transmit_skb+0x5e4/0x610 <c0234b36> __tcp_push_pending_frames+0x676/0x740
>> <c0207f81> __alloc_skb+0x51/0x100 <c022b817> tcp_sendmsg+0x897/0x980
>> <c0153fa9> core_sys_select+0x1b9/0x2b0 <c0241f1d> inet_sendmsg+0x3d/0x50
>> <c0202a8f> do_sock_write+0x8f/0xa0 <c020301f> sock_aio_write+0x5f/0x70
>> <c01443d3> do_sync_write+0xc3/0x100 <c01247f0> autoremove_wake_function+0x0/0x40
>> <c0144ca1> vfs_write+0xa1/0x140 <c01451d3> sys_write+0x43/0x70
>> <c0102ae7> syscall_call+0x7/0xb
>>
>> Does it tell you anything already? Is there something I may instrument? What
>> could the driver do wrong to trigger such bug?
>
> Do you have CONFIG_NET_SCHED enabled?
>
Yes. Would it make a difference /wrt to that warning when I switch it off?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2007-01-03 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 13:08 d80211: How does TX flow control work? Jan Kiszka
2007-01-03 17:52 ` Jiri Benc
2007-01-03 18:10 ` Jan Kiszka
2007-01-03 18:18 ` Jiri Benc
2007-01-03 18:50 ` Jan Kiszka [this message]
2007-01-07 0:00 ` Jan Kiszka
2007-01-08 20:18 ` Jan Kiszka
2007-01-10 18:20 ` Jiri Benc
2007-01-10 18:29 ` Simon Barber
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=459BFB05.9040608@web.de \
--to=jan.kiszka@web.de \
--cc=ivdoorn@gmail.com \
--cc=jbenc@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=rt2400-devel@lists.sourceforge.net \
/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).