From owner-freebsd-current Mon Jan 12 11:24:11 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA15754 for current-outgoing; Mon, 12 Jan 1998 11:24:11 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA15584; Mon, 12 Jan 1998 11:23:35 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id OAA00277; Mon, 12 Jan 1998 14:23:25 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199801121923.OAA00277@dyson.iquest.net> Subject: Re: random (?) SIGBUS in -current In-Reply-To: from Julian Elischer at "Jan 12, 98 10:31:00 am" To: julian@whistle.com (Julian Elischer) Date: Mon, 12 Jan 1998 14:23:25 -0500 (EST) Cc: phk@freebsd.org, dyson@freebsd.org, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Julian Elischer said: > > kernel from late last night > system got 85% through 'make world' before a process hung in 'D' state. > The rest of the system seemed ok. > > no sign of SIGBUS though. > I cannot reproduce the problem, with testing and compiles on 8MB, 16MB, and 112MB systems. PHK, could you tell me more about your system? Are you running anything special, that I can reproduce the problem? 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.) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig.