Re: FreeBSD 8.0 - network stack crashes?

On Tuesday 03 November 2009 02:02:08 Weldon S Godfrey 3 wrote:
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?

Are you perhaps using em(4)? There was an mbuf leak in the driver, which was fixed recently.
You can check mbuf usage with netstat -m.

--
Pieter de Goeje
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: FreeBSD 8.0 - network stack crashes?
    ... 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, enter the debugger, force a kernel dump file to be created and then proceed with post-mortem examination of the kernel at your leisure. ... If you can provoke your problem with using WITNESS that would probably be great, but it will slow down your production machine noticeably. ... Keep the dump file, someone might ask you for more information. ...
    (freebsd-current)
  • Re: updating in single-user mode
    ... > I don't reccommend doing installworld or kernel in multiuser, ... > had any problems doing it on a lightly loaded machine. ... You will then need console access to fix it. ...
    (freebsd-questions)
  • kernel update
    ... Newbie RedHat user here. ... I do not have console access to. ... kernel version 2.4.20-8 ... If I reboot the machine, it will be a long plain ...
    (linux.redhat.install)
  • Re: kernel update
    ... > I do not have console access to. ... > How do I install a new kernel remotely and make sure all is ok before I ... If I reboot the machine, it will be a long plain ...
    (linux.redhat.install)
  • Re: computer becomes slow when compiling something
    ... Try the same thing again without INVARIANTS and WITNESS, both of which can consume a lot of CPU in kernel on a very active system, especially if lots of vnodes are being allocated and freed. ... If it's broke, don't fix it. ...
    (freebsd-current)