kern/148807: 8.1-RELEASE "panic: sbdrop" and "panic: sbsndptr:
sockbuf _ and mbuf _ clashing" under heavy load
Mike Andrews
mandrews at bit0.com
Wed Jul 21 06:20:01 UTC 2010
>Number: 148807
>Category: kern
>Synopsis: 8.1-RELEASE "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" under heavy load
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Jul 21 06:20:01 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Mike Andrews
>Release: 8.1-RELEASE amd64
>Organization:
>Environment:
FreeBSD bourbon.fark.com 8.1-RELEASE FreeBSD 8.1-RELEASE #6: Sat Jul 17 18:30:12 EDT 2010 root at beer.int.fark.com:/usr/obj/usr/src/sys/FARK64 amd64
>Description:
Under heavy load (i.e. enough to make an 8 GB machine start to swap) I'm seeing multiple (identical) machines panic repeatedly with the above panic messages. The panics go away once load goes down.
Also very occasionally seeing "em0: discard frame w/o packet header" before the panics, though not very often.
Hardware is five identical Supermicro PDSMI+ systems, Q6600, 8 GB ECC memory.
The only references I'm finding to these panics on Google seem to point at either IPv6 or em as potential issues, and we're using both. :) Specifically http://groups.google.com/group/mailing.freebsd.net/browse_thread/thread/28db45413a889411 looks VERY similar. I have not yet tried shutting off IPv6 or at least switching some services back to IPv4. (Our v6 usage is all internal-only.)
core.txt.* files are at http://www.bit0.com/tmp/core.txt.20100721.tar.gz
I have minidumps as well but as they may contain some proprietary data I'd rather not post 'em online, however I can run whatever kgdb commands are needed to help troubleshoot. :)
>How-To-Repeat:
See above
>Fix:
Unknown
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list