Bug 283426

Summary: panic in sbappendaddr_locked()
Product: Base System Reporter: Robin Haberkorn <robin.haberkorn>
Component: kernAssignee: freebsd-net (Nobody) <net>
Status: New ---    
Severity: Affects Many People CC: franco
Priority: --- Keywords: crash, regression
Version: 14.2-RELEASE   
Hardware: amd64   
OS: Any   
Attachments:
Description Flags
Log files from /var/crash and lspci none

Description Robin Haberkorn 2024-12-20 00:38:56 UTC
Created attachment 255963 [details]
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.
Comment 1 Robin Haberkorn 2024-12-20 19:27:13 UTC
It cannot have anything to do with the ethernet driver, since I wasn't connected via ethernet, but via wifi (if_iwm), which is also apparent from the backtrace. So it might have something to do with this driver. I doubt so however since it did not change between 14.1 and 14.2.
Comment 2 Gleb Smirnoff freebsd_committer freebsd_triage 2024-12-24 18:44:16 UTC
Hi! Can you please share the core file in a private email to me?

You may use my PGP key to encrypt your mail:
https://docs.freebsd.org/en/articles/pgpkeys/#_gleb_smirnoff_glebiusfreebsd_org
Comment 3 Robin Haberkorn 2024-12-25 17:37:34 UTC
(In reply to Gleb Smirnoff from comment #2)

I am a bit afraid, that these dumps could contain private information. Perhaps you can tell me what to look for in kgdb instead.