From owner-freebsd-ppc@FreeBSD.ORG Sat Jan 6 17:44:44 2007 Return-Path: X-Original-To: freebsd-ppc@freebsd.org Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9834716A416 for ; Sat, 6 Jan 2007 17:44:44 +0000 (UTC) (envelope-from matt@genesi-usa.com) Received: from mail.genesi-usa.com (mithrandir.softwarenexus.net [66.98.186.96]) by mx1.freebsd.org (Postfix) with ESMTP id 7BE7513C448 for ; Sat, 6 Jan 2007 17:44:44 +0000 (UTC) (envelope-from matt@genesi-usa.com) Received: from 82-36-241-164.cable.ubr02.brom.blueyonder.co.uk ([82.36.241.164] helo=[192.168.1.136]) by mail.genesi-usa.com with esmtpa (Exim 4.63 (FreeBSD)) (envelope-from ) id 1H3FQz-000Dt1-8B; Sat, 06 Jan 2007 17:34:21 +0000 Message-ID: <459FE009.1000705@genesi-usa.com> Date: Sat, 06 Jan 2007 17:44:41 +0000 From: Matt Sealey User-Agent: Thunderbird 2.0b1 (Windows/20061206) MIME-Version: 1.0 To: Andrew Turner References: <20070106233822.7d70be78@hermies.int.fubar.geek.nz> In-Reply-To: <20070106233822.7d70be78@hermies.int.fubar.geek.nz> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org Subject: Re: More on the EFIKA X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Jan 2007 17:44:44 -0000 "loaded before boot" by that do you mean they're in there from the firmware or you're assuming the FreeBSD boot loader does it? -- Matt Sealey Genesi, Manager, Developer Relations Andrew Turner wrote: > I have got a little further at booting on an EFIKA. > > I noticed there are already TLB exception handlers loaded before boot. > Using these I can read and write to an address in virtual memory. On > the second write the kernel will panic with: > > panic: mtx_lock() of spin mutex (null) > @ /a/andrew/freebsd/efika/sys/kern/kern_sx.c:172 > KDB: enter: panic > [thread pid 0 tid 0 ] > Stopped at 0x29f3dc: lwz r11, r1, 0x0 > db> bt > Tracing pid 0 tid 0 td 0x4d89d8 > 0x0048cc00: at panic+0x134 > 0x0048cca0: at _mtx_lock_flags+0xb4 > 0x0048ccd0: at _sx_xlock+0x40 > 0x0048ccf0: at _vm_map_lock_read+0x40 > 0x0048cd00: at vm_map_lookup+0x90 > 0x0048cd40: at vm_fault+0xb0 > 0x0048ce30: at trap_pfault+0x170 > 0x0048ce60: at trap+0x23c > 0x0048cf00: at powerpc_interrupt+0xac > 0x0048cf20: kernel DSI write trap @ 0xd0005000 by powerpc_init+0x410: > srr1=0x3032 r1=0x48cfd0 cr=0x20004024 xer=0 ctr=0x101a5f0 > dsisr=0x42000000 0x0048cfd0: at powerpc_init+0x404 > 0x0048d000: at __start+0x90 > db> > > Removing the reads/writes I can the kernel up to the call to > vm_mem_init in the system initialization tasks. The panic is identical > to the one above. > > Has anyone got any ideas as to where I can look to fix this panic? > > Andrew > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org"