From owner-freebsd-current Mon Mar 13 11:31: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id D5FAF37BE4D for ; Mon, 13 Mar 2000 11:30:54 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA80430 for ; Mon, 13 Mar 2000 14:30:50 -0500 (EST) Message-Id: <200003131930.OAA80430@cs.rpi.edu> To: current@freebsd.org Subject: calcru / microuptime problem Date: Mon, 13 Mar 2000 14:30:49 -0500 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have had these problems ever since upgrading to -current about a month ago. The kernel very regularly spews out messages like: > Mar 13 14:23:39 gemini /kernel: calcru: negative time of -2663631 usec for pid 568 (sshd2) or a message that "microuptime() went backwards'. I have noticed that these messages usually coincide with moderate to heavy disk IO. I do not have the dmesg or kernel config here with me right now, but I believe I can provide most of the usefull information. The system is an ASUS P2B-DS running ROM revision 1009. It has 2 Pentium II - 400Mhz CPUs, and is running with 'device apm flags 0x20' to get the stat-clock (this was needed in FreeBSD-3.x, I have not yet tried without it. I am also running vinum across 3 disks, one Ultra-2-wide SCSI, and 2 IDE (each on their own bus). Furthermore I am running xntpd to keep my clock in sync. Any suggestions? -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message