From owner-freebsd-current@FreeBSD.ORG Sun Jun 1 07:56:23 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B98737B401 for ; Sun, 1 Jun 2003 07:56:23 -0700 (PDT) Received: from sccrmhc11.attbi.com (sccrmhc11.attbi.com [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8CAB43FDD for ; Sun, 1 Jun 2003 07:55:02 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([12.232.168.4]) by attbi.com (sccrmhc11) with ESMTP id <20030601145501011006rh8te>; Sun, 1 Jun 2003 14:55:01 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id HAA73412; Sun, 1 Jun 2003 07:55:00 -0700 (PDT) Date: Sun, 1 Jun 2003 07:55:00 -0700 (PDT) From: Julian Elischer To: Martin Blapp In-Reply-To: <20030601112540.V94836@cvs.imp.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: vm-related panic with 5.1RC1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jun 2003 14:56:23 -0000 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" >