Date: Sun, 5 Mar 2017 21:52:22 -0500 From: Lee D <embaudarm@gmail.com> To: Alexander Tarasikov <alexander.tarasikov@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: How approach debugging a kernel crash? Message-ID: <CANC_bnO-gERs=jf2i7E3BNo5TCQaiq3rFw%2BS4Bqu1hkhpUCHSw@mail.gmail.com> In-Reply-To: <CAMChaFwecuGAojE2mmT4=K-qseAkMBrsEpstgx=xPfJOndmCOA@mail.gmail.com> References: <CANC_bnOUD1TDdrqYWpn4kw4kva8v4q1tpyUAGmm5bpVEU=RDrA@mail.gmail.com> <CAMChaFwecuGAojE2mmT4=K-qseAkMBrsEpstgx=xPfJOndmCOA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you, I will give that a try. I didn't know about the FAR. Lee On Fri, Mar 3, 2017 at 9:57 AM, Alexander Tarasikov < alexander.tarasikov@gmail.com> wrote: > Hi, > the kernel prints the FAR, the fault address register, and the registers. > Looks like it crashes inside the fault handler itself? > > I would go to the "abort_handler" or "exception_exit" and add debugging > prints to UART into there to catch the initial abort. Hope this leads > somewhere > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANC_bnO-gERs=jf2i7E3BNo5TCQaiq3rFw%2BS4Bqu1hkhpUCHSw>