From owner-freebsd-current  Fri Jul  5 23: 0:22 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 7D62D37B401
	for <freebsd-current@freebsd.org>; Fri,  5 Jul 2002 23:00:14 -0700 (PDT)
Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F054F43E31
	for <freebsd-current@freebsd.org>; Fri,  5 Jul 2002 23:00:13 -0700 (PDT)
	(envelope-from julian@elischer.org)
Received: from InterJet.elischer.org ([12.232.206.8])
          by sccrmhc03.attbi.com
          (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP
          id <20020706060013.GPSG903.sccrmhc03.attbi.com@InterJet.elischer.org>;
          Sat, 6 Jul 2002 06:00:13 +0000
Received: from localhost (localhost.elischer.org [127.0.0.1])
	by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA16739;
	Fri, 5 Jul 2002 22:56:43 -0700 (PDT)
Date: Fri, 5 Jul 2002 22:56:41 -0700 (PDT)
From: Julian Elischer <julian@elischer.org>
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: freebsd-current@freebsd.org
Subject: Re: more on dumping
In-Reply-To: <15654.31389.772589.952477@grasshopper.cs.duke.edu>
Message-ID: <Pine.BSF.4.21.0207052242550.16316-100000@InterJet.elischer.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG



On Sat, 6 Jul 2002, Andrew Gallatin wrote:

> 
> 
> 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?
> 

It depends.

the previous thread should have been put back onto the run queue
before the interrupt thread was scheduled.




> 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
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message