Date: Tue, 20 Jan 2026 18:40:17 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 292616] FreeBSD 14 to 15 upgrade reboot loop if watchdogd is enabled Message-ID: <bug-292616-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292616 Bug ID: 292616 Summary: FreeBSD 14 to 15 upgrade reboot loop if watchdogd is enabled Product: Base System Version: 15.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: mandrews@bit0.com Just as an FYI: If watchdogd is enabled -- which it is NOT by default so the impact of this may be low -- during a freebsd-upgrade from FreeBSD 14.x to 15.0, and you are temporarily running the 15 kernel with the 14 userland... then watchdogd will kick in and reboot before you can get far enough in the boot process to actually install the 15 userland. I suspect it's for similar reasons as the existing 15.0 errata about ipfw (bug 291562). Workaround is similar and simple too: simply "sysrc watchdogd_enable=No" before the upgrade and "sysrc watchdogd_enable=Yes" afterwards. This bit me when upgrading some cloud servers a few weeks ago. Fortunately they offered remote KVM so I was able to figure it out pretty fast, boot to single user mode, and manually edit /etc/rc.conf to deal with both that and ipfw. This probably doesn't apply to pkgbase upgrades from 14.3 to 15.0, but then there's an errata about that too. :) I'm not necessarily looking for a fix here since there's an easy workaround and it's a weird non-default config anyway -- it's more of an FYI in case anyone else bumps into this. -- 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-292616-227>