From owner-freebsd-questions@FreeBSD.ORG Wed Mar 10 14:12:54 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5815D16A4CE for ; Wed, 10 Mar 2004 14:12:54 -0800 (PST) Received: from smtp.nildram.co.uk (smtp.nildram.co.uk [195.112.4.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0F7543D2F for ; Wed, 10 Mar 2004 14:12:53 -0800 (PST) (envelope-from mark@ukug.uk.freebsd.org) Received: from ukug.uk.freebsd.org (parish.gotadsl.co.uk [62.3.235.43]) by smtp.nildram.co.uk (Postfix) with ESMTP id ED43F2F7676; Wed, 10 Mar 2004 22:12:48 +0000 (GMT) Message-ID: <404F92E7.2090702@ukug.uk.freebsd.org> Date: Wed, 10 Mar 2004 22:12:55 +0000 From: Mark Ovens User-Agent: Mozilla Thunderbird 7.0 (X11/20040307) X-Accept-Language: en-us, en MIME-Version: 1.0 To: darom@filmkern.com References: <22997.206.169.45.183.1078952848.squirrel@mail.filmkern.com> In-Reply-To: <22997.206.169.45.183.1078952848.squirrel@mail.filmkern.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: SOLVED :-) Re: Wierd time changes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2004 22:12:54 -0000 Denis R. wrote: > Hi Mark! > > Gee, who would have thought that it was the keyboard. Thanks for your > ideas. I recompiled the kernel (Compaq SP700 dual PII-450) following the > NOTES guidelines and your email, with these enabled: > # To make an SMP kernel, the next two are needed > options SMP # Symmetric MultiProcessor Kernel > device apic # I/O APIC > > options NO_MIXED_MODE > options BROKEN_KEYBOARD_RESET > options EISA_SLOTS=12 > > and in /boot/loader.conf > kern.timecounter.method=1 > > I still got the broken time (10 second test lasts 22 seconds). The server > also hung upon the 'reboot' command while releasing the CPU1. Since it is I had that (hanging) at one point; IIRC it was NO_MIXED_MODE that caused it. > a production server, I switched back to my single CPU kernel. > > If you have any other suggestions, I'd appreciate the input. > Only to try with different value for kern.timecounter.method, but that's just a guess. Does the output from ''sysctl -a kern.timecounter'' yield any clues? Apart from that I really can't be of any help. I take it you've done the obvious and searched the mailing list and Google? Regards, Mark > Thanks, > Denis > > >>>>>>>>>>>> > I've solved it and I bet you can't guess what it was - it > was the fscking keyboard!!! > > After spending the last 8 hours building kernels (about 20) with > unnecessary stuff removed and trying various options documented in > /sys/i386/conf/NOTES I finally nailed it down. What made me wonder was a > kernel option BROKEN_KEYBOARD_RESET > > > > >