Date: Wed, 24 Aug 2005 10:31:02 -0400 From: Jason <jason@monsterjam.org> To: stable@freebsd.org Subject: Re: calcru: runtime went backwards and hard lockup in 5.4-STABLE Message-ID: <20050824143102.GA48072@monsterjam.org> In-Reply-To: <44wtmbto1v.fsf@be-well.ilk.org> References: <20050823135800.GA10072@monsterjam.org> <44wtmbto1v.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Not really, but the values are making *huge* jumps back and forth, so > it's not just a matter of missing some interrupts in your case. > > > Is this really a problem? how can I squelch it? > > It does seem to be a problem. It may be a hardware problem with your > timekeeping source. Try changing the timecounter. ok, so I dont know if it will help, but I disabled ACPI by putting hint.acpi.0.disabled="1" in my /boot/device.hints now I see kern.timecounter.choice: TSC(-100) i8254(0) dummy(-1000000) (in my dmesg at boot, I see Timecounter "i8254" frequency 1193182 Hz quality 0) im pretty sure the first and second items (TSC and one next to it) changed since I removed ACPI and I dont see those messages in my syslog anymore.. so I guess thats a good sign. Jason
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050824143102.GA48072>