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

    Kernel panic 4-5 Nov (i386)

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    89 Posts 17 Posters 36.8k 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.
    • W
      wallabybob
      last edited by

      I've seen similar panics in a build of 9-Nov. More in http://forum.pfsense.org/index.php/topic,29927.0.html

      1 Reply Last reply Reply Quote 0
      • B
        Beerman
        last edited by

        Same panic here: http://forum.pfsense.org/index.php/topic,30048.0.html

        1 Reply Last reply Reply Quote 0
        • F
          FisherKing
          last edited by

          Beerman, Wallabybob, I'm curious, what nic is assigned to your WAN? Or what driver is your WAN using?

          1 Reply Last reply Reply Quote 0
          • W
            wallabybob
            last edited by

            I'm using rl0 for my WAN interface. I could easily swap to vr0 or a wireless link or a USB NIC if you thought it worthwhile to gather some more data. I can reproduce my problem fairly easily.

            1 Reply Last reply Reply Quote 0
            • E
              Efonnes
              last edited by

              My Alix 2c3 has this happen when updating and randomly at some other times when accessing the web gui.  WAN is vr1 and uses only DHCP, LAN is vr0, and I have ath0 for an access point on OPT1.

              PJ2: Some good information there.  It looks like it is crashing in the same function at the same line of code every time, called from the same code path.

              1 Reply Last reply Reply Quote 0
              • W
                wallabybob
                last edited by

                I swapped interfaces so vr0 was my WAN and on three restarts I've hit the same panic: syncache: mbuf too small

                1 Reply Last reply Reply Quote 0
                • F
                  FisherKing
                  last edited by

                  I had wondered if it was just an issue w/ intel nics.  Sounds like it's not that specific.  Thanks Wallabybob.

                  1 Reply Last reply Reply Quote 0
                  • B
                    Beerman
                    last edited by

                    @PJ2:

                    Beerman, Wallabybob, I'm curious, what nic is assigned to your WAN? Or what driver is your WAN using?

                    My WAN is on vr2_vlan7. (ALIX Board)

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

                      Any updates on this already?

                      We are also facing this problem here…
                      We stumbled over this "bug" (or whatever it is) a few weeks ago, when we tried to update to the newest snapshot...
                      Normally we used to update every few days and then suddenly we got this "Fatal Trap 12"-Error during the update...

                      It seems to be related to the update-system of pfSense, as it occurs either when checking for a new FW or trying to
                      download a new FW (using the Web-Interface or the Shell doesn't matter, the Trap comes anyway).
                      (I have attached a screenshot of our system)

                      We are using pfSense on >10 boxes, all with the same HW.
                      We have already switched the complete HW, but the problem stays the same (so I doubt that it is related to HW).

                      WAN1: ste0
                      WAN2: ste1
                      LAN: vr0

                      Hopefully there will be a fix soon (as we want to be able to upgrade again, also because of the now fixed PPTP-Bug)...

                      Thanks a lot and best regards,

                      Christian

                      pfSense_ERROR.jpg
                      pfSense_ERROR.jpg_thumb

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

                        Hello everybody,

                        are there already any news on this?
                        As I can on other threads here, the "kernel panic"-problem seems to be happening to a lot of people…

                        Is this a bug in FreeBSD itself oder pfSense?

                        Thanks and best regards,

                        Christian

                        1 Reply Last reply Reply Quote 0
                        • E
                          eri--
                          last edited by

                          I am looking into it and will post when a solution is checked in.

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

                            Perfect, ermal,

                            thank you  :)

                            Best regards,

                            Chris

                            1 Reply Last reply Reply Quote 0
                            • F
                              FisherKing
                              last edited by

                              Yeah - thanks for looking into this ermal.  It's hard to to much other testing when we can't do anything w/ the GUI. :)

                              Let us know if you need any other information.  I can probably arrange remote access to the box if you can't reproduce this on your hardware.

                              1 Reply Last reply Reply Quote 0
                              • M
                                mbartosch
                                last edited by

                                Hi,

                                unhappy camper as well. Using the snapshot from 2010-11-18 I tried to configure an interface group, after this I got trapped in a kernel trap - reboot loop.

                                Running on a Soekris 5501.

                                FreeBSD/i386 bootstrap loader, Revision 1.1
                                (sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org, Thu Nov 18 07:57:55 EST 20)
                                …
                                vlan7: changing name to 'lagg0_vlan2920'                                       
                                vlan8: changing name to 'lagg0_vlan2921'                                       
                                vlan9: changing name to 'lagg0_vlan2930'                                       
                                vlan10: changing name to 'lagg0_vlan2931'

                                Fatal trap 12: page fault while in kernel mode                                 
                                cpuid = 0; apic id = 00                                                       
                                fault virtual address  = 0x14                                                 
                                fault code              = supervisor read, page not present                   
                                instruction pointer    = 0x20:0xc095d504                                     
                                stack pointer          = 0x28:0xc33fbb48                                     
                                frame pointer          = 0x28:0xc33fbb78                                     
                                code segment            = base 0x0, limit 0xfffff, type 0x1b                   
                                                        = DPL 0, pres 1, def32 1, gran 1                       
                                processor eflags        = interrupt enabled, resume, IOPL = 0                 
                                current process        = 11 (swi4: clock)                                     
                                trap number            = 12                                                   
                                panic: page fault                                                             
                                cpuid = 0                                                                     
                                Uptime: 29s

                                1 Reply Last reply Reply Quote 0
                                • E
                                  eri--
                                  last edited by

                                  Give a shot at tomorrows snapshots.

                                  1 Reply Last reply Reply Quote 0
                                  • F
                                    FisherKing
                                    last edited by

                                    Wahoo!  Thanks ermal!

                                    1 Reply Last reply Reply Quote 0
                                    • B
                                      bEsTiAn
                                      last edited by

                                      coming from my own thread :
                                      http://forum.pfsense.org/index.php/topic,30207.msg157592.html
                                      Unfortunately, using latest available snaphost, the crash repeats, after 1 or 2 minutes uptime

                                      1 Reply Last reply Reply Quote 0
                                      • F
                                        FisherKing
                                        last edited by

                                        Yeah - I installed the 2010-11-25 update and experienced the same thing.

                                        Ermal - do you need a backtrace from the current snapshot, or is what you have already sufficient?

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          mbartosch
                                          last edited by

                                          Hi,

                                          doesn't look good yet, using the snapshot from yesterday (sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org, Thu Nov 25 10:39:16 EST 20).

                                          I just created the first LAGG interface from vr2 and vr3 on my Soekris 5501. Immediately after clicking the apply button in the web interface:

                                          Fatal trap 12: page fault while in kernel mode                                 
                                          cpuid = 0; apic id = 00                                                       
                                          fault virtual address  = 0xc                                                 
                                          fault code              = supervisor read, page not present                   
                                          instruction pointer    = 0x20:0xc09bbc2d                                     
                                          stack pointer          = 0x28:0xe5dbec04                                     
                                          frame pointer          = 0x28:0xe5dbec24                                     
                                          code segment            = base 0x0, limit 0xfffff, type 0x1b                   
                                                                  = DPL 0, pres 1, def32 1, gran 1                       
                                          processor eflags        = interrupt enabled, resume, IOPL = 0                 
                                          current process        = 11 (irq9: vr2)                                       
                                          trap number            = 12                                                   
                                          panic: page fault                                                             
                                          cpuid = 0                                                                     
                                          Uptime: 17h58m38s                                                             
                                          Cannot dump. Device not defined or unavailable.

                                          1 Reply Last reply Reply Quote 0
                                          • E
                                            eri--
                                            last edited by

                                            Hmmm sorry i thought i had pushed the patch to repo!
                                            Just did though try with next snaps.

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