Fault on nofault entry

  • 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.

  • Rebel Alliance Developer Netgate

    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.

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

  • Rebel Alliance Developer Netgate

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

  • Rebel Alliance Developer Netgate

    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.

  • 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

  • after the 3rd reboot, it stayed up.

  • Rebel Alliance Developer Netgate

    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)

  • 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.

Log in to reply