From owner-freebsd-current@FreeBSD.ORG Fri Aug 14 12:39:58 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0756D106568C for ; Fri, 14 Aug 2009 12:39:58 +0000 (UTC) (envelope-from ru@FreeBSD.org) Received: from mail.vega.ru (mail.vega.ru [90.156.167.5]) by mx1.freebsd.org (Postfix) with ESMTP id B82838FC55 for ; Fri, 14 Aug 2009 12:39:57 +0000 (UTC) Received: from [10.100.124.99] (port=63174 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MbvXs-0004kJ-5F; Fri, 14 Aug 2009 16:06:08 +0400 Date: Fri, 14 Aug 2009 16:06:02 +0400 From: Ruslan Ermilov To: Ian FREISLICH Message-ID: <20090814120602.GA64565@edoofus.dev.vega.ru> References: <20090814080044.A93661@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: "Bjoern A. Zeeb" , FreeBSD current mailing list Subject: Re: panic in netisr (I think) + DUMP FAILED (ERROR 6) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2009 12:39:58 -0000 On Fri, Aug 14, 2009 at 10:47:05AM +0200, Ian FREISLICH wrote: > "Bjoern A. Zeeb" wrote: > > On Fri, 14 Aug 2009, Ian Freislich wrote: > > > > Hi, > > > > > I finally hooked up a console to this machine because its dumps > > > have been broken or corrupted for many months. Sadly there isn't > > > much more infonmation than this console capture. > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > cpuid = 10; apic id = 0a > > > fault virtual address = 0x1f5cd38 > > ... > > > Uptime: 6d13h28m14s > > > > this has been fixed two days ago. Seeing your uptime you do not have > > the fix. Please update to latest RELENG_8 or HEAD. > > I suspected that. > > 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). Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer