From owner-freebsd-current@FreeBSD.ORG Sun Feb 5 06:15:57 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 3619516A426 for ; Sun, 5 Feb 2006 06:15:57 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE37543D48 for ; Sun, 5 Feb 2006 06:15:56 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id k156Fuuj004599; Sat, 4 Feb 2006 22:15:56 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id k156Fu0Z004598; Sat, 4 Feb 2006 22:15:56 -0800 (PST) (envelope-from sgk) Date: Sat, 4 Feb 2006 22:15:56 -0800 From: Steve Kargl To: Doug White Message-ID: <20060205061556.GA4551@troutmask.apl.washington.edu> References: <20060131212209.GA870@troutmask.apl.washington.edu> <20060201010157.GA604@troutmask.apl.washington.edu> <20060201042122.GA27796@troutmask.apl.washington.edu> <20060204214535.S45494@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060204214535.S45494@carver.gumbysoft.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: panic: Memory modified after free X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 05 Feb 2006 06:15:57 -0000 On Sat, Feb 04, 2006 at 09:51:32PM -0800, Doug White wrote: > Sorry for the late response on this, but I just debugged similar issues on > a Tyan S2892. The problem there was that the system would panic in unusual > places under load. The root cause was that the BIOS was not down-clocking > the DIMM speeds under high-load situations (e.g, all DIMM slots > populated), which caused random memory corruption. Updating to BIOS v2.00 > fixed the problem. > > Make sure you are running BIOS v3.04 or later on your S2882. The BIOS > download for that motherboard is: > > http://www.tyan.com/support/html/b_s2882.html > > The other option is to remove DIMMs from the system. > Updating the bios is the first thing I did. IIRC, I'm at 3.05. The "Memory modified after free" is a real problem somewhere deep inside devfs. See cognet's last commit to tty_pty.c. However, I'll look into the DIMM timing issues because I have been experiencing some lock-ups (not panics) when my system is under heavy load. I've tested the memory with memtest86+ more than once, and it appears to be good. -- Steve