Modify

Opened 7 years ago

Closed 7 years ago

Last modified 2 years ago

#8908 closed defect (wontfix)

Madwifi trying to use the queue on the wrong device ath0

Reported by: alberto@… Owned by: developers
Priority: normal Milestone: Backfire 10.03.1
Component: packages Version: Backfire 10.03.1 RC4
Keywords: madwifi Cc:

Description

I am using Openwrt 10.03 r25655 compiled with Madwifi driver on an Atheros AR2315 based AP in master mode.

When traffic raises I often get this type of messages:

2011-02-09T05:36:25+01:00 192.168.20.2 iq-ap: Virtual device ath0 asks to queue packet!
2011-02-09T05:36:25+01:00 192.168.20.2 iq-ap: Virtual device ath0 asks to queue packet!
2011-02-09T05:36:25+01:00 192.168.20.2 iq-ap: Virtual device ath0 asks to queue packet!
2011-02-09T05:36:25+01:00 192.168.20.2 iq-ap: Virtual device ath0 asks to queue packet!
2011-02-09T05:36:25+01:00 192.168.20.2 iq-ap: Virtual device ath0 asks to queue packet!
2011-02-09T05:36:25+01:00 192.168.20.2 iq-ap: Virtual device ath0 asks to queue packet!
2011-02-09T05:36:25+01:00 192.168.20.2 iq-ap: Virtual device ath0 asks to queue packet!
2011-02-09T05:36:25+01:00 192.168.20.2 iq-ap: Virtual device ath0 asks to queue packet!
2011-02-09T05:36:25+01:00 192.168.20.2 iq-ap: Virtual device ath0 asks to queue packet!
2011-02-09T06:13:42+01:00 192.168.20.2 iq-ap: __ratelimit: 25 callbacks suppressed
2011-02-09T06:13:42+01:00 192.168.20.2 iq-ap: Virtual device ath0 asks to queue packet!

When this messages are logged bandwidth halves and then, when they stop, it comes back to the max value.

Digging the source code I found that "Virtual device %s asks to queue packet!" message is logged by the kernel (function dev_queue_xmit() in net/core/dev.c) because the passed device has got zero length queue.
That's right because ath0, as a virtual ap (software device), must have its txqueuelen set to 0.
The point is: HOW madwifi can send a packet to the virtual interface ath0 instead of the real interface wifi0?
Infact, looking at the madwifi code, dev_queue_xmit() is always called by function ieee80211_parent_queue_xmit() that uses the following line to dispatch the packet to wifi0:

/* Dispatch the packet to the parent device */
        skb->dev = vap->iv_ic->ic_dev;
{{{

Can anyone who knows better madwifi code give an explanation useful to fix the code?
}}}

Attachments (0)

Change History (3)

comment:1 Changed 7 years ago by alberto@…

Sorry for the missing summary.

Admins, can you please change it to:

"Madwifi trying to use the queue on the wrong device ath0"

comment:2 Changed 7 years ago by jow

  • Summary changed from Vi to Madwifi trying to use the queue on the wrong device ath0

comment:3 Changed 7 years ago by nbd

  • Resolution set to wontfix
  • Status changed from new to closed

madwifi development has stopped, consider switching to ath5k

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.