From owner-freebsd-alpha Fri Sep 15 19:20:15 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id DC30C37B422; Fri, 15 Sep 2000 19:20:13 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id TAA42547; Fri, 15 Sep 2000 19:20:09 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009160220.TAA42547@pike.osd.bsdi.com> Subject: Re: Loader badly broken on the alpha In-Reply-To: from Matthew Jacob at "Sep 15, 2000 06:51:06 pm" To: mjacob@feral.com Date: Fri, 15 Sep 2000 19:20:09 -0700 (PDT) Cc: alpha@FreeBSD.ORG, dcs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote: > > And you just noticed? Hello? What the hell do you think I've been saying... I heard you, which is why I wasn't surprised when it died on me, but I hadn't seen it myself yet. Also, I tried to pinpoint what revision broke it but failed in my attempts to do so and wanted to try to communicate that to hopefully make it easier to pinpoint when it did actually break. If that makes any sense. > On Fri, 15 Sep 2000, John Baldwin wrote: > > > Well, after a rather long and frustrating afternoon, it seems that > > revision of the loader after Fri Sep 8 16:30 2000 UTC is broken for > > the alpha arch. I've tried to narrow things down to see if it was just > > the 4th changes or the pnp changes, but have been unable to get anything > > to boot except for a binary and 4th files from that date. I've even > > tried removing all of the 4th stuff and /boot/loader.rc and the newer > > loader binaries still break. Every time they break, they trigger a > > kernel stack not valid fault. My guess is that ficl is recursing in an > > infinite loop somewhere, that it is recursing too deeply and using up > > all available memory, or that something is failing to handle error conditions > > and is dereferencing a NULL pointer. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message