Re: Panic at init on arm (Seagate Dockstar) with -current

[Andy Ruhl <acruhl%gmail.com@localhost>]

On Sat, Oct 20, 2012 at 11:46 AM, matthew green <mrg%eterna.com.au@localhost> 
wrote:
> what is the bt here?  can you try a kernel with
> LOCKDEBUG option?  this looks more like a usb
> issue than an arm issue.

Here is the bt, and I'll have LOCKDEBUG output shortly:

db> bt
netbsd:vpanic+0x10
        scp=0xc01f8f58 rlv=0xc01f91f0 (netbsd:printf_nolog)
        rsp=0xc8a2ba70 rfp=0xc8a2ba84
        r7=0xc034ea90
netbsd:panic+0x14
        scp=0xc01f91e0 rlv=0xc01f19a4 (netbsd:lockdebug_abort+0x78)
        rsp=0xc8a2ba98 rfp=0xc8a2bac0
netbsd:lockdebug_abort+0x10
        scp=0xc01f193c rlv=0xc011a4dc (netbsd:mutex_abort+0x2c)
        rsp=0xc8a2bac4 rfp=0xc8a2bad0
        r7=0x00000080 r6=0xc047faec
        r5=0xc048f170 r4=0xc048f168
netbsd:mutex_abort+0x10
        scp=0xc011a4c0 rlv=0xc011a6f8 (netbsd:mutex_enter+0x68)
        rsp=0xc8a2bad4 rfp=0xc8a2bb00
netbsd:mutex_enter+0x10
        scp=0xc011a6a0 rlv=0xc0136154 (netbsd:tc_ticktock+0x3c)
        rsp=0xc8a2bb04 rfp=0xc8a2bb14
        r10=0x00000000 r9=0x00000006
        r8=0x00000000 r7=0x00000080 r6=0xc047faec r5=0xc2351d20
        r4=0xc048f168
netbsd:tc_ticktock+0x10
        scp=0xc0136128 rlv=0xc0101ce4 (netbsd:hardclock+0xc0)
        rsp=0xc8a2bb18 rfp=0xc8a2bb2c
        r4=0xc8a2bbf0
netbsd:hardclock+0x10
        scp=0xc0101c34 rlv=0xc0162554 (netbsd:clockhandler+0x10)
        rsp=0xc8a2bb30 rfp=0xc8a2bb3c
        r5=0xc047fae4 r4=0xc22d23c8
netbsd:clockhandler+0x10
        scp=0xc0162554 rlv=0xc01a745c (netbsd:pic_dispatch+0x34)
        rsp=0xc8a2bb40 rfp=0xc8a2bb5c
netbsd:pic_dispatch+0x10
        scp=0xc01a7438 rlv=0xc01a77e8 (netbsd:pic_do_pending_ints+0x2d4)
        rsp=0xc8a2bb60 rfp=0xc8a2bbc8
        r6=0xc047faec r5=0xc047fae4
        r4=0x00000001
netbsd:pic_do_pending_ints+0x10
        scp=0xc01a7524 rlv=0xc0161b50 (netbsd:mvsoc_irq_handler+0x74)
        rsp=0xc8a2bbcc rfp=0xc8a2bbec
        r10=0x00000012 r9=0xc2347b0c
        r8=0x00000000 r7=0x0000009e r6=0xc8a2bbf0 r5=0x00000000
        r4=0x00000001
netbsd:mvsoc_irq_handler+0x10
        scp=0xc0161aec rlv=0xc00febec (netbsd:irq_entry+0x6c)
        rsp=0xc8a2bbf0 rfp=0xc8a2bc6c
        r8=0x00000000 r7=0x00000013
        r6=0x00000000 r5=0x00000020 r4=0xc03930d0
c0495090
        scp=0xc0495090 rlv=0x00000000 (0)
        rsp=0x00000001 rfp=0xffffffff
data_abort_handler: data_aborts fsr=0x1 far=0xffffffff
Fatal kernel mode data abort: 'Alignment Fault 1'
trapframe: 0xc8a2b348
FSR=00000001, FAR=ffffffff, spsr=a0000053
r0 =00000001, r1 =ffffffff, r2 =c8a2bc60, r3 =ffffffff
r4 =c0495090, r5 =ffffffff, r6 =c01f98cc, r7 =00000000
r8 =c8a2bbc8, r9 =0000fff3, r10=00000001, r11=c8a2b818
r12=c8a2b2f0, ssp=c8a2b39c, slr=c01f8c4c, pc =c00462d8

Faulted in DDB; continuing...
db>

Andy