From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 13:35:18 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8FA8516A46B for ; Fri, 16 Feb 2007 13:35:18 +0000 (UTC) (envelope-from ilja@lynx.ee) Received: from mail.lynx.ee (mail.lynx.ee [212.7.7.23]) by mx1.freebsd.org (Postfix) with ESMTP id D974313C4AA for ; Fri, 16 Feb 2007 13:35:17 +0000 (UTC) (envelope-from ilja@lynx.ee) Received: from localhost (unknown [127.0.0.1]) by mail.lynx.ee (Postfix) with ESMTP id 7324DB940; Fri, 16 Feb 2007 15:33:14 +0200 (EET) X-Virus-Scanned: amavisd-new at lynx.ee Received: from mail.lynx.ee ([127.0.0.1]) by localhost (pinkfloyd.lynx.ee [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhYXWhzxLmyv; Fri, 16 Feb 2007 15:33:05 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by mail.lynx.ee (Postfix) with ESMTP id 9F887B92B; Fri, 16 Feb 2007 15:33:05 +0200 (EET) Received: from 84-50-157-3-dsl.est.estpak.ee (84-50-157-3-dsl.est.estpak.ee [84.50.157.3]) by secure.lynx.ee (Horde MIME library) with HTTP; Fri, 16 Feb 2007 15:33:05 +0200 Message-ID: <20070216153305.xhr6va74g8gkogsw@secure.lynx.ee> Date: Fri, 16 Feb 2007 15:33:05 +0200 From: Ilja Morozov To: Luigi Rizzo References: <20070215143551.A94883@xorpc.icir.org> <20070216031518.A4090@xorpc.icir.org> In-Reply-To: <20070216031518.A4090@xorpc.icir.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.2) Cc: freebsd-net@freebsd.org Subject: Re: iwi leaks memory? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2007 13:35:18 -0000 as I mentioned before - I had the same problem in place with very poor =20 wifi signal. and I did also some apm suspends using "zzz" . Can =20 suspend affect it ? unfortunately I didn't make any statistics dumps or similar, because =20 was very busy and just restarted box. IBM T42 FreeBSD wind.kalakala 6.2-STABLE FreeBSD 6.2-STABLE #33: Sat Feb 10 =20 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 =20 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 : > On Fri, Feb 16, 2007 at 08:41:09AM +0200, V.Chukharev wrote: >> On Fri, 16 Feb 2007 00:35:51 +0200, Luigi Rizzo 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 =20 >> 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) ? > > =09cheers > =09luigi > >> > =09cheers >> > =09luigi >> > >> > 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 =20 >> cycles of switching down/up. >> >> In a place with a bad wireless connection I needed to do that =20 >> quite a number of times >> >> (that was the simplest way to restore connectivity I knew), and =20 >> after 5-10 cycles I needed >> >> to reboot my notebook totally. >> >> >> >> Can anybody with iwi () confirm =20 >> (or better unconfirm) >> >> that doing >> >> >> >> for ii in `jot 100`; do sudo ifconfig iwi0 down; sleep 2; =20 >> 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 memo= ry >> >> >> >> A fix for this would be even better ;)) >> >> >> >> Thanks, >> >> -- >> >> V. Chukharev >> >> _______________________________________________ >> >> freebsd-net@freebsd.org mailing list >> >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > >> --=20 Best regards, Ilja Morozov