Date: Mon, 15 Dec 2003 14:19:34 +0100 From: Andy Hilker <ah@cryptobank.de> To: jroberson@chesapeake.net Cc: freebsd-current@freebsd.org Subject: Re: sched_add: KSE 0xc82290c0 is still assigned to a run queue Message-ID: <20031215131934.GB98494@goodhope.crypta.net>
next in thread | raw e-mail | index | archive | help
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.
> > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031215131934.GB98494>