Bug 252795 - Reproducable kernel panic an aarch64 (panic: bad link elm 0xfff.... prev->next != elm)
Summary: Reproducable kernel panic an aarch64 (panic: bad link elm 0xfff.... prev->nex...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: arm (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-arm (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-18 08:24 UTC by Gordon Bergling
Modified: 2021-01-18 16:07 UTC (History)
1 user (show)

See Also:

Attachments
Stacktrace arm64 UFS panic (412.45 KB, image/jpeg)
2021-01-18 16:07 UTC, Gordon Bergling 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gordon Bergling freebsd_committer 2021-01-18 08:24:07 UTC 
I recently hit a reproducible kernel panic an arm64 (RPi4B) while running a kyua test run. After bisecting the tests I narrowed it down to 'sys/netpfil/pf/route_to:v6'.

The FreeBSD revision is b7ab6832cd98 with

arm64: Trim duplicate code from cpu_fork_kthread_handler()
https://reviews.freebsd.org/D28182

and

arm64: Clear FPU flags in the pcb in cpu_copy_thread()
https://reviews.freebsd.org/D28183

applied for KTLS.

Kernel configuration is
include		GENERIC
options		RATELIMIT
options		TCPHPTS
options		ROUTE_MPATH
options		FIB_ALGO
options		KERN_TLS
options		RANDOM_FENESTRASX
device		pass
options		MMCCAM
nodevice	mmc
nodevice	mmcsd
options IOMMU

src.conf is
WITH_MALLOC_PRODUCTION=1
WITH_EXTRA_TCP_STACKS=1
WITH_BEARSSL=1
WITH_PIE=1
WITH_RETPOLINE=1
WITHOUT_CLEAN=1
Comment 1 Ed Maste freebsd_committer 2021-01-18 14:57:34 UTC 
Can you paste the backtrace?
Comment 2 Gordon Bergling freebsd_committer 2021-01-18 16:07:29 UTC 
Created attachment 221710 [details]
Stacktrace arm64 UFS panic

@emaste, I have attached a screenshot of the stack trace. The left part of the screen isn't visible. I have tried to workaround it in config.txt, but I wasn't be able to solve that. If I can provide a short version of the stack trace via ddb, just let me know.