calcru: runtime went backwards and hard lockup in 5.4-STABLE

From: Jason (jason_at_monsterjam.org)
Date: 08/23/05

  • Next message: Oleg Korecky: "USB camera" 
    Date: Tue, 23 Aug 2005 09:58:00 -0400
To: stable@freebsd.org

    hey folks..
    Im running on a compaq proliant dual 733Mhz computer with 1 gig o memory..
    I was running 5.4-STABLE a few weeks ago with no problem.. I did a make world about a
    week ago, and now I see lots of messages in syslog..
    Aug 22 17:20:40 monsterjam kernel: calcru: runtime went backwards from 77810370 usec to
    77203
    321 usec for pid 48 (swi5: clock sio)
    Aug 22 17:20:40 monsterjam kernel: calcru: runtime went backwards from 17036511 usec to
    16595
    708 usec for pid 71 (schedcpu)
    Aug 22 17:20:40 monsterjam kernel: calcru: runtime went backwards from 77810370 usec to
    77203
    365 usec for pid 48 (swi5: clock sio)
    Aug 22 17:20:40 monsterjam kernel: calcru: runtime went backwards from 17036511 usec to
    16595
    708 usec for pid 71 (schedcpu)
    Aug 22 17:20:40 monsterjam kernel: calcru: runtime went backwards from 77810370 usec to
    77203
    463 usec for pid 48 (swi5: clock sio)

    and I see
    http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#CALCRU-NEGATIVE
    but this info seems to only apply to 4.x.

    Is this really a problem? how can I squelch it?

    the other reason I ask is because ive had 2 HARD lockups since upgrading. I have since
    compiled a debugging kernel..

    (in my kernel config)
    makeoptions DEBUG=-g
    options GDB
    options DDB
    options KDB
    (this look right?)

    I have a serial connection hooked up to this server and I cannot even break into the
    debugger when it hangs.

    regards,
    Jason

    _______________________________________________
    freebsd-stable@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-stable
    To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"

  • Next message: Oleg Korecky: "USB camera"

    Relevant Pages

    • Two (2) Lock Order Reversion - tracking RELENG_7
      ... usec for pid 827 ... calcru: runtime went backwards from 4534 usec to 4267 usec for pid 919 ...
      (freebsd-current)
    • calcru: runtime went backwards
      ... EXCL by thread 0xffffff0001289360 (pid 1013) ... calcru: runtime went backwards from 33275 usec to 290 usec for pid 999 ...
      (freebsd-current)
    • Re: calcru: runtime went backwards (and lock order reversal)
      ... FreeBSD is a registered trademark of The FreeBSD Foundation. ... "runtime went backwards" messages. ... runtime went backwards from 469322 usec to 3929 usec for pid ... runtime went backwards from 13323 usec to 109 usec for pid 998 ...
      (freebsd-current)
    • Crash
      ... 107491627102 usec for pid 60113 ... runtime went backwards from 107492416053 usec to 107491839468 ... calcru: runtime went backwards from 107492416053 usec to 107492051756 usec ...
      (freebsd-stable)
    • calcru: runtime went backwards
      ... problems with the clock going backwards. ... calcru: runtime went backwards from 10542602 usec to 10542600 usec for pid ...
      (freebsd-questions)