[Bug 273715] dumpon: Kernel panic on boot when enabling dumpon over IP

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 11 Sep 2023 09:32:34 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273715

            Bug ID: 273715
           Summary: dumpon: Kernel panic on boot when enabling dumpon over
                    IP
           Product: Base System
           Version: 13.2-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: grembo@FreeBSD.org

Basic setup:

Host running bhyve vms. VMs use dumpon over IP to write crash dumps to the VM
host. This used to work ok in 13.1 (booting these machines using a 13.1 kernel
still works). With 13.2, dumpon (ironically) causes a panic on boot.

Configuration:

ifconfig_vtnet0_name="uplink"
ifconfig_uplink="inet 192.168.255.3/24"
defaultrouter="192.168.255.1"

vlans_uplink="vlanone vlantwo"

create_args_vlanone="vlan 1001"
ifconfig_vlanone="inet 10.1.1.1/24"

create_args_vlantwo="vlan 1002"
ifconfig_vlantwo="inet 10.1.2.1/24"

dumpdev="uplink"
dumpon_flags="-k /root/netdump_public.pem -i 0 -c 192.168.255.3 -s
192.168.255.1 -g 192.168.255.1"


Panic:


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x500
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff80deea11
stack pointer           = 0x28:0xfffffe00f7fda9a0
frame pointer           = 0x28:0xfffffe00f7fda9d0
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 26 (dumpon)
trap number             = 12
panic: page fault
cpuid = 0
time = 1694419470
KDB: stack backtrace:
#0 0xffffffff80c53e45 at kdb_backtrace+0x65
#1 0xffffffff80c067c1 at vpanic+0x151
#2 0xffffffff80c06663 at panic+0x43
#3 0xffffffff810b1fa7 at trap_fatal+0x387
#4 0xffffffff810b1fff at trap_pfault+0x4f
#5 0xffffffff81088ed8 at calltrap+0x8
#6 0xffffffff80def0c6 at netdump_ioctl+0x4c6
#7 0xffffffff80a9d736 at devfs_ioctl+0xc6
#8 0xffffffff80cf91d4 at vn_ioctl+0x1a4
#9 0xffffffff80a9ddee at devfs_ioctl_f+0x1e
#10 0xffffffff80c748fd at kern_ioctl+0x26d
#11 0xffffffff80c745e0 at sys_ioctl+0x100
#12 0xffffffff810b289c at amd64_syscall+0x10c
#13 0xffffffff810897eb at fast_syscall_common+0xf8
Uptime: 1s

When commenting out dumpon in /etc/rc.conf, the vm boots just fine.

-- 
You are receiving this mail because:
You are the assignee for the bug.