From owner-freebsd-current Tue Nov 14 14:18:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id D283737B4C5; Tue, 14 Nov 2000 14:18:33 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp245.osd.bsdi.com [204.216.28.245]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eAEMITB01664; Tue, 14 Nov 2000 14:18:29 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001114225059.B4195@roaming.cacheboy.net> Date: Tue, 14 Nov 2000 14:18:59 -0800 (PST) From: John Baldwin To: Adrian Chadd Subject: Re: Current has hosed the i8254 timecounter... Cc: freebsd-current@FreeBSD.org, Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Nov-00 Adrian Chadd wrote: > On Mon, Nov 13, 2000, Poul-Henning Kamp wrote: >> >> It seems that something recently toasted the quasi-magic i8254 timecounter >> code to the point of unusability. >> >> On my laptop I run a ntpdate every minute, and the result looks like this: >> > > I'm seeing something similar with -current on this laptop here. Magically, > if I jiggle the mouse whilst playing an mp3, things start to skip and the > clock goes *way* off way (sometimes by a few seconds in a few seconds. :) That is probably due to the random harvesting thread. Or rather, that the overhead of ithreads together with the random kthread and the load of playing mp3's is starving your CPU. Do you have any idle time at all when this happens? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message