pfSense 2.6.0 stable crashing with panic "Unknown caching mode 23"
-
@thatpickledude In general, with PC hardware I find random/changing crash errors are usually bad memory. You might run a memory test just to rule that out.
-
@steveits Thanks! Ram tests look good, unfortunately
Strangely, I can't replicate the issue again. Wish I knew what happened, but this appears to be intermittent.
-
Mmm, hard to imagine it could be bad ram in VM. But it sure behaves like it I agree.
-
@stephenw10 said in pfSense 2.6.0 stable crashing with panic "Unknown caching mode 23":
Mmm, hard to imagine it could be bad ram in VM.
Well now that you say that….
Missed that tidbit. Host, maybe. Worth a shot to rule it out.Recently had a client’s year old PC start throwing STOP errors every few days. Windows memory test passed. Finally a tech took memtest or something there and it flagged the RAM. No issues after replacing it.
-
Okay... It's still happening. Getting a new unique crash though, so that may be progress. Panic string is:
vm_fault: fault on nofault entry, addr: 0xffffffff83d92000. Also getting morepage faultcrashes. RAM checks out, and xcp-ng is updated with the latest patches.vm_fault crash:
info.0
textdump.tar.0Page fault crash:
info.0
textdump.tar.0 -
Hmm, they're all different. This 'feels' like some sort of hypervisor feature incompatibility.
Like maybe flexible virtual memory or disk size which is known to cause problems with some other hypervisors.
Were you running pfSense in xcp before?
Steve
-
@stephenw10 Different hardware (two R710 in an HA pair), but yes. No real issue before. Maybe I'll try a reinstall in BIOS mode instead of UEFI
-
Updated BIOS (was one patch version behind) and am updating to 2.7 DEVEL hoping this is a diver issue causing some weird compatibility that can be fixed in FreeBSD 14. Fingers crossed
-
@thatpickledude Did you ever figure this out? I'm having the exact same issue with the exact same messages...
-
What are you actually seeing? The backtraces above are different.
Steve
