[Bug 286759] Fatal trap 12: page fault while in kernel mode - Melonax NIC on FreeBSD14.2
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 286759] Fatal trap 12: page fault while in kernel mode - Melonax NIC on FreeBSD14.2"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 286759] Fatal trap 12: page fault while in kernel mode - Melonax NIC on FreeBSD14.2"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 286759] Fatal trap 12: page fault while in kernel mode - Melonax NIC on FreeBSD14.2"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 286759] Fatal trap 12: page fault while in kernel mode - Mellanox NIC on FreeBSD14.2"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 13 May 2025 07:15:27 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286759
Bug ID: 286759
Summary: Fatal trap 12: page fault while in kernel mode -
Melonax NIC on FreeBSD14.2
Product: Base System
Version: 14.2-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: bugs@FreeBSD.org
Reporter: karthickhari1995gamer@gmail.com
Created attachment 260367
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=260367&action=edit
kernel panic log
I’m running a reverse proxy setup as a clustered environment. Recently, two of
the nodes unexpectedly rebooted due to a kernel panic, where the kernel
attempted to access an invalid memory address. I'm not sure why this issue
occurred suddenly, or why it affected only these two specific servers and never
happened again so far.
For context, both affected servers are virtual machines running on separate KVM
hosts and having Mellanox NIC cards. The exception appears to have occurred
during the tcp_default_output function, though I’m not certain of the exact
root cause.
Unfortunately, crash dumps were not enabled at the time. As such, I only have
the kernel panic messages from dmesg for reference, which I have attached here
Also, I’d like to check whether this is a known issue or if there’s any ongoing
analysis related to it.
--
You are receiving this mail because:
You are the assignee for the bug.