From owner-freebsd-stable Tue Jun 8 13:19:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from andyo.prime.net (P1M4.prime.net.ua [195.64.229.36]) by hub.freebsd.org (Postfix) with ESMTP id 15CD014ED5; Tue, 8 Jun 1999 13:19:08 -0700 (PDT) (envelope-from andyo@prime.net.ua) Received: from prime.net.ua (localhost [127.0.0.1]) by andyo.prime.net (8.9.3/8.9.3) with ESMTP id XAA00524; Tue, 8 Jun 1999 23:20:35 +0300 (EET DST) Message-ID: <375D7B0A.89AE7C53@prime.net.ua> Date: Tue, 08 Jun 1999 23:20:26 +0300 From: =?koi8-r?Q?=E1=CE=C4=D2=C5=CA=20=F7=2E=20=EF=CC=C5=CA=CE=C9=CB?= (Andy V. Oleynik) Reply-To: andyo@prime.net.ua Organization: =?koi8-r?Q?=ED=2D=E9=CE=C6=CF?= X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) X-Accept-Language: ru, uk, en MIME-Version: 1.0 To: freebsd-question@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Drammatical clock latancy in 3.2-R(S) for some MBD:( & where to find solution Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subscribers of stable & questions should see some of messages about kernel clock latancy about 55 min per hour. Doug tald there bug somewhere. Is the /usr/src/sys/kern/kern_clock.c correct place to find a problem? And if so can somebody enlight what is FreeBSD's kernel clock setup algorithm? -- Andy V. Oleynik (When U aim for perfection, U discover it's a moving target ö80) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message