From owner-freebsd-alpha Sat Jan 9 04:56:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26592 for freebsd-alpha-outgoing; Sat, 9 Jan 1999 04:56:25 -0800 (PST) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26568 for ; Sat, 9 Jan 1999 04:56:22 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id MAA30996; Sat, 9 Jan 1999 12:57:13 GMT Date: Sat, 9 Jan 1999 12:57:13 +0000 (GMT) From: Doug Rabson To: Wilko Bulte cc: FreeBSD-alpha mailing list Subject: Re: porting to EB64+ / Alpine In-Reply-To: <199901090024.BAA09214@yedi.iaf.nl> 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 Sat, 9 Jan 1999, Wilko Bulte wrote: > I hacked a bit on the EB64+ bits taken from NetBSD and I am as far as > getting: > > boot: ethernet address: 00:00:f8:20:7f:45 > netbbinfo invalid > boot: ethernet address: 00:00:f8:20:7f:45 > netbbinfo invalid > boot: ethernet address: 00:00:f8:20:7f:45 > /kernel data=0x1de1d8+0x27e60 syms=[0x8+0x405d8+0x8+0x2bcd2] > Entering kernel at 0xfffffc0000320500... > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.0-CURRENT #1: Wed Dec 30 22:07:15 CET 1998 > root@axp33.iaf.nl:/usr/src/sys/compile/ALPINE > EB64+ > Alpha 21064A Evaluation Board 274 MHz, 274MHz > 8192 byte page size, 1 processor. > CPU: EV45 (21064A) major=6 minor=2 > OSF PAL rev: 0x100070002012d > real memory = 65028096 (63504K bytes) > avail memory = 58335232 (56968K bytes) > Preloaded elf kernel "kernel" at 0xfffffc0000576000. > apecs0: > isa0 > Probing for devices on PCI bus 0: > ncr0: rev 0x01 int a irq 7 on pci0.5.0 > de0: rev 0x23 int a irq 0 on pci0.6.0 > de0: DEC 21040 [10Mb/s] pass 2.3 > de0: address 00:00:f8:20:7f:45 > vga0: rev 0x16 int a irq 1 on pci0.7.0 > chip0: rev 0x03 on pci0.8.0 > mcclock0: at port 0x70-0x71 on isa0 > sc0 at port 0x60-0x6f irq 1 on isa0 > sc0: CGA <16 virtual consoles, flags=0x0> > sio0 at port 0x3f8-0x3ff irq 4 on isa0 > sio0: type 16550A > sio1: reserved for low-level i/o > panic: possible stack overflow > > panic > Stopped at Debugger..ng+0x24: ldq ra,0(sp) > <0xfffffc0000578230> 698b8,sp=0xfffffc0000578230> > db> > > I have also seen 'panic: clock not attached'. As I'm trying to find my way > around in the kernel source tree I appreciate any hints. This usually happens if an interrupt is enabled but not handled. The interrupt exception tries to return but is immediately reentered with a few bytes less stack. You would get the "clock not attached" if mcclock isn't probed properly but I can see that its present in your dmesg. Strange. -- 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