From owner-freebsd-ppc@FreeBSD.ORG  Sat Jan  6 10:38:41 2007
Return-Path: <owner-freebsd-ppc@FreeBSD.ORG>
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 285B216A407
	for <freebsd-ppc@freebsd.org>; Sat,  6 Jan 2007 10:38:41 +0000 (UTC)
	(envelope-from andrew@fubar.geek.nz)
Received: from fep03.xtra.co.nz (fep03.xtra.co.nz [210.54.141.243])
	by mx1.freebsd.org (Postfix) with ESMTP id B51E813C44C
	for <freebsd-ppc@freebsd.org>; Sat,  6 Jan 2007 10:38:37 +0000 (UTC)
	(envelope-from andrew@fubar.geek.nz)
Received: from serv.int.fubar.geek.nz ([222.155.174.46])
	by fep03.xtra.co.nz with ESMTP
	id <20070106103829.QQGL16699.fep03.xtra.co.nz@serv.int.fubar.geek.nz>
	for <freebsd-ppc@freebsd.org>; Sat, 6 Jan 2007 23:38:29 +1300
Date: Sat, 6 Jan 2007 23:38:22 +1300
From: Andrew Turner <andrew@fubar.geek.nz>
To: freebsd-ppc@freebsd.org
Message-ID: <20070106233822.7d70be78@hermies.int.fubar.geek.nz>
X-Mailer: Claws Mail 2.6.1 (GTK+ 2.10.6; i386-portbld-freebsd6.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: 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 <freebsd-ppc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ppc>,
	<mailto:freebsd-ppc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ppc>
List-Post: <mailto:freebsd-ppc@freebsd.org>
List-Help: <mailto:freebsd-ppc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ppc>,
	<mailto:freebsd-ppc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Jan 2007 10:38:41 -0000

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