[Bug 228750] panic on zfs mirror removal

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Oct 15 00:28:53 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228750

--- Comment #14 from Roger Hammerstein <cheeky.m at live.com> ---
(In reply to Allan Jude from comment #13)

actually there is no panic on the console.


kgdb /boot/kernel/kernel /var/crash/vmcore.2


Unread portion of the kernel message buffer:




Fatal trap 12: page fault while in kernel mode
Fatal trap 12: page fault while in kernel mode

cpuid = 19; apic id = 26

fault virtual address   = 0x0
fault code              = supervisor read data, page not present

instruction pointer     = 0x20:0xffffffff8243df34

Fatal trap 12: page fault while in kernel mode
stack pointer           = 0x28:0xfffffe023ca77750
frame pointer           = 0x28:0xfffffe023ca77780
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         = 0 (zio_free_issue_2_3)
trap number             = 12
panic: page fault
cpuid = 19
KDB: stack backtrace:
#0 0xffffffff80b40df7 at kdb_backtrace+0x67

#1 0xffffffff80afa337 at vpanic+0x177
#2 0xffffffff80afa1b3 at panic+0x43
#3 0xffffffff80f7c38f at trap_fatal+0x35f
#4 0xffffffff80f7c3e9 at trap_pfault+0x49
#5 0xffffffff80f7ba8c at trap+0x29c
#6 0xffffffff80f5bfcc at calltrap+0x8
#7 0xffffffff824bc89b at vdev_indirect_io_start+0x9b
#8 0xffffffff824e9fa9 at zio_vdev_io_start+0x2a9
#9 0xffffffff824e68ec at zio_execute+0xbc
#10 0xffffffff824e61fb at zio_nowait+0xcb
#11 0xffffffff824c248f at vdev_mirror_io_start+0x41f
#12 0xffffffff824e9e5c at zio_vdev_io_start+0x15c
#13 0xffffffff824e68ec at zio_execute+0xbc
#14 0xffffffff80b52694 at taskqueue_run_locked+0x154
#15 0xffffffff80b537f8 at taskqueue_thread_loop+0x98
#16 0xffffffff80abd963 at fork_exit+0x83
#17 0xffffffff80f5cf8e at fork_trampoline+0xe

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-fs mailing list