From owner-freebsd-current@FreeBSD.ORG Mon Feb 23 08:37:02 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 346F116A4CE for ; Mon, 23 Feb 2004 08:37:02 -0800 (PST) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E29C943D2F for ; Mon, 23 Feb 2004 08:37:01 -0800 (PST) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) i1NGb1Tr020316 for ; Mon, 23 Feb 2004 11:37:01 -0500 (EST) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i1NGb1cl020315 for freebsd-current@freebsd.org; Mon, 23 Feb 2004 11:37:01 -0500 (EST) Date: Mon, 23 Feb 2004 11:37:01 -0500 From: Ken Smith To: freebsd-current@freebsd.org Message-ID: <20040223163701.GB19907@electra.cse.Buffalo.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: 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 16:37:02 -0000 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 up and running a 3-day old kernel. The other two ref machines in the cluster (amd64/sparc64) don't seem to be suffering from whatever this problem is, their daily rebuild/reboot cron jobs have been working fine. Thanks. -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |