From owner-freebsd-current Tue Apr 21 09:48:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11244 for freebsd-current-outgoing; Tue, 21 Apr 1998 09:48:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from euthyphro.uchicago.edu (euthyphro.uchicago.edu [128.135.21.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11139 for ; Tue, 21 Apr 1998 16:48:00 GMT (envelope-from sfarrell@phaedrus.uchicago.edu) Received: from phaedrus.uchicago.edu (phaedrus [128.135.21.10]) by euthyphro.uchicago.edu (8.8.6/8.8.4) with ESMTP id LAA26952; Tue, 21 Apr 1998 11:47:51 -0500 (CDT) Received: (from sfarrell@localhost) by phaedrus.uchicago.edu (8.8.8/8.8.5) id LAA28660; Tue, 21 Apr 1998 11:47:50 -0500 (CDT) To: Stephen McKay Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: vm_page_free: freeing busy page References: <199804210540.PAA08950@troll.dtir.qld.gov.au> From: sfarrell+lists@farrell.org Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 21 Apr 1998 11:47:50 -0500 In-Reply-To: Stephen McKay's message of "Tue, 21 Apr 1998 15:40:48 +1000" Message-ID: <87n2dfp1e1.fsf@phaedrus.uchicago.edu> Lines: 16 X-Mailer: Gnus v5.6.3/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen McKay writes: > So, I'm stumped. Any body else got any good ideas? Well, no, but I got a question: in freebsd current, what prevents the kernel from reallocating a process' memory after it calls exit() and before it is finished freeing its memory up? I'm reading in the 4.4BSD book p. 155 that they raise the interrupt level, and I understand that doesn't work for SMP. So presumably there is some new mechanism for this in current? (which might be related to this crash??) -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message