From owner-freebsd-current Tue Jan 9 3:58:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id DDDF437B400 for ; Tue, 9 Jan 2001 03:58:04 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f09Bw2N15845; Tue, 9 Jan 2001 12:58:02 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: bogus microuptime() warnings? In-Reply-To: Your message of "09 Jan 2001 12:49:39 +0100." Date: Tue, 09 Jan 2001 12:58:02 +0100 Message-ID: <15843.979041482@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dag-Erling Smorgrav writes: >Poul-Henning Kamp writes: >> No, this is either a problem reading the i8254 timecounter reliably >> or an interrupt latency problem. > >Given that this is -CURRENT, interrupt latency is a likely >explanation... > >Going off on a tangent, I'm getting a lot fewer "hwptr went backwards" >with the latest -CURRENT than I used to... That's also the irq-latency if I understand it right. The latency went from "abysmal" to "bad" recently. We used to do "ok". -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message