yes,, this exactly fits the symptoms!
I've committed it.
(it's definitly wrong)
assume this will solv ethe problem.
now why doesn't MINE fail?
On Sat, 9 Feb 2002 [EMAIL PROTECTED] wrote:
> > hmmmm so what is the difference between your kernel and mine that works?
> >
> > just out of curiosity, have you tried a very latest -current?
> > do you have your own config? how does GENERIC behave?
> > (what kind of disks do you have?)
>
> It looks like a call to setrunqueue() was incorrectly dropped in
> the latest version of kern_shutdown.c.
>
> Index: kern_shutdown.c
> ===================================================================
> RCS file: /home/ncvs/src/sys/kern/kern_shutdown.c,v
> retrieving revision 1.118
> diff -u -r1.118 kern_shutdown.c
> --- kern_shutdown.c 7 Feb 2002 20:58:44 -0000 1.118
> +++ kern_shutdown.c 9 Feb 2002 01:11:18 -0000
> @@ -272,6 +272,7 @@
> DROP_GIANT();
> for (subiter = 0; subiter < 50 * iter; subiter++) {
> mtx_lock_spin(&sched_lock);
> + setrunqueue(curthread);
> curthread->td_proc->p_stats->p_ru.ru_nvcsw++;
> mi_switch(); /* Allow interrupt
>threads to run */
> mtx_unlock_spin(&sched_lock);
>
>
> - Tor Egge
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
