From e53ae3b7988658d21fe97864dee33838e281ea58 Mon Sep 17 00:00:00 2001 From: jeff Date: Mon, 10 Mar 2008 09:50:29 +0000 Subject: - Don't rely on a side effect of sched_prio() to set the initial ts_runq for thread0. Set it directly in sched_setup(). This fixes traps on boot seen on some machines. Reported by: phk --- sys/kern/sched_ule.c | 1 + 1 file changed, 1 insertion(+) (limited to 'sys/kern/sched_ule.c') diff --git a/sys/kern/sched_ule.c b/sys/kern/sched_ule.c index 0427807..a4117cf 100644 --- a/sys/kern/sched_ule.c +++ b/sys/kern/sched_ule.c @@ -1250,6 +1250,7 @@ sched_setup(void *dummy) /* Add thread0's load since it's running. */ TDQ_LOCK(tdq); thread0.td_lock = TDQ_LOCKPTR(TDQ_SELF()); + tdq_runq_pick(tdq, &td_sched0); tdq_load_add(tdq, &td_sched0); tdq->tdq_lowpri = thread0.td_priority; TDQ_UNLOCK(tdq); -- cgit v1.1