From owner-freebsd-alpha Wed Oct 18 9:22: 1 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.cafes.net (mail.cafes.net [207.65.182.25]) by hub.freebsd.org (Postfix) with ESMTP id B121337B4E5; Wed, 18 Oct 2000 09:21:58 -0700 (PDT) Received: from mail.cafes.net (mail.cafes.net [207.65.182.25]) by mail.cafes.net (8.9.3/8.9.3) with ESMTP id LAA17085; Wed, 18 Oct 2000 11:21:56 -0500 Date: Wed, 18 Oct 2000 11:21:56 -0500 (CDT) From: Mike Eldridge To: John Baldwin Cc: freebsd-alpha@FreeBSD.org Subject: Re: Alpha 4.x releases (production quality?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 18 Oct 2000, John Baldwin wrote: > On 18-Oct-00 Mike Eldridge wrote: > > On Wed, 18 Oct 2000, Kris Kirby wrote: > >> Would a general concensus of the folks on -alpha agree that FreeBSD 4.x > >> for the Alpha is stable enough for a production server? > > > > I wouldn't. I can't even get the thing installed. The kernel panics as > > it's trying to boot. Linux runs fine on it. I've looked for help, but I > > can't find any. Oh well, back to Linux I guess. :) > > The kernel doesn't panic on boot, the loader does. The SRM message you get > (kernel stack not valid halt) is treating the loader as the kernel. The loader runs fine, it prints out "Entering kernel at " and it starts to come up, prints out the kernel build date, etc, and then panics after printing out about 50 "dec_axppci_33_intr_map: bad interrupt pin 192" messages. I can't find any information anywhere about what's going on. I've tried two different identical alphas and they both do the same thing. Mike ----------------------------------------------------- Save the whales. Feed the hungry. Free the mallocs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message