Date: Thu, 19 Dec 2002 16:52:59 +0000 (GMT) From: Gavin Atkinson <gavin@ury.york.ac.uk> To: current@freebsd.org Subject: Panic: memory modified after free Message-ID: <20021219151949.Y54430-100000@ury.york.ac.uk>
next in thread | raw e-mail | index | archive | help
Hi,
Running 5.0-RC as of yesterday on i386. background fsck was in progress,
but other than that system was idle. Logged in as root on the console, had
cd'd to a ports directory. (note that it panics almost instantly when
using the console, but lasts upto 10 minutes when in use over ssh)
Running "make deinstall" triggered this panic:
Memory modified after free 0xc1891c00(1020)
panic: Most recently used by none
#10 0xc0204cfb in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:503
#11 0xc032c7dd in mtrash_ctor (mem=0xc1891c00, size=0, arg=0x0)
at /usr/src/sys/vm/uma_dbg.c:138
#12 0xc032b1e7 in uma_zalloc_arg (zone=0xc0b653c0, udata=0x0, flags=0)
at /usr/src/sys/vm/uma_core.c:1358
#13 0xc01f95ad in malloc (size=6, type=0xc03cfb00, flags=0)
at /usr/src/sys/kern/kern_malloc.c:182
#14 0xc01df80c in exec_elf32_imgact (imgp=0xd0e18b88) at imgact_elf.c:804
#15 0xc01ec952 in kern_execve (td=0xc1924620, fname=---Can't read userspace from dump, or kernel process---)
at /usr/src/sys/kern/kern_exec.c:313
#16 0xc01ed430 in execve (td=0x0, uap=0x0) at /usr/src/sys/kern/kern_exec.c:698
#17 0xc035f90e in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 135232232, tf_esi =
135232268, tf_ebp = -1077937688, tf_isp = -790524556, tf_ebx = 0, tf_edx =
135232268, tf_ecx = 135232303, tf_eax = 59, tf_trapno = 12, tf_err = 2,
tf_eip = 134723319, tf_cs = 31, tf_eflags = 642, tf_esp = -1077937716,
tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:1033
#18 0xc034faad in Xint0x80_syscall () at {standard input}:140
---Can't read userspace from dump, or kernel process---
The machine seems perfectly stable in single user mode. It also seems
pretty stable at the moment with linux emulation, usbd, sendmail, ipv6,
nfs server and moused enables commented out of rc.conf. I will try to add
one at a time tonight to determine which is at fault.
Gavin
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021219151949.Y54430-100000>