August 25 HEAD on MIPS32 (routerstation pro) started throwing issues

[Adrian Chadd]

Hi!

I just updated a test AP at home to the latest -HEAD ,and here's what
I was greeted with:

Aug 28 08:07:57 init: login_getclass: unknown class 'daemon'
BAD_PAGE_FAULT: pid 27 tid 100045 (mount), uid 0: pc 0x40514dd0 got a
read fault (type 0x2) at 0x4040011c
Trapframe Register Dump:
        zero: 0 at: 0x7fffffff  v0: 0   v1: 0x404000fc
        a0: 0x54        a1: 0x40400000  a2: 0   a3: 0x1
        t0: 0   t1: 0x40c0300c  t2: 0x40800168  t3: 0x2f
        t4: 0x40c00030  t5: 0   t6: 0x748       t7: 0x402c70
        t8: 0x13        t9: 0x40514d58  s0: 0x3 s1: 0x40418798
        s2: 0   s3: 0x404ec4    s4: 0x40418798  s5: 0x40418798
        s6: 0   s7: 0   k0: 0   k1: 0
        gp: 0x405ec910  sp: 0x7ffee348  s8: 0   ra: 0x4051534c
        sr: 0xfc13      mullo: 0x6719   mulhi: 0xc      badvaddr: 0x4040011c
        cause: 0x8      pc: 0x40514dd0
Page table info for pc address 0x40514dd0: pde = 0x813da000, pte = 0xa00569da
Dumping 4 words starting at pc address 0x40514dd0:
8c700020 32030ff0 00032102 240300ff
Page table info for bad address 0x4040011c: pde = 0x813da000, pte = 0
pid 27 (mount), uid 0: exited on signal 11
BAD_PAGE_FAULT: pid 32 tid 100045 (mount), uid 0: pc 0x40514dd0 got a
read fault (type 0x2) at 0x4040011c
Trapframe Register Dump:
        zero: 0 at: 0x7fffffff  v0: 0   v1: 0x404000fc
        a0: 0x54        a1: 0x40400000  a2: 0   a3: 0x1
        t0: 0   t1: 0x40c0300c  t2: 0x40800168  t3: 0x2f
        t4: 0x40c00030  t5: 0   t6: 0x748       t7: 0x402c70
        t8: 0x13        t9: 0x40514d58  s0: 0x3 s1: 0x40418798
        s2: 0   s3: 0x404ec4    s4: 0x40418798  s5: 0x40418798
        s6: 0   s7: 0   k0: 0   k1: 0
        gp: 0x405ec910  sp: 0x7ffee348  s8: 0   ra: 0x4051534c
        sr: 0xfc13      mullo: 0x6719   mulhi: 0xc      badvaddr: 0x4040011c
        cause: 0x8      pc: 0x40514dd0
Page table info for pc address 0x40514dd0: pde = 0x813d8000, pte = 0xa00569da
Dumping 4 words starting at pc address 0x40514dd0:
8c700020 32030ff0 00032102 240300ff
Page table info for bad address 0x4040011c: pde = 0x813d8000, pte = 0

If I run my startup script commands manually then there's a 50% chance
it'll work and a 50% chance the above occurs.

Does anyone have any ideas? Alan, is there anything recent in the
pmap/VM code churn that may have caused this?



-a