Date: Tue, 23 Dec 2008 13:57:39 +0200 From: "Vladimir V. Kobal" <vlad@prokk.net> To: <gnn@freebsd.org> Cc: freebsd-net@freebsd.org Subject: RE: Panic on boot with em1 attached Message-ID: <000201c964f5$aa94e6a0$ffbeb3e0$@net> In-Reply-To: <7ik59sgrgd.wl%gnn@neville-neil.com> References: <004a01c961ec$ec136540$c43a2fc0$@net> <7ik59sgrgd.wl%gnn@neville-neil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000201c964f5$aa94e6a0$ffbeb3e0$>