Systems Crash & Reboot



  • Hi Folks

    We had a system crash this morning whereby our firewall became unresponsive to attempts to log into the GUI. After rebooting the device the system spontaneously rebooted twice again. We had a look through the system logs and nothing seems obvious to us at the moment as to the cause.

    System details are as follows

    Version 2.2.5-RELEASE (amd64)
    built on Wed Nov 04 15:49:37 CST 2015
    FreeBSD 10.1-RELEASE-p24

    Platform pfSense
    CPU Type AMD GX-415GA SOC with Radeon™ HD Graphics
    4 CPUs: 1 package(s) x 4 core(s)

    Once we got back into the GUI we uploaded the crash report. https://doc.pfsense.org/index.php/Obtaining_Panic_Information_for_Developers states

    "After a panic/crash leading to a reboot, a box will appear on the dashboard to view and automatically submit a crash report. If the crash report is submitted, call attention to it on the forum where a developer with sufficient access can retrieve the report and analyze it."

    We have submitted the crash report and so I would like to call attention to it here in the hope that a developer would a few moments to be able to analyze it and give us some feedback on a cause and any steps we need to take to prevent the issue from happening again.


  • Rebel Alliance Developer Netgate

    I see one crash report submitted today from the IP address you posted from. Assuming that's it, it looks like it might be a hardware issue.

    The place it crashed is highly unlikely to have a bug (pretty deep in FreeBSD code), and given your description of the event, I would start investigating it from a hardware angle.

    You could move up to a current version (2.3.2) on the off chance it's a FreeBSD bug fixed there, but that's much less likely than a hardware/power/cooling issue.



  • Thanks Jimp. I appreciate you coming back to me. Does the crash report indicate a specific piece of hardware ?


  • Rebel Alliance Developer Netgate

    No, it doesn't. Sometimes if it's a disk it will crash in a filesystem operation but this was quite deep in the kernel, so probably not a disk but something more fundamental.



  • Thanks Jimp. Again, I appreciate your time looking into it.


Log in to reply