From owner-freebsd-current@FreeBSD.ORG Fri Oct 24 09:41:49 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 E14B716A4B3 for ; Fri, 24 Oct 2003 09:41:49 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 514A043FDD for ; Fri, 24 Oct 2003 09:41:49 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 4291D72DA3; Fri, 24 Oct 2003 09:41:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 3FC2272DA2; Fri, 24 Oct 2003 09:41:49 -0700 (PDT) Date: Fri, 24 Oct 2003 09:41:49 -0700 (PDT) From: Doug White To: othermark In-Reply-To: Message-ID: <20031024093830.C89064@carver.gumbysoft.com> References: <20031022150112.X71676@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: panic: Memory modified after free 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: Fri, 24 Oct 2003 16:41:50 -0000 On Thu, 23 Oct 2003, othermark wrote: > these are fibre 1000 base sx connections. They don't attach correctly in > the 5.0-release kernel as well (with the exact same error), but it does > continue to boot correctly. These are hardwired into the bus, and I'm > unable to disable them. :( Onboard fiber? What kind of system is this? > > That or perhaps you have bad memory. Do you have ECC RAM in the system? > > I'm not positive, so I'm going to say no, but I'm also fairly sure that > the memory is good. I ran make buildworld on 5.0 successfully w/o any > problems. Slow bios memcheck at startup is good. That memcheck is useless, sadly. You might track down a copy of memtest86 and run it on your system just to be sure. Its a much more intensive diagnostic. > this seems similar to: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/53566 > > except the last user is of memory is different. I suspect the actual last user is irrelevant; its a leaking pointer reference somewhere and the memory allocator is handing the memory block it points to back out to some innocent bystander who triggers the panic. > I think the next step is to move up to a 5.1-release kernel and see if > it boots as well as the 5.0-release does, or provides a more interesting > panic. Have you emailed the em driver maintainer yet? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org