[Bug 283426] panic in sbappendaddr_locked()
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 283426] panic in sbappendaddr_locked()"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 20 Dec 2024 00:38:56 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283426
Bug ID: 283426
Summary: panic in sbappendaddr_locked()
Product: Base System
Version: 14.2-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: kern
Assignee: bugs@FreeBSD.org
Reporter: robin.haberkorn@googlemail.com
Created attachment 255963
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255963&action=edit
Log files from /var/crash and lspci
I had two similar kernel panics in 4 days. It's apparently caused by or
triggered by the processing of incoming UDP packets. The source(?) port appears
to have been 43780 in both cases.
Looking through the backtrace, I cannot easily explain this.
# uname -a
FreeBSD thinkpad-x270 14.2-RELEASE FreeBSD 14.2-RELEASE
releng/14.2-n269506-c8918d6c7412 GENERIC amd64
This bug never ever happened on 14.1, pointing to a regression.
I attached `lspci -vvxxx` as well. The network driver is em(4).
Next, I will try intel-em-kmod.
Since I219-LM is not a particularly rare adapter, I assume this might affect
many people.
I have the vmcore files as well, but they are large (around 2GB), so I will
upload them somewhere only on request.
--
You are receiving this mail because:
You are the assignee for the bug.