Date: Fri, 14 Aug 2009 15:47:16 +0200 From: Ian FREISLICH <ianf@clue.co.za> To: Ruslan Ermilov <ru@FreeBSD.org> Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, FreeBSD current mailing list <current@freebsd.org> Subject: Re: panic in netisr (I think) + DUMP FAILED (ERROR 6) Message-ID: <E1Mbx7k-0001zP-UW@clue.co.za> In-Reply-To: <20090814120602.GA64565@edoofus.dev.vega.ru> References: <20090814120602.GA64565@edoofus.dev.vega.ru> <20090814080044.A93661@maildrop.int.zabbadoz.net> <E1MbqAJ-0001Cm-0j@clue.co.za> <E1MbsRG-0001Ra-AY@clue.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
Ruslan Ermilov wrote: > On Fri, Aug 14, 2009 at 10:47:05AM +0200, Ian FREISLICH wrote: > > Do you have any idea why kernel dumps are not working as shown in > > the OP? > > > There was a message, "Attempt to write outside dump device boundaries.", > that explains that. Search the mailing list archives where I explained > the underlying bug with current versions of FreeBSD (in short page maps > get updated while we're writing a dump, due to interrupts still enabled). And then, this bug is probably why my dumps have been unusable since about 12 months now? These (2) servers have a continuous interrupt rate in excess of 40k/s, network related, so interrupts during dumping are highly likely. Reading that thread I'm given to believe that the problem exists only for mini-dumps. I've had crashes without cores with (and without) mini-dumps enabled, but I've only recently started capturing console output, so I'll see what happens on its next crash. They reliably crash at least once a week. Ian -- Ian Freislich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1Mbx7k-0001zP-UW>