From owner-freebsd-current@FreeBSD.ORG Tue May 26 00:25:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 702B4106566C for ; Tue, 26 May 2009 00:25:04 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id 52E6D8FC20 for ; Tue, 26 May 2009 00:25:04 +0000 (UTC) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=rmac.psg.com) by ran.psg.com with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1M8kTX-000LNJ-T2 for freebsd-current@freebsd.org; Tue, 26 May 2009 00:25:04 +0000 Received: from rmac.local.psg.com (localhost [127.0.0.1]) by rmac.psg.com (Postfix) with ESMTP id 2E4121A1798F for ; Tue, 26 May 2009 09:25:03 +0900 (JST) Date: Tue, 26 May 2009 09:25:02 +0900 Message-ID: From: Randy Bush To: FreeBSD Current User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.7 Emacs/22.3 (i386-apple-darwin9.6.0) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: kern/134011 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 May 2009 00:25:04 -0000 [ yes, dear, i know i should not run current on production systems. but then, if no one does, how are we gonna shake out proplems under load and real life conditions. someone has to do it. ] this bug is now causing system lockup when the midnight gmt jobs run on one system and it manifesting with less serious consequences on three others. the servers are all racked and remote but have serial console access. how can i be of help finding this one? randy