Bruce Evans writes:
> 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 t
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 afte
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 all
Bruce Evans 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
> > thr
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?
>
> The alpha seems to get
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.
th
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
