From owner-freebsd-alpha Mon Mar 15 7:43:48 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 768141537E for ; Mon, 15 Mar 1999 07:43:40 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id KAA08390; Mon, 15 Mar 1999 10:43:21 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id KAA90477; Mon, 15 Mar 1999 10:43:07 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 15 Mar 1999 10:43:06 -0500 (EST) To: Thomas Valentino Crimi Cc: alpha@FreeBSD.ORG, paul@originative.co.uk Subject: Re: New bootblocks In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14061.10536.602675.696939@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thomas Valentino Crimi writes: > Excerpts from FreeBSD-Alpha: 15-Mar-99 New bootblocks by > paul@originative.co.uk > > halt code = 2 > > kernel stack not valid halt > > PC = 184ec > > > > > I had this same problem, too, making it worse was that I had played > around with my boot.conf and guess what, unload was halting (in the > older bootblocks, wasn't this recently fixed?) > > One good replacement to fixit disks I found was that the emergecy > shell, while lacking ls (use echo *) did have ifconfig, ppp and > mount_nfs if you happen to have a machine nearby to stick an alpha dist > on for binaries. The way I got my machine to boot doens't seem like > more than luck (replaced bootblocks and booted of an old kernel). Just > wanted to share the fixit trick for all who may come to need it. > In addition to the bootblocks, there's also some breakage in revision 1.24 of kern/kern_lock.c which causes alphas to crash in strange ways just after they print the copyright & before they size memory. I've pointed this out to Julian, and he committed a fix last night. Make sure that you have the latest revision of kern_lock.c. If, for whatever reason, you cannot update your sources the fix was: diff -u -b -B -c -r1.24 kern_lock.c *** kern_lock.c 1999/03/12 03:09:29 1.24 --- kern_lock.c 1999/03/15 00:43:37 *************** *** 215,221 **** * lock itself ). */ if (lkp->lk_lockholder != pid) { ! if (p->p_flag & P_DEADLKTREAT) { error = acquire( lkp, extflags, --- 215,221 ---- * lock itself ). */ if (lkp->lk_lockholder != pid) { ! if (p && (p->p_flag & P_DEADLKTREAT)) { error = acquire( lkp, extflags, Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message