From owner-freebsd-current@FreeBSD.ORG Wed Feb 1 12:46:25 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 A9E5D16A420 for ; Wed, 1 Feb 2006 12:46:25 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6D1943D45 for ; Wed, 1 Feb 2006 12:46:24 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by rosebud.otenet.gr (8.13.4/8.13.4/Debian-8) with SMTP id k11CkMx6025223; Wed, 1 Feb 2006 14:46:22 +0200 Received: by flame.pc (Postfix, from userid 1001) id 1D3F81152D; Wed, 1 Feb 2006 14:45:52 +0200 (EET) Date: Wed, 1 Feb 2006 14:45:51 +0200 From: Giorgos Keramidas To: Steve Kargl Message-ID: <20060201124551.GE33948@flame.pc> References: <20060131212209.GA870@troutmask.apl.washington.edu> <20060201010157.GA604@troutmask.apl.washington.edu> <20060201042122.GA27796@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060201042122.GA27796@troutmask.apl.washington.edu> 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: Wed, 01 Feb 2006 12:46:25 -0000 On 2006-01-31 20:21, Steve Kargl wrote: > > Thing are looking positively horrid. A kernel from a cvsup with > > a date=2006.01.25.00.00.00 appears to work fine. A kernel from with > > date=2006.01.27.00.00.00 dies with > > > > dev_relthread() at dev_relthread+0x2e > > devfs_close() at devfs_close+0x1b6 > > VOP_CLOSE_APV() at VOP_CLOSE_APV+0x74 > > vn_close() at vn_close+0x8d > > vn_closefile() at vn_closefile+0x5a > > fdrop_locked() at fdrop_locked+0xa1 > > closef() at closef+0x35f > > fdfree() at fdfree+0x513 > > exit1() at exit1+0x360 > > sys_exit() at sys_exit+0xe > > a 2006.01.26.12.00.00.00 kernel dies a similar death. > Unfortnately, this panic took out a portion of /usr/include > and /usr/src. I can't prove it yet, but I think the > pts code may be the trigger. With a kernel & userland built with DEBUG_FLAGS='-g' from last night, I manager to kill my amd64 laptop completely. The last kernel I had working fine is from 25/Jan/2006, so something after this is that broke. The bug here manifests as unusable vty's in multiuser mode, but things seem to work relatively ok in single-user mode (i.e. I see no panics, yet). I've reinstalled 5.4-RELEASE from a CD-ROM, so bringing this up to CURRENT of 25-Jan will take a while though :(