From owner-freebsd-current@FreeBSD.ORG  Sun May 30 13:35:58 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4034A16A4CE
	for <current@freebsd.org>; Sun, 30 May 2004 13:35:58 -0700 (PDT)
Received: from mail.sandvine.com (sandvine.com [199.243.201.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CE89E43D31
	for <current@freebsd.org>; Sun, 30 May 2004 13:35:57 -0700 (PDT)
	(envelope-from don@sandvine.com)
Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72)
	id <KYKJZ2M7>; Sun, 30 May 2004 16:35:56 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337051D8DEA@mail.sandvine.com>
From: Don Bowman <don@sandvine.com>
To: Don Bowman <don@sandvine.com>,
	"'current@freebsd.org'" <current@freebsd.org>
Date: Sun, 30 May 2004 16:35:55 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: sysctl lock, system lockup
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 30 May 2004 20:35:58 -0000

From: Don Bowman [mailto:don@sandvine.com]
> On the console i ran 'top', but it wouldn't start,
> giving:
> 
> load: 0.00  cmd: top 4282 [sysctl lock] 0.00u 0.00s 0% 180k
> 
> as the status. I can't ^C it, can't ssh in.
> can still ping the device.
> 
> It was doing a backgound fsck from an earlier hang.
> 
> i have called panic from db, not sure if the core will
> work properly or not.

As a followup... i did get a vmcore, and matching kernel.debug,
if someone can suggest what i might look @?

--don