Date: Tue, 31 Jan 2006 20:21:22 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: freebsd-current@freebsd.org Subject: Re: panic: Memory modified after free Message-ID: <20060201042122.GA27796@troutmask.apl.washington.edu> In-Reply-To: <20060201010157.GA604@troutmask.apl.washington.edu> References: <20060131212209.GA870@troutmask.apl.washington.edu> <20060201010157.GA604@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 31, 2006 at 05:01:57PM -0800, Steve Kargl wrote: > On Tue, Jan 31, 2006 at 01:22:09PM -0800, Steve Kargl wrote: > > The system is a dual proc Tyan K8S Pro with 12 GB of memory. > > The kernel is UP. This was recorded by hand. I have the crash dump. > > > > Memory modified after free 0xffffff02505e0c00(504) val=deadc0dd @ > > 0xffffff02505e0cd0 > > > > 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. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060201042122.GA27796>