Bugzilla – Bug 1598
iwl4965 packet loss with 802.11b AP
Last modified: 2008-06-15 18:04:50
You need to log in before you can comment on or make changes to this bug.
I experience very bad network quality (almost unusable) with my laptop. Network card is : 03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61) I'm using ubuntu hardy with kernel 2.6.24-8-generic My access point is a Linksys BEFW11S4 (802.11b only). Network uses WEP encryption. modules loads correctly, firmware is uploaded correctly. AP is recognized and associated to (both manually or with network manager). Link quality is very good ( > 90%). Output of iwconfig wlan0 : wlan0 IEEE 802.11g ESSID:"fast306" Nickname:"" Mode:Managed Frequency:2.457 GHz Access Point: 00:0C:41:A5:A8:9A Bit Rate=11 Mb/s Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2346 B Encryption key:F04D-0989-62 Power Management:off Link Quality=99/100 Signal level=-53 dBm Noise level=-95 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 First weird thing, it indicates iEEE802.11g instead of b. Now the real problem: ping 192.168.0.1 (the access point) returns: PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=150 time=84.9 ms 64 bytes from 192.168.0.1: icmp_seq=1 ttl=150 time=135 ms (DUP!) 64 bytes from 192.168.0.1: icmp_seq=2 ttl=150 time=42.5 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=150 time=72.2 ms (DUP!) 64 bytes from 192.168.0.1: icmp_seq=3 ttl=150 time=45.4 ms 64 bytes from 192.168.0.1: icmp_seq=3 ttl=150 time=67.4 ms (DUP!) 64 bytes from 192.168.0.1: icmp_seq=4 ttl=150 time=53.1 ms 64 bytes from 192.168.0.1: icmp_seq=5 ttl=150 time=36.4 ms 64 bytes from 192.168.0.1: icmp_seq=6 ttl=150 time=41.2 ms 64 bytes from 192.168.0.1: icmp_seq=8 ttl=150 time=23.0 ms 64 bytes from 192.168.0.1: icmp_seq=8 ttl=150 time=62.8 ms (DUP!) 64 bytes from 192.168.0.1: icmp_seq=9 ttl=150 time=33.8 ms 64 bytes from 192.168.0.1: icmp_seq=10 ttl=150 time=29.6 ms 64 bytes from 192.168.0.1: icmp_seq=11 ttl=150 time=44.9 ms 64 bytes from 192.168.0.1: icmp_seq=12 ttl=150 time=34.5 ms 64 bytes from 192.168.0.1: icmp_seq=13 ttl=150 time=43.3 ms 64 bytes from 192.168.0.1: icmp_seq=13 ttl=150 time=76.5 ms (DUP!) 64 bytes from 192.168.0.1: icmp_seq=14 ttl=150 time=47.7 ms 64 bytes from 192.168.0.1: icmp_seq=15 ttl=150 time=20.4 ms 64 bytes from 192.168.0.1: icmp_seq=16 ttl=150 time=36.6 ms 64 bytes from 192.168.0.1: icmp_seq=17 ttl=150 time=36.1 ms 64 bytes from 192.168.0.1: icmp_seq=18 ttl=150 time=33.2 ms 64 bytes from 192.168.0.1: icmp_seq=18 ttl=150 time=78.4 ms (DUP!) 64 bytes from 192.168.0.1: icmp_seq=19 ttl=150 time=28.9 ms 64 bytes from 192.168.0.1: icmp_seq=20 ttl=150 time=47.9 ms 64 bytes from 192.168.0.1: icmp_seq=21 ttl=150 time=50.4 ms --- 192.168.0.1 ping statistics --- 22 packets transmitted, 20 received, +6 duplicates, 9% packet loss, time 21005ms rtt min/avg/max/mdev = 20.427/50.322/135.904/24.102 ms duplicates and packet loss. I can barely surf the web, downloads never exceeds 15kb/s and connection drops frequently. Here is an output of dmesg with debug=0x43fff --------------------------------------------------------------------------------- [ 424.434947] iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.2.0 [ 424.434959] iwl4965: Copyright(c) 2003-2007 Intel Corporation [ 424.435130] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17 [ 424.435154] PCI: Setting latency timer of device 0000:03:00.0 to 64 [ 424.436275] iwl4965: Detected Intel Wireless WiFi Link 4965AGN [ 424.680811] iwl4965: Tunable channels: 11 802.11bg, 13 802.11a channels [ 424.683215] wmaster0: Selected rate control algorithm 'iwl-4965-rs' [ 424.732867] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 437.728910] wlan0: Initial auth_alg=0 [ 437.728924] wlan0: authenticate with AP 00:0c:41:a5:a8:9a [ 437.730524] wlan0: RX authentication from 00:0c:41:a5:a8:9a (alg=0 transaction=2 status=0) [ 437.730531] wlan0: authenticated [ 437.730535] wlan0: associate with AP 00:0c:41:a5:a8:9a [ 437.735560] wlan0: RX AssocResp from 00:0c:41:a5:a8:9a (capab=0x15 status=0 aid=10) [ 437.735567] wlan0: associated [ 437.739100] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 440.850670] wmaster0: RX WEP frame with unknown keyidx 0 (A1=00:13:e8:7d:3c:17 A2=00:0c:41:a5:a8:9a A3=00:07:cb:0d:68:25) [ 443.105627] wmaster0: RX WEP frame with unknown keyidx 0 (A1=00:13:e8:7d:3c:17 A2=00:0c:41:a5:a8:9a A3=00:07:cb:0d:68:25) [ 443.171978] wmaster0: RX WEP frame with unknown keyidx 0 (A1=00:13:e8:7d:3c:17 A2=00:0c:41:a5:a8:9a A3=00:07:cb:0d:68:25) [ 443.420807] wmaster0: RX WEP frame with unknown keyidx 0 (A1=00:13:e8:7d:3c:17 A2=00:0c:41:a5:a8:9a A3=00:07:cb:0d:68:25) [ 443.664685] wmaster0: RX WEP frame with unknown keyidx 0 (A1=00:13:e8:7d:3c:17 A2=00:0c:41:a5:a8:9a A3=00:07:cb:0d:68:25) [ 443.761118] wmaster0: RX WEP frame with unknown keyidx 0 (A1=00:13:e8:7d:3c:17 A2=00:0c:41:a5:a8:9a A3=00:07:cb:0d:68:25) [ 450.181205] wmaster0: RX WEP frame with unknown keyidx 0 (A1=ff:ff:ff:ff:ff:ff A2=00:0c:41:a5:a8:9a A3=00:11:f5:a6:a0:84) [ 450.181938] wmaster0: RX WEP frame with unknown keyidx 0 (A1=ff:ff:ff:ff:ff:ff A2=00:0c:41:a5:a8:9a A3=00:11:f5:a6:a0:84) [ 450.927485] wmaster0: RX WEP frame with unknown keyidx 0 (A1=ff:ff:ff:ff:ff:ff A2=00:0c:41:a5:a8:9a A3=00:11:f5:a6:a0:84) [ 451.676450] wmaster0: RX WEP frame with unknown keyidx 0 (A1=ff:ff:ff:ff:ff:ff A2=00:0c:41:a5:a8:9a A3=00:11:f5:a6:a0:84) [ 452.978354] wlan0: no IPv6 routers present [ 441.708071] iwl4965: I iwl_rx_handle r = 163, i = 162, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 441.738647] iwl4965: I iwl_rx_handle r = 164, i = 163, REPLY_4965_RX, 0xc3 [ 441.742026] iwl4965: I iwl_rx_handle r = 166, i = 164, REPLY_4965_RX, 0xc3 [ 441.742038] iwl4965: I iwl_rx_handle r = 166, i = 165, STATISTICS_NOTIFICATION, 0x9d [ 441.742047] iwl4965: I iwl4965_get_temperature Running temperature calibration [ 441.742052] iwl4965: I iwl4965_get_temperature Calib values R[1-3]: 410 13960 -13154 R4: -3286 [ 441.742056] iwl4965: I iwl4965_get_temperature Calibrated temperature: 327K, 54C [ 441.742060] iwl4965: I iwl_hw_rx_statistics Temperature changed from 51C to 54C [ 441.742064] iwl4965: I iwl4965_is_temp_calib_needed Getting warmer, delta 3, [ 441.742067] iwl4965: I iwl4965_is_temp_calib_needed Thermal txpower calib needed [ 441.743392] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0470, 28 bytes at 112[16]:4 [ 441.743409] iwl4965: U iwl_enqueue_hcmd Sending command REPLY_TX_PWR_TABLE_CMD (#97), seq: 0x0471, 140 bytes at 113[17]:4 [ 441.743952] iwl4965: I iwl_rx_handle r 168 i 166 No handler needed for SENSITIVITY_CMD, 0xa8 [ 441.743959] iwl4965: I iwl_rx_handle r 168 i 167 No handler needed for REPLY_TX_PWR_TABLE_CMD, 0x97 [ 441.810421] iwl4965: I iwl_rx_handle r = 169, i = 168, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 441.997722] iwl4965: I iwl_rx_handle r = 171, i = 169, REPLY_4965_RX, 0xc3 [ 441.997744] iwl4965: I iwl_rx_handle r = 171, i = 170, STATISTICS_NOTIFICATION, 0x9d [ 441.997825] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0472, 28 bytes at 114[18]:4 [ 441.998390] iwl4965: I iwl_rx_handle r 172 i 171 No handler needed for SENSITIVITY_CMD, 0xa8 [ 442.322222] iwl4965: I iwl_rx_handle r = 173, i = 172, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 442.458113] iwl4965: I iwl_rx_handle r = 175, i = 173, REPLY_4965_RX, 0xc3 [ 442.458135] iwl4965: I iwl_rx_handle r = 175, i = 174, STATISTICS_NOTIFICATION, 0x9d [ 442.458203] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0473, 28 bytes at 115[19]:4 [ 442.458767] iwl4965: I iwl_rx_handle r 176 i 175 No handler needed for SENSITIVITY_CMD, 0xa8 [ 442.713796] iwl4965: I iwl_rx_handle r = 178, i = 176, REPLY_4965_RX, 0xc3 [ 442.713817] iwl4965: I iwl_rx_handle r = 178, i = 177, STATISTICS_NOTIFICATION, 0x9d [ 442.714395] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0474, 28 bytes at 116[20]:4 [ 442.714961] iwl4965: I iwl_rx_handle r 179 i 178 No handler needed for SENSITIVITY_CMD, 0xa8 [ 442.788137] iwl4965: I iwl_rx_handle r = 180, i = 179, REPLY_4965_RX, 0xc3 [ 442.826376] iwl4965: I iwl_rx_handle r = 182, i = 180, REPLY_4965_RX, 0xc3 [ 442.826398] iwl4965: I iwl_rx_handle r = 182, i = 181, STATISTICS_NOTIFICATION, 0x9d [ 442.826989] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0475, 28 bytes at 117[21]:4 [ 442.827559] iwl4965: I iwl_rx_handle r 183 i 182 No handler needed for SENSITIVITY_CMD, 0xa8 [ 442.833963] iwl4965: I iwl_rx_handle r = 184, i = 183, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 443.164026] iwl4965: I iwl_rx_handle r = 186, i = 184, REPLY_4965_RX, 0xc3 [ 443.164049] iwl4965: I iwl_rx_handle r = 186, i = 185, STATISTICS_NOTIFICATION, 0x9d [ 443.164463] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0476, 28 bytes at 118[22]:4 [ 443.165032] iwl4965: I iwl_rx_handle r 187 i 186 No handler needed for SENSITIVITY_CMD, 0xa8 [ 443.345796] iwl4965: I iwl_rx_handle r = 188, i = 187, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 443.767568] iwl4965: I iwl_rx_handle r = 190, i = 188, REPLY_4965_RX, 0xc3 [ 443.767591] iwl4965: I iwl_rx_handle r = 190, i = 189, STATISTICS_NOTIFICATION, 0x9d [ 443.857556] iwl4965: I iwl_rx_handle r = 191, i = 190, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 444.105243] iwl4965: I iwl_rx_handle r = 193, i = 191, REPLY_4965_RX, 0xc3 [ 444.105266] iwl4965: I iwl_rx_handle r = 193, i = 192, STATISTICS_NOTIFICATION, 0x9d [ 444.105391] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0477, 28 bytes at 119[23]:4 [ 444.105954] iwl4965: I iwl_rx_handle r 194 i 193 No handler needed for SENSITIVITY_CMD, 0xa8 [ 444.350684] iwl4965: I iwl_rx_handle r = 195, i = 194, REPLY_4965_RX, 0xc3 [ 444.351242] iwl4965: I iwl_rx_handle r = 196, i = 195, STATISTICS_NOTIFICATION, 0x9d [ 444.353041] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0478, 28 bytes at 120[24]:4 [ 444.353604] iwl4965: I iwl_rx_handle r 197 i 196 No handler needed for SENSITIVITY_CMD, 0xa8 [ 444.369287] iwl4965: I iwl_rx_handle r = 198, i = 197, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 444.463232] iwl4965: I iwl_rx_handle r = 199, i = 198, REPLY_4965_RX, 0xc3 [ 444.463785] iwl4965: I iwl_rx_handle r = 200, i = 199, STATISTICS_NOTIFICATION, 0x9d [ 444.873971] iwl4965: I iwl_rx_handle r = 201, i = 200, REPLY_4965_RX, 0xc3 [ 444.881079] iwl4965: I iwl_rx_handle r = 202, i = 201, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 445.046400] iwl4965: I iwl_rx_handle r = 203, i = 202, REPLY_4965_RX, 0xc3 [ 445.046967] iwl4965: I iwl_rx_handle r = 204, i = 203, STATISTICS_NOTIFICATION, 0x9d [ 445.046993] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0479, 28 bytes at 121[25]:4 [ 445.047564] iwl4965: I iwl_rx_handle r 205 i 204 No handler needed for SENSITIVITY_CMD, 0xa8 [ 445.281699] iwl4965: I iwl_rx_handle r = 206, i = 205, REPLY_4965_RX, 0xc3 [ 445.282263] iwl4965: I iwl_rx_handle r = 207, i = 206, STATISTICS_NOTIFICATION, 0x9d [ 445.282290] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x047A, 28 bytes at 122[26]:4 [ 445.282850] iwl4965: I iwl_rx_handle r 208 i 207 No handler needed for SENSITIVITY_CMD, 0xa8 [ 445.392871] iwl4965: I iwl_rx_handle r = 209, i = 208, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 445.506797] iwl4965: I iwl_rx_handle r = 210, i = 209, REPLY_4965_RX, 0xc3 [ 445.507357] iwl4965: I iwl_rx_handle r = 211, i = 210, STATISTICS_NOTIFICATION, 0x9d [ 445.507375] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x047B, 28 bytes at 123[27]:4 [ 445.507946] iwl4965: I iwl_rx_handle r 212 i 211 No handler needed for SENSITIVITY_CMD, 0xa8 [ 445.885249] iwl4965: I iwl_rx_handle r = 213, i = 212, REPLY_4965_RX, 0xc3 [ 445.885815] iwl4965: I iwl_rx_handle r = 214, i = 213, STATISTICS_NOTIFICATION, 0x9d [ 445.885840] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x047C, 28 bytes at 124[28]:4 [ 445.886412] iwl4965: I iwl_rx_handle r 215 i 214 No handler needed for SENSITIVITY_CMD, 0xa8 [ 445.904658] iwl4965: I iwl_rx_handle r = 216, i = 215, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 445.922466] iwl4965: I iwl_rx_handle r = 217, i = 216, REPLY_4965_RX, 0xc3 [ 446.110356] iwl4965: I iwl_rx_handle r = 218, i = 217, REPLY_4965_RX, 0xc3 [ 446.110923] iwl4965: I iwl_rx_handle r = 219, i = 218, STATISTICS_NOTIFICATION, 0x9d [ 446.110950] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x047D, 28 bytes at 125[29]:4 [ 446.111531] iwl4965: I iwl_rx_handle r 220 i 219 No handler needed for SENSITIVITY_CMD, 0xa8 [ 446.222901] iwl4965: I iwl_rx_handle r = 221, i = 220, REPLY_4965_RX, 0xc3 [ 446.223457] iwl4965: I iwl_rx_handle r = 222, i = 221, STATISTICS_NOTIFICATION, 0x9d [ 446.223476] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x047E, 28 bytes at 126[30]:4 [ 446.224046] iwl4965: I iwl_rx_handle r 223 i 222 No handler needed for SENSITIVITY_CMD, 0xa8 [ 446.416452] iwl4965: I iwl_rx_handle r = 224, i = 223, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 446.448010] iwl4965: I iwl_rx_handle r = 225, i = 224, REPLY_4965_RX, 0xc3 [ 446.448573] iwl4965: I iwl_rx_handle r = 226, i = 225, STATISTICS_NOTIFICATION, 0x9d [ 446.448600] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x047F, 28 bytes at 127[31]:4 [ 446.449170] iwl4965: I iwl_rx_handle r 227 i 226 No handler needed for SENSITIVITY_CMD, 0xa8 [ 446.806071] iwl4965: I iwl_rx_handle r = 228, i = 227, REPLY_4965_RX, 0xc3 [ 446.918620] iwl4965: I iwl_rx_handle r = 230, i = 228, STATISTICS_NOTIFICATION, 0x9d [ 446.918636] iwl4965: I iwl_rx_handle r = 230, i = 229, REPLY_4965_RX, 0xc3 [ 446.919071] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0480, 28 bytes at 128[0]:4 [ 446.919182] iwl4965: I iwl_rx_handle r = 232, i = 230, STATISTICS_NOTIFICATION, 0x9d [ 446.919190] iwl4965: I iwl_rx_handle r 232 i 231 No handler needed for SENSITIVITY_CMD, 0xa8 [ 446.919271] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0481, 28 bytes at 129[1]:4 [ 446.919830] iwl4965: I iwl_rx_handle r 233 i 232 No handler needed for SENSITIVITY_CMD, 0xa8 [ 446.928231] iwl4965: I iwl_rx_handle r = 234, i = 233, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 446.964234] iwl4965: I iwl_rx_handle r = 235, i = 234, REPLY_4965_RX, 0xc3 [ 446.970721] iwl4965: I iwl_rx_handle r = 236, i = 235, REPLY_4965_RX, 0xc3 [ 446.970731] iwl4965: I iwl4965_rx_reply_rx Dropping (dup): 00:13:e8:7d:3c:17, 00:0c:41:a5:a8:9a, 00:0c:41:a5:a8:9a [ 447.440023] iwl4965: I iwl_rx_handle r = 237, i = 236, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 447.542377] iwl4965: I iwl_rx_handle r = 238, i = 237, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 447.542405] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0482, 28 bytes at 130[2]:4 [ 447.542964] iwl4965: I iwl_rx_handle r 239 i 238 No handler needed for SENSITIVITY_CMD, 0xa8 [ 447.644720] iwl4965: I iwl_rx_handle r = 240, i = 239, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 447.747104] iwl4965: I iwl_rx_handle r = 241, i = 240, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 447.850152] iwl4965: I iwl_rx_handle r = 242, i = 241, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 447.951803] iwl4965: I iwl_rx_handle r = 243, i = 242, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 448.017644] iwl4965: I iwl_rx_handle r = 244, i = 243, REPLY_4965_RX, 0xc3 [ 448.054162] iwl4965: I iwl_rx_handle r = 245, i = 244, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 448.074728] iwl4965: I iwl_rx_handle r = 246, i = 245, REPLY_4965_RX, 0xc3 [ 448.075308] iwl4965: I iwl_rx_handle r = 247, i = 246, STATISTICS_NOTIFICATION, 0x9d [ 448.075330] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0483, 28 bytes at 131[3]:4 [ 448.075900] iwl4965: I iwl_rx_handle r 248 i 247 No handler needed for SENSITIVITY_CMD, 0xa8 [ 448.156529] iwl4965: I iwl_rx_handle r = 249, i = 248, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 448.442983] iwl4965: I iwl_rx_handle r = 250, i = 249, REPLY_4965_RX, 0xc3 [ 448.443548] iwl4965: I iwl_rx_handle r = 251, i = 250, STATISTICS_NOTIFICATION, 0x9d [ 448.443575] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0484, 28 bytes at 132[4]:4 [ 448.444148] iwl4965: I iwl_rx_handle r 252 i 251 No handler needed for SENSITIVITY_CMD, 0xa8 [ 448.668330] iwl4965: I iwl_rx_handle r = 253, i = 252, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 448.678277] iwl4965: I iwl_rx_handle r = 254, i = 253, REPLY_4965_RX, 0xc3 [ 448.678838] iwl4965: I iwl_rx_handle r = 255, i = 254, STATISTICS_NOTIFICATION, 0x9d [ 448.678863] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0485, 28 bytes at 133[5]:4 [ 448.679435] iwl4965: I iwl_rx_handle r 0 i 255 No handler needed for SENSITIVITY_CMD, 0xa8 [ 448.913584] iwl4965: I iwl_rx_handle r = 1, i = 0, REPLY_4965_RX, 0xc3 [ 448.914146] iwl4965: I iwl_rx_handle r = 2, i = 1, STATISTICS_NOTIFICATION, 0x9d [ 448.914170] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0486, 28 bytes at 134[6]:4 [ 448.914743] iwl4965: I iwl_rx_handle r 3 i 2 No handler needed for SENSITIVITY_CMD, 0xa8 [ 449.054473] iwl4965: I iwl_rx_handle r = 4, i = 3, REPLY_4965_RX, 0xc3 [ 449.159085] iwl4965: I iwl_rx_handle r = 5, i = 4, REPLY_4965_RX, 0xc3 [ 449.159652] iwl4965: I iwl_rx_handle r = 6, i = 5, STATISTICS_NOTIFICATION, 0x9d [ 449.159678] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0487, 28 bytes at 135[7]:4 [ 449.160250] iwl4965: I iwl_rx_handle r 7 i 6 No handler needed for SENSITIVITY_CMD, 0xa8 [ 449.180093] iwl4965: I iwl_rx_handle r = 8, i = 7, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 449.496740] iwl4965: I iwl_rx_handle r = 9, i = 8, REPLY_4965_RX, 0xc3 [ 449.497304] iwl4965: I iwl_rx_handle r = 10, i = 9, STATISTICS_NOTIFICATION, 0x9d [ 449.497328] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0488, 28 bytes at 136[8]:4 [ 449.497899] iwl4965: I iwl_rx_handle r 11 i 10 No handler needed for SENSITIVITY_CMD, 0xa8 [ 449.691899] iwl4965: I iwl_rx_handle r = 12, i = 11, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 449.732625] iwl4965: I iwl_rx_handle r = 13, i = 12, REPLY_4965_RX, 0xc3 [ 449.733185] iwl4965: I iwl_rx_handle r = 14, i = 13, STATISTICS_NOTIFICATION, 0x9d [ 449.733209] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x0489, 28 bytes at 137[9]:4 [ 449.733780] iwl4965: I iwl_rx_handle r 15 i 14 No handler needed for SENSITIVITY_CMD, 0xa8 [ 449.875184] iwl4965: I iwl_rx_handle r = 16, i = 15, REPLY_4965_RX, 0xc3 [ 449.875751] iwl4965: I iwl_rx_handle r = 17, i = 16, STATISTICS_NOTIFICATION, 0x9d [ 449.987737] iwl4965: I iwl_rx_handle r = 18, i = 17, REPLY_4965_RX, 0xc3 [ 449.988303] iwl4965: I iwl_rx_handle r = 19, i = 18, STATISTICS_NOTIFICATION, 0x9d [ 450.099627] iwl4965: I iwl_rx_handle r = 20, i = 19, REPLY_4965_RX, 0xc3 [ 450.203674] iwl4965: I iwl_rx_handle r = 21, i = 20, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 450.212837] iwl4965: I iwl_rx_handle r = 22, i = 21, REPLY_4965_RX, 0xc3 [ 450.213394] iwl4965: I iwl_rx_handle r = 23, i = 22, STATISTICS_NOTIFICATION, 0x9d [ 450.715454] iwl4965: I iwl_rx_handle r = 24, i = 23, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 450.806190] iwl4965: I iwl_rx_handle r = 25, i = 24, REPLY_4965_RX, 0xc3 [ 450.806740] iwl4965: I iwl_rx_handle r = 26, i = 25, STATISTICS_NOTIFICATION, 0x9d [ 451.149914] iwl4965: I iwl_rx_handle r = 27, i = 26, REPLY_4965_RX, 0xc3 [ 451.227239] iwl4965: I iwl_rx_handle r = 28, i = 27, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 451.307378] iwl4965: I iwl_rx_handle r = 29, i = 28, REPLY_4965_RX, 0xc3 [ 451.307937] iwl4965: I iwl_rx_handle r = 30, i = 29, STATISTICS_NOTIFICATION, 0x9d [ 451.739030] iwl4965: I iwl_rx_handle r = 31, i = 30, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 451.757599] iwl4965: I iwl_rx_handle r = 32, i = 31, REPLY_4965_RX, 0xc3 [ 451.758161] iwl4965: I iwl_rx_handle r = 33, i = 32, STATISTICS_NOTIFICATION, 0x9d [ 451.870147] iwl4965: I iwl_rx_handle r = 34, i = 33, REPLY_4965_RX, 0xc3 [ 451.870711] iwl4965: I iwl_rx_handle r = 35, i = 34, STATISTICS_NOTIFICATION, 0x9d [ 452.194789] iwl4965: I iwl_rx_handle r = 36, i = 35, REPLY_4965_RX, 0xc3 [ 452.250813] iwl4965: I iwl_rx_handle r = 37, i = 36, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 452.668219] iwl4965: I iwl_rx_handle r = 38, i = 37, REPLY_4965_RX, 0xc3 [ 452.668784] iwl4965: I iwl_rx_handle r = 39, i = 38, STATISTICS_NOTIFICATION, 0x9d [ 452.762599] iwl4965: I iwl_rx_handle r = 40, i = 39, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 452.903522] iwl4965: I iwl_rx_handle r = 41, i = 40, REPLY_4965_RX, 0xc3 [ 452.904086] iwl4965: I iwl_rx_handle r = 42, i = 41, STATISTICS_NOTIFICATION, 0x9d [ 453.026259] iwl4965: I iwl_rx_handle r = 43, i = 42, REPLY_4965_RX, 0xc3 [ 453.026814] iwl4965: I iwl_rx_handle r = 44, i = 43, STATISTICS_NOTIFICATION, 0x9d [ 453.026842] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x048A, 28 bytes at 138[10]:4 [ 453.027401] iwl4965: I iwl_rx_handle r 45 i 44 No handler needed for SENSITIVITY_CMD, 0xa8 [ 453.234971] iwl4965: I iwl_rx_handle r = 46, i = 45, REPLY_4965_RX, 0xc3 [ 453.261566] iwl4965: I iwl_rx_handle r = 47, i = 46, REPLY_4965_RX, 0xc3 [ 453.262124] iwl4965: I iwl_rx_handle r = 48, i = 47, STATISTICS_NOTIFICATION, 0x9d [ 453.262150] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x048B, 28 bytes at 139[11]:4 [ 453.262720] iwl4965: I iwl_rx_handle r 49 i 48 No handler needed for SENSITIVITY_CMD, 0xa8 [ 453.274391] iwl4965: I iwl_rx_handle r = 50, i = 49, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 453.374469] iwl4965: I iwl_rx_handle r = 51, i = 50, REPLY_4965_RX, 0xc3 [ 453.375031] iwl4965: I iwl_rx_handle r = 52, i = 51, STATISTICS_NOTIFICATION, 0x9d [ 453.375052] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x048C, 28 bytes at 140[12]:4 [ 453.375621] iwl4965: I iwl_rx_handle r 53 i 52 No handler needed for SENSITIVITY_CMD, 0xa8 [ 453.599231] iwl4965: I iwl_rx_handle r = 54, i = 53, REPLY_4965_RX, 0xc3 [ 453.599797] iwl4965: I iwl_rx_handle r = 55, i = 54, STATISTICS_NOTIFICATION, 0x9d [ 453.599823] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x048D, 28 bytes at 141[13]:4 [ 453.600386] iwl4965: I iwl_rx_handle r 56 i 55 No handler needed for SENSITIVITY_CMD, 0xa8 [ 453.786174] iwl4965: I iwl_rx_handle r = 57, i = 56, MISSED_BEACONS_NOTIFICATION, 0xa2 [ 453.824335] iwl4965: I iwl_rx_handle r = 58, i = 57, REPLY_4965_RX, 0xc3 [ 453.824900] iwl4965: I iwl_rx_handle r = 59, i = 58, STATISTICS_NOTIFICATION, 0x9d [ 453.824925] iwl4965: U iwl_enqueue_hcmd Sending command SENSITIVITY_CMD (#a8), seq: 0x048E, 28 bytes at 142[14]:4 [ 453.825499] iwl4965: I iwl_rx_handle r 60 i 59 No handler needed for SENSITIVITY_CMD, 0xa8 (this output was generated during the ping command above). the driver shipped with ubuntu seemed old so I tried the following combinations: iwlwifi 1.2.23/1.2.24/1.2.25 with vanilla kernel 2.6.23 as well as compat-wireless-2.6 (iwlwifi 1.2.23k) with vanilla kernel 2.6.24 2.6.25-rc1 wireless-everything.git (commit b7daedae212131703346655b63a1ace877aa783f) The behaviour is the same as with the ubuntu kernel and the old driver with the following differences: - I don't get as much debugging output (with debug=0x43fff) - iwconfig lists IEEE 802.11 (instead of 802.11g as previously). Please let me know if I can perform more tests.
I also add that: The same laptop under Windows vista works correctly with this AP Another laptop under windows XP works correctly with this AP Another laptop under ubuntu hardy with driver ipw2200 works with this AP.
Hi, how about the kernel-2.6.25rc2 with iwlwifi-1.2.26 built in? I tried to connect with a B-only AP with this snapshot on my fedora core7 system, no packet dupicate, only 4% packet loss. 186 packets transmitted, 178 received, 4% packet loss, time 185181ms rtt min/avg/max/mdev = 0.973/6.907/92.434/12.398 ms However, sometimes it failed to set up the connection with AP.I've reported this with bug#1621http://bughost.org/bugzilla/show_bug.cgi?id=1621
(In reply to comment #2) > Hi, how about the kernel-2.6.25rc2 with iwlwifi-1.2.26 built in? Hi, I tried this (as well as the wireless-everything git and the compat-wireless patches for stable kernels as soon as there are changes in the iwlwifi driver). Indeed the duplicates disappear but the packet loss is still there and the overall performances haven't changed. (I suspect the packet loss to increase with the traffic but this is just a guess). However, I made an interesting discovery. It turns out that I had not checked thoroughly with windows vista but it exhibits the same behaviour. (I was mislead by windows ping command which only sends 3 packets by default and did not try to surf the web, since I don't use vista...). This makes me think that it could be a firmware related issue. I confirmed this by testing in a clean environment (unplugged the chordless phone which I thought was responsible at first and moved everything out of the neighbour's AP range). I tried many combinations of non authentication, wep and wpa, with the same results. Signal quality is always above 98% yet the packet loss is still there. This is really an issue since B access points are still widely used for "free" internet access all around (library, coffee place, my house :D, ... ). Let me know if I can test anything else.
Tested this with snapshot 03282008 on 4965AGN card, I also found that there's a sever packet loss in B-Only mode. AP I used is D-Link DIR635, with ping to it after association, I got: 101 packets transmitted, 78 received, 22% packet loss, time 100062ms rtt min/avg/max/mdev = 0.647/22.116/1003.305/113.369 ms, pipe 2
Also tested with snapshot 04042008 (via compat-wireless), kernel 2.6.24-14-generic (stock ubuntu kernel in hardy), same (AP Linksys BEFW11S4 802.11b only). ping -c 100 192.168.0.1 returns: --- 192.168.0.1 ping statistics --- 100 packets transmitted, 84 received, 16% packet loss, time 99027ms rtt min/avg/max/mdev = 14.027/41.406/88.522/16.787 ms http downloads are around 30kb/s max, (agains around 600kb/s with ethernet on this laptop or via wifi on another laptop). Same stats under windows vista (i.e. packet loss and poor dl rate).
Tested on kernel 2.6.25, iwl4965 seems work better for this version, here is the result: 121 packets transmitted, 119 received, 1% packet loss, time 120067ms rtt min/avg/max/mdev = 0.618/4.139/43.596/6.242 ms
tested on snapshot 04252008, this is fixed for me. Kim, if it's also fixed for you ,how about change the status to fixed?
(In reply to comment #7) > tested on snapshot 04252008, this is fixed for me. Kim, if it's also fixed for > you ,how about change the status to fixed? I'm not sure. Indeed packet lost in ping does not seem significant any more (around 2% max), but I still have terrible download/upload rate (never above 30ko/s on the local network). Furthermore, even if almost all pings return, they take a long time. For instance, pinging the access point I have sometimes many seconds interval between ping n and ping n+1 but strangely, the packet isn't dropped. Again, at the very same spots, other laptops are working just fine. The card takes also a long time to authenticate to the AP (and fails often, I have to retry many times). It does'nt seem to matter what encryption I use (WEP, TKIP,...). I just had access to another B access point. I'll test and let you know shortly.
Running vanilla 2.6.25.3. Same behavior - ~3% pings to AP lost (more if you limit the reply timeout to a sensible number), crappy network performance. I can get up to 50 kB/s when downloading from the internet but only half of it when transferring between local machines (the other machines reach 10x that speed). This renders UPnP file sharing with my PS3 pretty useless :) AP: D-Link DI-514, 802.11b Seems to work correctly with G and N networks.
Here for me B-band association works well, no packet loss, and data transfer between Local machines can reach 100KB/s around. I tried with latest snapshot on D-Link DIR635 AP and Linksys WRT300N AP.
(In reply to comment #10) > Here for me B-band association works well, no packet loss, and data transfer > between Local machines can reach 100KB/s around. |-------------->data transfer results is tested with Linksys AP, I found that sometimes it would lose connection with D-Link AP in B-only mode if I do data transfer. But if I don't transfer data, only send ping packets, connection won't lose, and no ping packets loss.
(In reply to comment #11) > (In reply to comment #10) > > Here for me B-band association works well, no packet loss, and data transfer > > between Local machines can reach 100KB/s around. > |-------------->data transfer results is tested with Linksys > AP, I found that sometimes it would lose connection with D-Link AP in B-only > mode if I do data transfer. But if I don't transfer data, only send ping > packets, connection won't lose, and no ping packets loss. > I confirm this behaviour. Pinging the AP or any machine on the internet is now fine (almost always 0% packet loss) but data transfer are painfully slow (around 100 kb/s on lan, 60kb/s from the internet). I tried latest compat-wireless snapshot (which reflects the wireless-testing git as of May 18 2008). I tried with no/wep/tkip authentication, but the result is the same. I emphasize that I have the same behaviour (that is poor network performance) with windows Vista which (quite naively) leads me to think that this can be a bug in the firmware or in some code shared between the windows and linux driver (if any). It could also be a hardware problem but this seems unlikely since others are experiencing the same problems and the card works fine in G mode.
Nguyen, in recent snapshots ping packets to B_only AP don't lose anymore, how about change the status of this bug to "fixed"? You can open another bug for the transfer rate issue.
(In reply to comment #13) > Nguyen, in recent snapshots ping packets to B_only AP don't lose anymore, how > about change the status of this bug to "fixed"? You can open another bug for > the transfer rate issue. > Seems reasonable. However I'm away for a couple of days and don't have the time to do a proper bug report right now. I'll do it sometime next week if nobody do it in the mean time.
(In reply to comment #13) > Nguyen, in recent snapshots ping packets to B_only AP don't lose anymore, how > about change the status of this bug to "fixed"? You can open another bug for > the transfer rate issue. > I added some comments in bug #1669 which was opened recently and seems to match my issues. I think its ok to close this bug (the ping issue is indeed gone).
Mark to "Fixed" according to Kim's last comment