Re: Experiences with 7.0-CURRENT and vmware.

On Thu, May 10, 2007 at 12:54:45PM +0000, Darren Reed wrote:
> On Thu, May 10, 2007 at 01:28:16PM +0100, Robert Watson wrote:
> > 
> > On Thu, 10 May 2007, Darren Reed wrote:
> > 
> > >I'm using FreeBSD 7.0-CURRENT under vmware and there are a few issues.
> 
> Redirecting to current_at_...
> 
> > >First, time. hint.hw.acpi.disabled="1" This appears to make _no_ 
> > >difference to time keeping on FreeBSD 7 and nor does it seem to have any 
> > >impact on ACPI being loaded.  Do I need to recompile a new kernel without 
> > >it or is there a new way to disable ACPI?
> > 
> > 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".
> My current loader.conf:
> 
> vm.kmem_size=536870912
> vm.kmem_size_max=536870912
> unset acpi_load

acpi_load="NO" to disable the module

> hint.acpi.0.disabled=1
> hint.apci.0.disabled=1

dunno what apci does :)

> hint.acpi.0.disabled="1"

This is the one that should work.  Can you confirm that you see it in
the loader environment by doing 'show'?

> hint.apci.0.disabled="1"
> vfs.zfs.arc_max=402653184
> 
> Booting with this gives me:
>  kernel: Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
> 
> and ACPI enabled.
> 
> > >I should add that FreeBSD 6, with the same setting, is no better and that 
> > >I need to run ntpdate every 5-10 minutes via crontab in order to keep good 
> > >time (timekeeping is *really* bad.)  In one instance, i was watching 
> > >"zpool iostat 1" and it appeared like the rows were muching up at a rate 
> > >of 2 a second for a minute or so. How do I disable TSC timekeeping?  
> > >(NetBSD has this disabled by default in their kernels.)  Or is there 
> > >somethign else I must do?
> > 
> > kern.timecounter.hardware: ACPI-fast
> > kern.timecounter.choice: TSC(800) ACPI-fast(1000) i8254(0) dummy(-1000000)
> > 
> > I believe you can simply set kern.timecounter.hardware=APCI-fast and it 
> > will do what you expect.  An interesting question is why it selects what is 
> > arguably the wrong one; a post to current_at_ might help resolve that.
> 
> Hmm.
> 
> # sysctl kern.timecounter.hardware="ACPI-fast"
> kern.timecounter.hardware: ACPI-safe
> sysctl: kern.timecounter.hardware: Invalid argument

kern.timecounter.choice

Kris