Date: Mon, 16 Jul 2018 15:24:13 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 229167] [Hyper-V] [Jun 19, 2018] Recently FreeBSD VM panics during boot-up, especially with Mellanox VF configured Message-ID: <bug-229167-27103-7AITQwJpHI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229167-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-229167-27103@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=3D229167 --- Comment #27 from pete@twisted.org.uk --- Here is a 'bt' from the last ZFS boot attempt, in case it helps. ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 10.000 msec usb_needs_explore_all: no devclass vmbus0: version 3.0 hvet0: <Hyper-V event timer> on vmbus0 Event timer "Hyper-V" frequency 10000000 Hz quality 1000 storvsc0: <Hyper-V IDE> on vmbus0 storvsc1: <Hyper-V IDE> on vmbus0 hvkbd0: <Hyper-V KBD> on vmbus0 hvheartbeat0: <Hyper-V Heartbeat> on vmbus0 hvkvp0: <Hyper-V KVP> on vmbus0 da0 at blkvsc0 bus 0 scbus2 target 0 lun 0 da0: <Msft Virtual Disk 1.0> Fixed Direct Access SPC-3 SCSI device da0: 300.000MB/s transfers da0: Command Queueing enabled da0: 30720MB (62914560 512 byte sectors) hvshutdown0: da1 at blkvsc1 bus 0 scbus3 target 1 lun 0 da1: <Msft Virtual Disk 1.0> Fixed Direct Access SPC-3 SCSI device da1: 300.000MB/s transfers da1: Command Queueing enabled da1: 32768MB (67108864 512 byte sectors) <Hyper-V Shutdown> on vmbus0 hvtimesync0: <Hyper-V Timesync> on vmbus0 hvtimesync0: RTT hvvss0: <Hyper-V VSS> on vmbus0 hn0: <Hyper-V Network Interface> on vmbus0 hn0: got notify, nvs type 128 hn0: Ethernet address: 00:0d:3a:2e:a3:c7 hn0: link state changed to UP storvsc2: <Hyper-V SCSI> on vmbus0 storvsc3: <Hyper-V SCSI> on vmbus0 pcib1: <Hyper-V PCI Express Pass Through> on vmbus0 WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from zfs:zroot/ROOT/default []... pci1: <PCI bus> on pcib1 mlx4_core0: <mlx4_core> at device 2.0 on pci1 <6>mlx4_core: Mellanox ConnectX core driver v3.4.1 (October 2017) mlx4_core: Initializing mlx4_core mlx4_core0: Detected virtual function - running in slave mode mlx4_core0: Sending reset mlx4_core0: Sending vhcr0 mlx4_core0: HCA minimum page size:512 mlx4_core0: Timestamping is not supported in slave mode mlx4_en mlx4_core0: Activating port:1 mlxen0: Ethernet address: 00:0d:3a:2e:a3:c7 <4>mlx4_en: mlx4_core0: Port 1: Using 4 TX rings mlxen0: link state changed to DOWN <4>mlx4_en: mlx4_core0: Port 1: Using 4 RX rings hn0: link state changed to DOWN <4>mlx4_en: mlxen0: Using 4 TX rings <4>mlx4_en: mlxen0: Using 4 RX rings <4>mlx4_en: mlxen0: Initializing port Fatal trap 12: page fault while in kernel mode cpuid =3D 3; apic id =3D 03 fault virtual address =3D 0x1d8 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff80c6a3ea stack pointer =3D 0x28:0xfffffe00004bb950 frame pointer =3D 0x28:0xfffffe00004bb960 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 0 (vmbusdev) [ thread pid 0 tid 100105 ] Stopped at vrefact+0xa: cmpl $0x4,ll+0x1b7(%r14) db> bt Tracing pid 0 tid 100105 td 0xfffff80004a02580 vrefact() at vrefact+0xa/frame 0xfffffe00004bb960 namei() at namei+0x20d/frame 0xfffffe00004bba20 vn_open_cred() at vn_open_cred+0x213/frame 0xfffffe00004bbb60 linker_load_module() at linker_load_module+0x4cf/frame 0xfffffe00004bbe70 kern_kldload() at kern_kldload+0xf1/frame 0xfffffe00004bbec0 mlx4_request_modules() at mlx4_request_modules+0x93/frame 0xfffffe00004bbf80 mlx4_load_one() at mlx4_load_one+0x3196/frame 0xfffffe00004bc630 mlx4_init_one() at mlx4_init_one+0x410/frame 0xfffffe00004bc690 linux_pci_attach() at linux_pci_attach+0x411/frame 0xfffffe00004bc6f0 device_attach() at device_attach+0x3f3/frame 0xfffffe00004bc730 device_probe_and_attach() at device_probe_and_attach+0x71/frame 0xfffffe00004bc760 bus_generic_attach() at bus_generic_attach+0x18/frame 0xfffffe00004bc780 pci_attach() at pci_attach+0xd5/frame 0xfffffe00004bc7c0 device_attach() at device_attach+0x3f3/frame 0xfffffe00004bc800 device_probe_and_attach() at device_probe_and_attach+0x71/frame 0xfffffe00004bc830 bus_generic_attach() at bus_generic_attach+0x18/frame 0xfffffe00004bc850 vmbus_pcib_attach() at vmbus_pcib_attach+0x95e/frame 0xfffffe00004bc940 device_attach() at device_attach+0x3f3/frame 0xfffffe00004bc980 device_probe_and_attach() at device_probe_and_attach+0x71/frame 0xfffffe00004bc9b0 vmbus_add_child() at vmbus_add_child+0x6a/frame 0xfffffe00004bc9e0 taskqueue_run_locked() at taskqueue_run_locked+0x14c/frame 0xfffffe00004bca= 40 taskqueue_thread_loop() at taskqueue_thread_loop+0x88/frame 0xfffffe00004bc= a70 fork_exit() at fork_exit+0x84/frame 0xfffffe00004bcab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00004bcab0 --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- db> --=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-229167-27103-7AITQwJpHI>