From owner-freebsd-sparc64@FreeBSD.ORG Tue Sep 28 16:10:10 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 854DF16A4CE; Tue, 28 Sep 2004 16:10:10 +0000 (GMT) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 281A243D3F; Tue, 28 Sep 2004 16:10:10 +0000 (GMT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (localhost [127.0.0.1]) i8SGA8TH001031; Tue, 28 Sep 2004 12:10:08 -0400 (EDT) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i8SGA5FE001020; Tue, 28 Sep 2004 12:10:05 -0400 (EDT) Date: Tue, 28 Sep 2004 12:09:54 -0400 From: Ken Smith To: John Baldwin Message-ID: <20040928160953.GC27640@electra.cse.Buffalo.EDU> References: <20040921064450.GA54998@xor.obsecurity.org> <20040928071241.GA74512@xor.obsecurity.org> <200409281131.03448.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200409281131.03448.jhb@FreeBSD.org> User-Agent: Mutt/1.4.1i cc: Kris Kennaway cc: freebsd-sparc64@freebsd.org cc: sparc64@freebsd.org Subject: Re: Memory modified after free 0xfffff8001b210e00(504) val=deadc0dd @ 0xfffff8001b21 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Sep 2004 16:10:10 -0000 On Tue, Sep 28, 2004 at 11:31:03AM -0400, John Baldwin wrote: > On Tuesday 28 September 2004 03:12 am, Kris Kennaway wrote: > > > I just got this panic on an SMP sparc package machine running 6.0: > > > > > > Memory modified after free 0xfffff8001b210e00(504) val=deadc0dd @ > > > 0xfffff8001b210f20 panic: Most recently used by file desc > > Unfortunately it's hard to track these down as we really need to know where it > was free'd() from and UMA/malloc do not currently have the ability to tell us > that. What scares me is he keeps sending them here to the sparc64 list and I haven't seen him send any to other lists... [ Just kidding Kris! :-] But ... Where might a file desc structure be mis-handled that would be specific to sparc64? That's what is a little scary... -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |