On Wed, 14 Apr 2010 20:10:09 +0300 Andriy Gapon <a...@icyb.net.ua> wrote:
> Indeed, that almost sounds too good to be true :-) > Couple of questions: > 1. Could you please check in dmesg if hpet attaches normally now or > still has an error? > 2. Do you have to run ntpdate after each power-off or is everything > OK after the first run? > 3. Have you ever set time on this machine before (in BIOS, other OS, > etc)? > 4. Can you please double-check that lapic_allclocks is zero in > kernel? You can run 'kgdb /boot/kernel/kernel /dev/mem' and then > 'print lapic_allclocks' > > Thanks! > -- > Andriy Gapon 1: %dmesg | grep -i hpet ACPI HPET table warning: Sequence is non-zero (2) acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0 acpi_hpet0: HPET never increments, disabling device_attach: acpi_hpet0 attach returned 6 2: Yes, I have to run it every time for it to work. Not once my CPU load is detected after reboot, unless running ntpd. 3: Yes, I had problems with mounts in the future and whatnot. I don't remember what I used where, but on Linux I used to remove a file, /var/lib/hwclock/adjtime and run ntpd - for the things to get in line. 4: In the debugger it prints: $1 = 0, so I suppose yeah, it is set to zero. Laterz! -- Mihai _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
