From owner-freebsd-net@FreeBSD.ORG  Fri Feb 16 21:10:27 2007
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 D124616A407;
	Fri, 16 Feb 2007 21:10:27 +0000 (UTC)
	(envelope-from chukharev@mail.ru)
Received: from mx2.mail.ru (mx2-2.mail.ru [194.67.23.122])
	by mx1.freebsd.org (Postfix) with ESMTP id 8BD8813C461;
	Fri, 16 Feb 2007 21:10:27 +0000 (UTC)
	(envelope-from chukharev@mail.ru)
Received: from [85.156.232.99] (port=61667 helo=localhost)
	by mx2.mail.ru with asmtp 
	id 1HIALa-0003wT-00; Sat, 17 Feb 2007 00:10:26 +0300
Date: Fri, 16 Feb 2007 23:10:24 +0200
To: "Jeremie Le Hen" <jeremie@le-hen.org>
From: "V.Chukharev" <chukharev@mail.ru>
Content-Type: text/plain; charset=utf-8
MIME-Version: 1.0
References: <op.tns7i21z0g54sc@localhost>
	<20070216174317.GZ64768@obiwan.tataz.chchile.org>
Content-Transfer-Encoding: 7bit
Message-ID: <op.tnu03mar0g54sc@localhost>
In-Reply-To: <20070216174317.GZ64768@obiwan.tataz.chchile.org>
User-Agent: Opera Mail/9.10 (FreeBSD)
Cc: freebsd-net@freebsd.org, cognet@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 <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Feb 2007 21:10:27 -0000

On Fri, 16 Feb 2007 19:43:17 +0200, Jeremie Le Hen <jeremie@le-hen.org> wrote:

> Hi,
>
> cognet@ has once provided me a tiny hack to the iwi(4) driver and
> I never get such errors.  Maybe I'm not suffering enough UP/DOWN
> cycles to trigger it, but it might be worth trying it.
>
> Note that he has insisted that this is a *hack*.
>
> The patch is attached.  Please let us know if it makes things
> better.

I cannot apply the patch ;-(
It seems it's for CURRENT, and I run STABLE.

> Regards,

All the best,
-- 
V. Chukharev