From owner-freebsd-hackers  Tue Aug 12 21:55:27 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA21145
          for hackers-outgoing; Tue, 12 Aug 1997 21:55:27 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA21140
          for <hackers@FreeBSD.ORG>; Tue, 12 Aug 1997 21:55:25 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id VAA07728;
	Tue, 12 Aug 1997 21:57:34 -0700 (PDT)
Message-Id: <199708130457.VAA07728@implode.root.com>
To: Julian Elischer <julian@whistle.com>
cc: hackers@FreeBSD.ORG
Subject: Re: 2.2.2+ crash.. more info 
In-reply-to: Your message of "Tue, 12 Aug 1997 18:59:07 PDT."
             <33F114EB.167EB0E7@whistle.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 12 Aug 1997 21:57:34 -0700
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>the fact that the process got put on the a sleep queue while it was
>on the runnable queue. suggests that maybe an interrupt driver
>ran 'tsleep' while curproc had the value of this process in it..
>(does it get cleared when the idle process is running, or does it still
>point to the last runnable process?
>(I guess I'll go look at that).

   It gets set to NULL when idle is running.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project