From owner-freebsd-bugs@FreeBSD.ORG Wed Apr 18 00:50:10 2007 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 292BD16A401 for ; Wed, 18 Apr 2007 00:50:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id F3A0A13C455 for ; Wed, 18 Apr 2007 00:50:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l3I0o9jW027998 for ; Wed, 18 Apr 2007 00:50:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l3I0o9vs027994; Wed, 18 Apr 2007 00:50:09 GMT (envelope-from gnats) Date: Wed, 18 Apr 2007 00:50:09 GMT Message-Id: <200704180050.l3I0o9vs027994@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kris Kennaway Cc: Subject: Re: kern/111793: FreeBSD 6.2-RELEASE #0 Deadlocks randomly X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kris Kennaway List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2007 00:50:10 -0000 The following reply was made to PR kern/111793; it has been noted by GNATS. From: Kris Kennaway To: "Charles A. Newcomer" 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 On Tue, Apr 17, 2007 at 09:36:48PM +0000, Charles A. Newcomer wrote: > > >Number: 111793 > >Category: kern > >Synopsis: FreeBSD 6.2-RELEASE #0 Deadlocks randomly > >Confidential: no > >Severity: critical > >Priority: high > >Responsible: freebsd-bugs > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Tue Apr 17 21:50:02 GMT 2007 > >Closed-Date: > >Last-Modified: > >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 > analysed 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. 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