Date: Sat, 12 Jan 2013 08:10:01 GMT From: Mark Linimon <linimon@lonesome.com> To: freebsd-ipfw@FreeBSD.org Subject: Re: kern/174749: Unexpected change of default route Message-ID: <201301120810.r0C8A1qH004307@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/174749; it has been noted by GNATS. From: Mark Linimon <linimon@lonesome.com> To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/174749: Unexpected change of default route Date: Sat, 12 Jan 2013 02:01:07 -0600 ----- Forwarded message from Vadim Urazaev <demiurg@tica.com.ua> ----- Date: Fri, 11 Jan 2013 07:46:05 +0200 From: Vadim Urazaev <demiurg@tica.com.ua> To: Radek Krejča <radek.krejca@starnet.cz> Cc: freebsd-ipfw@freebsd.org, freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: RE: kern/174749: Unexpected change of default route Do some body know how can we debug kernel memory corruption on live system? We need to find out which function/subsystem is cause of this mess. Or maybe is there some way to lock particular memory area, where default gateway lies and watch which subsystem will cause system crash? ----- End forwarded message -----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201301120810.r0C8A1qH004307>