From owner-freebsd-threads@FreeBSD.ORG Sun Aug 15 23:04:01 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF0CB16A4CE; Sun, 15 Aug 2004 23:04:01 +0000 (GMT) Received: from mx1.imp.ch (mx1.imp.ch [157.161.9.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8457643D1F; Sun, 15 Aug 2004 23:04:00 +0000 (GMT) (envelope-from mb@imp.ch) Received: from mx2.imp.ch (mx2o [157.161.9.17]) by mx1.imp.ch (8.12.11/8.12.11) with ESMTP id i7FN3r9U090572; Mon, 16 Aug 2004 01:03:54 +0200 (CEST) (envelope-from mb@imp.ch) Received: from mx2.imp.ch (localhost [127.0.0.1]) by mx2.imp.ch (8.12.11/8.12.11/Submit) with ESMTP id i7FN3pH1064833; Mon, 16 Aug 2004 01:03:51 +0200 (CEST) (envelope-from mb@imp.ch) Received: (from clamav@localhost) by mx2.imp.ch (8.12.11/8.12.11/Submit) id i7FN3o5T064829; Mon, 16 Aug 2004 01:03:50 +0200 (CEST) (envelope-from mb@imp.ch) Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) by ns1.imp.ch (MIMEDefang) with ESMTP id i7FN3kZW031731; Mon, 16 Aug 2004 01:03:50 +0200 (CEST) Date: Mon, 16 Aug 2004 01:03:46 +0200 (CEST) From: Martin Blapp To: John Polstra In-Reply-To: Message-ID: <20040816010320.N20538@cvs.imp.ch> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Resent: Yes X-Spam-Checksum: a31e8437fc8cd41681b976b4fce5bd4a X-Virus-Message-Status: No X-Virus-Status: No, scantime="0.0075 seconds" X-Spam-Status: No, hits=-4.9 required=5 scantime="2.3598 seconds" tests=BAYES_00 X-Scanned-By: MIMEDefang 2.44 cc: threads@freebsd.org cc: mbr@freebsd.org cc: Robert Watson Subject: RE: thread-unsafe syslog code in libc? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Aug 2004 23:04:01 -0000 Hi, > Or, maybe the system ran out of mbufs and the send() did fail, causing > disconnectlog to be used and exercising the race. An out of mbufs > condition might also contribute to the kernel panic you mentioned. This didn't happen. Martin