From owner-freebsd-current Thu Jan 9 11:49:42 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CCD337B401 for ; Thu, 9 Jan 2003 11:49:40 -0800 (PST) Received: from grassmarket.ucs.ed.ac.uk (grassmarket.ucs.ed.ac.uk [129.215.166.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DB7043F1E for ; Thu, 9 Jan 2003 11:49:34 -0800 (PST) (envelope-from bruce@cran.org.uk) Received: from fourtytwo (12266209.resnet.ed.ac.uk [10.6.0.100] (may be forged)) by grassmarket.ucs.ed.ac.uk (8.11.6/8.11.6) with ESMTP id h09JnLh23543 for ; Thu, 9 Jan 2003 19:49:27 GMT Received: from bruce by fourtytwo with local (Exim 3.36 #1 (Debian)) id 18Wiie-0000Cm-00 for ; Thu, 09 Jan 2003 19:52:00 +0000 Date: Thu, 9 Jan 2003 19:52:00 +0000 From: Bruce Cran To: current@freebsd.org Subject: LOR in vfs_mount.c and panic during sysinstall Message-ID: <20030109195200.GA748@fourtytwo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I tried installing today's snapshot, 5.0-CURRENT-20030109-JPSNAP.iso from snapshots.jp.freebsd.org. I went away and came back to the following panic, which happened while sysinstall was copying files: kernel: trap 12, code=0 stopped at vfs_setdirty+0x59: movzwl 0x6e(%ebx),%eax the trace returned the following functions: vfs_setdirty vfs_busy_pages bwrite bawrite ffs_bupdate ffs_sync sync_fsync sched_sync fork_exit fork_trampoline() trap 0x1, eip=0, esp=0xd69b2d7c, ebp=0 I tried again, and, after getting to the same place: lock order reversal 1st 0xc44a3ce0 process lock (process lock) @ /usr/src/sys/kern/vfs_mount.c: 1144 2nd: 0xc476ec34 filedesc structure (filedesc structure) @ /usr/src/sys/kern/vfs_mount.c: 1151 I don't know if this is a known problem, and I do know my motherboard can be a bit buggy. My computer's an Athlon XP on a A7V-266E motherboard. I was trying to install FreeBSD on /dev/ad0s3. Is this the bug as reported in the TODO list on the web site? -- Bruce Cran To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message