From owner-freebsd-alpha Tue Oct 13 14:25:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28746 for freebsd-alpha-outgoing; Tue, 13 Oct 1998 14:25:27 -0700 (PDT) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from friley-185-114.res.iastate.edu (friley-185-114.res.iastate.edu [129.186.185.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28715 for ; Tue, 13 Oct 1998 14:25:22 -0700 (PDT) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Received: from friley-185-114.res.iastate.edu (loopback [127.0.0.1]) by friley-185-114.res.iastate.edu (8.9.1/8.9.1) with ESMTP id QAA04010 for ; Tue, 13 Oct 1998 16:25:07 -0500 (CDT) (envelope-from ccsanady@friley-185-114.res.iastate.edu) Message-Id: <199810132125.QAA04010@friley-185-114.res.iastate.edu> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-alpha@FreeBSD.ORG Subject: kernel traps on boot.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 13 Oct 1998 16:25:07 -0500 From: Chris Csanady Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I seem to be having quite a bit of trouble with booting kernels in the last couple of days. It has almost looked random. Currently I have 2 boxes, with identical kernels and boot blocks and one of them simply fails to boot. :( I get the following: 1978288+179496 [32859+1492+246528+139953] Entering /kernel at 0xfffffc0000320500... [ preserving 425904 bytes of kernel symbol table ] Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-BETA #0: Tue Oct 13 14:46:15 CDT 1998 ccsanady@ariel.scl.ameslab.gov:/usr/src/sys/compile/ARIEL EB164 Digital AlphaPC 164LX 533 MHz, 531MHz 8192 byte page size, 1 processor. real memory = 534929408 (522392K bytes) avail memory = 516169728 (504072K bytes) fatal kernel trap: trap entry = 0x4 (unaligned access fault) a0 = 0x2fe00000c3e00003 a1 = 0x28 a2 = 0x1 pc = 0xfffffc0000364640 ra = 0xfffffc0000484358 curproc = 0 ddbprinttrap from 0xfffffc0000364640 ddbprinttrap(0x2fe00000c3e00003, 0x28, 0x1, 0x4) panic: trap panic Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffc000057bb58> db> trace Debugger() at Debugger+0x2c panic() at panic+0xf4 trap() at trap+0x658 XentUna() at XentUna+0x20 parse_module_symbols() at parse_module_symbols+0x38 (null)() at 0x6 db> Regardless, should a alignment trap cause the machine to die? I think in NetBSD, they just print it to the console. Has anyone else noticed similar behavior? Not being able to reliably build a kernel makes it really hard to get things done. I finally have my GNIC II driver mostly working on the alpha too. Oh well.. I think it's a bit late for 3.0 anyways. Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message