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

    Fault on nofault entry

    Scheduled Pinned Locked Moved 1.2.3-PRERELEASE-TESTING snapshots - RETIRED
    10 Posts 2 Posters 6.3k 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
      Sifter
      last edited by

      My unit is rebooting after it throws the below error.  Can someone interpret this error for me?  Im also still getting watchdog timeouts.

      Version  1.2.3-RC1
      built on Wed Apr 22 16:21:49 EDT 2009
      Platform embedded

      After hitting option 8 to go to shell from the console, it throws this:

      Warning: no access to tty (Inappropriate ioctl for device).
      Thus no job control in this shell.
      firewall:~#  panic: vm_fault: fault on nofault entry, addr: c1dbc000
      Uptime: 10m1s
      Cannot dump. No dump device defined.

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        Try a 1.2.3-RC2 nanobsd snapshot.

        It's hard today what that problem might be, but the only way it can really be fixed is if it's tested and reproduced with the most current code. The watchdog timeouts were fixed after RC1, I believe.

        Also it will help to know exactly what hardware you're using (ALIX, WRAP, Soekris, etc)

        Sadly, it could also be a hardware problem which would make it even more difficult to trace.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • S
          Sifter
          last edited by

          When I go to the downloads section, Im not seeing RC2.

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            Try one from here:

            http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/nanobsd/?C=M;O=D

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • S
              Sifter
              last edited by

              What is the difference between the 4g, 2g, 1g, and 512meg releases besides just their sizes?

              1 Reply Last reply Reply Quote 0
              • jimpJ
                jimp Rebel Alliance Developer Netgate
                last edited by

                That's it, just their sizes. That is the size of CF card they are meant to be used with.

                You can use a smaller size image if you like, however.

                Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                Need help fast? Netgate Global Support!

                Do not Chat/PM for help!

                1 Reply Last reply Reply Quote 0
                • S
                  Sifter
                  last edited by

                  ok pulled the 512meg one and imaged it with physdiskwrite.  on the first boot I got this:

                  Fatal trap 12: page fault while in kernel mode
                  fault virtual address  = 0x0
                  fault code              = supervisor write, page not present
                  instruction pointer    = 0x20:0xc0a2d566
                  stack pointer          = 0x28:0xe6b7ab7c
                  frame pointer          = 0x28:0xe6b7ab9c
                  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        = 130 (php)
                  trap number            = 12
                  panic: page fault
                  Uptime: 45s
                  Cannot dump. No dump device defined.
                  Automatic reboot in 15 seconds - press a key on the console to abort

                  Second boot….

                  Configuring firewall......done.
                  Starting webConfigurator...done.
                  Starting DHCP service...done.
                  Starting DNS forwarder...done.
                  Setting up microcode and tx/rx offloading...done.
                  Starting FTP helpers...done.
                  Final filter pass......done.
                  Generating RRD graphs...done.
                  Starting DHCP service...done.
                  Starting CRON... done.
                  Executing rc.d items...
                  Starting /usr/local/etc/rc.d/*.sh...done.
                  appending output to nohup.out
                  Bootup complete
                  panic: vm_fault: fault on nofault entry, addr: c1d60000
                  Uptime: 31s
                  Cannot dump. No dump device defined.
                  Automatic reboot in 15 seconds - press a key on the console to abort

                  1 Reply Last reply Reply Quote 0
                  • S
                    Sifter
                    last edited by

                    after the 3rd reboot, it stayed up.

                    1 Reply Last reply Reply Quote 0
                    • jimpJ
                      jimp Rebel Alliance Developer Netgate
                      last edited by

                      Unfortunately, it might be time to try a different CF card…

                      I'm not sure if there is a CF image for a memory tester like memtest86+ out there or not... I'd try to rule out dodgy hardware before going much further.

                      It's possible there is a problem with that nano image as well, but unusual that it would stay up after successive boots. (Unless the hardware was warming up and fails more when cold)

                      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                      Need help fast? Netgate Global Support!

                      Do not Chat/PM for help!

                      1 Reply Last reply Reply Quote 0
                      • S
                        Sifter
                        last edited by

                        Im running this on a watchguard x700, and it seemed to do ok with monowall loaded previously.  Although, hardware can go bad in the blink of an eye.

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