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

    Frequent crashes with APU2

    Scheduled Pinned Locked Moved General pfSense Questions
    25 Posts 6 Posters 6.6k 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.
    • J Offline
      j.koopmann
      last edited by

      1000000

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

        That's fine. There's mbuf in the backtrace, which at times can be indicative of mbuf exhaustion. Wouldn't be the case there though.

        I noticed one potentially relevant change. Let's try going back to 2.3 and see what happens. First backup your config and be ready to reinstall just in case as this isn't widely tested, but it does seem to work fine.

        Change your /usr/local/etc/pkg/repos/pfSense.conf to contain the following:

        FreeBSD: { enabled: no }
        
        pfSense-core: {
          url: "pkg+http://pkg.pfsense.org/pfSense_v2_3_0_amd64-core",
          mirror_type: "srv",
          signature_type: "fingerprints",
          fingerprints: "/usr/local/share/pfSense/keys/pkg"
          enabled: yes
        }
        
        pfSense: {
          url: "pkg+http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0",
          mirror_type: "srv",
          signature_type: "fingerprints",
          fingerprints: "/usr/local/share/pfSense/keys/pkg"
          enabled: yes
        }
        
        

        Then run:

        pkg update -f
        pkg upgrade -fy
        

        and reboot when it's done.

        1 Reply Last reply Reply Quote 0
        • J Offline
          j.koopmann
          last edited by

          Ok.

          Will download 2.2.6 and 2.3 images later, backup and try to step back. Will keep you posted. Might take a few hours.

          Thanks for the great support!!!!

          1 Reply Last reply Reply Quote 0
          • J Offline
            j.koopmann
            last edited by

            Downgrade worked however the kernel is still

            pfSense-kernel-pfSense-2.3.1.a.20160506.1958 pfSense kernel (pfSense)

            I got a "is locked" message for this package during upgrade (or rather downgrade). So the one thing that needed downgrading is not… :-(

            1 Reply Last reply Reply Quote 0
            • J Offline
              j.koopmann
              last edited by

              ok. pkg unlock and a few more tries resulted in a 2.3 system with kernel

              pfSense-kernel-pfSense-2.3    pfSense kernel (pfSense)

              Let's wait and see.

              1 Reply Last reply Reply Quote 0
              • J Offline
                j.koopmann
                last edited by

                Next crash this time under 2.3. However after reboot no crashlogs/dumps… Will keep looking but probably step down to 2.2.6 tomorrow... Need a stable system next week.

                1 Reply Last reply Reply Quote 0
                • J Offline
                  JorgeOliveira
                  last edited by

                  Just out of curiously what are the specs on which you are running pfSense?

                  This issue may boil down to an incompatibility with any hardware in the system, so details would be appreciated.

                  Regards,
                  Jorge M. Oliveira

                  My views have absolutely no warranty express or implied. Always do your own research.

                  1 Reply Last reply Reply Quote 0
                  • J Offline
                    j.koopmann
                    last edited by

                    Sure,

                    Standard apu 1c with an msata hdd.

                    1 Reply Last reply Reply Quote 0
                    • D Offline
                      DESIGN-COMPANY
                      last edited by

                      Have the same problem with version 2.3 and 2.3.1 with APU 1d4 Board AMD G-T40E Processor. Interrupts 50%. No traffic on LAN and WAN.

                      Only power off is possible and then power on.

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

                        The third crash was also a completely different backtrace from the first two. I'm guessing that's some kind of issue after disabling additional cores maybe in combination with https://redmine.pfsense.org/issues/6296

                        It's definitely not after upgrading to 2.3.1. I suspect once the root IPsec issue is fixed and you're not disabling the additional cores, the crashes will be gone.

                        @DESIGN-COMPANY:

                        Have the same problem with version 2.3 and 2.3.1 with APU 1d4 Board AMD G-T40E Processor. Interrupts 50%. No traffic on LAN and WAN.

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

                        1 Reply Last reply Reply Quote 0
                        • J Offline
                          j.koopmann
                          last edited by

                          Hi cmb,

                          just experienced a completely new crash with 2.3, four cores enabled. Looking different as it also gave a backtrace. I uploaded the crash and will give you the details via PM.

                          Regards,
                            JP

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

                            From further review and private conversation, this can be summarized as "frequent crashes with APU2", it has no relation to 2.3 or 2.3.1. Some of the crashes match things people were getting on APU2 with 2.2.6 as well.

                            1 Reply Last reply Reply Quote 0
                            • J Offline
                              j.koopmann
                              last edited by

                              Agreed.

                              However: How to proceed (if not in this threat)? PM? A new thread in another forum (and if so which one would be the correct one)?

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

                                You can continue here. I'll move the thread since it's not 2.3.1-related.

                                The default for AES-NI is off (with the exception of hardware we sell), which is why that one sticks out at me. In the other thread, it wouldn't have been anything config-related as far as certain features in use or not, so anything hardware-related is what came to mind. AES-NI seems most potentially suspect given the remainder of your config.

                                1 Reply Last reply Reply Quote 0
                                • J Offline
                                  j.koopmann
                                  last edited by

                                  Brilliant support (can't really say that enough)!

                                  I turned it off, will wait for the next reboot and then see how this behaves.

                                  I just checked a config-backup from end of march and to the best of my knowledge aesni was turned on there as well:

                                  <crypto_hardware>aesni</crypto_hardware>

                                  And as mentioned in the PM the crashes seem to have started in May (or end of April) after several changes to the config but this part was left untouched. Still I will see what happens and let you know!

                                  Regards,
                                    JP

                                  1 Reply Last reply Reply Quote 0
                                  • J Offline
                                    j.koopmann
                                    last edited by

                                    No change. Still crashing.

                                    1 Reply Last reply Reply Quote 0
                                    • R Offline
                                      rhyslewis
                                      last edited by

                                      @j.koopmann:

                                      No change. Still crashing.

                                      Curious that temps are not getting high ?.. I had one freeze up as I had incorrectly mounted the heatsink to the APU2C4 case:)

                                      Do you have one of these boards –> http://www.pcengines.ch/apu2c4.htm

                                      1 Reply Last reply Reply Quote 0
                                      • J Offline
                                        j.koopmann
                                        last edited by

                                        I do and had thought of that. I was sure to have mounted it correctly but hey it might have loosened. How can I monitor the temperature. Looked for it today but could not find anything.

                                        1 Reply Last reply Reply Quote 0
                                        • J Offline
                                          j.koopmann
                                          last edited by

                                          Ok. I found a module and am logging temp every minute. So far the CPU temp is around 59C which should be well within limits…

                                          1 Reply Last reply Reply Quote 0
                                          • J Offline
                                            JuSt Floppy
                                            last edited by

                                            Hi,

                                            I run 2.3 Update 1 with my APU2 without any problem.
                                            Uptime: 13 Days 02 Hours 32 Minutes 51 Seconds
                                            Following packages are installed:
                                            Backup sysutils 0.4_1
                                            Cron sysutils 0.3.6_2
                                            RRD_Summary sysutils 1.3.1_2
                                            Shellcmd sysutils 1.0.2_2

                                            Temp is always 56.6 °C and very stable.

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