Re: wlan/wpi are more broken than 3 weeks.
On Saturday 01 January 2011 19:47:21 you wrote: On Mon, Dec 27, 2010 at 02:05:25AM +0100, Bernhard Schmidt wrote: On Monday 27 December 2010 01:32:56 Steve Kargl wrote: On Sun, Dec 26, 2010 at 11:25:05PM +0100, Bernhard Schmidt wrote: [ .. ] If you can get debug output while the UPs/DOWNs happen, that would help a lot. Sorry about the delay. The laptop has been in Windows land for the last week. I finally have a log where the interface is going UP/DOWN and have wlandebug in effect. It's 220KB. You can find it at Thanks http://troutmask.apl.washington.edu/~kargl/wlan0.msg wlan0: AMRR decreasing rate 48 (txcnt=35 retrycnt=14) wlan0: recv deauthenticate (reason 2) wlan0: ieee80211_new_state_locked: RUN - AUTH (nrunning 0 nscanning 0) I've seen those before, though, I never figured out if there is a way to bypass that. What's happening here is that the AP detects that you've ben idle (as in not sending frames) for quite a while (the rate decrease does indicate that) and kicks you with a 'auth no longer valid' message. This seems to be a 'feature' of your AP and not an issue with the driver, at least I do not see any connection. As a workaround try to ping something behind the AP. -- Bernhard ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wlan/wpi are more broken than 3 weeks.
On Mon, Dec 27, 2010 at 02:05:25AM +0100, Bernhard Schmidt wrote: On Monday 27 December 2010 01:32:56 Steve Kargl wrote: On Sun, Dec 26, 2010 at 11:25:05PM +0100, Bernhard Schmidt wrote: How about providing the info I asked for last time? Now that you have build the necessary options into the kernel you should be able to run with wlandebug 0x enabled. Perhaps, I got busy with real life work, and perhaps, I forgot you asked for this info. In the end, /var/log/messages get stuff full of Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 37 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 38 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 34 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 38 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 38 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 41 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 32 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 34 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 41 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 41 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 37 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 32 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 35 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 because apparently this message isn't rate limited. So, perhaps, this is the problem? I don't think so, those messages are usually an indicator for a successful connection. AP sends those as a 'hello, i'm still here' kinda thing. You should be able to supress those with 'wlandebug 0x -dumppkts'. If you can get debug output while the UPs/DOWNs happen, that would help a lot. Sorry about the delay. The laptop has been in Windows land for the last week. I finally have a log where the interface is going UP/DOWN and have wlandebug in effect. It's 220KB. You can find it at http://troutmask.apl.washington.edu/~kargl/wlan0.msg -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
wlan/wpi are more broken than 3 weeks.
First reported here, http://lists.freebsd.org/pipermail/freebsd-current/2010-December/021664.html I now see a never ending spew in /var/log/messages of laptop:kargl[232] tail /var/log/messages Dec 26 07:41:12 laptop kernel: wlan0: link state changed to DOWN Dec 26 07:41:12 laptop kernel: wlan0: link state changed to UP Dec 26 07:45:42 laptop kernel: wlan0: link state changed to DOWN Dec 26 07:45:42 laptop kernel: wlan0: link state changed to UP Dec 26 07:49:42 laptop kernel: wlan0: link state changed to DOWN Dec 26 07:49:42 laptop kernel: wlan0: link state changed to UP Dec 26 07:54:12 laptop kernel: wlan0: link state changed to DOWN Dec 26 07:54:12 laptop kernel: wlan0: link state changed to UP Dec 26 07:58:27 laptop kernel: wlan0: link state changed to DOWN Dec 26 07:58:27 laptop kernel: wlan0: link state changed to UP So, the good news appears to be that 3 weeks ago wlan/wpi could stay up for 7 to 9 minutes before cycling DOWN/UP. While the bad news is that today, the DOWN/UP cycle last for 4 to 5 minutes. -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wlan/wpi are more broken than 3 weeks.
On 26/12/10 02:55 PM, Steve Kargl wrote: First reported here, http://lists.freebsd.org/pipermail/freebsd-current/2010-December/021664.html I now see a never ending spew in /var/log/messages of laptop:kargl[232] tail /var/log/messages Dec 26 07:41:12 laptop kernel: wlan0: link state changed to DOWN Dec 26 07:41:12 laptop kernel: wlan0: link state changed to UP Dec 26 07:45:42 laptop kernel: wlan0: link state changed to DOWN Dec 26 07:45:42 laptop kernel: wlan0: link state changed to UP Dec 26 07:49:42 laptop kernel: wlan0: link state changed to DOWN Dec 26 07:49:42 laptop kernel: wlan0: link state changed to UP Dec 26 07:54:12 laptop kernel: wlan0: link state changed to DOWN Dec 26 07:54:12 laptop kernel: wlan0: link state changed to UP Dec 26 07:58:27 laptop kernel: wlan0: link state changed to DOWN Dec 26 07:58:27 laptop kernel: wlan0: link state changed to UP So, the good news appears to be that 3 weeks ago wlan/wpi could stay up for 7 to 9 minutes before cycling DOWN/UP. While the bad news is that today, the DOWN/UP cycle last for 4 to 5 minutes. have you compiled with IEEE_DEBUG ? I would also like knowing which wireless NIC you're using. Is this bug related to a USB wireless card ? I have similar issues (recurring) on Freebsd 8.1. my current understanding is that USB wireless on FreeSD is somewhat a itchy business.. Regards -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer E-mail: e...@gthcfoundation.org Work phone: +1 514-962-7703 Website (Company): https://www.gthc.org/ Website (Blog): https://www.gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wlan/wpi are more broken than 3 weeks.
On Sun, Dec 26, 2010 at 04:43:48PM -0500, Etienne Robillard wrote: On 26/12/10 02:55 PM, Steve Kargl wrote: First reported here, http://lists.freebsd.org/pipermail/freebsd-current/2010-December/021664.html I now see a never ending spew in /var/log/messages of laptop:kargl[232] tail /var/log/messages Dec 26 07:58:27 laptop kernel: wlan0: link state changed to DOWN Dec 26 07:58:27 laptop kernel: wlan0: link state changed to UP So, the good news appears to be that 3 weeks ago wlan/wpi could stay up for 7 to 9 minutes before cycling DOWN/UP. While the bad news is that today, the DOWN/UP cycle last for 4 to 5 minutes. have you compiled with IEEE_DEBUG ? Yes. I would also like knowing which wireless NIC you're using. Is this bug related to a USB wireless card ? I have similar issues (recurring) on Freebsd 8.1. my current understanding is that USB wireless on FreeSD is somewhat a itchy business.. It's a nic builtin into a Dell D530 laptop. laptop:kargl[202] dmesg | grep wpi wpi0: Intel(R) PRO/Wireless 3945ABG mem 0xfe8ff000-0xfe8f irqi 17 at device 0.0 on pci12 I just backed out revision 214894 to test whether this is the problematic commit. http://svn.freebsd.org/viewvc/base/head/sys/dev/wpi/if_wpi.c?view=log -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wlan/wpi are more broken than 3 weeks.
On Sunday 26 December 2010 22:39:58 Steve Kargl wrote: On Sun, Dec 26, 2010 at 04:43:48PM -0500, Etienne Robillard wrote: On 26/12/10 02:55 PM, Steve Kargl wrote: First reported here, http://lists.freebsd.org/pipermail/freebsd-current/2010-December/021664 .html I now see a never ending spew in /var/log/messages of laptop:kargl[232] tail /var/log/messages Dec 26 07:58:27 laptop kernel: wlan0: link state changed to DOWN Dec 26 07:58:27 laptop kernel: wlan0: link state changed to UP So, the good news appears to be that 3 weeks ago wlan/wpi could stay up for 7 to 9 minutes before cycling DOWN/UP. While the bad news is that today, the DOWN/UP cycle last for 4 to 5 minutes. have you compiled with IEEE_DEBUG ? Yes. How about providing the info I asked for last time? Now that you have build the necessary options into the kernel you should be able to run with wlandebug 0x enabled. I would also like knowing which wireless NIC you're using. Is this bug related to a USB wireless card ? I have similar issues (recurring) on Freebsd 8.1. my current understanding is that USB wireless on FreeSD is somewhat a itchy business.. It's a nic builtin into a Dell D530 laptop. laptop:kargl[202] dmesg | grep wpi wpi0: Intel(R) PRO/Wireless 3945ABG mem 0xfe8ff000-0xfe8f irqi 17 at device 0.0 on pci12 I just backed out revision 214894 to test whether this is the problematic commit. http://svn.freebsd.org/viewvc/base/head/sys/dev/wpi/if_wpi.c?view=log -- Bernhard ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wlan/wpi are more broken than 3 weeks.
On Sun, Dec 26, 2010 at 11:25:05PM +0100, Bernhard Schmidt wrote: How about providing the info I asked for last time? Now that you have build the necessary options into the kernel you should be able to run with wlandebug 0x enabled. Perhaps, I got busy with real life work, and perhaps, I forgot you asked for this info. In the end, /var/log/messages get stuff full of Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 37 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 38 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 34 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 38 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 38 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 41 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 32 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 34 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 41 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 41 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 37 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 32 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 35 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 because apparently this message isn't rate limited. So, perhaps, this is the problem? -- Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: wlan/wpi are more broken than 3 weeks.
On Monday 27 December 2010 01:32:56 Steve Kargl wrote: On Sun, Dec 26, 2010 at 11:25:05PM +0100, Bernhard Schmidt wrote: How about providing the info I asked for last time? Now that you have build the necessary options into the kernel you should be able to run with wlandebug 0x enabled. Perhaps, I got busy with real life work, and perhaps, I forgot you asked for this info. In the end, /var/log/messages get stuff full of Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 37 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 38 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 34 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 38 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 38 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 41 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:04 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 32 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 34 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 41 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 41 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 37 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 32 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 35 Dec 26 16:30:05 laptop kernel: wlan0: received beacon from 00:18:e7:d4:f2:1b rssi 40 because apparently this message isn't rate limited. So, perhaps, this is the problem? I don't think so, those messages are usually an indicator for a successful connection. AP sends those as a 'hello, i'm still here' kinda thing. You should be able to supress those with 'wlandebug 0x -dumppkts'. If you can get debug output while the UPs/DOWNs happen, that would help a lot. -- Bernhard ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
