John Baldwin wrote: > On Friday 05 August 2005 10:01 am, Eric Anderson wrote: > >>John Baldwin wrote: >> >>>On Tuesday 02 August 2005 04:57 pm, Eric Anderson wrote: >>> >>>>John Baldwin wrote: >>>> >>>>>On Tuesday 02 August 2005 04:28 pm, Eric Anderson wrote: >>>>> >>>>>>Ok, here's a small list of issues pending that I can see on -current >>>>>>(and I saw these on 6- branch too before 7.0). >>>>>> >>>>>>- Time ticks along correctly, but anything using an interval will be 2x >>>>>>off. For instance - ping will only send a ping every 2 seconds instead >>>>>>of every second. systat -vmstat 1 refreshes every 2 seconds, etc. >>>>>>Disabling APIC 'fixes' it. >>>>> >>>>>Are you using the i8254 timecounter or some other timecounter? >>>> >>>>kern.timecounter.choice: TSC(800) ACPI-fast(1000) i8254(0) >>>>dummy(-1000000) kern.timecounter.hardware: ACPI-fast >>>> >>>>Which is the default (I'm not forcing anything anywhere). I believe at >>>>one time I tried i8254, but it made no difference. I can try it again >>>>if you think it's a worthy experiment. >>> >>>I would try both i8254 and TSC and see if it makes a difference. >> >>Can I do this via sysctl, or do I need to rebuild my kernel? > > > sysctl. Just write the name of the new one to kern.timecounter.hardware > I've done that, with no effect. I've tried this same hard drive in a different laptop, and it works ok, so it's something with the way it detects the hardware I suppose. The laptops are very different. Both are using ACPI-fast. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------Received on Tue Aug 09 2005 - 11:55:55 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:41 UTC