Date: Wed, 18 Feb 2026 19:32:10 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 288345] poudriere run, hanging umounts, system fails to reboot due to hanging processes Message-ID: <bug-288345-227-eCr6z5h9vL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-288345-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=288345 --- Comment #41 from Craig Leres <leres@freebsd.org> --- (In reply to Craig Leres from comment #40) The GENERIC-DEBUG finally produced a panic/crashdump. About 15 minutes into the scheduled poudriere bulk build this morning it panic'ed. The ipmi console showed: panic: not reclaimed nullfs vnode and a kgdb prompt. It clearly had saved the crash dump. Naively I entered "continue" and was relegated to waiting for it to save the crash dump again... Then I entered "reset" and the system rebooted, and saved the crash dump which is now here: https://ee.lbl.gov/.bsd-C6sfr/ I think it's interesting that D state problems most commonly occur during the first ~30 minutes of the build. I know the package build rate is high at first as many quick-to-build ports are built. I'm guessing a test script that repeatedly creates and deletes zfs partitions in the way that poudriere does would trigger this bug. -- 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-288345-227-eCr6z5h9vL>