VM lock panic on PandaBoard

Tim Kientzle tim at kientzle.com
Fri Aug 29 03:32:40 UTC 2014


Tried today to get my PandaBoard running again.  The Crochet board config needed a couple of minor tweaks but then it seems to build okay.  First boot lasted a few minutes before it panicked, but then I rebuilt a new kernel (enabling WITNESS and INVARIANTS) and things are looking worse.

This is -CURRENT r270695 with the PANDABOARD config, where the boot halts with the below message and backtrace.  I also notice that second processor doesn’t seem to be launching.  Anyone need any more information before I put this back in the closet?

(I’ll be away for the weekend, so may not be able to provide additional info until Tuesday night after work.)


Starting file system checks:
/dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/mmcsd0s2a: clean, 3664195 free (531 frags, 457958 blocks, 0.0% fragmentation)
Mounting local file systems:.
panic: Lock vm object not exclusively locked @ /usr/src/sys/vm/vm_map.c:4054

cpuid = 0
KDB: enter: panic
[ thread pid 99 tid 100045 ]
Stopped at      $d:     ldrb    r15, [r15, r15, ror r15]!
db> bt
Tracing pid 99 tid 100045 td 0xc3dd1320
db_trace_self() at db_trace_self
         pc = 0xc05079ec  lr = 0xc0231bb0 (db_stack_trace+0xf4)
         sp = 0xefad03b8  fp = 0xefad03d0
        r10 = 0xc08e5b0c
db_stack_trace() at db_stack_trace+0xf4
         pc = 0xc0231bb0  lr = 0xc0231520 (db_command+0x270)
         sp = 0xefad03d8  fp = 0xefad0478
         r4 = 0x00000000  r5 = 0x00000000
         r6 = 0x00000000
db_command() at db_command+0x270
         pc = 0xc0231520  lr = 0xc0231284 (db_command_loop+0x60)
         sp = 0xefad0480  fp = 0xefad0490
         r4 = 0xc054eaa2  r5 = 0xc056a2c3
         r6 = 0xc08e5af8  r7 = 0xefad0660
         r8 = 0x00000000  r9 = 0xc05ff918
        r10 = 0xc0641df4
db_command_loop() at db_command_loop+0x60
         pc = 0xc0231284  lr = 0xc0233c4c (db_trap+0xd8)
         sp = 0xefad0498  fp = 0xefad05b8
         r4 = 0x00000000  r5 = 0xc08e5b04
         r6 = 0xc0641e18
db_trap() at db_trap+0xd8
         pc = 0xc0233c4c  lr = 0xc039bd20 (kdb_trap+0x15c)
         sp = 0xefad05c0  fp = 0xefad05e0
         r4 = 0x00000000  r5 = 0x00000001
         r6 = 0xc0641e18  r7 = 0xefad0660
kdb_trap() at kdb_trap+0x15c
         pc = 0xc039bd20  lr = 0xc051f680 (undefinedinstruction+0x2a4)
         sp = 0xefad05e8  fp = 0xefad0658
         r4 = 0x00000000  r5 = 0x00000000
         r6 = 0xc051f32c  r7 = 0xe7ffffff
         r8 = 0xc3dd1320  r9 = 0xc039b48c
        r10 = 0xefad0660
undefinedinstruction() at undefinedinstruction+0x2a4
         pc = 0xc051f680  lr = 0xc05096d4 (exception_exit)
         sp = 0xefad0660  fp = 0xefad06b8
         r4 = 0xc056a318  r5 = 0x00000001
         r6 = 0xc0633970  r7 = 0xc0633b08
         r8 = 0xefad06f4  r9 = 0xc08e759c
        r10 = 0xc3dd1320
exception_exit() at exception_exit
         pc = 0xc05096d4  lr = 0xc039b480 (kdb_enter+0x40)
         sp = 0xefad06b0  fp = 0xefad06b8
         r0 = 0xc0641e04  r1 = 0x00000000
         r2 = 0xc056de7c  r3 = 0x000000aa
         r4 = 0xc056a318  r5 = 0x00000001
         r6 = 0xc0633970  r7 = 0xc0633b08
         r8 = 0xefad06f4  r9 = 0xc08e759c
        r10 = 0xc3dd1320 r12 = 0x00000000
$a() at $a
         pc = 0xc039b490  lr = 0xc0362958 (vpanic+0x130)
         sp = 0xefad06c0  fp = 0xefad06e0
         r4 = 0x00000100
vpanic() at vpanic+0x130
         pc = 0xc0362958  lr = 0xc03629c8 (kproc_shutdown)
         sp = 0xefad06e8  fp = 0xefad06ec
         r4 = 0xc3f71dd0  r5 = 0x00000fd6
         r6 = 0xc058c073  r7 = 0xc3f71dc0
         r8 = 0x20051000  r9 = 0xc0b0b9e0
        r10 = 0xc3f749b0
kproc_shutdown() at kproc_shutdown
         pc = 0xc03629c8  lr = 0x00000000 (0)
         sp = 0xefad06f4  fp = 0xefad0720
         r4 = 0xc03629c8  r5 = 0xefad06f4
Unable to unwind into user mode



More information about the freebsd-arm mailing list