Date: Sun, 6 Apr 2008 17:24:07 +0200 From: Guido van Rooij <guido@gvr.org> To: Jeremy Chadwick <koitsu@freebsd.org> Cc: David Malone <dwmalone@maths.tcd.ie>, freebsd-stable@freebsd.org Subject: Re: NTP on amd74 + powernow issues Message-ID: <20080406152407.GA1836@gvr.gvr.org> In-Reply-To: <20080405105803.GA2947@eos.sc1.parodius.com> References: <20080404174605.GA41929@gvr.gvr.org> <20080404194238.GA75601@walton.maths.tcd.ie> <20080405091349.GA78080@gvr.gvr.org> <20080405105803.GA2947@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 05, 2008 at 03:58:03AM -0700, Jeremy Chadwick wrote: > On Sat, Apr 05, 2008 at 11:13:49AM +0200, Guido van Rooij wrote: > > On Fri, Apr 04, 2008 at 08:42:38PM +0100, David Malone wrote: > > > On Fri, Apr 04, 2008 at 07:46:05PM +0200, Guido van Rooij wrote: > > > > I've got a amd64 system where I;m using powernow. I am using th i8254 > > > > timecounter. I keep getting time resets from ntp: > > > > > > I don't think the i8254 should be effected by the i8254. Are there > > > any other choices listed under kern.timecounter.choice? I have one > > > amd64 machine running powerd to control the powernow stuff and it > > > works OK with the ACPI timer. > > > > Nope: > > kern.timecounter.choice: TSC(800) i8254(0) dummy(-1000000) > > > > IIRC I couldn't boot at all with acpi, so I disabled it. > > ACPI-fast should address the problem you're seeing with NTP drift. > > It would then be best to figure out why your machine won't boot with > ACPI enabled. > This lead to a panic as is described here: http://bsd.haofood.net/2005/11/21/work-around-for-busted-rs-acpi-long/ The panic occurs because a \0 is in the namespace. It was suggested to fix the problem by overwriting \0 with X or _ when loading the acpi tables. This has not been fixed and there is no bios update for the motherboard... -Guido
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080406152407.GA1836>