Re: sched_add: KSE 0xc82290c0 is still assigned to a run queue

From: Andy Hilker <ah_at_cryptobank.de>
Date: Mon, 15 Dec 2003 14:19:34 +0100
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.
> > >
Received on Mon Dec 15 2003 - 04:19:37 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:34 UTC