From owner-freebsd-current Mon Jan 26 14:39:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10892 for current-outgoing; Mon, 26 Jan 1998 14:39:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10875 for ; Mon, 26 Jan 1998 14:39:33 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA01741; Mon, 26 Jan 1998 17:37:44 -0500 (EST) (envelope-from toor) Message-Id: <199801262237.RAA01741@dyson.iquest.net> Subject: Re: symorder: Cannot allocate memory In-Reply-To: <199801261708.AA07176@gamecock.unx.sas.com> from David Quattlebaum at "Jan 26, 98 12:08:26 pm" To: sasdrq@unx.sas.com (David Quattlebaum) Date: Mon, 26 Jan 1998 17:37:44 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk David Quattlebaum said: > I am trying to build a debug kernel at 3.0-current and keep > getting: > > loading kernel > rearranging symbols > symorder: Cannot allocate memory > There were some problems on earlier versions of 3.0-current. Try something supped very recently. (vfs.ioopt can cause problems very similar to what you are talking about.) -- 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.