Date: Fri, 13 Oct 2017 02:28:53 -0400 From: grarpamp <grarpamp@gmail.com> To: freebsd-current@freebsd.org Subject: Re: LOR panic on mount -uw Message-ID: <CAD2Ti2_jLvg5D3-67SqLkzONeN3=mhOWfQtdzZx=OTVhgjJ6Ug@mail.gmail.com> In-Reply-To: <2176358.5m1KsgFnXX@ralph.baldwin.cx> References: <CAD2Ti2-6W_b04fHen5XHiT-bFQZ9CncZptUbDP0yaHbg7gjnUA@mail.gmail.com> <2176358.5m1KsgFnXX@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 12, 2017 at 11:15 AM, John Baldwin <jhb@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD2Ti2_jLvg5D3-67SqLkzONeN3=mhOWfQtdzZx=OTVhgjJ6Ug>