Date: Thu, 1 Jun 2000 09:38:26 -0700 (PDT) From: sussman@collab.net To: freebsd-gnats-submit@FreeBSD.org Subject: kern/18949: infinite "microuptime() went backwards" messages -- caused by intense disk access Message-ID: <20000601163826.F219B37BF16@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 18949 >Category: kern >Synopsis: infinite "microuptime() went backwards" messages -- caused by intense disk access >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 01 09:40:01 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Ben Collins-Sussman >Release: 4.0 >Organization: Collab.Net >Environment: 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 >Description: This problem is identical, I think, to kern/18858, and possibly kern/18798. 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. >How-To-Repeat: Intense UDMA disk access on this particular motherboard. 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.) >Fix: ? >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000601163826.F219B37BF16>