From owner-freebsd-current Wed May 15 6:44:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 0564437B408; Wed, 15 May 2002 06:44:21 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA02288; Wed, 15 May 2002 09:44:20 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g4FDhoH26770; Wed, 15 May 2002 09:43:50 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15586.26134.343204.649876@grasshopper.cs.duke.edu> Date: Wed, 15 May 2002 09:43:50 -0400 (EDT) To: Dag-Erling Smorgrav Cc: alpha@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: loader failure In-Reply-To: References: X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes: > Trying to boot with a newly-built loader (make world earlier today > from fresh sources) results in: <..> > boot failure > > no matter which kernel I try to boot. Booting my new kernel with the > old loader (from the DP1 dist) works fine until it tries to start > init(8): <..> > The loader problem is possibly a compiler issue > (since DP1 was built with gcc 2.95 while my world was built with 3.1). > The init problem is probably a UFS2 f*up; the code has obviously not > been tested on a 64-bit architecture (the UFS2 stuff broke the kernel > build). My 2 cents - the kernel & world (including loader) were fine as of Friday (both built with gcc3, modulo the atomic fixes for vm_object.c that jhb / alc / jeff came up with on Saturday). Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message