iwi leaks memory?

[Ilja Morozov]

as I mentioned before - I had the same problem in place with very poor  
wifi signal. and I did also some apm suspends using "zzz" . Can  
suspend affect it ?
unfortunately I didn't make any statistics dumps or similar, because  
was very busy and just restarted box. IBM T42

FreeBSD wind.kalakala 6.2-STABLE FreeBSD 6.2-STABLE #33: Sat Feb 10  
17:38:43 EET 2007

logs related to the problem:

Feb 16 11:55:22 wind kernel: iwi0: link state changed to UP
Feb 16 11:55:30 wind dhclient: New IP Address (iwi0): 192.168.1.101
Feb 16 11:55:30 wind dhclient: New Subnet Mask (iwi0): 255.255.255.0
Feb 16 11:55:30 wind dhclient: New Broadcast Address (iwi0): 192.168.1.255
Feb 16 11:55:30 wind dhclient: New Routers (iwi0): 192.168.1.1
Feb 16 12:01:50 wind kernel: iwi0: link state changed to DOWN
Feb 16 12:01:52 wind kernel: iwi0: link state changed to UP
Feb 16 12:01:52 wind dhclient: New IP Address (iwi0): 192.168.1.101
Feb 16 12:01:52 wind dhclient: New Subnet Mask (iwi0): 255.255.255.0
Feb 16 12:01:52 wind dhclient: New Broadcast Address (iwi0): 192.168.1.255
Feb 16 12:01:52 wind dhclient: New Routers (iwi0): 192.168.1.1
Feb 16 12:06:11 wind kernel: iwi0: link state changed to DOWN
Feb 16 12:06:16 wind kernel: iwi0: device timeout
Feb 16 12:06:16 wind kernel: iwi0: could not allocate firmware DMA memory
Feb 16 12:18:39 wind su: ilja to root on /dev/ttyp1
Feb 16 12:18:56 wind kernel: iwi0: could not allocate firmware DMA memory
Feb 16 12:19:27 wind last message repeated 2 times
Feb 16 12:19:27 wind kernel: firmware_get: failed to load firmware  
image iwi_bss
Feb 16 12:19:27 wind kernel: iwi0: could not load firmware
Feb 16 12:19:27 wind dhclient[37467]: iwi0: not found
Feb 16 12:19:27 wind dhclient[37467]: exiting.
Feb 16 12:19:27 wind dhclient[37468]: connection closed
Feb 16 12:19:27 wind dhclient[37468]: exiting.



Quoting Luigi Rizzo <rizzo at icir.org>:

> On Fri, Feb 16, 2007 at 08:41:09AM +0200, V.Chukharev wrote:
>> On Fri, 16 Feb 2007 00:35:51 +0200, Luigi Rizzo <rizzo at icir.org> wrote:
>>
>> > will have a look at this.
>> > Which version of if_iwi.c are you using ?
>>
>> Thanks.
>> $ grep -i __FBSDID /usr/src/sys/dev/iwi/if_iwi.c
>> __FBSDID("$FreeBSD: src/sys/dev/iwi/if_iwi.c,v 1.8.2.12 2007/01/23   
>> 22:17:48 jhb Exp $");
>>
>> It's STABLE, updated couple of days ago.
>
> ok i tried your script to do ifconfig up and down
> and it does not give me the problem you see (at least not until 100).
> Do you see the error always at the same point ? Any other things
> e.g. how is the iwi_bss loaded (manually, from /boot/loader or
> automatically) ?
>
> 	cheers
> 	luigi
>
>> > 	cheers
>> > 	luigi
>> >
>> > On Thu, Feb 15, 2007 at 11:34:48PM +0200, 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
>> >>
>> >> A fix for this would be even better ;))
>> >>
>> >> Thanks,
>> >> --
>> >> V. Chukharev
>> >> _______________________________________________
>> >> freebsd-net at freebsd.org mailing list
>> >> http://lists.freebsd.org/mailman/listinfo/freebsd-net
>> >> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>> >
>>


-- 
Best regards,
  Ilja Morozov