From owner-freebsd-current@FreeBSD.ORG Sun Feb 28 20:56:47 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D866D106564A; Sun, 28 Feb 2010 20:56:47 +0000 (UTC) (envelope-from brampton@gmail.com) Received: from mail-fx0-f223.google.com (mail-fx0-f223.google.com [209.85.220.223]) by mx1.freebsd.org (Postfix) with ESMTP id 219018FC19; Sun, 28 Feb 2010 20:56:46 +0000 (UTC) Received: by fxm23 with SMTP id 23so107572fxm.3 for ; Sun, 28 Feb 2010 12:56:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=9/td5I/+XU9HGh4IIColLZ0DeRzEWyCVmsqXI655hUY=; b=Jd2obOLja39OlrjkKpgdCLSi8QjNTAXtUDsDPd317FZu+3Y7ISVs8XwwL+tMZ3WEqL F6+PpwmObXpJpzpL1mF/PQYt4GUV1KGj9Jr56utGzI2/5z772U9XY+bOVB1tTG6mxb3o UrTXGhUN01qjftgehZON+S0KbQEHKXE79nYzM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; b=KIuVHPqdqKheEK+MrHvMRuSuaNBD06H1PwX/Nes/zmp6YLb4e/Sf4NS9w398u8Ujul Z6APoAZM6xvme87m4tc+NeRilT9U3oe9zTtA5fgMi7EVNKb0OvNLe2LXsJqxudKtPrDM yMyf+sFsj2eMbxI3psZMBAueRTDAMuX94MNR8= MIME-Version: 1.0 Sender: brampton@gmail.com Received: by 10.223.14.71 with SMTP id f7mr2646702faa.48.1267390596591; Sun, 28 Feb 2010 12:56:36 -0800 (PST) Date: Sun, 28 Feb 2010 20:56:36 +0000 X-Google-Sender-Auth: 42d1d40b81104ac0 Message-ID: From: Andrew Brampton To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Attilio Rao Subject: minidump fails on SMP machines 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: Sun, 28 Feb 2010 20:56:47 -0000 Hello, When many interrupts are firing on my amd64 SMP machine, and a panic occurs, dump will fail with the error "Attempt to write outside dump device boundaries". This problem has been discussed before[1][2], and I even filled a PR about it last year[3]. >From what I understand the reason this occurs is because interrupts are not disabled on all cores during the dump. There was even a TODO comment about this in kern_shutdown.c 414 /* XXX This doesn't disable interrupts any more. Reconsider? */ 415 splhigh(); However, looking at my FreeBSD 8.0 and HEAD source, these two lines were removed by commit r196198 by attilio. Now that commit seems to deal with disabling interrupts on other cores, but perhaps not specifically to fix this bug. So my question is, should this dump bug now be fixed? Or should the XXX comment been left in? Or is the dump bug caused by something else? I would appreciate this problem being fixed, as it causes me a lot of headaches when trying to debug my kernel module :(. On a side note, I read that my problem only occurs when using minidump. Is it possible to do a full dump to avoid this problem, if so how? thanks Andrew [1] http://lists.freebsd.org/pipermail/freebsd-current/2008-January/082752.html [2] http://lists.freebsd.org/pipermail/freebsd-current/2008-June/086574.html [3] http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/139614