On Thu, 15 Feb 2007, at 23:34, V.Chukharev wrote: > Hi, > > It seems that iwi driver cannot survive more than just a few cycles of > switching down/up. > In a place with a bad wireless connection I needed to do that quite a number > of times > (that was the simplest way to restore connectivity I knew), and after 5-10 > cycles I needed > to reboot my notebook totally. > > Can anybody with iwi (<Intel(R) PRO/Wireless 2200BG>) confirm (or better > unconfirm) > that doing > > for ii in `jot 100`; do sudo ifconfig iwi0 down; sleep 2; sudo ifconfig > iwi0 up; done > > always results in the following messages (and lost connectivity): > > Feb 15 09:43:59 chu kernel: iwi0: link state changed to DOWN > Feb 15 09:44:13 chu kernel: iwi0: link state changed to UP > Feb 15 09:44:13 chu kernel: iwi0: link state changed to DOWN > Feb 15 09:44:18 chu kernel: iwi0: device timeout > Feb 15 09:44:20 chu kernel: iwi0: could not allocate firmware DMA memory
+1 - link goes down whatever the AP is after some time. ifconfig down & up works until the point i get the DMA error. While insisting i can sometimes get back connectivity (while ifconfig iwi0 | grep "no carrier"; do ifconfig iwi0 up; sleep 10; done) but after a few steps of that dance i'm left with rebooting or finding a plug. this on a T42, tracking more or less regularly -current. As far as i remember, i've "always" had this problem with this laptop / intel chip (2200BG) _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
