From owner-freebsd-alpha Tue Mar 2 2: 2:38 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id BBBED14C58; Tue, 2 Mar 1999 02:02:31 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA83921; Tue, 2 Mar 1999 10:01:46 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 2 Mar 1999 10:01:46 +0000 (GMT) From: Doug Rabson To: Gary Palmer Cc: alpha@freebsd.org Subject: Re: new kernel -> panic In-Reply-To: <94672.920340214@gjp.erols.com> 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 Mon, 1 Mar 1999, Gary Palmer wrote: > > Haven't updated my build box in a while, so decided to build myself a > new kernel. Got an interesting result. boot -v output enclosed: > > ... > > unexpected machine check: > > mces = 0x1 > vector = 0x660 > param = 0xfffffc0000006060 > pc = 0xfffffc0000430a4c > ra = 0xfffffc000033dd78 > curproc = 0 > > panic: machine check > > Apart from the isp0 errors (which I don't remember), that panic isn't > good :) > > Anyone got any ideas? Thanks, Could you figure out what the closest symbols to the pc and ra in the error report are. That should show what bit of code is causing the machine check. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message