Jan Kiszka wrote: > 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() >>> ieee80211_master_start_xmit+0x105/0x430 [80211] __ip_ct_refresh_acct+0x4d/0x60 >>> tcp_packet+0x941/0x970 qdisc_restart+0x92/0x100 >>> dev_queue_xmit+0xbd/0x1a0 ieee80211_subif_start_xmit+0x468/0x480 [80211] >>> skb_clone+0x3a/0x1a0 nf_hook_slow+0x4d/0xc0 >>> dev_queue_xmit+0x115/0x1a0 ip_output+0x1c3/0x200 >>> ip_finish_output+0x0/0x180 ip_queue_xmit+0x36b/0x3b0 >>> dst_output+0x0/0x10 usb_hcd_giveback_urb+0x2d/0x60 [usbcore] >>> tcp_v4_send_check+0x82/0xd0 tcp_v4_send_check+0x82/0xd0 >>> tcp_transmit_skb+0x5e4/0x610 __tcp_push_pending_frames+0x676/0x740 >>> __alloc_skb+0x51/0x100 tcp_sendmsg+0x897/0x980 >>> core_sys_select+0x1b9/0x2b0 inet_sendmsg+0x3d/0x50 >>> do_sock_write+0x8f/0xa0 sock_aio_write+0x5f/0x70 >>> do_sync_write+0xc3/0x100 autoremove_wake_function+0x0/0x40 >>> vfs_write+0xa1/0x140 sys_write+0x43/0x70 >>> 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? >> Sorry, this was most probably false alarm for the official stack. The problem now appears to be related to a patch against d80211 that is only present in the rt2x00 CVS. Jan