Date: Thu, 21 Jun 2001 17:00:45 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: <mjacob@feral.com> Cc: John Baldwin <jhb@FreeBSD.ORG>, <alpha@FreeBSD.ORG> Subject: Re: more panics, with some traceback info.... Message-ID: <15154.24701.724278.688574@grasshopper.cs.duke.edu> In-Reply-To: <20010621081950.Q18589-100000@wonky.feral.com> References: <20010621081950.Q18589-100000@wonky.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This looks very similar to other pmap corruption panics that have been posted in the past.. Is this at boot, or does it take a while for it to panic? Can somebody re-review my pmap_emulate_reference() hacks? Drew Matthew Jacob writes: > > > panic: blockable sleep lock (sleep mutex) Giant @ ../../vm/vm_fault.c:213 > cpuid = 0; panic > db> t > Debugger() at Debugger+0x34 > panic() at panic+0x178 > witness_lock() at witness_lock+0x240 > vm_fault() at vm_fault+0x108 > trap() at trap+0xf78 > XentMM() at XentMM+0x2c > --- memory management fault (from ipl 7) --- > hardclock() at hardclock+0x308 > handleclock() at handleclock+0x22c > alpha_clock_interrupt() at alpha_clock_interrupt+0x68 > interrupt() at interrupt+0xb8 > XentInt() at XentInt+0x28 > --- interrupt (from ipl 0) --- > witness_unlock() at witness_unlock+0x50 > zalloc() at zalloc+0x28c > get_pv_entry() at get_pv_entry+0x70 > pmap_insert_entry() at pmap_insert_entry+0x34 > pmap_enter_quick() at pmap_enter_quick+0x214 > pmap_object_init_pt() at pmap_object_init_pt+0x1b8 > vm_map_insert() at vm_map_insert+0x37c > elf_load_section() at elf_load_section+0x33c > exec_elf_imgact() at exec_elf_imgact+0x528 > execve() at execve+0x274 > syscall() at syscall+0x708 > XentSys() at XentSys+0x64 > --- syscall (59, FreeBSD ELF, execve) --- > --- user mode --- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15154.24701.724278.688574>