From owner-freebsd-current Mon Jan 12 12:59:29 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA29491 for current-outgoing; Mon, 12 Jan 1998 12:59:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA29462; Mon, 12 Jan 1998 12:58:55 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id VAA01162; Mon, 12 Jan 1998 21:54:23 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "John S. Dyson" cc: julian@whistle.com, dyson@freebsd.org, current@freebsd.org Subject: Re: random (?) SIGBUS in -current In-reply-to: Your message of "Mon, 12 Jan 1998 15:47:26 EST." <199801122047.PAA00534@dyson.iquest.net> Date: Mon, 12 Jan 1998 21:54:23 +0100 Message-ID: <1160.884638463@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199801122047.PAA00534@dyson.iquest.net>, "John S. Dyson" writes: >Poul-Henning Kamp said: >> >> It looks like some page gets stolen, and the object isn't updated >> accordingly... >> >> >Note that the new code follows the "rules" fairly precisely regarding the >> >vnode free list. Some parts of the system might not be able to deal with >> >it yet (maybe.) >> >> But this would be related to pages, they die with a pagefault... >> >Vnodes, objects and pages are all intimately related to each other. Yes, but the program runs part of the way before it dies, so we're not talking an entire vnode, object, but only a page or two... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!"