Bugzilla – Bug 430
'excluded because of storming' caused by AUTH_SEQ_1_FAIL
Last modified: 2007-03-26 02:16:55
You need to log in before you can comment on or make changes to this bug.
Problem reported on mailing list by Athanasios Leontaris on Friday 11/24/2004 6:50pm (Pacific standard time) ----------------------------------------------------------- Association is lost - and I have to rmmod and modprobe the driver again to make it work - at a rate of at least once per day with both 0.14 and 0.15 on a IBM ThinkPad T41, vanilla kernel 2.6.9, hotplug-2004_3_29 and wireless_tolls-27pre26. WEP-128bit Open mode connection. Nothing is dumped to /var/log/messages.... This has never happened before with either the 0.13 or previous drivers. It was definitely introduced in 0.14. ---------------------------------------- This is a followup to my previous problem report. I loaded the module with "debug=255" and when the association was lost it went into an _infinite_ loop dumping the following stuff. It cannot associate because of _storming_ it seems....Now I have to rmmod and modprobe it again. This never happened with 0.13 or previous drivers. Hopefully it will help you to track down the bug. ipw2200: U ipw_send_cmd Sending SSID command (#8), 10 bytes 00000000 {HEX(MY_AP_SSID)} MY_AP_SSID ipw2200: I ipw_irq_tasklet Command completed. ipw2200: U ipw_send_cmd Sending SCAN_REQUEST_EXT command (#26), 96 bytes 00000000 93 00 00 00 4B 01 02 03 04 05 06 07 08 09 0A 0B ....K... ........ 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 04 44 44 44 44 44 ........ ...DDDDD 00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000050 00 00 00 00 00 00 00 00 78 00 00 00 14 00 64 00 ........ x.....d. ipw2200: I ipw_irq_tasklet Command completed. ipw2200: U ipw_best_network Network 'AP1' excluded because of storming. ipw2200: U ipw_best_network Network 'AP2' excluded because of privacy mismatch: on != off. ipw2200: U ipw_best_network Network 'AP3' excluded because of ESSID mismatch: 'MY_AP_SSID'. ipw2200: U ipw_best_network Network 'AP4' excluded because of ESSID mismatch: 'MY_AP_SSID'. ipw2200: U ipw_best_network Network 'AP5' excluded because of ESSID mismatch: 'MY_AP_SSID'. ipw2200: U ipw_best_network Network 'MY_AP_SSID' excluded because of storming. ipw2200: U ipw_best_network Network 'AP6' excluded because of ESSID mismatch: 'MY_AP_SSID'. ipw2200: U ipw_best_network Network 'AP7' excluded because of privacy mismatch: on != off. ipw2200: U ipw_best_network Network 'AP8' excluded because of age: 15547ms. ipw2200: U ipw_associate Scan completed, no valid APs matched [CFG 0x00000142] ipw2200: U ipw_associate Channel unlocked. ipw2200: U ipw_associate ESSID locked to 'MY_AP_SSID' ipw2200: U ipw_associate BSSID unlocked. ipw2200: U ipw_associate PRIVACY on ipw2200: U ipw_associate RATE MASK: 0x00000FFF
Can you provide the part of the log that shows the association attempt occuring, including the reason for association failure? Setting the debug log to 0x3fff will ensure that is captured. Also, in the debug log below it wasn't clear if you edited the log or not. The following: ipw2200: U ipw_best_network Network 'AP1' excluded because of storming. ipw2200: U ipw_best_network Network 'MY_AP_SSID' excluded because of storming. is concerning. Did the first line originally say 'MY_AP_SSID' excluded because of storming, or is the log showing that an SSID different than your configured SSID was being attempted? Thanks, James
I have the info requested below, generated by dmesg -c in a while loop and piped through a function to give time since epoch. Further, I was thinking of disabling the "storming" section of the driver, are there any nasty implications for this - why does it need to be there at all?
Created an attachment (id=211) [details] Debug output for dmesg This was generated using the following script: #!/bin/bash LOGFILE=/tmp/dmesg.log logstr() { if [ X"$1" != "X" ] ; then echo `epochtime` "$*" >> $LOGFILE echo `epochtime` "$*" fi } while true ; do dmesg -c | while read THISLINE ; do logstr "$THISLINE" done done where epochtime.c is 'main(){ printf("%d", time()); }' There is a hell of a lot of it, but I figured, better too much info than too little right :)
Created an attachment (id=212) [details] Patch to allow disabling of storming protection This is a simple patch to add a parameter to the module which allows the disabling of storming protection. Directions for use: Apply patch,compile modprobe ipw2200 storming_protection=0 If you don't put the extra parameter on, the module will behave exactly as it does now.
This may or may not be germane: I've discovered that I get the "excluded because of storming" message if the AP security mode is WPA. This driver can't handle WPA at the moment. If I change the AP's security mode to WEP, the messages go away and I can connect without difficulty.
Running ipw2200 with debug="0x3FFF" on a ThinkPad T41, 2.6.9 and 0.19 driver (WEP-128bit OPEN) I get much more frequent losses of connectivity now; it seems the connection drops are much more frequent compared to when the bug first appeared. The cuplrit seems to be again the storming protection. Attached is the error log from dmesg (as much as I was able to capture): ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 2 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 3 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 4 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 5 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 6 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 7 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 8 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 9 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 10 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 11 ipw2200: I ipw_rx_notification type = 13 (4 bytes) ipw2200: I ipw_rx_notification Scan completed: type 11, 11 channels, 1 status ipw2200: U ipw_best_network Network 'AP1' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP2' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP3' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP4' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'MY_AP' excluded because of storming. ipw2200: U ipw_best_network Network 'AP5' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP6' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP7' excluded because of hidden ESSID. ipw2200: U ipw_best_network Network 'AP8' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP9' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_debug_config Scan completed, no valid APs matched [CFG 0x00000142] ipw2200: U ipw_debug_config Channel unlocked. ipw2200: U ipw_debug_config ESSID locked to 'MY_AP' ipw2200: U ipw_debug_config BSSID unlocked. ipw2200: U ipw_debug_config PRIVACY on ipw2200: U ipw_debug_config RATE MASK: 0x00000FFF ipw2200: U ipw_send_cmd Sending SSID command (#8), 10 bytes 00000000 MY_AP ipw2200: I ipw_irq_tasklet Command completed. ipw2200: U ipw_send_cmd Sending SCAN_REQUEST_EXT command (#26), 96 bytes 00000000 B9 00 00 00 4B 01 02 03 04 05 06 07 08 09 0A 0B ....K... ........ 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 04 44 44 44 44 44 ........ ...DDDDD 00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000050 00 00 00 00 00 00 00 00 14 00 00 00 14 00 14 00 ........ ........ ipw2200: I ipw_irq_tasklet Command completed. ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 1 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 2 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 3 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 4 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 5 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 6 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 7 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 8 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 9 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 10 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 11 ipw2200: I ipw_rx_notification type = 13 (4 bytes) ipw2200: I ipw_rx_notification Scan completed: type 11, 11 channels, 1 status ipw2200: U ipw_best_network Network 'AP1' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP2' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP3' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP4' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'MY_AP' excluded because of storming. ipw2200: U ipw_best_network Network 'AP5' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP6' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP7' excluded because of hidden ESSID. ipw2200: U ipw_best_network Network 'AP8' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP9' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_debug_config Scan completed, no valid APs matched [CFG 0x00000142] ipw2200: U ipw_debug_config Channel unlocked. ipw2200: U ipw_debug_config ESSID locked to 'MY_AP' ipw2200: U ipw_debug_config BSSID unlocked. ipw2200: U ipw_debug_config PRIVACY on ipw2200: U ipw_debug_config RATE MASK: 0x00000FFF ipw2200: U ipw_send_cmd Sending SCAN_REQUEST_EXT command (#26), 96 bytes 00000000 BA 00 00 00 4B 01 02 03 04 05 06 07 08 09 0A 0B ....K... ........ 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 03 33 33 33 33 33 ........ ...33333 00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000050 00 00 00 00 00 00 00 00 14 00 00 00 14 00 14 00 ........ ........ ipw2200: I ipw_irq_tasklet Command completed. ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 1 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 2 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 3 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 4 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 5 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 6 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 7 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 8 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 9 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 10 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 11 ipw2200: I ipw_rx_notification type = 13 (4 bytes) ipw2200: I ipw_rx_notification Scan completed: type 11, 11 channels, 1 status ipw2200: U ipw_best_network Network 'AP1' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP2' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP3' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP4' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'MY_AP' excluded because of storming. ipw2200: U ipw_best_network Network 'AP5' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP6' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP7' excluded because of hidden ESSID. ipw2200: U ipw_best_network Network 'AP8' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP9' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_debug_config Scan completed, no valid APs matched [CFG 0x00000142] ipw2200: U ipw_debug_config Channel unlocked. ipw2200: U ipw_debug_config ESSID locked to 'MY_AP' ipw2200: U ipw_debug_config BSSID unlocked. ipw2200: U ipw_debug_config PRIVACY on ipw2200: U ipw_debug_config RATE MASK: 0x00000FFF ipw2200: U ipw_send_cmd Sending SSID command (#8), 10 bytes 00000000 MY_AP ipw2200: I ipw_irq_tasklet Command completed. ipw2200: U ipw_send_cmd Sending SCAN_REQUEST_EXT command (#26), 96 bytes 00000000 BB 00 00 00 4B 01 02 03 04 05 06 07 08 09 0A 0B ....K... ........ 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 04 44 44 44 44 44 ........ ...DDDDD 00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000050 00 00 00 00 00 00 00 00 14 00 00 00 14 00 14 00 ........ ........ ipw2200: I ipw_irq_tasklet Command completed. ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 1 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 2 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 3 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 4 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 5 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 6 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 7 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 8 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 9 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 10 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 11 ipw2200: I ipw_rx_notification type = 13 (4 bytes) ipw2200: I ipw_rx_notification Scan completed: type 11, 11 channels, 1 status ipw2200: U ipw_best_network Network 'AP1' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP2' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP3' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP4' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'MY_AP' excluded because of storming. ipw2200: U ipw_best_network Network 'AP5' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP6' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP7' excluded because of hidden ESSID. ipw2200: U ipw_best_network Network 'AP8' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP9' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_debug_config Scan completed, no valid APs matched [CFG 0x00000142] ipw2200: U ipw_debug_config Channel unlocked. ipw2200: U ipw_debug_config ESSID locked to 'MY_AP' ipw2200: U ipw_debug_config BSSID unlocked. ipw2200: U ipw_debug_config PRIVACY on ipw2200: U ipw_debug_config RATE MASK: 0x00000FFF ipw2200: U ipw_send_cmd Sending SCAN_REQUEST_EXT command (#26), 96 bytes 00000000 BC 00 00 00 4B 01 02 03 04 05 06 07 08 09 0A 0B ....K... ........ 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 03 33 33 33 33 33 ........ ...33333 00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000050 00 00 00 00 00 00 00 00 14 00 00 00 14 00 14 00 ........ ........ ipw2200: I ipw_irq_tasklet Command completed. ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 1 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 2 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 3 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 4 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 5 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 6 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 7 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 8 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 9 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 10
Kent - With the storming disable patch, does the driver re-associate successfully with your AP without any problems? Thanks, James
Kent -- From your kernel log, we see these lines: 1103784219 ipw2200: U ipw_associate_network associating: 'NETGEAR' 00:09:5b:dc:ec:5e 1103784219 ipw2200: I ipw_rx_notification authenticated: 'NETGEAR' 00:09:5b:dc:ec:5e 1103784219 ipw2200: I ipw_rx_notification disassociated: 'NETGEAR' 00:09:5b:dc:ec:5e This occurs every time it tries to associate with network 'NETGEAR'. For several seconds following that, it won't attempt to associate w/ that AP (and will report the 'storming' message). The driver then tries (and succeeds) in associating with network 'taylor'. It appears that is a weak AP and frequent beacons being lost resulted in it going into roaming mode. What is the AP model for NETGEAR, and do you have any authentication mechanisms employed (MAC filter, 802.1x, WPA, etc.)?
I also happen to have the NETGEAR WGR614v2 with WEP set at OPEN and a 128bit key...haven't tried the patch though. Hopefully it will get fixed in 0.20.
Created an attachment (id=229) [details] Test patch to gather additional data Can you try the attached patch and gather debug info again at the 0x3fff level? It doesn't change the functionality of storming, but I am hoping it might provide more data that would allow us to better determine if storm protection needs to be enabled for a particular AP or not. Thanks, James
Attached is the new dmesg output with 0.21 and the latest patch for additional information. The following is repeated in an infinite loop. The # since last assoc attempt naturally increases. ipw2200: U ipw_send_cmd Sending SSID command (#8), 10 bytes 00000000 MY_AP_HEX ipw2200: I ipw_irq_tasklet Command completed. ipw2200: U ipw_send_cmd Sending SCAN_REQUEST_EXT command (#26), 96 bytes 00000000 59 03 00 00 4B 01 02 03 04 05 06 07 08 09 0A 0B Y...K... ........ 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 04 44 44 44 44 44 ........ ...DDDDD 00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000050 00 00 00 00 00 00 00 00 14 00 00 00 14 00 14 00 ........ ........ ipw2200: I ipw_irq_tasklet Command completed. ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 1 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 2 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 3 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 4 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 5 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 6 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 7 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 8 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 9 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 10 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 11 ipw2200: I ipw_rx_notification type = 13 (4 bytes) ipw2200: I ipw_rx_notification Scan completed: type 11, 11 channels, 1 status ipw2200: U ipw_best_network Network 'AP1' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP2' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP3' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP4' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'MY_AP' excluded because of storming (6923 since last assoc attempt). ipw2200: U ipw_best_network Network 'AP5' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP6' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP7' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP8' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP9' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP10' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP11' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP12' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_debug_config Scan completed, no valid APs matched [CFG 0x00000142] ipw2200: U ipw_debug_config Channel unlocked. ipw2200: U ipw_debug_config ESSID locked to 'MY_AP' ipw2200: U ipw_debug_config BSSID unlocked. ipw2200: U ipw_debug_config PRIVACY on ipw2200: U ipw_debug_config RATE MASK: 0x00000FFF ipw2200: U ipw_send_cmd Sending SCAN_REQUEST_EXT command (#26), 96 bytes 00000000 5A 03 00 00 4B 01 02 03 04 05 06 07 08 09 0A 0B Z...K... ........ 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 03 33 33 33 33 33 ........ ...33333 00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000050 00 00 00 00 00 00 00 00 14 00 00 00 14 00 14 00 ........ ........ ipw2200: I ipw_irq_tasklet Command completed. ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 1 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 2 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 3 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 4 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 5 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 6 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 7 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 8 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 9 ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 10 ipw2200: I ipw_rx_notification type = 25 (4 bytes) ipw2200: I ipw_rx_notification type = 12 (46 bytes) ipw2200: I ipw_rx_notification Scan result for channel 11 ipw2200: I ipw_rx_notification type = 13 (4 bytes) ipw2200: I ipw_rx_notification Scan completed: type 11, 11 channels, 1 status ipw2200: U ipw_best_network Network 'AP1' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP2' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP3' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP4' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'MY_AP' excluded because of storming (6924 since last assoc attempt). ipw2200: U ipw_best_network Network 'AP5' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP6' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP7' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP8' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP9' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP10' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP11' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_best_network Network 'AP12' excluded because of ESSID mismatch: 'MY_AP'. ipw2200: U ipw_debug_config Scan completed, no valid APs matched [CFG 0x00000142] ipw2200: U ipw_debug_config Channel unlocked. ipw2200: U ipw_debug_config ESSID locked to 'MY_AP' ipw2200: U ipw_debug_config BSSID unlocked. ipw2200: U ipw_debug_config PRIVACY on ipw2200: U ipw_debug_config RATE MASK: 0x00000FFF
I need the part of the debug log that captures the association attempt, not just the rescanning. The portion I want would be around something like this: ipw2200: U ipw_associate_network associating: 'MY_AP' 00:09:5b:dc:ec:5e ipw2200: I ipw_rx_notification authenticated: 'MY_AP' 00:09:5b:dc:ec:5e ipw2200: I ipw_rx_notification disassociated: 'MY_AP' 00:09:5b:dc:ec:5e only with one more line thrown in there from the patch that you applied that will (hopefully) give the reason for why the disassociation is occurring.
This was captured with metalog in /var/log/kernel/current and contains the moment it associated and then lost association and send anew a SCAN request. For some reason metalog does not hold as much information as dmesg (which fills up veery quickly and the connection loss disappears...is there some way to increase the dmesg history? I tried dmesg -sSIZE to no avail) does. For example the attempts with each AP are not logged, only the best one is mentioned. Jan 21 08:50:46 [kernel] ipw2200: U ipw_wx_set_essid Setting ESSID: 'AP' (10) Jan 21 08:50:46 [kernel] ipw2200: I ipw_irq_tasklet Command completed. Jan 21 08:50:46 [kernel] ipw2200: I ipw_rx_notification type = 10 (4 bytes) Jan 21 08:50:46 [kernel] ipw2200: I ipw_rx_notification type = 25 (4 bytes) Jan 21 08:50:46 [kernel] ipw2200: I ipw_rx_notification type = 12 (46 bytes) - Last output repeated twice - Jan 21 08:50:46 [kernel] ipw2200: U ipw_net_open dev->open Jan 21 08:50:46 [kernel] ipw2200: I ipw_rx_notification type = 12 (46 bytes) - Last output repeated 2 times - Jan 21 08:50:46 [kernel] ipw2200: I ipw_rx_notification type = 25 (4 bytes) Jan 21 08:50:46 [kernel] ipw2200: I ipw_rx_notification type = 12 (46 bytes) - Last output repeated 5 times - Jan 21 08:50:47 [kernel] ipw2200: I ipw_rx_notification type = 13 (4 bytes) Jan 21 08:50:47 [kernel] ipw2200: I ipw_irq_tasklet Command completed. - Last output repeated 6 times - Jan 21 08:50:47 [kernel] ipw2200: I ipw_rx_notification type = 11 (4 bytes) Jan 21 08:50:47 [kernel] ipw2200: I ipw_rx_notification type = 10 (59 bytes) Jan 21 08:50:47 [kernel] ipw2200: I ipw_rx_notification type = 25 (4 bytes) - Last output repeated 567 times - Jan 21 08:51:51 [kernel] ipw2200: I ipw_rx_notification type = 17 (8 bytes) - Last output repeated 7 times - Jan 21 08:51:52 [kernel] ipw2200: U ipw_best_network Netowrk 'SOME_AP' excluded because of non-network ESSID. Jan 21 08:51:52 [kernel] ipw2200: I ipw_rx_notification type = 17 (8 bytes) - Last output repeated 8 times - Jan 21 08:51:53 [kernel] ipw2200: I ipw_irq_tasklet Command completed. Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 17 (8 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 10 (4 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_irq_tasklet Command completed. - Last output repeated twice - Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 12 (46 bytes) - Last output repeated 4 times - Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 25 (4 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 12 (46 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 25 (4 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 12 (46 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 25 (4 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 12 (46 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 25 (4 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 12 (46 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 25 (4 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 12 (46 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 25 (4 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 12 (46 bytes) Jan 21 08:51:53 [kernel] ipw2200: I ipw_rx_notification type = 13 (4 bytes) Jan 21 08:51:53 [kernel] ipw2200: U ipw_send_cmd Sending SCAN_REQUEST_EXT command (#26), 96bytes Jan 21 08:51:53 [kernel] ipw2200: I ipw_irq_tasklet Command completed.
I'm not seeing any attachements or logs showing the associating/authenticated/disassociated sequence. Are you setting the debug level to 0x3fff? You can check the current debug level via the 'dvals' script in the source directory. Also, make sure you are running 0.21 + attachment 229 [details] (patch to gather additional data). I haven't used metalog, so I don't know how to configure it.
*** Bug 547 has been marked as a duplicate of this bug. ***
I have applied the patch, I am awaiting it to storm (I don't mean the major snow storms either) ;-)
I guess it's a jiffies rewind problem. Can you please test below patch?
Created an attachment (id=239) [details] use time_after for jiffies comparing
Patch applied, now waiting for it to storm. This should occur during normal use but it is not predictable.
The patch broke associating the AP: Jan 26 20:36:18 segfault kernel: ipw2200: U ipw_best_network Network '<hidden> (aa:bb:cc:dd:ee:ff)' excluded because of hidden ESSID. Jan 26 20:36:18 segfault kernel: ipw2200: U ipw_best_network Network 'hgnis (00:06:25:c4:cc:91)' excluded because of storming (4294785 since last assoc attempt). Jan 26 20:36:18 segfault kernel: ipw2200: U ipw_best_network Network 'SMC (00:04:e2:93:16:0a)' excluded because of storming (4294785 since last assoc attempt). Jan 26 20:36:18 segfault kernel: ipw2200: U ipw_debug_config Scan completed, no valid APs matched [CFG 0x00000140] Jan 26 20:36:19 segfault kernel: ipw2200: I ipw_rx_notification Scan completed: type 11, 11 channels, 1 status Jan 26 20:36:19 segfault kernel: ipw2200: U ipw_best_network Network '<hidden> (aa:bb:cc:dd:ee:ff)' excluded because of hidden ESSID. Jan 26 20:36:19 segfault kernel: ipw2200: U ipw_best_network Network 'hgnis (00:06:25:c4:cc:91)' excluded because of ESSID mismatch: 'sh0n.net'. Jan 26 20:36:19 segfault kernel: ipw2200: U ipw_best_network Network 'SMC (00:04:e2:93:16:0a)' excluded because of ESSID mismatch: 'sh0n.net'. Jan 26 20:36:19 segfault kernel: ipw2200: U ipw_best_network Network 'sh0n.net (aa:bb:cc:dd:ee:ff)' excluded because of storming (4294786 since last assoc attempt). Jan 26 20:36:19 segfault kernel: ipw2200: U ipw_debug_config Scan completed, no valid APs matched [CFG 0x00000142] Reverted back: if (network->last_associate + (HZ * 5) > jiffies) { /* if (time_after(network->last_associate + (HZ *5UL), jiffies)) { */
Created an attachment (id=241) [details] update version Fix a bug in the first patch, otherwise it won't be able to associate in the first 5 minutes. With this patch, we should not see "storming (x since last asso attempt)", where x is a number > 5. In the case x <= 5, we currently consider it as storming. But as James said, it is not always the case. We need to find out the reason why the card is disassociated from AP.
Applied.. now to wait for it to get into a storming situation.
Setting to NEEDSMOREDATA till patch is tested.
I have been using the 1.0.0 driver since it first came out and I had no disassociation "event" at all. This is the first truly stable driver for me ever since this problem surfaced with 0.14. As far as my hardware configuration is concerned, I definitely regard this bug as solved/closed. Thanks for all your work on this.
I too am seeing the storming bug, using version 1.0.1 of the ipw2200 driver. Attached are copies of my /var/log/messages file, showing 3 reboots, and 3 different situations Feb 26 10am BOOT (file: Feb26.messages.txt) : --- Feb 26 10:36:52 --- essid set to "GadgetHome" by boot scripts --- Feb 26 10:36:57 --- Boot scripts fail to find GadgetHome, revert to ANY --- Feb 26 10:38:22 --- I manually go in and try to start networking essid = GadgetHome --- Feb 26 10:43:59 --- shutdown -h now Connection never established Feb 27 noon (file: Feb27.messages.1.txt) --- Feb 27 12:12:15 --- essid set to "GadgetHome" by boot scripts --- Feb 27 12:12:16 --- Associated Feb 27 9 pm BOOT (file Feb27.messages.2.txt): --- Feb 27 21:08:41 --- essid set to "GadgetHome" by boot scripts --- Feb 27 21:08:42 --- first storming message --- Feb 27 21:09:01 --- finally manages to connect
oops, due to the size of the attachments, I couldn't put them here. But I uploaded them to http://www.kralevich.com/ipw2200/ Please see the three files in that correspond to the timeline above. Thanks.
Can you please disable WEP and see if it still exist? It would be also helpful to know the result of disabling the storming check w/ below test patch.
Created an attachment (id=274) [details] disable storming check
Please do not change the version field. This field allows us to keep track of which version the original bug was reported against.
Anybody tried the disable storming checking yet?
setting to needsmoredata till more info is provided.
I'm experiencing this problem at home (5-12 aviable APs), but not at work (Just one AP visible). I'm using the 1.0.4-driver. I'll attach a debug-dmesg when i get home.
Hi Carl-Christian, Do you still see this problem in 1.0.6? Can you provide a debug log at 0x43fff?
Sorry I didn't reply earlier. I'm using 1.0.6 now, and there is no more storming. I get an "ipw2200: Firmware error detected. Restarting." in the syslog once in a while, but I haven't noticed any connection drops. Works for me, you can close this bug.
This works fine in 1.0.6 for me.
Based on last 2 comments, marking as fixed. If other people on the cc list still see this in 1.0.6, please feel free to re-open.
I'm still experiencing this problem with the driver in Linus' git tree. Sometimes it has been successful to associate to my AP (WRT54G with WEP disabled), but usually it fails reporting the storming error. This is the output with debug=0xffff during the association: -------------------------------------------------------------------------- ipw2200: U ipw_best_network Network 'ratatuia (00:0f:66:51:c0:80)' is a viable match. ipw2200: U ipw_associate_network Assocation attempt: 'ratatuia', channel 4, 802.11g [12], long[:long], enc=off. ipw2200: U ipw_send_cmd SSID command (#8) 8 bytes: 0x00000023 00000000 72 61 74 61 74 75 69 61 ratatuia ipw2200: I ipw_irq_tasklet Command completed. ipw2200: U ipw_send_cmd SUPPORTED_RATES command (#22) 16 bytes: 0x00000023 00000000 02 0C 00 00 82 84 8B 96 24 30 48 6C 0C 12 18 60 ........ $0Hl...` ipw2200: I ipw_irq_tasklet Command completed. ipw2200: U ipw_send_cmd SYSTEM_CONFIG command (#6) 20 bytes: 0x00000023 00000000 01 00 00 00 01 00 01 00 01 00 00 01 00 00 00 00 ........ ........ 00000010 00 00 01 00 .... ipw2200: I ipw_irq_tasklet Command completed. ipw2200: U ipw_associate_network Association sensitivity: -46 ipw2200: U ipw_send_cmd SENSITIVITY_CALIB command (#42) 4 bytes: 0x00000023 00000000 42 00 00 00 B... ipw2200: I ipw_irq_tasklet Command completed. ipw2200: U ipw_send_cmd ASSOCIATE command (#21) 40 bytes: 0x00000123 00000000 04 00 00 00 00 00 00 02 00 0F 66 51 C0 80 00 00 ........ ..fQ.... 00000010 00 00 80 FD 18 3E 01 04 0A 00 64 00 00 0F 66 51 .....>.. ..d...fQ 00000020 C0 80 00 00 00 00 00 00 ........ ipw2200: I ipw_irq_tasklet Command completed. ipw2200: U ipw_associate_network associating: 'ratatuia' 00:0f:66:51:c0:80 ipw2200: I ipw_rx_notification type = 11 (4 bytes) ipw2200: I ipw_rx_notification AUTH_SEQ_1_FAIL ipw2200: I ipw_rx_notification type = 10 (4 bytes) ipw2200: I ipw_rx_notification disassociated: 'ratatuia' 00:0f:66:51:c0:80 ipw2200: U ipw_send_cmd SCAN_REQUEST_EXT command (#26) 96 bytes: 0x00000023 00000000 03 02 00 00 4B 01 02 03 04 05 06 07 08 09 0A 0B ....K... ........ 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 03 33 33 33 33 33 ........ ...33333 00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000050 00 00 00 00 00 00 00 00 78 00 00 00 14 00 14 00 ........ x....... ipw2200: I ipw_irq_tasklet Command completed. -------------------------------------------------------------------------- Subsequent tries give this storming error: -------------------------------------------------------------------------- ipw2200: U ipw_best_network Network 'ratatuia (00:0f:66:51:c0:80)' excluded because of storming (0s since last assoc attempt). ipw2200: U ipw_debug_config Scan completed, no valid APs matched [CFG 0x00000340] ipw2200: U ipw_debug_config Channel unlocked. ipw2200: U ipw_debug_config ESSID unlocked. ipw2200: U ipw_debug_config BSSID unlocked. ipw2200: U ipw_debug_config PRIVACY off ipw2200: U ipw_debug_config RATE MASK: 0x00000FFF ipw2200: U ipw_send_cmd SCAN_REQUEST_EXT command (#26) 96 bytes: 0x00000023 00000000 04 02 00 00 4B 01 02 03 04 05 06 07 08 09 0A 0B ....K... ........ 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000030 00 00 00 00 00 00 00 00 00 00 03 33 33 33 33 33 ........ ...33333 00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........ 00000050 00 00 00 00 00 00 00 00 78 00 00 00 14 00 14 00 ........ x....... ipw2200: I ipw_irq_tasklet Command completed. -------------------------------------------------------------------------- This is the portion making the association fails: ipw2200: I ipw_rx_notification type = 11 (4 bytes) ipw2200: I ipw_rx_notification AUTH_SEQ_1_FAIL ipw2200: I ipw_rx_notification type = 10 (4 bytes) If it is useful I have an Acer TM380 with an IPW2200 (rev 05) with pci id 0000:02:01.0 (as reported by lspci). I have not yet tested the disabled storming check patch.
With the storming check disabled it just keeps on failing to associate with the same AUTH_SEQ_1_FAIL error.
(In reply to comment #38) > With the storming check disabled it just keeps on failing to associate with the > same AUTH_SEQ_1_FAIL error. Take a look at bug 765 and 763.
Could you check bug#763 and bug#765? Mark it as NEED_MORE_DATA
In bug #763 the driver can associate and then the bitrate drops to 0kb/s, while my card cannot associate at all. Bug #765 has been resolved upgrading the wrt firmware, but upgrading my AP to the last version of the firmware (OpenWRT White Russian rc4) doesn't do any good... Maybe I can test with another firmware for the router. I can also recompile a instrumented kernel driver, if someone will assist me to instrument it... :)
Even with the official firmware 4.20.8 it gives the same error, so I've reverted to the openwrt one.
Please try other APs to make sure it's not an AP related problem.
Will try. But the AP is happily working with other wireless card (I use a prism54 PCMCIA card), so it should work...
set this bug to resolved, feel free to reopen if you can still find it.
I'm currently having this problem with v1.1.2 and a Motorola WR850G AP, running Openwrt Whiterussian RC5. My other wireless network cards (Orinoco, Prism 2 and on Linksys), all 802.11b only, doesn't stop working when this happens. Interesting to notice that I get the excluded by storming message during reassociation attempt, with values > 1000ms. The problem will happen more often during heavy load. Some interesting sections of the log: ipw2200: I ipw_rx_notification Scan completed: type 11, 11 channels, 1 status ipw2200: U ipw_best_network Network '<hidden> (00:0c:e5:4a:21:6f)' excluded because of hidden ESSID. ipw2200: U ipw_best_network Network 'MY_AP (00:0c:e5:4a:21:6f)' excluded because of storming (1210ms since last assoc attempt). ipw2200: U ipw_debug_config Scan completed, no valid APs matched [CFG 0x000000C3] ipw2200: U ipw_associate_network associating: 'MY_AP' 00:0c:e5:4a:21:6f ipw2200: I ipw_rx_notification type = 11 (4 bytes) ipw2200: I ipw_rx_notification AUTH_SEQ_1 ipw2200: I ipw_rx_notification type = 10 (4 bytes) ipw2200: I ipw_rx_notification disassociated: 'MY_AP' 00:0c:e5:4a:21:6f Only my notebook (ipw2200) is affected when this problem happens. I can't be 100% sure this is not a problem on the AP, of course, but it doesn't look like. Now, the really interesting message (for me) is: ipw2200: I ipw_rx_notification authentication failed (0x4A21): Unknown status value. ipw2200: I ipw_rx_notification deauthenticated: 'MY_AP' 00:0c:e5:4a:21:6f A little bellow, I'll get: ipw2200: U ipw_associate_network Reassocation attempt: 'MY_AP', channel 6, 802.11g [4], long[:long], enc=off. ipw2200: U __ipw_send_cmd SSID command (#8) 14 bytes: 0x00100423 and a little bellow that, I get the Associating -> AUTH_SEQ_1 -> Disassociating.
Submited to the wrong bug entry. Sorry.
Verify this bug according to comment #44. It is more than six months when the comment #44, if anyone still finds this problem, please reopen.
I've finally resolved my problem. Even if I thought I had checked, my access point didn't have my mac address in the whitelist thus refusing any association returning AUTH_SEQ_1_FAIL. I'm sorry for the noise. %-) Still, the message about "storming" confused me: could be made more clear when the access point refuses the association, instead of blaming it of "storming"? Thank you all.