From owner-freebsd-current@FreeBSD.ORG  Fri Sep 10 19:45:05 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 82A1816A4CE
	for <freebsd-current@freebsd.org>;
	Fri, 10 Sep 2004 19:45:05 +0000 (GMT)
Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 57D5B43D49
	for <freebsd-current@freebsd.org>;
	Fri, 10 Sep 2004 19:45:05 +0000 (GMT)
	(envelope-from julian@elischer.org)
Received: from elischer.org (julian.vicor-nb.com [208.206.78.97])
	by mail.vicor-nb.com (Postfix) with ESMTP
	id 164D17A3D2; Fri, 10 Sep 2004 12:45:02 -0700 (PDT)
Message-ID: <4142043D.2050405@elischer.org>
Date: Fri, 10 Sep 2004 12:45:01 -0700
From: Julian Elischer <julian@elischer.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516
X-Accept-Language: en, hu
MIME-Version: 1.0
To: Sean McNeil <sean@mcneil.com>
References: <1094722377.1083.3.camel@server.mcneil.com>
In-Reply-To: <1094722377.1083.3.camel@server.mcneil.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-current@freebsd.org
Subject: Re: setrunqueue() panic
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: Fri, 10 Sep 2004 19:45:05 -0000



Sean McNeil wrote:

>I've experienced this on my amd64 system.  Had no problems at all with
>SCHED_ULE and no PREEMPTION, but since building a new kernel with these
>I have:
>
>Sep  9 02:20:03 server syslogd: kernel boot file is /boot/kernel/kernel
>Sep  9 02:20:03 server kernel: setrunqueue(): corrupt kq_runq, td= 0xffffff003767e520
>Sep  9 02:20:03 server kernel: panic: deadlock in setrunqueue
>Sep  9 02:20:03 server kernel: KDB: enter: panic
>Sep  9 02:20:03 server kernel:
>Sep  9 02:20:03 server kernel:
>

yeah we are keenly aware of this..

is this in 6.0  or RELENG_5?