tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: diagnostic assertion "anon->an_lock == amap->am_lock"



On Thu, 16 Jun 2011 15:17:32 +0100
Mindaugas Rasiukevicius <rmind%netbsd.org@localhost> wrote:

> Can you please get a backtrace?

I'm now running a more recent kernel (from yesterday morning). This
time it hit `"pmap == curpmap" failed: file
"/build/src/sys/arch/x86/x86/pmap.c", line 757`

I should mention that this is a replaced motherboard that hasn't been
stress tested with builds before 5.99.53. Maybe I should try running a
5.99.52 for a while?

Anyway, backtraces are:
cpu0:
breakpoint()
panic()
kern_assert()
pmap_map_ptes()
pmap_extract()
uvm_fault_internal()
trap()

cpu1:
lapic_gettick()
lapic_delay()
panic()
mi_switch()
sleepq_block()
cv_wait()
rf_RaidIOThread()

cpu2:
?()

cpu3:
kmem_poison_fill()
kmem_free()
netbsd_elf64_signature()
netbsd_elf64_probe()
exec_elf64_makecmds()
check_exec()
execve1()
syscall()

Again, let me know what, if any, more useful info to provide.

kind regards
dieter


> 
> Thanks.
> 
> -- 
> Mindaugas


Home | Main Index | Thread Index | Old Index