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.
    • 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
                          • J
                            jlepthien
                            last edited by

                            Is this probably the same issue that hits me here: http://forum.pfsense.org/index.php/topic,30465.0.html

                            | apple fanboy | music lover | network and security specialist | in love with cisco systems |

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

                              Hi,

                              @ermal:

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

                              just to give a quick head-up: I have tried the latest snapshot and it seems to have fixed the problem. No kernel panic yes with extensive VLAN on LAGG interfaces config fiddling (but no actual traffic over these yet).

                              Thanks for fixing this,

                              Martin

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

                                same here
                                uptime 2 hours and increasing :)

                                thanks a lot once more for the hard and continuous work

                                1 Reply Last reply Reply Quote 0
                                • J
                                  jlepthien
                                  last edited by

                                  Still not possible for me to add my second wireless interface…

                                  See http://forum.pfsense.org/index.php/topic,30465.0.html

                                  Still rebooting then...

                                  | apple fanboy | music lover | network and security specialist | in love with cisco systems |

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

                                    Go over to your thread jlepthien do not hijack this one.

                                    1 Reply Last reply Reply Quote 0
                                    • J
                                      jlepthien
                                      last edited by

                                      Well, doesn't this look kinda the same problem? And since you are the one fixing this I thought you might be interesting. If you do not want the info on bugs I'll happily install 1.2.3 again and leave the testing up to you…

                                      | apple fanboy | music lover | network and security specialist | in love with cisco systems |

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

                                        Unfortunately, I am still fighting with the kernel panic  :'( :'( :'( :'(

                                        I had hopefully upgraded to "Sat Nov 27 03:13:22 EST 2010 "-Build via USB-Stick, which worked pretty fine.
                                        Today, I tried to use the built-in update feature and… BANG! Kernel-Panic (Fatal Trap 12), see attached screenshot...
                                        (the screenshot is from an older build, but the error is still the same)

                                        ermal, are you still fighting this problem? :-)

                                        Hopefully there will be a solution soon :)

                                        Best regards,

                                        Christian

                                        pfSense_ERROR.jpg
                                        pfSense_ERROR.jpg_thumb

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

                                          without a backtrace i cannot say that this is related to this.

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

                                            I tested both the 27th and 29th snapshots, doing an upgrade to the 27th and then a clean install for the 29th.  Kernel panic still pops up for me under the same conditions as before.  Oddly, the panic doesn't happen until after the update / install has been in place for a while (1-4 hours?)  If I install an update, both GUI and fetch and will work for a bit, then a couple hours later, I run fetch from the console or log into the GUI again and it bonks almost immediately.

                                            I'll get a current backtrace for you in the next hour or two.

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