Experiences with 7.0-CURRENT and vmware.

Dag-Erling Smørgrav des at des.no
Thu May 10 15:11:59 UTC 2007


Darren Reed <darrenr at hub.freebsd.org> writes:
> On Thu, May 10, 2007 at 01:28:16PM +0100, Robert Watson wrote:
> > Have you tried hint.acpi.0.disabled=1 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=1".

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="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 at 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
-- 
Dag-Erling Smørgrav - des at des.no


More information about the freebsd-current mailing list