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

    pFsense + 22.05 keeps crashing

    Scheduled Pinned Locked Moved General pfSense Questions
    16 Posts 5 Posters 1.9k 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.
    • S
      skogs
      last edited by

      @geekypr I know that motherboard has 3 NICs... 2 good ones and 1 Realtek. If you're utilizing the Realtek NIC for anything you might need to search forums here for that specific fix action.

      G 1 Reply Last reply Reply Quote 0
      • G
        geekypr @skogs
        last edited by

        @skogs Thanks, that third NIC is for IPMI. Not using it.
        It worked for a week or two, today it started to crash again.

        Attached is the latest dump file;
        textdump.tar

        Maybe I have a bad memory module. I just removed one (have 4GB x2) and will monitor behavior.

        I hope there's something in the dump that can be find to resolve this issue.

        Again, thank you for the help here...

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

          Still show an NMI error:

          <2>NMI ISA 28, EISA 0
          NMI/cpu2 ... going to debugger
          

          If it's not an actual hardware issue it's something FreeBSD cannot handle IMO.

          Did you test running anything else on it? Some burn-in test maybe?

          Steve

          G 1 Reply Last reply Reply Quote 0
          • G
            geekypr @stephenw10
            last edited by

            @stephenw10
            stress_ng can be an option?

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

              Sure, whatever you have access to. If you can boot and run some other OS without seeing any issues then it could be something FreeBSD specific.

              1 Reply Last reply Reply Quote 0
              • A
                AdriftAtlas
                last edited by

                Are you still having crashes?

                Both dumps are related to cpu power management. Are C-States enabled in the BIOS?

                What is the output of the following executed from shell:

                sysctl machdep | grep -i idle
                
                G 1 Reply Last reply Reply Quote 0
                • G
                  geekypr @AdriftAtlas
                  last edited by

                  @adriftatlas Apologies for my late reply.

                  This is the output;

                  machdep.idle: acpi
                  machdep.idle_available: spin, mwait, hlt, acpi
                  machdep.idle_apl31: 0
                  machdep.idle_mwait: 1

                  It was fine until last night. Attached is the latest dump file.
                  What I noticed is, last night I got high humidity environment. And also remember the same environment before. I just don't think is related, but, I can't figure it out why all of the sudden it crashes.
                  textdump.tar

                  Trowed in other memory stick from another working server, just to make sure.
                  It's frustrating......

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

                    Still hard to ignore the NMI errors for me. But if you can disable power saving features in the BIOS as a test you may as well.

                    You do have Speedstep (C-states) enabled:

                    est0: <Enhanced SpeedStep Frequency Control> on cpu0
                    

                    So you could also just disable powerd in System > Advanced > Misc

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • A
                      AdriftAtlas
                      last edited by

                      https://www.supermicro.com/products/archive/motherboard/x9scm-f

                      This motherboard is more than a decade old. Unless you updated the BIOS recently you're likely running old CPU microcode.

                      The BMC also likely has a watchdog that may be throwing NMIs, worth updating that too. There is a jumper on the motherboard for it and a BIOS setting, see page 57 in the manual:
                      https://www.supermicro.com/manuals/motherboard/C202_C204/MNL-1270.pdf

                      Latest BIOS:
                      1/6/2021 2.3a
                      https://www.supermicro.com/en/support/resources/downloadcenter/firmware/MBD-X9SCM-F/BIOS

                      Latest BMC:
                      3.52
                      https://www.supermicro.com/en/support/resources/downloadcenter/firmware/MBD-X9SCM-F/BMC

                      Other things to try:

                      • Disable "Power Technology" in BIOS; see page 76 in manual
                      • Disable PowerD in pfSense as suggested by @stephenw10
                      • Set CPU idle to HALT instead of ACPI or MWAIT:
                      sysctl machdep.idle_mwait=0
                      sysctl machdep.idle=hlt
                      
                      G 1 Reply Last reply Reply Quote 1
                      • G
                        geekypr @AdriftAtlas
                        last edited by

                        @adriftatlas Thanks!
                        I will try that over the weekend.
                        (powerD is disabled)

                        Keep you posted...

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