Subject: Re: hardclock(9) for cobalt
To: None <port-cobalt@netbsd.org>
From: Toru Nishimura <locore32@gaea.ocn.ne.jp>
List: port-cobalt
Date: 07/29/2004 09:03:06
KIYOHARA Takashi kiyohara@kk.iij4u.or.jp discovered;

> As for cobalt, hardclock(9) is called before initclock() is called. Since
> softclock_si is NULL if callout_reset(9) (or etc...) is called at this
> time, it will carry out panic.

It' looks a plain error.
No interrupt service routine should be called before the entire
configuration stage is well done and kernel gets ready to serve.

Toru Nishimura/ALKYL Technology