From owner-freebsd-current@FreeBSD.ORG Wed May 23 04:29:04 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 327DF1065674; Wed, 23 May 2012 04:29:04 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from brane.freislich.nom.za (brane.freislich.nom.za [41.154.0.9]) by mx1.freebsd.org (Postfix) with ESMTP id AF7528FC0A; Wed, 23 May 2012 04:29:03 +0000 (UTC) Received: from [10.0.2.220] (helo=clue.co.za) by brane.freislich.nom.za with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1SX3C1-0000Fl-8N; Wed, 23 May 2012 06:29:01 +0200 Received: from localhost ([127.0.0.1] helo=clue.co.za) by clue.co.za with esmtp (Exim 4.76 (FreeBSD)) (envelope-from ) id 1SX3Bt-0000qb-JF; Wed, 23 May 2012 06:28:53 +0200 To: John Baldwin From: Ian FREISLICH In-Reply-To: <201205221641.13091.jhb@freebsd.org> References: <201205221641.13091.jhb@freebsd.org> X-Attribution: BOFH Date: Wed, 23 May 2012 06:28:53 +0200 Message-Id: X-Missing-rDNS: 10.0.2.220 Cc: freebsd-current@freebsd.org 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: Wed, 23 May 2012 04:29:04 -0000 John Baldwin wrote: > 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:15 96 > > 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. (kgdb) frame 7 #7 0xc0878682 in pmap_enter (pmap=0xc09e4060, va=3359633408, access=7 '\a', m=0xc191bf70, prot=7 '\a', wired=1) at /usr/src/sys/i386/i386/pmap.c:1596 1596 root = vm_page_splay(mpte->pindex, root); (kgdb) l 1591 root = pmap->pm_root; 1592 if (root == NULL) { 1593 mpte->left = NULL; 1594 mpte->right = NULL; 1595 } else { 1596 root = vm_page_splay(mpte->pindex, root); 1597 if (mpte->pindex < root->pindex) { 1598 mpte->left = root->left; 1599 mpte->right = root; 1600 root->left = NULL; Ian -- Ian Freislich