From owner-freebsd-current@FreeBSD.ORG Tue May 22 20:41:15 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19FBD1065676 for ; Tue, 22 May 2012 20:41:15 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id E560D8FC0C for ; Tue, 22 May 2012 20:41:14 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 627BEB91A; Tue, 22 May 2012 16:41:14 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 22 May 2012 16:41:13 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p13; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201205221641.13091.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 22 May 2012 16:41:14 -0400 (EDT) Cc: Ian FREISLICH Subject: Re: panic in vfs_lookup/kern_statat_vnhook? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2012 20:41:15 -0000 On Tuesday, May 22, 2012 2:36:06 pm Ian FREISLICH wrote: > Hi > > I've had quite a few reproduceable panics that look to be VFS > related. The trigger is relatively heavy concurrent disk IO. > I can trigger it easily two ways: > > 1. running my backup script which essentially does: > cd /; rsync --one-file-system --delete -aHv . /backup > cd /tmp; rsync --one-file-system --delete -aHv . /backup/tmp > cd /usr; rsync --one-file-system --delete -aHv . /backup/usr > cd /var; rsync --one-file-system --delete -aHv . /backup/var > > 2. While updating with cvsup or csup, launch firefox. > > Both reliably provoke the panic: > > #0 doadump (textdump=1) at pcpu.h:244 > #1 0xc06aa895 in kern_reboot (howto=260) > at /usr/src/sys/kern/kern_shutdown.c:454 > #2 0xc06aad36 in panic (fmt=Variable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:642 > #3 0xc087adee in trap_fatal (frame=0xedb365c8, eva=28) > at /usr/src/sys/i386/i386/trap.c:1022 > #4 0xc087aed8 in trap_pfault (frame=0xedb365c8, usermode=0, eva=28) > at /usr/src/sys/i386/i386/trap.c:875 > #5 0xc087bc4d in trap (frame=0xedb365c8) at /usr/src/sys/i386/i386/trap.c:546 > #6 0xc086687c in calltrap () at /usr/src/sys/i386/i386/exception.s:169 > #7 0xc0878682 in pmap_enter (pmap=0xc09e4060, va=3359633408, access=7 '\a', > m=0xc3073f70, prot=7 '\a', wired=1) at /usr/src/sys/i386/i386/pmap.c:1596 This is the actual panic. Can you go to this frame? The VFS bits don't matter, the pmap code blew up trying to malloc another vnode. > This same panic was reported some time back in: > Subject: [panic] zfs_zget() panic during 'svn update' > From: Glen Barber > Date: Thu, 17 May 2012 16:18:51 -0400 > To: freebsd-current@FreeBSD.org > > http://people.freebsd.org/~gjb/zfs_zget-panic.kgdb.txt This is a completely different and (AFAICT) unrelated panic. -- John Baldwin