Been having random system freezes since I built the system in May. It will run fine for a few days then just freeze with no mention of anything I can use in /var/log/messages or var/crash. It'll reboot fine, then throw itself into a long fsck. The fsck will find and fix things as the partitions were forcibly un-mounted. Then the system runs great.
Hardware components are off-the-shelf and new this year.
uname-a reads as follows:
I am using this rig as a personal workstation. Gnome is installed @ v2.30 and I have GNOME_ENABLE="YES" in /etc/rc.conf. Whether I leave the system logged into Gnome or just at the login screen, the problem exists.
I had been getting:
-type of errors, and thought those were the problem. I got rid of them with the help of DutchDaemon's post in this thread:
http://forums.freebsd.org/showthread.php?t=2805&highlight=calcru%3A+runtime+backwards
by disabling CPU EIST function in BIOS. That cleared up the 'calcru: runtime went backwards' errors, but still the freezing occurs.
Some more system info:
So I am thinking that there is a problem with time on this computer. The computer keeps accurate time, but maybe there is a system-level mis-communication between the BIOS and the OS. Any help greatly appreciated.
Thanks.
Hardware components are off-the-shelf and new this year.
uname-a reads as follows:
Code:
8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
I am using this rig as a personal workstation. Gnome is installed @ v2.30 and I have GNOME_ENABLE="YES" in /etc/rc.conf. Whether I leave the system logged into Gnome or just at the login screen, the problem exists.
I had been getting:
Code:
kernel: calcru: runtime went backwards from 1327 usec to 1308 usec for pid 1437 (getty)
-type of errors, and thought those were the problem. I got rid of them with the help of DutchDaemon's post in this thread:
http://forums.freebsd.org/showthread.php?t=2805&highlight=calcru%3A+runtime+backwards
by disabling CPU EIST function in BIOS. That cleared up the 'calcru: runtime went backwards' errors, but still the freezing occurs.
Some more system info:
Code:
$ dmesg | grep Timecounter
Timecounter "i8254" frequency 1193182 Hz quality 0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
Timecounter "HPET" frequency 14318180 Hz quality 900
Timecounters tick every 1.000 msec
$ sysctl kern.timecounter.hardware
kern.timecounter.hardware: ACPI-fast
So I am thinking that there is a problem with time on this computer. The computer keeps accurate time, but maybe there is a system-level mis-communication between the BIOS and the OS. Any help greatly appreciated.
Thanks.