pfsense Error, cant figured out the event log

ayame

I searched on the internet about this log error, but i didn't find any conclusion at all... The error is this bellow.

//
Crash report begins. Anonymous machine information:

amd64
12.3-STABLE
FreeBSD 12.3-STABLE RELENG_2_6_0-n226742-1285d6d205f pfSense

Crash report details:

No PHP errors found.

Filename: /var/crash/info.0
Dump header from device: /dev/ada0p2
Architecture: amd64
Architecture Version: 4
Dump Length: 74752
Blocksize: 512
Compression: none
Dumptime: Mon Mar 7 20:37:42 2022
Hostname: pfSense.objsaobernardo
Magic: FreeBSD Text Dump
Version String: FreeBSD 12.2-STABLE fd0f54f44b5c(RELENG_2_5_0) pfSense
Panic String: NMI indicates hardware failure
Dump Parity: 427253586
Bounds: 0
Dump Status: good

Filename: /var/crash/textdump.tar.0
//

Some topics said that this was an error from NIC, or memory and even motherboard but idk what is the real problem from this error, only that the hardware couldn't do the dump.

This is one of the servers, on the other location (that is a school too) has the same link of internet but the ip shows as 10.xxxx.xxx, but i think its a private IP from AWS.

And this is my first topic so sorry for any errors or misunderstanding.

Thx for the help

stephenw10

Can we see the actual crash report?

Like it says: NMI indicates hardware failure

Is this the first time you've seen it?

Steve

ayame

Yes this is the first time i see a crash report, and the first time I post a forum, I'm a trainee here in Brazil and work here. But no one could really answer me so I came to a forum.
Here bellow was the file that i downloaded from pfsense
info.0 textdump.tar.0

Thx Steve
Vitor

stephenw10

Backtrace:

db:0:kdb.enter.default>  bt
Tracing pid 11 tid 100003 td 0xfffff80005211000
kdb_enter() at kdb_enter+0x37/frame 0xffffffff83726320
vpanic() at vpanic+0x197/frame 0xffffffff83726370
panic() at panic+0x43/frame 0xffffffff837263d0
nmi_call_kdb() at nmi_call_kdb+0x3c/frame 0xffffffff83726400
nmi_call_kdb_smp() at nmi_call_kdb_smp+0x38/frame 0xffffffff83726430
trap() at trap+0x1fa/frame 0xffffffff83726540
nmi_calltrap() at nmi_calltrap+0x8/frame 0xffffffff83726540
--- trap 0x13, rip = 0xffffffff81364e71, rsp = 0xfffffe0024f9e9c0, rbp = 0xfffffe0024f9e9d0 ---
spinlock_exit() at spinlock_exit+0x31/frame 0xfffffe0024f9e9d0
timercb() at timercb+0xbc/frame 0xfffffe0024f9ea20
hpet_intr_single() at hpet_intr_single+0x1b3/frame 0xfffffe0024f9ea50
hpet_intr() at hpet_intr+0xa1/frame 0xfffffe0024f9ea90
intr_event_handle() at intr_event_handle+0x92/frame 0xfffffe0024f9eae0
intr_execute_handlers() at intr_execute_handlers+0x52/frame 0xfffffe0024f9eb10
Xapic_isr1() at Xapic_isr1+0xdc/frame 0xfffffe0024f9eb10
--- interrupt, rip = 0xffffffff8152f1b5, rsp = 0xfffffe0024f9ebe0, rbp = 0xfffffe0024f9ebf0 ---
cpu_idle() at cpu_idle+0xe5/frame 0xfffffe0024f9ebf0
sched_idletd() at sched_idletd+0x326/frame 0xfffffe0024f9ecb0
fork_exit() at fork_exit+0x7e/frame 0xfffffe0024f9ecf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0024f9ecf0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---

Panic:

re1: reset never completed!
re1: PHY write failed
re1: PHY write failed
re1: PHY write failed
re1: PHY write failed
re1: PHY write failed
re1: PHY write failed
re1: PHY write failed
<2>NMI ISA a0, EISA ff
<2>RAM parity error, likely hardware failure.
panic: NMI indicates hardware failure
cpuid = 0
time = 1646685462
KDB: enter: panic

That Realtek watchdog timeout might be solvable by using the alternative re(4) driver.

That RAM parity error looks like bad RAM though. That's old hardware it could just be failing.

I would run a RAM test on that to be sure. Boot memtest86 or similar.

Steve

ayame

@stephenw10
Thx a lot Steve this was a very good overhaul for me and a good thing to me understand more this. Helped me a lot and thx to show whre was the errors I couldn't figured out.

And yes this is a very old hardware that no one never maintain the hardware.

Vitor