From owner-freebsd-current Mon Dec 31 15:42:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id ECA4137B41B for ; Mon, 31 Dec 2001 15:42:05 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBVNoZj02969; Mon, 31 Dec 2001 15:50:35 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112312350.fBVNoZj02969@mass.dis.org> To: Julian Elischer Cc: current@freebsd.org, msmith@mass.dis.org Subject: Re: anyone seen this? Makes system unbooable. In-Reply-To: Message from Julian Elischer of "Mon, 31 Dec 2001 11:22:17 PST." Date: Mon, 31 Dec 2001 15:50:35 -0800 From: Mike Smith 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 > I upgraded by cvs on saturday night, > Sunday I didn't use it. > Monday I tried to boot it. but the loader says: > ASSERT > and the system reboots > > I'd LOVE to know wha the assert is but really My opical neurons take at > least 20mSecs to fire and by the time I've found the Asssert line > I'm already running on afterimage. > > How about adding a sleep after the Assert write so that it can actually > be read? Is it printing "ASSERT ", or "Assertion failed:"? The string "ASSERT" doesn't exist anywhere in the loader or libstand. If you want to add a pause after an assertion failure (not a bad idea really), do it in src/lib/libstand/assert.c. > In the meanwhile does anyone know what the problem might be.. > I'm recvsuping (I had to boot off a cdrom) and will recompile the > bootblocks, but some idea of the problem might be nice.. You *are* aware that you can boot loader.old by hitting a key while the spinner is paused, before the loader starts, right? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message