From owner-freebsd-current@FreeBSD.ORG  Sat Dec 13 11:13:12 2003
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 C758C16A4CE
	for <freebsd-current@freebsd.org>;
	Sat, 13 Dec 2003 11:13:12 -0800 (PST)
Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU
	[128.205.32.2])	by mx1.FreeBSD.org (Postfix) with ESMTP id BD41243D2D
	for <freebsd-current@freebsd.org>;
	Sat, 13 Dec 2003 11:13:11 -0800 (PST)
	(envelope-from kensmith@cse.Buffalo.EDU)
Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1])
	hBDJDBus014224	for <freebsd-current@freebsd.org>;
	Sat, 13 Dec 2003 14:13:11 -0500 (EST)
Received: (from kensmith@localhost)
	by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id hBDJDAn2014223
	for freebsd-current@freebsd.org; Sat, 13 Dec 2003 14:13:10 -0500 (EST)
Date: Sat, 13 Dec 2003 14:13:10 -0500
From: Ken Smith <kensmith@cse.Buffalo.EDU>
To: freebsd-current@freebsd.org
Message-ID: <20031213191310.GA14083@electra.cse.Buffalo.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Subject: amd64 -current kernel...
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: Sat, 13 Dec 2003 19:13:12 -0000


[ Note this is a -current issue, not necessarily a 5.2-RC issue. ]

Just FYI, the amd64 reference machine in the cluster (sledge) hasn't been
happy with the -current kernel for the past two days.  This is
what the console logs say:

SMP: AP CPU #1 Launched!
panic: sched_add: KSE 0xffffff01e9121000 is still assigned to a run queue
cpuid = 1;
boot() called on cpu#1

syncing disks, buffers remaining...
done
Uptime: 1s
panic: mi_switch: switch in a critical section
cpuid = 1;
boot() called on cpu#1
Uptime: 1s
panic: msleep
cpuid = 1;
boot() called on cpu#1
Uptime: 1s
panic: msleep
cpuid = 1;
boot() called on cpu#1
Uptime: 1s
panic: msleep
cpuid = 1;
boot() called on cpu#1
Uptime: 1s
panic: msleep


-- 
						Ken Smith
- From there to here, from here to      |       kensmith@cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |