Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    Intel Celeron N4000 (Gemini Lake) / panic

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 225 Views 2 Watching
    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.
    • F Offline
      fanno
      last edited by

      Hello

      I was toled redmine was not the location to post it.

      I think its a bug mainly because fresh install vs upgrads has same result.
      (granded my experiance may be limited, so i could ofcause be wrong)

      2.8.1 vs 2.9.0

      https://redmine.pfsense.org/issues/17080

      I am not sure what sub forum this should be posted in so i hope this is ok.

      the workaround/fix:
      https://docs.netgate.com/pfsense/en/latest/releases/2-9-0.html#hardware-errata

      Do NOT work, at least not for me.
      my pfsence box is a Intel Celeron N4000 (Gemini Lake) NOT a Celeron J, i think this is a key differance

      I am happy to try out different things but i have reached the limmit of my knowledge.

      might also note that i get this in upgrade AND clean install of 2.9.0

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

        Your screenshot here definitely shows the known acpi_spmc bug.

        Adding that loader line should prevent it. With that line present it won't load the driver so it can't hit that panic.

        So either the workaround may not have been added quite right or it may have hit some other panic.

        What did you see after adding the workaround loader line?

        F 1 Reply Last reply Reply Quote 0
        • F Offline
          fanno @stephenw10
          last edited by

          @stephenw10

          (manualy typed in so may be wrong) had monitor connected to take a image (image is on original thread)

          GDB: no debug ports pressent
          KDB: no dubygger backends: ddb
          KDB: current backend: ddb
          --<<BOOT>>---
          panic:running without device atpic requires a local APIC
          cpuid = 0
          time = 1
          KDB: enter: panic
          [thread pic 0 tid 0 ]
          stopped at kdb_enter+0x33: novw $0,28cb242(%rip)
          db>

          So it appear disabled, that said i am a noob in this area i have zero kernal knowledge, but to me it appear like the fix dont work. unless ofcause i am doing something wrong.

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

            That's a different panic. It looks like you disabled ACPI in the BIOS perhaps? Modern OSes require ACPI to boot so re-enable that or reset the bios to defaults and re-test.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
            Privacy Policy · Cookie Policy