Re: calcru: runtime went backwards (and lock order reversal)

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_at_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