Date: Sat, 6 Jul 2002 10:33:43 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Julian Elischer <julian@elischer.org> Cc: freebsd-current@freebsd.org Subject: Re: more on dumping Message-ID: <15654.65479.31155.182179@grasshopper.cs.duke.edu> In-Reply-To: <Pine.BSF.4.21.0207052242550.16316-100000@InterJet.elischer.org> References: <15654.31389.772589.952477@grasshopper.cs.duke.edu> <Pine.BSF.4.21.0207052242550.16316-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15654.65479.31155.182179>