Date: Sun, 29 Nov 2009 14:29:37 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: =?ISO-8859-15?Q?Eirik_=D8verby?= <ltning@anduin.net> Cc: pyunyh@gmail.com, weldon@excelsusphoto.com, freebsd-current@freebsd.org, Gavin Atkinson <gavin@freebsd.org> Subject: Re: FreeBSD 8.0 - network stack crashes? Message-ID: <alpine.BSF.2.00.0911291427240.80654@fledge.watson.org> In-Reply-To: <74BFE523-4BB3-4748-98BA-71FBD9829CD5@anduin.net> References: <A1648B95-F36D-459D-BBC4-FFCA63FC1E4C@anduin.net> <20091129013026.GA1355@michelle.cdnetworks.com> <74BFE523-4BB3-4748-98BA-71FBD9829CD5@anduin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --621616949-1483411841-1259504977=:80654 Content-Type: TEXT/PLAIN; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT On Sun, 29 Nov 2009, Eirik Øverby wrote: > I just did that (-rxcsum -txcsum -tso), but the numbers still keep rising. > I'll wait and see if it goes down again, then reboot with those values to > see how it behaves. But right away it doesn't look too good .. It would be interesting to know if any of the counters in the output of netstat -s grow linearly with the allocation count in netstat -m. Often times leaks are associated with edge cases in the stack (typically because if they are in common cases the bug is detected really quickly!) -- usually error handling, where in some error case the unwinding fails to free an mbuf that it should free. These are notoriously hard to track down, unfortunately, but the stats output (especially where delta alloc is linear to delta stat) may inform the situation some more. Robert N M Watson Computer Laboratory University of Cambridge --621616949-1483411841-1259504977=:80654--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0911291427240.80654>