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 Message-ID: <Pine.BSF.4.21.0207052242550.16316-100000@InterJet.elischer.org> In-Reply-To: <15654.31389.772589.952477@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0207052242550.16316-100000>