Date: Wed, 26 Jun 2013 19:51:00 -0500 (CDT) From: Alan Amesbury <amesbury@oitsec.umn.edu> To: FreeBSD-gnats-submit@freebsd.org Subject: amd64/180018: System panics when bsnmpd is started Message-ID: <20130627005100.EDC235CFC7@tumbrel.oitsec.umn.edu> Resent-Message-ID: <201306270100.r5R100Vh070461@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 180018 >Category: amd64 >Synopsis: System panics when bsnmpd is started >Confidential: no >Severity: critical >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 27 01:00:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Alan Amesbury >Release: FreeBSD 9.1-RELEASE-p4 amd64 >Organization: >Environment: System: FreeBSD tumbrel.oitsec.umn.edu 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #3: Wed Jun 26 15:47:13 CDT 2013 root@tumbrel.oitsec.umn.edu:/usr/obj/usr/src/sys/OITSEC-9 amd64 Hardware is a Dell PowerEdge R620 with current BIOS (1.6.0). OS was just updated to 9.1-RELEASE-p4. >Description: Starting bsnmpd on this system triggers a panic. The hardware is thought to be OK, but dedicated testing of RAM, etc., isn't possible at the moment. I've captured two backtraces and, to my admittedly novice eye, they appear identical. Output to follow shortly. >How-To-Repeat: Starting bsnmpd reliably triggers this panic. >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130627005100.EDC235CFC7>