From owner-freebsd-current Fri Jul 5 22: 6: 6 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 2067437B400 for ; Fri, 5 Jul 2002 22:06:05 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6200C43E3B for ; Fri, 5 Jul 2002 22:06:04 -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 BAA08641 for ; Sat, 6 Jul 2002 01:06:03 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g6655XM29951; Sat, 6 Jul 2002 01:05:33 -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: <15654.31389.772589.952477@grasshopper.cs.duke.edu> Date: Sat, 6 Jul 2002 01:05:33 -0400 (EDT) To: freebsd-current@freebsd.org Subject: more on dumping 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 OK, current is really confusing me. When we are panic'ing and syncing disks, how are we supposed to come back to the current thread which caused the dump after we do an mi_switch() to allow an interrupt thread to run? The alpha seems to get stuck running various sorts of kernel processes, but it never comes back to the one that caused the dump. How is this supposed to work? Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message