From owner-freebsd-current@FreeBSD.ORG  Mon Dec 15 05:19:37 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 AAE3816A4CE
	for <freebsd-current@freebsd.org>;
	Mon, 15 Dec 2003 05:19:37 -0800 (PST)
Received: from mail.crypta.net (cryptobank.biz [217.160.183.210])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2A93443D32
	for <freebsd-current@freebsd.org>;
	Mon, 15 Dec 2003 05:19:36 -0800 (PST)
	(envelope-from ah@cryptobank.de)
Received: by mail.crypta.net (Postfix, from userid 1001)
	id C1AD578CCD; Mon, 15 Dec 2003 14:19:34 +0100 (CET)
Date: Mon, 15 Dec 2003 14:19:34 +0100
From: Andy Hilker <ah@cryptobank.de>
To: jroberson@chesapeake.net
Message-ID: <20031215131934.GB98494@goodhope.crypta.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-PGP-Key: http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0xEC6E1071
X-PGP-Fingerprint: 9B2E 5892 AD93 D5C5 FB8E  3912 35D6 951B EC6E 1071
Organization: cryptobank - Andy Hilker
cc: freebsd-current@freebsd.org
Subject: Re: sched_add: KSE 0xc82290c0 is still assigned to a run queue
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: Mon, 15 Dec 2003 13:19:37 -0000


Hi,

> > nearly the same problem here...
> > "... KSE 0xc39c60c60 ..."
> >
> > sched_ule.c version: 1.89
> 
> I should have this fixed tonight, thanks.

sched_ule.c version: 1.90 fixed this issue, but with "kern.smp.disabled=1"
in loader.conf boot hangs after mounting root and /sbin/init (boot
-v). 
Without this option machine boots up.  With sched_ule.c version
1.85 and "smp.disabled", machine boots up, too.

bye,
Andy


> > > As of today's -current.
> > >
> > > I tried to use SCHED_ULE.  It works fine with SCHED_4BSD, but changing
> > > options to SCHED_ULE, it failed to boot.
> > >
> > > ----- console
> > > ...
> > > GEOM: create disk cd0 dp=0xc8594e00
> > > GEOM: create disk cd1 dp=0xc8594600
> > > SMP: AP CPU #1 Launched!
> > > cd1 at ata1 bus 0 target 1 lun 0
> > > cd1: <MATSHITA DVD-RAM LF-D310 A116> Removable CD-ROM SCSI-0 device
> > > cd1: 16.000MB/s transfers
> > > cd1: cd present [1 x 2048 byte records]
> > > panic: sched_add: KSE 0xc82290c0 is still assigned to a run queue
> > > cpuid = 1;
> > > Debugger("panic")
> > > -----
> > >
> > > Though panic message is there, it didn't go to DDB.  Sending break
> > > from serial console did not help.
> > >