Date: Tue, 17 Apr 2007 23:31:50 GMT From: "Charles A. Newcomer"<charles@iapc.net> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/111799: FreeBSD 6.X Deadlocks randomly (Network) Message-ID: <200704172331.l3HNVo86002789@www.freebsd.org> Resent-Message-ID: <200704172340.l3HNe7AX022767@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 111799 >Category: kern >Synopsis: FreeBSD 6.X Deadlocks randomly (Network) >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 23:40:07 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. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704172331.l3HNVo86002789>