From owner-freebsd-net@FreeBSD.ORG Tue Dec 23 11:58:00 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D06B106564A for ; Tue, 23 Dec 2008 11:58:00 +0000 (UTC) (envelope-from vlad@prokk.net) Received: from smtp.prokk.net (smtp.prokk.net [195.16.77.5]) by mx1.freebsd.org (Postfix) with ESMTP id 693538FC18 for ; Tue, 23 Dec 2008 11:57:55 +0000 (UTC) (envelope-from vlad@prokk.net) Received: from base (base.prokk.net [195.16.77.7]) by smtp.prokk.net (8.13.8/8.13.8) with ESMTP id mBNBvipI060768; Tue, 23 Dec 2008 13:57:49 +0200 (EET) (envelope-from vlad@prokk.net) From: "Vladimir V. Kobal" To: References: <004a01c961ec$ec136540$c43a2fc0$@net> <7ik59sgrgd.wl%gnn@neville-neil.com> In-Reply-To: <7ik59sgrgd.wl%gnn@neville-neil.com> Date: Tue, 23 Dec 2008 13:57:39 +0200 Organization: ProKK SE Message-ID: <000201c964f5$aa94e6a0$ffbeb3e0$@net> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AclkSe0Z5XzXd3ooQeemvJdYz0CefgAqruqA Content-Language: uk X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (smtp.prokk.net [195.16.77.5]); Tue, 23 Dec 2008 13:57:49 +0200 (EET) Cc: freebsd-net@freebsd.org Subject: RE: Panic on boot with em1 attached 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: Tue, 23 Dec 2008 11:58:00 -0000 With fastforwarding off the system works well and boots without panicing. As for the rtfree messages, they were caused by net.link.ether.inet.proxyall=1 and were not connected to panicing. Best regards, Vladimir -----Original Message----- From: gnn@freebsd.org [mailto:gnn@freebsd.org] Sent: Monday, December 22, 2008 5:28 PM To: Vladimir V. Kobal Cc: freebsd-net@freebsd.org Subject: Re: Panic on boot with em1 attached Hi, Can you try this with fastforwarding off? It looks like a double free somewhere in the ip_fastforward() routine. Someone frees m but does not NULL it out and at the drop: label the mbuf m is valid but the data within it has already been freed. Knowing if this is related only to the fast forwarding case will help. Best, George