Bug 18948

Summary: I have the same problem!
Product: Base System Reporter: Ben Collins-Sussman <sussman>
Component: kernAssignee: GNATS administrator <gnats-admin>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 1.0-RELEASE   
Hardware: Any   
OS: Any   

Description Ben Collins-Sussman 2000-06-01 17:40:01 UTC
 I have this same problem.  I can *absolutely* reproduce it by doing
 any sort of prolonged, intense disk access -- for example, building
 the "ispell" port.  (ispell builds some huge indices.)
 
 The "microuptime() went backward" messages are so numerous, that my
 system becomes destabilized;  the CPU load stays quite high,
 everything slows down, I have to reboot.  There's no way to stop the
 messages once they get started.
 
 
 I'm running FreeBSD 4.0 on a 700mhz Athlon system, an EP-7KXA motherboard.
 
 FreeBSD newton.collab.net 4.0-RELEASE FreeBSD 4.0-RELEASE #0: Thu May 4 14:49:56 CDT 2000 root@newton.collab.net:/usr/src/sys/compile/NEWTON-KERNEL i386
Comment 1 Steve Price freebsd_committer freebsd_triage 2000-06-04 07:16:14 UTC
State Changed
From-To: open->closed

Followup to kern/18858.