From nobody@FreeBSD.org  Thu Feb 28 15:28:16 2013
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1])
	by hub.freebsd.org (Postfix) with ESMTP id 5809288D
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 28 Feb 2013 15:28:16 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22])
	by mx1.freebsd.org (Postfix) with ESMTP id 30A8CB6C
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 28 Feb 2013 15:28:16 +0000 (UTC)
Received: from red.freebsd.org (localhost [127.0.0.1])
	by red.freebsd.org (8.14.5/8.14.5) with ESMTP id r1SFSFVh076614
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 28 Feb 2013 15:28:15 GMT
	(envelope-from nobody@red.freebsd.org)
Received: (from nobody@localhost)
	by red.freebsd.org (8.14.5/8.14.5/Submit) id r1SFSF0b076613;
	Thu, 28 Feb 2013 15:28:15 GMT
	(envelope-from nobody)
Message-Id: <201302281528.r1SFSF0b076613@red.freebsd.org>
Date: Thu, 28 Feb 2013 15:28:15 GMT
From: Asa Yeamans <asa@cs.txstate.edu>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Kernel Panic in udp_input @ offset 0x475
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         176510
>Category:       kern
>Synopsis:       [udp] [panic] Kernel Panic in udp_input @ offset 0x475
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    glebius
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Feb 28 15:30:00 UTC 2013
>Closed-Date:    Tue Mar 05 09:36:49 UTC 2013
>Last-Modified:  Tue Mar 05 09:36:49 UTC 2013
>Originator:     Asa Yeamans
>Release:        9.1
>Organization:
Texas State University
>Environment:
FreeBSD theonering 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec  4 09:23:10 UTC 2012     root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64

>Description:
FreeBSD 9.1 Release is kernel panicing very frequently on our network on (so far) one of our servers. In a 10 hour period it has occurred 14 times. In all cases the stack trace of the core dump is identical (or very near) indicating that all kernel panics are caused by the same underlying cause. Below is the common portion of the stack trace.
KDB: stack backtrace:
#0 0xffffffff809208a6 at kdb_backtrace+0x66
#1 0xffffffff808ea8be at panic+0x1ce
#2 0xffffffff80bd8240 at trap_fatal+0x290
#3 0xffffffff80bd857d at trap_pfault+0x1ed
#4 0xffffffff80bd8b9e at trap+0x3ce
#5 0xffffffff80bc315f at calltrap+0x8
#6 0xffffffff80a861d5 at udp_input+0x475
#7 0xffffffff80a043dc at ip_input+0xac
#8 0xffffffff809adafb at netisr_dispatch_src+0x20b
#9 0xffffffff809a35cd at ether_demux+0x14d
#10 0xffffffff809a38a4 at ether_nh_input+0x1f4
#11 0xffffffff809adafb at netisr_dispatch_src+0x20b

Inside this server there are two onboard nics of the "bce" type and 4 PCI nics of the "em" type. 

I have 16 core dump's and associated files with this identical crash comprising 16+ GB of data. I do not have a patch file at this time, but I am happy to try them out.
>How-To-Repeat:
Plug into our network. It happens on average every 45 minutes from, I'm guessing, a specific UDP packet that causes the udp_input to die.
>Fix:
Unknown

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-net 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Fri Mar 1 06:59:04 UTC 2013 
Responsible-Changed-Why:  
Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=176510 
State-Changed-From-To: open->closed 
State-Changed-By: glebius 
State-Changed-When: Tue Mar 5 09:36:16 UTC 2013 
State-Changed-Why:  
Fixed in stable/9 in r241435. 


Responsible-Changed-From-To: freebsd-net->glebius 
Responsible-Changed-By: glebius 
Responsible-Changed-When: Tue Mar 5 09:36:16 UTC 2013 
Responsible-Changed-Why:  
Fixed in stable/9 in r241435. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=176510 
>Unformatted:
