From owner-freebsd-bugs@FreeBSD.ORG Sat Apr 24 08:44:16 2010 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F5AE106566C for ; Sat, 24 Apr 2010 08:44:16 +0000 (UTC) (envelope-from littlesavage@orionet.ru) Received: from mail.orionet.ru (mail.orionet.ru [94.232.59.36]) by mx1.freebsd.org (Postfix) with ESMTP id 3ED648FC13 for ; Sat, 24 Apr 2010 08:44:15 +0000 (UTC) Received: from mail.orionet.ru (localhost [127.0.0.2]) by mail.orionet.ru (Postfix) with ESMTP id 654421E46E4; Sat, 24 Apr 2010 12:25:08 +0400 (MSD) Received: by mail.orionet.ru (Postfix, from userid 58) id 61C8E1E43BB; Sat, 24 Apr 2010 12:25:08 +0400 (MSD) X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on mail.orionet.ru X-Spam-Level: X-Spam-Status: No, score=-1.0 required=8.0 tests=ALL_TRUSTED autolearn=disabled version=3.3.0 Received: from ls.orionet.ru (unknown [94.232.59.106]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: littlesavage@orionet.ru) by mail.orionet.ru (Postfix) with ESMTPSA id 2F7091E4393; Sat, 24 Apr 2010 12:25:06 +0400 (MSD) Message-ID: <4BD2AA88.1010204@orionet.ru> Date: Sat, 24 Apr 2010 12:23:36 +0400 From: Alexey Illarionov User-Agent: Thunderbird 2.0.0.23 (X11/20091030) MIME-Version: 1.0 To: freebsd-bugs@FreeBSD.org References: <201004211300.o3LD0x44038439@freefall.freebsd.org> In-Reply-To: <201004211300.o3LD0x44038439@freefall.freebsd.org> Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: jh@FreeBSD.org Subject: Re: kern/145865: [kernel] [panic] kernel memory leak with disabled devd and hw.bus.devctl_disable=1 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Apr 2010 08:44:16 -0000 Hi jh@FreeBSD.org wrote: > Probably fixed in r206916. Can you confirm? Patch from r206916 has fixed this bug Thanks!