Re: LOR panic on mount -uw

2017-10-13 Thread grarpamp 
On Thu, Oct 12, 2017 at 11:15 AM, John Baldwin  wrote:
> 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.

With release kernels stack trace appears with this
message, then it sits in ddb, forget how to print panic?

panic: access but not attached


With snapshots, both panic and stacktrace print
but it doesn't ddb and goes straight to reboot. I forget
how to make those enter ddb or 15sec countdown?

In interim..
fatal trap 12 page fault while in kernel mode
supervosor read data page not present
process = mount


I did file a ticket with script so anyone with a blank
usb stick can recreate locally.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222948
___
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"

Re: LOR panic on mount -uw

2017-10-13 Thread grarpamp 
On Wed, Oct 11, 2017 at 5:18 PM, grarpamp  wrote:
> Let 12.0-current r324306 amd64 efi boot from usb to installer screen,

Another way to trigger this one is
boot snapshot install media single user verbose
mdmfs -s 10m md /mnt
umount -v /mnt
[LOR stack backtrace, remains usable]
___
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"

Re: LOR panic on mount -uw

2017-10-12 Thread John Baldwin 
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 0xfe0458a31550
> ffs_mount+0x1092/frame 0xfe0458a31700
> vfs_donmount+0x13b8/frame 0xfe0458a31940
> sys_nmount+0x72/frame 0xfe0458a31980
> amd64_syscall+0x79b/frame 0xfe0458a3a1b0
> Xfast_syscall+0xfb/frame 0xfe0458a31ab0
> syscall (378, FreeBSD ELF64, sys_nmount), rip = 0x800a88d6a, rsp =
> 0x7fffd428, rbp = 0x7fffd990
> 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"

LOR panic on mount -uw

2017-10-11 Thread grarpamp 
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 0xfe0458a31550
ffs_mount+0x1092/frame 0xfe0458a31700
vfs_donmount+0x13b8/frame 0xfe0458a31940
sys_nmount+0x72/frame 0xfe0458a31980
amd64_syscall+0x79b/frame 0xfe0458a3a1b0
Xfast_syscall+0xfb/frame 0xfe0458a31ab0
syscall (378, FreeBSD ELF64, sys_nmount), rip = 0x800a88d6a, rsp =
0x7fffd428, rbp = 0x7fffd990
kdb_enter+0x3b: movq $0,kdb_why
___
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"