From owner-freebsd-current Sun Feb 22 05:12:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27797 for freebsd-current-outgoing; Sun, 22 Feb 1998 05:12:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA27788; Sun, 22 Feb 1998 05:12:35 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id OAA11146; Sun, 22 Feb 1998 14:08:00 +0100 (CET) To: sos@FreeBSD.ORG cc: jhay@mikom.csir.co.za, freebsd-current@FreeBSD.ORG Subject: Re: clock code working properly in -current? In-reply-to: Your message of "Sun, 22 Feb 1998 14:09:03 +0100." <199802221309.OAA16435@sos.freebsd.dk> Date: Sun, 22 Feb 1998 14:07:59 +0100 Message-ID: <11144.888152879@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199802221309.OAA16435@sos.freebsd.dk>, Søren Schmidt writes: >Yes, but an old problem, it occurred together with Poul's first round of >clock changes 'bout a month ago. It is only seen on SMP systems. >I'm not sure its directly related to the clock changes, it might be some >other SMP change that crept in without me noticing. I've not checked but >it could look like all intr. counts are halfed, the actual interrups >doues occur though. A vmstat -i shows that the rates are OK... Yeah, I'm pretty convinced that this is not my doing and that it is harmless, or at least "mostly harmless" :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message