Waiting for DAD to complete for statically configured addresses...
Starting dhcpcd.
[ 30.0045097] uvm_fault(0x809baa20, c000, 2) -> e
[ 30.0145099] Fatal kernel mode data abort: 'Translation Fault (S)'
[ 30.0145099] trapframe: 0xbd6ffcf0
[ 30.0245102] FSR=00000805, FAR=0000c110, spsr=20050013
[ 30.0245102] r0 =0000c100, r1 =00000000, r2 =901d6000, r3 =00000000
[ 30.0345103] r4 =90b73070, r5 =00000000, r6 =00000000, r7 =809582f0
[ 30.0345103] r8 =00000000, r9 =808779c0, r10=00000000, r11=bd6ffd64
[ 30.0445106] r12=901d6000, ssp=bd6ffd40, slr=90b7307c, pc =8037b8d4
Stopped in pid 190.1 (sleep) at netbsd:uvm_pagefree+0x200: strne lr, [r0,
#0x010]
db{3}>
This of course is not good. Why this now? Things worked well the first 3 or so
times I booted it up. I see another dangerous "rabbit hole" involved with trying
to troubleshoot this. I had hoped to run "pkgsrc" using this new NetBSD system,
but I may need to rethink that in order to avoid going off on a tangent.
Now it is happy and running again. Three times is gave the above fault while booting, but now it has been sitting here for several hours running. Due to the fault I have a persistent error on the root filesystem check. I need to learn how to fix that (I can't just runs fsck on root with the system running). I tried this:
shutdown now fsck /dev/rld0a
And now it is back to giving me the fault on a reboot. It seems to blow up more often that boot successfully. This is not a system we can use for anything real.
Kyu / tom@mmto.org