From owner-freebsd-current@FreeBSD.ORG Thu May 10 15:11:59 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CB76516A402; Thu, 10 May 2007 15:11:59 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 89CA713C468; Thu, 10 May 2007 15:11:59 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 5379A20AA; Thu, 10 May 2007 17:11:53 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id CA7D620A8; Thu, 10 May 2007 17:11:52 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id A813A5226; Thu, 10 May 2007 17:11:52 +0200 (CEST) From: des@des.no (Dag-Erling =?utf-8?Q?Sm=C3=B8rgrav?=) To: Darren Reed References: <20070510111326.GA94093@hub.freebsd.org> <20070510132153.A91312@fledge.watson.org> <20070510125445.GA5460@hub.freebsd.org> Date: Thu, 10 May 2007 17:11:52 +0200 In-Reply-To: <20070510125445.GA5460@hub.freebsd.org> (Darren Reed's message of "Thu, 10 May 2007 12:54:45 +0000") Message-ID: <86bqgs90hz.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Robert Watson , current@freebsd.org Subject: Re: Experiences with 7.0-CURRENT and vmware. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2007 15:11:59 -0000 Darren Reed writes: > On Thu, May 10, 2007 at 01:28:16PM +0100, Robert Watson wrote: > > Have you tried hint.acpi.0.disabled=3D1 instead? This is what > > appears in acpi(4), and is what is used in various existing boot > > loader bits when I grep around. > In another reply it was "hint.apic.0.disabled=3D1". No, those are two different things. Disabling the APIC sometimes help with timekeeping on broken hardware. You would get swifter and better help if you put in a minimum amount of effort yourself. The correct way to disable ACPI (whether partially or entirely) is clearly documented in the acpi(4) man page. > Hmm. > > # sysctl kern.timecounter.hardware=3D"ACPI-fast" > kern.timecounter.hardware: ACPI-safe > sysctl: kern.timecounter.hardware: Invalid argument > > Or is this a loader.conf setting? No, you can change it at runtime, but it's quite possible that ACPI-fast is not available. You can tell which timecounters are available by checking kern.timecounter.choice. > btw, there are instances where you can be promopted 6 times for a > password when logging in with ssh, 3 times with "Password:" prompt > and another three with "root@hostname's password:" promopt. Yes. If that is a problem, there is an excellent sshd_config(5) man page which explains how to tweak your configuration. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no