Bugzilla – Bug 598
Rx drops data and reports errors
Last modified: 2005-04-11 23:16:44
You need to log in before you can comment on or make changes to this bug.
This is on DELL INSPIRON 6500, with a builtin ipw2200 running Mepis Linux 3.3. Upgraded ipw2200 driver to version 1.0.1. Firmware is 2.2. kernel is 2.6.10. As a result, The ipw2200 interface eth1 could not get an IP using DHCP. Modules loaded without error. >iwconfig eth1 eth1 IEEE 802.11g ESSID:"Omicron Main" Mode:Managed Frequency:2.412 GHz Access Point: 00:11:50:21:3C:5F Bit Rate=54 Mb/s Tx-Power=20 dBm RTS thr:off Fragment thr:off Power Management:off Link Quality=84/100 Signal level=-45 dBm Noise level=-83 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:640 Missed beacon:10 >ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:0E:35:FC:A7:58 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:1040 errors:14 dropped:677 overruns:0 frame:0 TX packets:17 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:4380 (4.2 KiB) Interrupt:7 Base address:0xc000 Memory:dfdfd000-dfdfdfff
I notice the difference in ifconfig before and after "iwlist scanning" Before: >ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:0E:35:FC:A7:58 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:1543 errors:23 dropped:996 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:6744 (6.5 KiB) Interrupt:7 Base address:0xc000 Memory:dfdfd000-dfdfdfff --------------------- After "iwlist scanning" >ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:0E:35:FC:A7:58 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:1593 errors:23 dropped:1029 overruns:0 frame:0 TX packets:28 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:6744 (6.5 KiB) Interrupt:7 Base address:0xc000 Memory:dfdfd000-dfdfdfff ----------------------------- output of the scan >iwlist scanning eth1 Scan completed : Cell 01 - Address: 00:11:50:21:3C:5F ESSID:"Omicron Main" Protocol:IEEE 802.11g Mode:Master Channel:1 Encryption key:off Bit Rate:54 Mb/s Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54 Signal level=-45 dBm Extra: Last beacon: 447ms ago
A couple more details that may be helpful in locating the bug: 1) The wireless LED indicator is not on after modules are loaded 2) Before upgrading to 1.0.1, 0.21 version was used. 0.21 version driver reports " drop data frame without data, type=0x80 subtype=0x80, len=??".
Hi Quanren, Can you try to limit the device to just 11b and see if things improve (also try different channels on the AP). We're trying to see if RF interference was causing your problem. To set the driver mode to 11b, use: iwpriv eth1 set_mode 2
hi Salwan, Here is the ifconfig output before and after setting it to 11b mode: Notice the number of Rx packets becomes 37 after the setting. Something goofy is happening. I think checking how the driver handling packet of type=0x80 is a good starting point to locate the bug. As to RF interference, eth1 works fine in the same environment in Windows. -------------------- eth1 Link encap:Ethernet HWaddr 00:0E:35:FC:A7:58 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:2500 errors:207 dropped:2402 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:2016 (1.9 KiB) Interrupt:7 Base address:0xc000 Memory:dfdfd000-dfdfdfff root@1[~]# iwpriv eth1 set_mode 2 root@1[~]# ifup eth1 Operation failed. Failed to bring up eth1. root@1[~]# ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:0E:35:FC:A7:58 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:37 errors:207 dropped:2540 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:2016 (1.9 KiB) Interrupt:7 Base address:0xc000 Memory:dfdfd000-dfdfdfff --------------------------
Could you give the information about what AP model and firmware you are using?
Could you also attach the debug data from ieee80211 at debug level 0x80 (DROP)? Other info from bug scrub: logics_sbux i suspect the data is still being dropped, but the message is now in ieee80211 instead of ipw2200 logics_sbux if the comment around that chunk of code is accurate, we may have something dealing w/ PSP
The AP is in "Mater" mode and the firmware is 2.2. How to get debug data from ieee80211 at debug level 0x80 (DROP)?
You can get debug data from ieee80211 with dmesg. You can set it with $ export IEEE80211_DEBUG=0x80 $ ./load
Here is the error from IEEE80211: ----------------------------------------- ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=610) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=610) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26) ieee80211: I ieee80211_rx RX: dropped data frame with no data (type=0x08, subtype=0x80, len=26)
The subtype 0x80 for type 0x8 (data) is reserved according to 802.11 1999 edition. I looked at 11b, 11g and 11i spec, but didn't find any extention for this bit. What's your AP brand? What's a "mater mode" for AP? Can you please switch your AP to other mode and see if the dmesg is different?
see comment #1. Please read all postings.
Nothing wrong with AP. The Ipw worked fine in Windows. If you can not debug, just say it, do not mess around.
Hi Quanren, I think what Yi asked is the protocol instead of mode. Does your AP use 802.11g protocol? If yes, could you switch AP to 802.11b to see whether the dmesg is different? The other possibility is that your AP has sent some packages which are not known to the driver. Could you tell us which AP you are using? (the model and the brand). Thanks a lot!
OK, it's 802.11 QoS packet. Our driver currently doesn't support WME/802.11e. It's in the TODO list though.