Date: Mon, 11 Sep 2023 09:57:25 +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-zBzEPz7DlR@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 #2 from Michael Gmelin <grembo@FreeBSD.org> --- (In reply to Mina Gali=C4=87 from comment #1) It boots okay when using vtnet0, when calling "service dumpon restart" after boot, the machine immediately reboots though. So it seems like something is wrong with aliases. When removing device aliases completely (and vlans, but I think these are unrelated), it boots okay and can be reconfigured (via the service command) after boot as well. Note that this is what it looks like: # service dumpon restart kernel dumps on priority: device 0: /dev/null server address: 192.168.255.1 client address: 192.168.255.3 gateway address: 192.168.255.1 dumpon: getifaddrs: Operation not permitted /etc/rc.d/dumpon: WARNING: unable to specify vtnet0 as a dump device Despite the warning, netdump works correctly (tested via sysctl debug.kdb.panic=3D1). --=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-zBzEPz7DlR>