On Wednesday, October 11, 2017 05:18:17 PM grarpamp wrote: > Let 12.0-current r324306 amd64 efi boot from usb to installer screen, > try to write zeroes to an unallocated part of ada0, mount -uw a > separate part of ada0 ... > > 1st 0xc5ce5f0 ufs kern/vfs_mount.c:1274 > 2nd 0xc565b78 devfs ufs/ffs/ffs_vfsops.c:1414 > > db_trace_self_wrapper > vpanic > kassert_panic+0x126 > g_access+0x2b9/frame 0xfffffe0458a31550 > ffs_mount+0x1092/frame 0xfffffe0458a31700 > vfs_donmount+0x13b8/frame 0xfffffe0458a31940 > sys_nmount+0x72/frame 0xfffffe0458a31980 > amd64_syscall+0x79b/frame 0xfffffe0458a3a1b0 > Xfast_syscall+0xfb/frame 0xfffffe0458a31ab0 > syscall (378, FreeBSD ELF64, sys_nmount), rip = 0x800a88d6a, rsp = > 0x7fffffffd428, rbp = 0x7fffffffd990 > kdb_enter+0x3b: movq $0,kdb_why
In this case the panic is separate from the LOR, and for a panic we really need the panic message in addition to the stack trace. -- John Baldwin _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
