Date: Mon, 02 Oct 2023 13:13:01 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 273715] dumpon: Kernel panic on boot when enabling dumpon over IP Message-ID: <bug-273715-227-9BqrHpxx9A@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273715-227@https.bugs.freebsd.org/bugzilla/> References: <bug-273715-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273715 --- Comment #8 from Michael Gmelin <grembo@FreeBSD.org> --- (In reply to Mark Johnston from comment #6) Hi, Thank you for the fix. I just checked, in 13.1 rcorder was: /etc/rc.d/sysctl /etc/rc.d/natd /etc/rc.d/dhclient /etc/rc.d/dumpon while on 13.2 rcorder is: /etc/rc.d/sysctl /etc/rc.d/natd /etc/rc.d/dumpon /etc/rc.d/dhclient So on 13.1, dumpon was called after interface renaming takes, while on 13.2, device renaming happens after dumpon is started (which exposed the bug). Without checking in more detail, this sounds like a plausible explanation. It also means, that - even after applying the fix - it's not possible to ha= ve a dumpon configuration in /etc/rc.conf that will work during runtime (service dumpon start) and also on boot, in case a renamed interface is used. This s= eems like something that would be worth addressing. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273715-227-9BqrHpxx9A>