I've created a 10.3-BETA2 image for Google Compute Engine using swills' script and am getting a panic on boot when the VM is configured with Local SSD as NVMe (--local-ssd interface="NVME"). This is a regression from 10.2-RELEASE which will boot successfully with an identical configuration. """ Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x60 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80e16019 stack pointer = 0x28:0xfffffe01bfff59c0 frame pointer = 0x28:0xfffffe01bfff59e0 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 = 12 (irq11: virtio_pci0+) [ thread pid 12 tid 100039 ] Stopped at nvme_ctrlr_intx_handler+0x39: cmpq $0,0x60(%rdi) db> bt Tracing pid 12 tid 100039 td 0xfffff8000422e000 nvme_ctrlr_intx_handler() at nvme_ctrlr_intx_handler+0x39/frame 0xfffffe01bfff59e0 intr_event_execute_handlers() at intr_event_execute_handlers+0xab/frame 0xfffffe01bfff5a20 ithread_loop() at ithread_loop+0x96/frame 0xfffffe01bfff5a70 fork_exit() at fork_exit+0x9a/frame 0xfffffe01bfff5ab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe01bfff5ab0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- """
Is have an inkling that r293673 may be at fault here, can you try reverting that change and see if it fixes the issue? On 22/02/2016 16:35, Andy Carrel via freebsd-stable wrote:> I've created a 10.3-BETA2 image for Google Compute Engine using swills' > script and am getting a panic on boot when the VM is configured with Local > SSD as NVMe (--local-ssd interface="NVME"). This is a regression from > 10.2-RELEASE which will boot successfully with an identical configuration. > > """ > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x60 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff80e16019 > stack pointer = 0x28:0xfffffe01bfff59c0 > frame pointer = 0x28:0xfffffe01bfff59e0 > 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 = 12 (irq11: virtio_pci0+) > [ thread pid 12 tid 100039 ] > Stopped at nvme_ctrlr_intx_handler+0x39: cmpq $0,0x60(%rdi) > db> bt > Tracing pid 12 tid 100039 td 0xfffff8000422e000 > nvme_ctrlr_intx_handler() at nvme_ctrlr_intx_handler+0x39/frame > 0xfffffe01bfff59e0 > intr_event_execute_handlers() at intr_event_execute_handlers+0xab/frame > 0xfffffe01bfff5a20 > ithread_loop() at ithread_loop+0x96/frame 0xfffffe01bfff5a70 > fork_exit() at fork_exit+0x9a/frame 0xfffffe01bfff5ab0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe01bfff5ab0 > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > """ > _______________________________________________ > freebsd-stable at freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
On 23/02/2016 3:35 AM, Andy Carrel via freebsd-stable wrote:> I've created a 10.3-BETA2 image for Google Compute Engine using swills' > script and am getting a panic on boot when the VM is configured with Local > SSD as NVMe (--local-ssd interface="NVME"). This is a regression from > 10.2-RELEASE which will boot successfully with an identical configuration. > > """ > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x60 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff80e16019 > stack pointer = 0x28:0xfffffe01bfff59c0 > frame pointer = 0x28:0xfffffe01bfff59e0 > 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 = 12 (irq11: virtio_pci0+) > [ thread pid 12 tid 100039 ] > Stopped at nvme_ctrlr_intx_handler+0x39: cmpq $0,0x60(%rdi) > db> bt > Tracing pid 12 tid 100039 td 0xfffff8000422e000 > nvme_ctrlr_intx_handler() at nvme_ctrlr_intx_handler+0x39/frame > 0xfffffe01bfff59e0 > intr_event_execute_handlers() at intr_event_execute_handlers+0xab/frame > 0xfffffe01bfff5a20 > ithread_loop() at ithread_loop+0x96/frame 0xfffffe01bfff5a70 > fork_exit() at fork_exit+0x9a/frame 0xfffffe01bfff5ab0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe01bfff5ab0 > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > """Hi Andy, Could you please create a Bugzilla issue for this. I've created a '10.3-BETA2' version so it can be tracked -- Regards Kubilay Bugmeister