From owner-freebsd-alpha Tue Aug 29 13:55:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 750B237B43C for ; Tue, 29 Aug 2000 13:55:06 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id QAA18910; Tue, 29 Aug 2000 16:55:05 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e7TKt5P02160; Tue, 29 Aug 2000 16:55:05 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 29 Aug 2000 16:55:05 -0400 (EDT) To: dfr@nlsystems.com Cc: freebsd-alpha@freebsd.org Subject: panic very early in boot X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14764.7637.838295.31768@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just tried to take my UP1000 to -current. Built the world & used make buildkernel / make installkernel to build the kernel. Sources were current as of 4am EDT. Plus version 1.2 of busspace.c I'm seeing a KSP not valid halt caused by taking a memory management fault very early in the boot process. After editing trap to print out all the faults it takes, I see this as the very first one (and the one that starts the spiral of faults in trap/vm_fault) fatal kernel trap: trap entry = 0x2 (memory management fault) a0 = 0xdeadbeeffeedface a1 = 0x1 a2 = 0x0 pc = 0xfffffc0000628aec ra = 0xfffffc0000628aa8 curproc = 0 This is coming from: (gdb) l *0xfffffc0000628aec 0xfffffc0000628aec is in siocnattach (../../isa/sio.c:3127). 3122 * to have the correct value. Also, if we didn't 3123 * just read the speed from the hardware, then we 3124 * need to set the speed in hardware so that 3125 * switching it later is null. 3126 */ 3127 cfcr = inb(siocniobase + com_cfcr); 3128 outb(siocniobase + com_cfcr, CFCR_DLAB | cfcr); 3129 outb(siocniobase + com_dlbl, 3130 COMBRD(comdefaultrate) & 0xff); 3131 outb(siocniobase + com_dlbh, The machine in question is a UP1000 (irongate chipset). Its running with a serial console.. I'm assuming the problem is with the new busspace. Does the 0xdeadbeeffeedface address mean anything to you? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message