Date: Fri, 11 Jun 2010 10:31:22 +0200 From: Jeremie Le Hen <jeremie@le-hen.org> To: Roman Bogorodskiy <bogorodskiy@gmail.com> Cc: Jeff Roberson <jroberson@jroberson.net>, current@freebsd.org Subject: Re: ffs_copyonwrite panics Message-ID: <20100611083122.GJ47836@felucia.tataz.chchile.org> In-Reply-To: <20100524112140.GB18511@rbogorodskiy> References: <20100518185201.GA2745@fsol> <alpine.BSF.2.00.1005190112030.1398@desktop> <20100523032720.GA89739@dirtyvegas> <alpine.BSF.2.00.1005231746040.1398@desktop> <20100524112140.GB18511@rbogorodskiy>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Roman, On Mon, May 24, 2010 at 03:21:41PM +0400, Roman Bogorodskiy wrote: > I am not sure how to save coredump as when the system boots after the > crash and starts saving coredump from swap partition to disk the system > crashes again. > > Generally, the system is almost unusable and in order to try a new > kernel I cross-compile it on my i386 laptop and copy in using livefs > cdrom. > > Do you have an idea how to save a trace? Sorry for the late reply. If you're still undergoing this issue, once your kernel has crashed and dumped his memory, you can reboot using your previously working kernel. You will be able to save the core to the disk. Regards, -- Jeremie Le Hen Humans are born free and equal. But some are more equal than others. Coluche
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100611083122.GJ47836>