port-cobalt: Re: dangerous for initialize of MIPS timer

Subject: Re: dangerous for initialize of MIPS timer
To: None <port-mips@NetBSD.org, port-cobalt@NetBSD.org>
From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
List: port-cobalt
Date: 09/24/2006 09:52:10

kiyohara@kk.iij4u.or.jp wrote:

> I think serious dangerous for initialization of MIPS timer.  My Cobalt
> Qube panic() in hardclock().  It reason for hardclock() is called before
> softclock is initialized. 

Yes, it could happen on my RaQ2 while it would be some timing dependent.

Maybe we should move _splnone() from autoconf.c:cpu_configure() to
mips/mips3_clockintr():cpu_initclocks(), but I wonder
we should still enable other interrupts than INT5 in
cpu_configure() or not. (since initclocks() is called
right after cpu_configure() in subr_autoconf.c).
---
Izumi Tsutsui