From owner-freebsd-current Sun Jan 5 3:12:13 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 598EA37B401; Sun, 5 Jan 2003 03:12:08 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96CC043E4A; Sun, 5 Jan 2003 03:12:07 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id WAA29424; Sun, 5 Jan 2003 22:12:04 +1100 Date: Sun, 5 Jan 2003 22:12:22 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: phk@FreeBSD.ORG Cc: walt , Subject: Re: VOP_STRATEGY on VCHR? In-Reply-To: <4314.1041762317@critter.freebsd.dk> Message-ID: <20030105220009.O462-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Sun, 5 Jan 2003 phk@FreeBSD.ORG wrote: > In message <3E17D52F.7050307@hotmail.com>, walt writes: > >After updating world and kernel this evening I saw this message fly by > >during the reboot: > > > >Mounting root from ufs:/dev/ad0s3a > > > >VOP_STRATEGY on VCHR > >: 0xc25fd000: tag none, type VCHR, usecount 5, writecount 0, refcount 6, flags (VV_OBJBUF), I get this too (except I fixed the misformatting of the message while reviewing the code, so that it is printed on 1 line with a non-bogus ":"). From /var/log/messages: % Jan 5 21:09:22 gamplex kernel: VOP_STRATEGY on VCHR: 0xc2697000: tag none, type VCHR, usecount 4, writecount 0, refcount 4, flags (VV_OBJBUF), % Jan 5 21:18:37 gamplex kernel: VOP_STRATEGY on VCHR: 0xc2697000: tag none, type VCHR, usecount 4, writecount 0, refcount 4, flags (VV_OBJBUF), (This shows a formatting bug in vprint() itself: the "," at the end.) > >Sorry, need DDB option to print backtrace I have the DDB option, so I don't get this. > It is probably the same problem as the one I just commited a fix for. I haven't cvsupped' the fix or debugged it yet. > If you get this again after upgrading, please put the DDB option in > your kernel and see if you can reproduce it so I get a traceback. > The vnode information alone seems not quite as useful as I had hoped. Neither is the traceback. db_trace() prints using db_printf() so the message never reaches log files. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message