From owner-freebsd-alpha@FreeBSD.ORG Sun Mar 6 17:38:33 2005 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE91516A4CE for ; Sun, 6 Mar 2005 17:38:33 +0000 (GMT) Received: from mx1.irtnog.org (ns1.irtnog.org [24.123.13.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7538F43D31 for ; Sun, 6 Mar 2005 17:38:33 +0000 (GMT) (envelope-from xenophon@irtnog.org) Received: from localhost (unknown [127.0.0.1]) by mx1.irtnog.org (Postfix) with ESMTP id 961A42181 for ; Sun, 6 Mar 2005 12:39:28 -0500 (EST) Received: from mx1.irtnog.org ([127.0.0.1]) by localhost (mx1.irtnog.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 69153-03 for ; Sun, 6 Mar 2005 12:36:59 -0500 (EST) Received: from irtnog.org (svr1.irtnog.org [10.63.0.100]) by mx1.irtnog.org (Postfix) with ESMTP id 5544020A8 for ; Sun, 6 Mar 2005 12:36:53 -0500 (EST) Content-class: urn:content-classes:message Date: Sun, 6 Mar 2005 12:35:51 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Thread-Topic: SRM error "kernel stack not valid halt" after rebooting FreeBSD 5.3 on AS2000 thread-index: AcUicvC/Er7pz/jPSEqsrTR1ZGHJzA== From: "Matthew X. Economou" To: X-Virus-Scanned: amavisd-new at irtnog.org Subject: SRM error "kernel stack not valid halt" after rebooting FreeBSD 5.3 on AS2000 X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Mar 2005 17:38:33 -0000 Speaking of boot problems, when I reboot my AlphaServer 2000 (running FreeBSD 5.3-RELEASE), the firmware loops, repeating the following messages: halted CPU 0 halt code =3D 2 kernel stack not valid halt PC =3D 0 CPU 0 restarting I cannot break into the console (neither via control-C, nor via a serial line hard break). I must hit the reset switch in order to continue. This can be most inconvenient as I do not always have physical access to this server. Is this a problem with FreeBSD or with the firmware? I realize I need to upgrade 5.3-RELEASE-p5 at there are at least two security-related bugs in 5.3-RELEASE. A cursory Google search resulted only in a number of posts about trying to install NetBSD, OpenBSD, FreeBSD, or Linux onto unsupported hardware. This error only happens after I halt the operating system. Best wishes, Matthew=20 --=20 "The challenge of a moral life is to do nothing that requires forgiveness." - Roger Ebert in his review of _The Woodsman_