From owner-freebsd-net@FreeBSD.ORG Fri Feb 16 13:35:17 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 AA78F16A468 for ; Fri, 16 Feb 2007 13:35:17 +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 6387313C47E 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 641ECB90C; Fri, 16 Feb 2007 15:13:47 +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 A0WldJ8xCenI; Fri, 16 Feb 2007 15:13:40 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by mail.lynx.ee (Postfix) with ESMTP id 93061B907; Fri, 16 Feb 2007 15:13:40 +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:13:40 +0200 Message-ID: <20070216151340.sihitp1o8wwc8404@secure.lynx.ee> Date: Fri, 16 Feb 2007 15:13:40 +0200 From: Ilja Morozov To: Luigi Rizzo References: <20070215143551.A94883@xorpc.icir.org> In-Reply-To: <20070215143551.A94883@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:17 -0000 Hi guys, today I had the same problems. src/sys/dev/iwi/if_iwi.c,v 1.8.2.12 2007/01/23 22:17:48 Quoting Luigi Rizzo : > will have a look at this. > Which version of if_iwi.c are you using ? > > =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 cycles =20 >> of switching down/up. >> In a place with a bad wireless connection I needed to do that quite =20 >> 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 (or =20 >> better unconfirm) >> that doing >> >> for ii in `jot 100`; do sudo ifconfig iwi0 down; sleep 2; sudo =20 >> 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@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ > 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 mailto:ilja@lynx.ee Lynx Computers O"U + 372 6313 000