From owner-freebsd-current Sat Oct 31 09:10:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19381 for freebsd-current-outgoing; Sat, 31 Oct 1998 09:10:35 -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 JAA19375 for ; Sat, 31 Oct 1998 09:10:33 -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 SAA14102; Sat, 31 Oct 1998 18:09:19 +0100 (CET) To: Wolfram Schneider cc: current@FreeBSD.ORG Subject: Re: calcru: negative time of -695317300 usec for pid In-reply-to: Your message of "Sat, 31 Oct 1998 17:26:06 +0100." <19981031172606.A20248@panke.de.freebsd.org> Date: Sat, 31 Oct 1998 18:09:18 +0100 Message-ID: <14100.909853758@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19981031172606.A20248@panke.de.freebsd.org>, Wolfram Schneider writes: >On 1998-10-31 15:09:53 +0100, Poul-Henning Kamp wrote: >> So is this better or worse than normal ? > >I see no differences to the version without the NTIMECOUNTER hack. >One of 26 `make world' failed, usually after 27 hours. >I'm running `make world' in a chroot environment. >My host is connected with a laplink cable. Hmm, theres a clue, the if_lp0 stuff may disable interrupts for VERY long periods of time. Try setting NTIMERCOUNTER way up, lets try 300 for a go. -- 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