Date: Sat, 13 Jun 2026 20:48:12 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 291294] panic during shutdown in callout_process Message-ID: <bug-291294-227-DFLdDjA6yJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-291294-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291294 Bjoern A. Zeeb <bz@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Not A Bug --- Comment #3 from Bjoern A. Zeeb <bz@FreeBSD.org> --- Well it is a bug but nothing compiled as part of the system yet. It's a LinuxKPI driver apparently not cancelling delayed work upon detach or rather scheduling it again afterwards... fault virtual address = 0xfffffe00a6297638 .. db> show dwork_log # dwork wq (NULL == cancelled) 214 0xfffffe00a6297600 0xfffff80003271700 -- state 1 timer delay 8 callout 0xfffffe00a6297638 .. << 213 0xfffffe00a6297600 0x0 -- state 0 idle delay 0 callout 0xfffffe00a6297638 .. << 212 0xfffffe00a6297600 0xfffff80003271700 -- state 1 timer delay 8 callout 0xfffffe00a6297638 .. << 211 0xfffffe00a6297600 0x0 -- state 0 idle delay 0 callout 0xfffffe00a6297638 .. << 210 0xfffffe00a6297600 0xfffff80003271700 -- state 1 timer delay 8 callout 0xfffffe00a6297638 .. << 209 0xfffffe00a6297600 0x0 -- state 0 idle delay 0 callout 0xfffffe00a6297638 .. << 208 0xfffffe00a6290978 0x0 -- state 0 idle delay 0 callout 0xfffffe00a62909b0 .. 207 0xfffffe00a6290978 0xfffff80003271580 -- state 1 timer delay 25 callout 0xfffffe00a62909b0 .. << 206 0xfffffe00a6297600 0xfffff80003271700 -- state 1 timer delay 8 callout 0xfffffe00a6297638 .. << 205 0xfffffe00a6297600 0xfffff80003271700 -- state 1 timer delay 2 callout 0xfffffe00a6297638 .. << 204 0xfffffe00a6297600 0xfffff80003271700 -- state 1 timer delay 8 callout 0xfffffe00a6297638 .. << I've by now looked up the work function as well so I know what to beat up... Not sure yet if there is any sane cleanup going on and one just does not notice as the other ones happen on a way lower frequency. Anyway, it's nothing in main yet so I am closing this for good for now. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-291294-227-DFLdDjA6yJ>