From owner-freebsd-current Sat Jul 6 9:44:51 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 4F51B37B400 for ; Sat, 6 Jul 2002 09:44:50 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07EE543E09 for ; Sat, 6 Jul 2002 09:44:49 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id CAA06979; Sun, 7 Jul 2002 02:44:40 +1000 Date: Sun, 7 Jul 2002 02:50:48 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Andrew Gallatin Cc: Julian Elischer , Subject: Re: more on dumping In-Reply-To: <15654.65479.31155.182179@grasshopper.cs.duke.edu> Message-ID: <20020707024114.A5419-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Sat, 6 Jul 2002, Andrew Gallatin wrote: > Julian Elischer writes: > > 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. > > Could it have anything to do with interrupt preemption being disabled on > alpha & enabled on i386? Very likely. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message