Date: Sat, 7 Jun 2008 01:28:10 +0200 From: "Michal Varga" <varga.michal@gmail.com> To: "Bob Johnson" <fbsdlists@gmail.com> Cc: Gardner Bell <gbell72@rogers.com>, freebsd-current@freebsd.org Subject: Re: calcru: runtime went backwards (and lock order reversal) Message-ID: <3f1fd1ea0806061628t2f63e229ofce2754198092dc@mail.gmail.com> In-Reply-To: <54db43990806061522v3db7b075mb563a16a123efa63@mail.gmail.com> References: <54db43990806061522v3db7b075mb563a16a123efa63@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, I've started geting a number of calcru errors after a recent upgrade to RELENG_7 May 30 2008 (from ~march 2008 RELENG_7), on a x86 Athlon machine that never exhibited these symptoms before. Didn't have time yet to investigate if it really is fbsd's fault or just a dying hw, so it would be quite daring to suggest a regression. I'll probably wait if more people turn out in some time with "me too", or if the hw just explodes..whatever comes first. m. On Sat, Jun 7, 2008 at 12:22 AM, Bob Johnson <fbsdlists@gmail.com> wrote: > The "runtime went backwards" errors are common and probably indicate a > problem servicing interrupts, either because of a driver problem or a > hardware problem. For example, on some motherboards, the Intel > SpeedStep implementation is buggy and can cause this error. Often, > changing the method used to update the system clock will solve the > problem. A Google search will give you lots of suggestions. > > - Bob
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3f1fd1ea0806061628t2f63e229ofce2754198092dc>