From owner-freebsd-stable Thu Feb 11 06:08:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20292 for freebsd-stable-outgoing; Thu, 11 Feb 1999 06:08:17 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20287 for ; Thu, 11 Feb 1999 06:08:16 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA23801; Thu, 11 Feb 1999 23:08:07 +0900 (JST) Message-ID: <36C2E0B2.4229F1AE@newsguy.com> Date: Thu, 11 Feb 1999 22:52:50 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Ludwig Pummer CC: stable@FreeBSD.ORG Subject: Re: calcru References: <4.1.19990210184153.009d9b60@mail-r> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ludwig Pummer wrote: > > At 05:41 PM 2/10/99 , Mike Smith wrote: > >> >calcru: negative time of -77208797 usec for pid 5230 (ssh1) > >> It means that you have funny > >> hardware (ISA cards?) and maybe also a driver that aggravates it. > > > >No, it means that our timecounter code is broken, and the author has > >been unwilling/unable to fix it for > 6 months. > > > >(He also got roundly canned for his presentation of it at Usenix, BTW.) > > Too bad about the presentation. > > But that means my Cyrix MediaGX system isn't really broken! Yay! > (it runs well enough but after a while i get calcru: negative time of -5000 > usec every day) This can be corrected by a kernel option, though. Or I *think* so. If one resorts to use the alternate algorithm for timecounter, things works. I don't recall how to do that, though. Also, it would seem that adding the apm driver to your kernel, or disactivating apm on your BIOS, also corrects the problem. In particular, one report, at least, was made of a BIOS in which the line "apm os" or "apm bios" set to deactivated did *not* really deactivate it, and another change had to be made to the BIOS to *really* deactivate it. Take your pick, search the mailing lists (I only read -hackers and -current, so it was on one of them). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message