Date: Mon, 2 Nov 2009 20:02:08 -0500 (EST) From: Weldon S Godfrey 3 <weldon@excelsusphoto.com> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 8.0 - network stack crashes? Message-ID: <alpine.BSF.2.00.0911021952220.1264@emmett.excelsus.com> In-Reply-To: <hcnt4c$12i$1@ger.gmane.org> References: <alpine.BSF.2.00.0911020747560.80499@emmett.excelsus.com> <hcnt4c$12i$1@ger.gmane.org>
index | next in thread | previous in thread | raw e-mail
If memory serves me right, sometime around Tomorrow, Ivan Voras told me: > Weldon S Godfrey 3 wrote: > >> I don't know how to troubleshoot this further on the server since I am not >> getting any problems indicated in logging, panics, cores, etc. > > If you have console access to the system, the generic advice would be to > compile a kernel with the kernel debugger - options KDB and DDB (see > http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html), > enter the debugger, force a kernel dump file to be created (by entering "call > doadump") and then proceed with post-mortem examination of the kernel at your > leisure (e.g. from a remote ssh console, etc). > > See > http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-deadlocks.html > for instructions on what information to collect. > > If you can provoke your problem with using WITNESS that would probably be > great, but it will slow down your production machine noticeably. When WITNESS > is enabled you might also get more information - such as LOR warnings, which > you should also collect. > > Keep the dump file, someone might ask you for more information. > Thanks, I will work on trying to get a system with those enabled. Another thought that came to mind that this sounds like some sort of network buffer exhaustion. Is there anything to look for there?home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0911021952220.1264>