Date: Mon, 06 Jul 2015 10:58:51 -0600 From: jd1008 <jd1008@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: best way to debug kernel panic on remote machine Message-ID: <559AB3CB.3010703@gmail.com> In-Reply-To: <559AA88E.3080407@gmx.com> References: <559AA88E.3080407@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/06/2015 10:10 AM, Nikos Vassiliadis wrote: > Hi, > > I have a system on a hosting provider and it panics. Any ideas how > to debug this without asking the provider to install serial cables? > I am thinking of reproducing the panic locally but there might be > an easier way. > > Thanks in advance, > Nikos > _______ Hi Nikos. Been there done that. Only way to debug a kernel panic on a remote machine is to first make sure that the remote machine's kernel is built to save the coredump and the krenel file copy into a crashdump directory. In addition, it would also require that the kernel be built with full debug enabled, and it symbols NOT STRIPPED!!! This way, the crashdump analyzer program will be able to show you the source lines of code.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?559AB3CB.3010703>