On 30/07/2007, at 2:10, YAMAMOTO Takashi wrote:

>> Any idea about what happens?
>
> hardclock without softintr_schedule is broken?

Seems to be the cause.  If I make "needsoftclock" be always true in  
kern_timeout.c:callout_hardclock, the machine works fine.  Similarly,  
adding "_setsoftintr(0)" just after the call to hardclock() from  
clockintr() does the same.

Otherwise, at some point the machine seems to stop receiving  
interrupts: not even clockintr is called.  See my last reply to the PR.

I'm at loss on how to debug this.  Any hints please? :-)

Thanks,

-- 
Julio M. Merino Vidal <jmmv84@gmail.com>