On Wed, Jan 16, 2002 at 04:06:14PM -0800, Jason R Thorpe wrote:

 > On Tue, Jan 15, 2002 at 02:46:05PM -0800, John Clark wrote:
 > 
 >  > Stopped in pid 0 (swapper) at   0xa0321d20:[u]vm_fault(0xa0366aec, 
 >  > a01e0000, 3,
 >  > 0) -> e
 >  > Unhandled trap (frame = 0xa01dba74)
 >  > Data abort: 'Translation fault (page)' status=007 address=a01e0000 
 >  > PC=a0321b80
 >  >       Stopped in pid 0 (swapper) at   0
 >  > xa0321b80:[u]vm_fault(0xa0366aec, a01e0000, 3, 0) -> e
 > 
 > ...
 > 
 > Okay, DDB seems to be slightly broken on ARM at the moment (is this true
 > for all ARM ports?  Can others speak up, please?).  I'm investigating.

Alright, there were some ... kind of silly bugs in the ARM DDB code.  Not
quite sure when they snuck in, but the DDB bits work now, at least:

NetBSD/evbarm (groovy-jumbo-jet.shagadelic.org) (console)

login: ~Stopped at      cpu_Debugger+0x10:      ldmdb   r11, {r11, r13, r15}
db> trace
cpu_Debugger+0xc
        scp=0xa0322650 rlv=0xa02063bc (comintr+0x10c)
        rsp=0xa4667d40 rfp=0xa4667d84
comintr+0xc
        scp=0xa02062bc rlv=0xa034bedc (nextinchain)
        rsp=0xa4667d88 rfp=0x00000000
        r10=0x00000008 r9=0x00000003
        r8=0x00000008 r7=0xa03b7c40 r6=0xa1084f00 r5=0xa034bd1c
        r4=0xa03b6820
db> c


NetBSD/evbarm (groovy-jumbo-jet.shagadelic.org) (console)

login: 


So, please update your sources again, and let's see if we can't track
down the cause of the panic, now :-)

You want to have:

	$NetBSD: pmap.c,v 1.34 2002/01/17 03:06:21 thorpej Exp $
	$NetBSD: db_interface.c,v 1.14 2002/01/17 03:52:06 thorpej Exp $

-- 
        -- Jason R. Thorpe <thorpej@wasabisystems.com>