Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Dockstar panic with recent -current

On Thursday 20 September 2012 06:13:35 Andy Ruhl wrote:
> Hello all,
> I built a kernel from -current synced as of today (Sept 19), and I'm
> getting a panic.
> I change the SHEEVAPLUG kernel to make it work with the Seagate
> Dockstar as outlined in an email from a few days ago.
> This is what I see:
> WARNING: clock lost 4646 days
> WARNING: using filesystem time
> warning: no /dev/console
> init: copying out path `/sbin/init' 11
> data_abort_handler: data_aborts fsr=0x1 far=0x28207697
> Fatal kernel mode data abort: 'Alignment Fault 1'
> trapframe: 0xc8a4ad00
> FSR=00000001, FAR=28207697, spsr=20000013
> r0 =00000004, r1 =00000000, r2 =c2076010, r3 =00000000
> r4 =28207665, r5 =00000000, r6 =00000000, r7 =c2076010
> r8 =c049b6bc, r9 =00000000, r10=00000000, r11=c8a4ad88
> r12=00000001, ssp=c8a4ad50, slr=c02c0b30, pc =c02c0bbc
> Stopped in pid 2.1 (sh) at      netbsd:uvm_pagealloc_pgfl+0xbc: ldrh    r3, 
> [r4, #0x32]
> db> bt

r4 = 0x28207665 - this is a strange kernel address. In fact it looks more like 
"ev (".
I compiled a SHEEVAPLUG kernel locally and could see any instances of that 
string. Maybe
you can get look at the memory around 0xc2076010 (r2)

netbsd:uvm_pagealloc_pgfl+0x68: ldr     r4, [r2, r1]
netbsd:uvm_pagealloc_pgfl+0x6c: add     r12, r5, #0x00000001
netbsd:uvm_pagealloc_pgfl+0x70: cmp     r4, #0x00000000
netbsd:uvm_pagealloc_pgfl+0x74: bne     netbsd:uvm_pagealloc_pgfl+0xbc
netbsd:uvm_pagealloc_pgfl+0xbc: ldrh    r3, [r4, #0x32]


Home | Main Index | Thread Index | Old Index