From owner-freebsd-threads@FreeBSD.ORG Sat Apr 30 22:30:06 2005 Return-Path: Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D31B116A4CE for ; Sat, 30 Apr 2005 22:30:06 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAA3F43D1D for ; Sat, 30 Apr 2005 22:30:06 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3UMU6Mj082588 for ; Sat, 30 Apr 2005 22:30:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j3UMU6g6082587; Sat, 30 Apr 2005 22:30:06 GMT (envelope-from gnats) Date: Sat, 30 Apr 2005 22:30:06 GMT Message-Id: <200504302230.j3UMU6g6082587@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: "Imri Zvik" Subject: RE: threads/80435: panic on high loads X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Imri Zvik List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2005 22:30:06 -0000 The following reply was made to PR threads/80435; it has been noted by GNATS. From: "Imri Zvik" To: "Daniel Eischen" Cc: , Subject: RE: threads/80435: panic on high loads Date: Sun, 1 May 2005 01:27:07 +0300 Hi, I've upgraded to RELENG_5 and now I get the following panic on high loads: #0 doadump () at pcpu.h:160 #1 0xc05aa9c7 in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:410 #2 0xc05aaced in panic (fmt=3D0xc07801c6 "ffs_blkfree: freeing free frag") at /usr/src/sys/kern/kern_shutdown.c:566 \#3 0xc068b052 in ffs_blkfree (fs=3D0xc39a5800, devvp=3D0xc39d3318, bno=3D2582296, size=3D6144, inum=3D41920) at /usr/src/sys/ufs/ffs/ffs_alloc.c:1795 #4 0xc0699440 in handle_workitem_freeblocks (freeblks=3D0xc3b93500, flags=3D0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:2507 #5 0xc0696aac in process_worklist_item (matchmnt=3D0x0, flags=3D0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:764 #6 0xc069683c in softdep_process_worklist (matchmnt=3D0x0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:630 #7 0xc05feba5 in sched_sync () at /usr/src/sys/kern/vfs_subr.c:1675 #8 0xc05959c1 in fork_exit (callout=3D0xc05fe6a4 , = arg=3D0x0, frame=3D0xe6b52d38) at /usr/src/sys/kern/kern_fork.c:791 #9 0xc06fdf3c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:209 uname -a output: FreeBSD proxy.inter.net.il 5.4-STABLE FreeBSD 5.4-STABLE #0: Fri Apr 29 15:27:25 IDT 2005 root@proxy.inter.net.il:/usr/obj/usr/src/sys/IGLD i386 Could it be a faulty hardware? (mem tests found no errors, motherboard/cpu tests also found no errors). -- Imri Zvik PGP (2.6.3ia) Public Key: http://mariska.inter.net.il/~imriz/imriz.pgp