On Dec 4, 2009, at 8:56 PM, Stefan Bethke wrote: > Am 04.12.2009 um 17:52 schrieb Stefan Bethke: > >> I'm getting panics like this every so often (couple weeks, sometimes just a >> few days.) A second machine that has identical hardware and is running the >> same source has no such problems. >> >> FreeBSD XXX.hanse.de 8.0-STABLE FreeBSD 8.0-STABLE #16: Tue Dec 1 14:30:54 >> UTC 2009 r...@xxx.hanse.de:/usr/obj/usr/src/sys/EISENBOOT amd64 >> >> # zpool status >> pool: tank >> state: ONLINE >> scrub: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> tank ONLINE 0 0 0 >> ad4s1d ONLINE 0 0 0 >> # cat /boot/loader.conf >> vfs.zfs.arc_max="512M" >> vfs.zfs.prefetch_disable="1" >> vfs.zfs.zil_disable="1" > > Got another, different one. Any tuning suggestions or similar? > > > #6 0xffffffff80586c7a in vm_map_entry_splay (addr=Variable "addr" is not > available. > ) > at /usr/src/sys/vm/vm_map.c:771 > #7 0xffffffff80587f37 in vm_map_lookup_entry (map=0xffffff00010000e8, > address=18446743523979624448, entry=0xffffff80625db170) > at /usr/src/sys/vm/vm_map.c:1021 > #8 0xffffffff80588aa3 in vm_map_delete (map=0xffffff00010000e8, > start=18446743523979624448, end=18446743523979689984) > at /usr/src/sys/vm/vm_map.c:2685 > #9 0xffffffff80588e61 in vm_map_remove (map=0xffffff00010000e8, > start=18446743523979624448, end=18446743523979689984) > at /usr/src/sys/vm/vm_map.c:2774 > #10 0xffffffff8057db85 in uma_large_free (slab=0xffffff005fcc7000) > at /usr/src/sys/vm/uma_core.c:3021 > #11 0xffffffff80325987 in free (addr=0xffffff80018b0000, > mtp=0xffffffff80ac61e0) at /usr/src/sys/kern/kern_malloc.c:471 > #12 0xffffffff80a36d03 in vdev_cache_evict (vc=0xffffff0001723ce0, > ve=0xffffff003dd52200) > at > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_cache.c:151 > #13 0xffffffff80a372ad in vdev_cache_read (zio=0xffffff005f5ca2d0) > at > /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_cache.c:182 Bad RAM/motherboard? My first thought when I read your first mail (re: identical hardware) was bad hardware, and this seems to point towards that too, no? Have you tried memtest86+?
Regards, Thomas_______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
