From owner-freebsd-current@FreeBSD.ORG Mon Feb 23 13:12:31 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 BB42C16A4CE for ; Mon, 23 Feb 2004 13:12:31 -0800 (PST) Received: from tea.blinkenlights.nl (tea.blinkenlights.nl [62.58.162.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7268343D1D for ; Mon, 23 Feb 2004 13:12:31 -0800 (PST) (envelope-from sten@blinkenlights.nl) Received: by tea.blinkenlights.nl (Postfix, from userid 101) id A7DA723B; Mon, 23 Feb 2004 22:07:47 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by tea.blinkenlights.nl (Postfix) with ESMTP id 948E61BD; Mon, 23 Feb 2004 22:07:47 +0100 (CET) Date: Mon, 23 Feb 2004 22:07:47 +0100 (CET) From: Sten Spans To: Ken Smith In-Reply-To: <20040223163701.GB19907@electra.cse.Buffalo.EDU> Message-ID: References: <20040223163701.GB19907@electra.cse.Buffalo.EDU> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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:12:31 -0000 On Mon, 23 Feb 2004, Ken Smith wrote: > > 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. same problem here, on a ds10. I initially blamed it one ule, but it seems to be something else introduced a few days ago. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem