From nobody@FreeBSD.org  Tue Apr 17 21:41:49 2007
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id EC37616A404
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 17 Apr 2007 21:41:49 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [69.147.83.33])
	by mx1.freebsd.org (Postfix) with ESMTP id DC14613C46A
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 17 Apr 2007 21:41:49 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id l3HLfnWf083293
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 17 Apr 2007 21:41:49 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id l3HLam54080562;
	Tue, 17 Apr 2007 21:36:48 GMT
	(envelope-from nobody)
Message-Id: <200704172136.l3HLam54080562@www.freebsd.org>
Date: Tue, 17 Apr 2007 21:36:48 GMT
From: "Charles A. Newcomer"<charles@iapc.net>
To: freebsd-gnats-submit@FreeBSD.org
Subject: FreeBSD 6.2-RELEASE #0 Deadlocks randomly
X-Send-Pr-Version: www-3.0

>Number:         111793
>Category:       kern
>Synopsis:       [hang] FreeBSD 6.2-RELEASE #0 Deadlocks randomly
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Apr 17 21:50:02 GMT 2007
>Closed-Date:    Tue Jun 12 08:34:52 GMT 2007
>Last-Modified:  Tue Jun 12 08:34:52 GMT 2007
>Originator:     Charles A. Newcomer
>Release:        FreeBSD 6.2-RELEASE #0
>Organization:
IAPC
>Environment:
FreeBSD vox.stes.org 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007     root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP  i386

>Description:
Compaq DL380 3.2 Dual Core Xeon using bge network driver (dual ports)
will randomly deadlock.  Only way to recover is power off.  No panic
dumps or any indicators in logs.  Looks like a spin
lock.

In our particular instance it occurs at aproximately 1 week intervals.

This problem has been present in all 6.X releases.

Using GIANT-LOCK on the network stack stops it (apparently) from happening.
Although under previous 6.X releases system would still occasionaly panic
(have not analyzed the cause; may be another reason)
>How-To-Repeat:
Unknown exactly.
We are running the latest asterisk12 port with phones on an inside lan
(192.168.X.X) bge1 and asterisk accepting SIP calls from a public IP
behind a Cisco PIX on bge0.

Just reinstalled from CD to FreeBSD 6.2-RELEASE #0 and locked after 4 days.
>Fix:
Somewhat of a work around is to configure the system for GIANT-LOCKing
on the network stack.

>Release-Note:
>Audit-Trail:

From: Kris Kennaway <kris@obsecurity.org>
To: "Charles A. Newcomer" <charles@iapc.net>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/111793: FreeBSD 6.2-RELEASE #0 Deadlocks randomly
Date: Tue, 17 Apr 2007 20:43:36 -0400

 Are you using ipfw or pf?  See the manpages for known deadlock
 conditions.
 
 If not, you need to configure your system to enable debugging and
 obtain the necessary information when the deadlock occurs; see the
 chapter on kernel debugging in the developers handbook.
 
 Kris
State-Changed-From-To: open->feedback 
State-Changed-By: linimon 
State-Changed-When: Sun Apr 22 07:29:39 UTC 2007 
State-Changed-Why:  
Note that submitter has been asked for feedback. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=111793 
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Tue Jun 12 08:34:37 UTC 2007 
State-Changed-Why:  
Feedback timeout (1 month). 

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