From owner-freebsd-bugs Mon Sep 23 11:25:59 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA26679 for bugs-outgoing; Mon, 23 Sep 1996 11:25:59 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA26662 for ; Mon, 23 Sep 1996 11:25:57 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <16210(8)>; Mon, 23 Sep 1996 11:25:20 PDT Received: from localhost ([127.0.0.1]) by crevenia.parc.xerox.com with SMTP id <177476>; Mon, 23 Sep 1996 11:25:12 -0700 X-Mailer: exmh version 1.6.7 5/3/96 To: "Chris Csanady" cc: freebsd-bugs@freebsd.org Subject: Re: Very disturbing boot block problems.. In-reply-to: Your message of "Tue, 17 Sep 1996 18:33:49 PDT." <199609180133.UAA01881@friley216.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Sep 1996 11:24:59 PDT From: Bill Fenner Message-Id: <96Sep23.112512pdt.177476@crevenia.parc.xerox.com> Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199609180133.UAA01881@friley216.res.iastate.edu>you write: >Error: C:1029 > 1023 (BIOS limit) > >Anyone else ever experienced this? Yup, I experienced this several times some months ago, and never got an explanation that made sense. If I booted kernel.old, and then copied the new kernel to / again, it would generally work after a few tries. There was just some location that would cause the boot blocks to choke. Bill