PfSense Crash Report



  • Hi. I have been having some issues with my router for the past couple of months. I have tried resetting to factory default, reformatting the router and installing different versions of pfSense, and trying to comb through logs and crash reports to figure out why the router keeps crashing despite the version of pfSense I use. I am fairly confident that it is hardware related at this point but I just need to know if the router is completely hosed or if I can buy a specific part to fix it. Thanks.

    IP: 209.60.158.242
    Approximate time of submitting crash report: Sept 21, 2017 08:40 am EST


  • Rebel Alliance Developer Netgate

    I don't see anything from that IP address, or anything near it. Around the stated time I saw submissions from some other IP addresses though. But without knowing which is yours I can't say anything for certain. Two of them were filesystem crashes, which a reinstall would have fixed, and the other was an issue with RADIUS and Captive Portal.

    If you get another crash report, copy and paste the contents into a text file and attach that here.



  • @jimp:

    I don't see anything from that IP address, or anything near it. Around the stated time I saw submissions from some other IP addresses though. But without knowing which is yours I can't say anything for certain. Two of them were filesystem crashes, which a reinstall would have fixed, and the other was an issue with RADIUS and Captive Portal.

    If you get another crash report, copy and paste the contents into a text file and attach that here.

    I apologize for the wild goose chase. I have attached the crash report. Thank you again.

    [pfSense Crash Report.txt](/public/imported_attachments/1/pfSense Crash Report.txt)


  • Rebel Alliance Developer Netgate

    The three crashes in there are all in different places and two of them are fairly short backtraces that don't have much that could have caused them except hardware issues since they are in low-level memory management operations. Usually memory in this case but it could be anything that could induce a similar condition (CPU/MB issue, cooling issue, flaky power, etc).



  • @jimp:

    The three crashes in there are all in different places and two of them are fairly short backtraces that don't have much that could have caused them except hardware issues since they are in low-level memory management operations. Usually memory in this case but it could be anything that could induce a similar condition (CPU/MB issue, cooling issue, flaky power, etc).

    That being said, what was the third crash? Was it something major or just a fluke? I only want to know so that way I can keep a look out for it in the future if it is something preventable. Thank you again for helping me clear this up.



  • So because there were three different hardware errors with my router, I bought a new router with a new NIC card and RAM and used a spare SSD that I had that I know was good when I put it in storage 3 months ago.

    I reinstall pfSense and restore my configuration and less than 15 minutes later, I get this crash report. Could someone please help me with this. Thank you.

    [Crash Report.txt](/public/imported_attachments/1/Crash Report.txt)


  • Rebel Alliance Developer Netgate

    You said it's a "new" NIC but that is an em device. Any current Intel card should be igb.

    db:0:kdb.enter.default>  bt
    Tracing pid 12 tid 100062 td 0xfffff8000360e4b0
    m_freem() at m_freem+0x20/frame 0xfffffe0062582720
    ip6_input() at ip6_input+0xa4c/frame 0xfffffe0062582900
    netisr_dispatch_src() at netisr_dispatch_src+0x62/frame 0xfffffe0062582970
    ether_demux() at ether_demux+0x116/frame 0xfffffe00625829a0
    ether_nh_input() at ether_nh_input+0x347/frame 0xfffffe0062582a00
    netisr_dispatch_src() at netisr_dispatch_src+0x62/frame 0xfffffe0062582a70
    em_rxeof() at em_rxeof+0x43f/frame 0xfffffe0062582af0
    em_msix_rx() at em_msix_rx+0x35/frame 0xfffffe0062582b20
    intr_event_execute_handlers() at intr_event_execute_handlers+0xab/frame 0xfffffe0062582b60
    ithread_loop() at ithread_loop+0x96/frame 0xfffffe0062582bb0
    fork_exit() at fork_exit+0x9a/frame 0xfffffe0062582bf0
    fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0062582bf0
    
    

    That crash is in a memory operation when handling incoming IPv6 input. It's possible it's an OS/driver issue. I don't see anyone else hitting any similar panics, either.



  • @jimp:

    You said it's a "new" NIC but that is an em device. Any current Intel card should be igb.

    All I meant by that is that we bought the same type card that we were running in our other routers that is "new" as it has never been used. I recognize that it is not the most cutting edge technology, but it is what we know will work based on our other router setups.

    As far as what the crash report says, is it something that can be solved by reinstalling the OS or by setting up IPv6? We never set up IPv6 in the past because we don't use it at our company but if that will solve our issues, then I am willing to set it up.


Log in to reply