From owner-freebsd-current Thu Nov 5 23:20:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27374 for freebsd-current-outgoing; Thu, 5 Nov 1998 23:20:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27366 for ; Thu, 5 Nov 1998 23:20:08 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id IAA02915; Fri, 6 Nov 1998 08:18:37 +0100 (CET) To: Bill Paul cc: current@FreeBSD.ORG Subject: Re: Grrr... calcru: negative time blah blah blah In-reply-to: Your message of "Thu, 05 Nov 1998 19:24:54 EST." <199811060024.TAA14156@skynet.ctr.columbia.edu> Date: Fri, 06 Nov 1998 08:18:37 +0100 Message-ID: <2913.910336717@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm still banging my head against this one. I'm working with a handfull of people who has this problem, trying to identify what the heck is happening. I can't reproduce it on any of my machines here. If you have an interrupt storm which could lock out hardclock() that will certainly screw things up badly. I have put some diagnostic patches at: http://www.freebsd.org/~phk/tc_diag.diff Please notice the patch to sysctl in there too, it is needed to print out all of the "delta history buffer". Please try these patches out, they will not panic the machine if the tests trigger, merely report some applicable details. If any of the tests trigger, please email me: /var/run/dmesg.boot `dmesg` `sysctl kern.timecounter` `sysctl debug` Mike, Shimon & Warner: There is one new check compared to the patch you have, but it is not critical (yet). Poul-Henning In message <199811060024.TAA14156@skynet.ctr.columbia.edu>, Bill Paul writes: >Recently, the EE department got a bunch of new Dell machines with >450Mhz PII CPUs. This one particular system is an SMP box with 512MB >of RAM and a 3D Labs Fire GL 100 adapter. Somebody installed >FreeBSD 3.0-RELEASE on this system (my brainwashing scheme is working! >Soon I will rule the wor--! Uh, wait. You didn't hear that.) and >discovered that this display adapter isn't supported by XFree86 (yet) >so they downloaded the XFCom_3DLabs server from somewhere. > >The system seems to run fin until they start this X server. The >server loads, but it does something unfriendly to the system that >produces the following errors: > >calcru: negative time of -36857 usec for pid 4036 (csh) >calcru: negative time of -51744 usec for pid 4043 (w) >calcru: negative time of -26704 usec for pid 4044 (ps) >calcru: negative time of -47557 usec for pid 4046 (reboot) >calcru: negative time of -46489 usec for pid 304 (hostname) >calcru: negative time of -24935 usec for pid 310 (ps) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message