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

[SAITOH Masanobu <msaitoh%execsw.org@localhost>]

(2012/09/28 1:57), SAITOH Masanobu wrote:
>  Hi.
> 
> (2012/09/27 2:59), Andy Ruhl wrote:
>> Hello all,
>>
>> I posted this on port-arm a few weeks ago and I have someone helping
>> me look at it, but I figured I would post again.
>>
>> My Seagate Dockstar has a panic with -current. The last time I built a
>> good kernel was August 23rd. I noticed a lot of changes since then.
>>
>> Here is what I see:
>>
>> cprng sysctl: WARNING insufficient entropy at creation.
>> boot device: <unknown>
>> root on sd0a dumps on sd0b
>> WARNING: clock lost 4652 days
>> WARNING: using filesystem time
>> WARNING: CHECK AND RESET THE DATE!
>> warning: no /dev/console
>> init: copying out path `/sbin/init' 11
>> fixup: pm 0xc2f1d8a8, va 0xbfffe000, ftype 2 - nothing to do!
>> fixup: l2 0xc22bcdc8, l2b 0xc22bce80, ptep 0xc22b8bf8, pl1pd 0xc04b2ffc
>> fixup: pte 0x7790ffe, l1pd 0x7fc0831, last code 0x17
>> Stopped in pid 1.1 (init) at    netbsd:cpu_Debugger+0x4:        bx      r14
>> db> bt
>> netbsd:pmap_fault_fixup+0x10
>>         scp=0xc01b72f4 rlv=0xc006371c (netbsd:data_abort_handler+0x384)
>>         rsp=0xc8a3fde0 rfp=0xc8a3fe4c
>>         r10=0xbfffe000 r9=0x00000002
>>         r8=0x00000017 r7=0xc8a3e000 r6=0x00000000 r5=0xc2f152c0
>>         r4=0xc8a3fe50
>> netbsd:data_abort_handler+0x10
>>         scp=0xc00633a8 rlv=0xc005532c (netbsd:address_exception_entry+0x50)
>>         rsp=0xc8a3fe50 rfp=0xc8a3ffac
>>         r10=0xc04c6e48 r9=0x00000000
>>         r8=0x00000001 r7=0x00000013 r6=0x0000002f r5=0x00000000
>>         r4=0xc03a2530
>> netbsd:start_init+0x10
>>         scp=0xc00e5310 rlv=0xc0037254 (netbsd:lwp_trampoline+0x14)
>>         rsp=0xc8a3ffb0 rfp=0x00000000
>>         r10=0xc04c6e48 r9=0xffffffff
>>         r8=0x00000005 r7=0x00000010 r6=0x00000000 r5=0xc2f152c0
>>         r4=0xc00e5300
>> db>
>>
>> I can run some other commands if needed. I'm not very experienced with
>> C or debuggers so I might need very basic instructions.
>>
>> Thanks.
>>
>> Andy
> 
> I have the same problem. In my experience, just typing "c<CR>" continue
> the processing since yesterday. The following commit is required to do
> this:
> 
>> Module Name: src
>> Committed By:        matt
>> Date:                Wed Sep 26 18:18:08 UTC 2012
>>
>> Modified Files:
>>      src/sys/arch/arm/arm32: pmap.c
>>
>> Log Message:
>> If we get a fault we shouldn't have, set pmap_needs_pte_sync and retry.
>>
>>
>> To generate a diff of this commit:
>> cvs rdiff -u -r1.237 -r1.238 src/sys/arch/arm/arm32/pmap.c
>>
>> Please note that diffs are not public domain; they are subject to the
>> copyright notices on the relevant files.


 This problem was disappeard by arm/arm32/pmap.c rev. 1.240.


-- 
-----------------------------------------------
                SAITOH Masanobu (msaitoh%execsw.org@localhost
                                 msaitoh%netbsd.org@localhost)