Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Big error

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    4 Posts 4 Posters 1.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      njanja
      last edited by

      Hi all

      After I have installed the program where I get up this message.
      PF1.JPG
      PF1.JPG_thumb

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        Are you running in a VM? There are other threads about this happening in various environments with different ways of setting clocks/NTP etc. e.g. a recent thread: http://forum.pfsense.org/index.php/topic,57234.0.html

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          I would hope he wouldn't be sending a photo of a screen if it was a VM, but you never know!  ;)

          Another possibility is a bad kern.timecounter.hardware selection.
          Usually the default choice is TSC. E.g.

          [2.0.2-RELEASE][root@pfsense.fire.box]/root(2): sysctl kern.timecounter.hardware
          kern.timecounter.hardware: TSC
          

          However if your processor has a variable frequency for whatever reason, speedstep, thermal throttling, turbo mode etc, then TSC can vary causing problems.

          You can check what your options are:

          [2.0.2-RELEASE][root@pfsense.fire.box]/root(6): sysctl kern.timecounter.choice
          kern.timecounter.choice: TSC(800) i8254(0) dummy(-1000000)
          
          

          The number is the quality of the time counter, TSC is highest quality as it ticks the fastest. You can choose, say, i8254 instead:

          [2.0.2-RELEASE][root@pfsense.fire.box]/root(7): sysctl kern.timecounter.hardware=i8254
          kern.timecounter.hardware: TSC -> i8254
          [2.0.2-RELEASE][root@pfsense.fire.box]/root(8): sysctl kern.timecounter.hardware
          kern.timecounter.hardware: i8254
          
          

          If that solves the problem you can add the sysctl to the table in System: Advanced: System Tunables:

          Steve

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            On physical hardware, that's usually caused by a buggy BIOS and upgrading it generally fixes. Though mucking with the timecounter sysctls may be a work around, as Steve noted.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.