From owner-freebsd-current Mon Jul 15 14:44: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5735637B400 for ; Mon, 15 Jul 2002 14:44:00 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A519043E58 for ; Mon, 15 Jul 2002 14:43:59 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA22797; Mon, 15 Jul 2002 17:43:58 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g6FLhSw50486; Mon, 15 Jul 2002 17:43:28 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15667.16896.808227.270806@grasshopper.cs.duke.edu> Date: Mon, 15 Jul 2002 17:43:28 -0400 (EDT) To: Peter Wemm Cc: freebsd-current@freebsd.org Subject: Re: panic: absolutely cannot call smp_ipi_shootdown with interrupts already disabled In-Reply-To: <20020715211406.451A43811@overcee.wemm.org> References: <15667.13541.978257.347017@grasshopper.cs.duke.edu> <20020715211406.451A43811@overcee.wemm.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Wemm writes: > Eww! Care to confirm that the following works? I was going to just commit > it since it is pretty obvious, but a brief sanity check would probably > be an idea. (beware, xterm cut/paste whitespace damage). > > ddb runs with interrupts disabled and the other cpus halted. We could not > get the 'ack' from the IPI. The panic was real - you'd have locked up hard > if it had not triggered. > > db_write_bytes temporarily changes a local cpu mapping and changes it back > while everything else is frozen. We do not need to do a coherent invalidate. That seems to work. Thanks! Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message