From owner-freebsd-current@FreeBSD.ORG Mon Feb 23 13:43:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F02516A4CE for ; Mon, 23 Feb 2004 13:43:53 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id C55DD43D1D for ; Mon, 23 Feb 2004 13:43:52 -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.12.10/8.12.10) with ESMTP id i1NLhnF6014328 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Feb 2004 16:43:49 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i1NLhiQY063776; Mon, 23 Feb 2004 16:43:44 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16442.29712.148987.927650@grasshopper.cs.duke.edu> Date: Mon, 23 Feb 2004 16:43:44 -0500 (EST) To: Ken Smith In-Reply-To: <20040223163701.GB19907@electra.cse.Buffalo.EDU> References: <20040223163701.GB19907@electra.cse.Buffalo.EDU> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-current@freebsd.org Subject: Re: Alpha ref machine is grumpy... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2004 21:43:53 -0000 Ken Smith writes: > > The alpha architecture reference machine in the cluster has been grumpy > about the -current kernel for the past two days. This is what we're > getting on the console: > > FreeBSD/alpha SRM disk boot, Revision 1.2 > (root@beast.freebsd.org, Mon Feb 23 07:07:25 PST 2004) > Memory: 2097152 k > Loading /boot/defaults/loader.conf > /boot/kernel/kernel data=0x34d3f0+0x3cb60 syms=[0x8+0x50580+0x8+0x40604] > > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > Entering /boot/kernel/kernel at 0xfffffc000033e3e0... > > halted CPU 0 > > halt code = 2 > kernel stack not valid halt > PC = 4 > boot failure > P00>>> > > If anyone has hints what the problem is or if anyone needs me to > do anything to help track it down let me know. It (beast) is back I'm guessing it followed a null function pointer. Maybe the recent device changes had some special affect on alpha. When it crashes, take a look at the return address. Its been a while, but I think its "e RA" at the P00>>> prompt. Drew