From owner-freebsd-current@FreeBSD.ORG Thu Oct 23 10:02: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 4490016A4B3 for ; Thu, 23 Oct 2003 10:02:49 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3A2543FB1 for ; Thu, 23 Oct 2003 10:02:46 -0700 (PDT) (envelope-from freebsd-current@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1ACirF-0004Ci-00 for ; Thu, 23 Oct 2003 19:02:45 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org Received: from sea.gmane.org ([80.91.224.252]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1ACirD-0004CY-00 for ; Thu, 23 Oct 2003 19:02:43 +0200 Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian)) id 1ACirD-00071l-00 for ; Thu, 23 Oct 2003 19:02:43 +0200 From: othermark Date: Thu, 23 Oct 2003 10:02:36 -0700 Lines: 59 Message-ID: References: <20031022150112.X71676@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org User-Agent: KNode/0.7.2 Sender: news 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: Thu, 23 Oct 2003 17:02:49 -0000 Thanks for looking at this. I'm still scratching my head on it. Doug White wrote: > On Mon, 20 Oct 2003, othermark wrote: >> I have a strange panic during the isa pnp code that does not occur with a >> 5.0-release kernel. ... > Can you pull out or disable the gig-e card? Its having trouble > initializing, and I'm wondering if its doing something bad in the process. 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. :( > 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. > Here is the panic again: > >> Memory modified after free 0xc4758800(2044) val=c4756800 @ 0xc47589dc >> panic: Most recently used by bus-sc this seems similar to: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/53566 except the last user is of memory is different. Speaking of memory 5.0 - release: real memory = 536870912 (512 MB) Physical memory chunk(s): ! 0x00001000 - 0x0009efff, 647168 bytes (158 pages) ! 0x0064f000 - 0x1fff7fff, 530223104 bytes (129449 pages) ! avail memory = 515031040 (491 MB) -current: real memory = 536870912 (512 MB) Physical memory chunk(s): ! 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) ! 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) ! 0x0000000000c26000 - 0x000000001f6d9fff, 514539520 bytes (125620 pages) ! avail memory = 511942656 (488 MB) 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. -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired);