Assertion failure in -current @ subr_pool.c:2568 on i386 (dual core)

[Geoff Wing <gcw%pobox.com@localhost>]

Anyone else getting this exec'ing /sbin/init?  subr_pool.c:1.164

Without ddb_onpanic=1 it can give something like

init: copying out path `/sbin/init' 11
panic: kernel diagnostic assertion "cur->pcg_avail == cur->pcg_size" failed: 
file "../../../../kern/subr_pool.c", line 2568
Begin traceback...
_prop_dictionary_keysym32_pool(3e,cfcf7500,ffffffff,cfcf74c0,ffffffff,cfd2e680,ffffffff,cfd2e540,ffffffff,cfd2ef80)
 at 0xc2d48e00
uvm_fault(0xc059a040, 0xdeadd000, 1) -> 0xe
fatal page fault in supervisor mode
trap type 6 code 0 eip c0353374 cs 8 eflags 10246 cr2 deaddead ilevel 6
panic: trap
Faulted in mid-traceback; aborting...
dumping to dev 0,1 offset 34567
dump 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 
34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 
7 6 5 4 3 2 1 

With ddb_onpanic=1 it didn't see the "dead*" type addresses but I might
have overlooked them.
It wouldn't give me a proper core (even though it dumped) so these are from
my chicken scratchings:

__kernassert(
pool_cache_put_slow(
pool_cache_put_addr(
pmap_free_pvs(
pmap_do_remove(
uvm_unmap_remove(
uvm_unmap1(
uvmspace_exec(
execve1(
sys_execve(
syscall(


Also, when booting with -a flag (prompt for device, init, etc.) at the
first or second prompt I get a LOCKDEBUG problem, something like:
        Kernel lock error: _kernel_lock: spinout

Any clues?

Regards,
Geoff