Date: Sun, 1 Jun 2003 07:55:00 -0700 (PDT) From: Julian Elischer <julian@elischer.org> To: Martin Blapp <mb@imp.ch> Cc: freebsd-current@freebsd.org Subject: Re: vm-related panic with 5.1RC1 Message-ID: <Pine.BSF.4.21.0306010751530.4662-100000@InterJet.elischer.org> In-Reply-To: <20030601112540.V94836@cvs.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 1 Jun 2003, Martin Blapp wrote: > > Hi all, > > I just got this panic during compile of openoffice > > Fatal trap 12 while in kernel mode > fault virtual address = 0x68 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0271f4d > stack pointer = 0x10:0xe6e51ab0 > frame pointer = 0x10:0xe6e51ae0 > code segement = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32, gran 1 > processor flags = interrupt enabled, resume, IOPL =1 > current process = 22362 > kernel: type 12 trap, code=0 > Stopped at _mtx_lock_sleep+0x16d: movl 0x68(%ecx),%edx > db> trace > _mtx_lock_sleep(c082f0b0,0,0,0,c0678415) at _mtx_lock_sleep+0x16d > vm_map_delete(c082f000, d0d0d000, d0d11000, e6effda0, c78d5720) at vm_map_delete+0x383) > vm_map_remove(c082f000, d0d0d000, d0d11000, e6e51b9c, c03b247f) at vm_map_remove+0x58) > kmem_free(c082f000, d0d0d000, 3000, 0, 80) at kmem_free+0x32 > cpu_thread_clean(c78d54c0, e6e51bb4,c78d54c0, c78d54c0, e6e51be4) at > cpu_thread_clean+0x7f > thread_free(c78d54c0, e6e51bd0, c0275839, c67a3000, c6abf030) at thread_free+0x14 > thread_reap(c78d55f0) at thread_reap+0x16c > thread_wait(c656b000, ffffffff, 0, c03feb34,0) at thread_wait+0x55 > wait1(c6569980, e6e51d10, 0, e6e51d40, c03b0dfa) at wait1+0x738 > wait5(c6569980, e6e51d10, 10, c6569980, 4) at wait4+0x20 > syscall(2f, 2f, 2f, bfbff074, 325) at syscall+0x2aa > Xint0x80_syscall() at Xint0x80_syscall()+0x1d > --- syscall (7, FreeBSD ELF32, wait4) eip = 0x807b28b, esp = 0xbfbfefbc, > ebp = 0xbfbfefd8) > > Unfortunatly my partition was too small, so I could not get a dump. I've > adjusted this now and the next time it panics I'll have one ready. This is with KSE right? I've seen this.. but never when I'm ready for it.. The 0xd0d11000 is always there.. it seems to be a symptom of the problem. It' probably an important clue.. I think it indicates a garbage pointer fo some type. > > Martin > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0306010751530.4662-100000>