Date: Thu, 15 Apr 2010 22:57:29 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Akephalos <akephalos.akephalos@gmail.com> Cc: Attilio Rao <attilio@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: CPU problems after 8.0-STABLE update Message-ID: <4BC76FA9.1020101@icyb.net.ua> In-Reply-To: <20100415205346.a5ff7d79.akephalos.akephalos@gmail.com> References: <q2v1468a0871004032332kd654e4c6s8fbb72ed16f73f0@mail.gmail.com> <v2m3bbf2fe11004040928y3751bca5qfb2870c1fc03ad71@mail.gmail.com> <h2i1468a0871004060450t59c81e76t947f8dbbe268b058@mail.gmail.com> <y2q3bbf2fe11004060551i94582c86j211bf2baf96e6f14@mail.gmail.com> <20100408042958.21d99cea.akephalos.akephalos@gmail.com> <4BBD81B6.4000109@icyb.net.ua> <20100408150436.f08ccbea.akephalos.akephalos@gmail.com> <4BBDDB15.4080406@icyb.net.ua> <20100408154422.071e0904.akephalos.akephalos@gmail.com> <4BBDE420.2060003@icyb.net.ua> <20100408162149.1a5bb8c7.akephalos.akephalos@gmail.com> <4BBDF02C.4020909@icyb.net.ua> <20100410072103.7a216222.akephalos.akephalos@gmail.com> <4BC4DCF0.9010209@icyb.net.ua> <20100414162800.76c6aeac.akephalos.akephalos@gmail.com> <4BC5C599.2000802@icyb.net.ua> <20100414194102.66a35582.akephalos.akephalos@gmail.com> <4BC5F6F1.8040805@icyb.net.ua> <20100415205346.a5ff7d79.akephalos.akephalos@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 15/04/2010 20:53 Akephalos said the following: > 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. I really suspect faulty hardware here. Maybe dead CMOS/NVRAM battery or dead crystal or some chip or circuit. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BC76FA9.1020101>