panic: Memory modified after free
sgk at troutmask.apl.washington.edu
Tue Jan 31 20:21:22 PST 2006
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.
More information about the freebsd-current