Subject: kern/29134: KASSERT(to_ticks > 0) getting tripped
To: None <firstname.lastname@example.org, email@example.com,>
From: Peter Seebach <firstname.lastname@example.org>
Date: 01/27/2005 14:55:00
>Synopsis: 2.0 kernel panicking with to_ticks > 0
>Arrival-Date: Thu Jan 27 14:55:00 +0000 2005
>Originator: Peter Seebach
>Release: NetBSD 2.0
System: NetBSD herd.plethora.net 2.0 NetBSD 2.0 (HERD) #1: Thu Jan 27 08:47:34 CST 2005 email@example.com:/usr/src/sys/arch/i386/compile/HERD i386
One of my servers dropped into DDB with the assertion to_ticks > 0.
A little after rebooting, it did it again. I rebooted again,
and interrupted ntpd, and nothing happened, but I haven't tested
to see whether that's it.
Run a 2.0 kernel on a mildly loaded dual-processor machine for
months without incident, then suddenly BANG! (Actually, kernel
was from mid-december.)
Not known. I rebuilt with DIAGNOSTIC off as an emergency fix.
I have savecore and the old kernel. The kernel was built with
-mcpu=i686, but no optimization, for reasons I really don't know