From owner-freebsd-current Sun Jan 5 22:21:39 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 296A337B401 for ; Sun, 5 Jan 2003 22:21:37 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B42443E4A for ; Sun, 5 Jan 2003 22:21:36 -0800 (PST) (envelope-from phk@freebsd.org) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id h066LTHj003021; Mon, 6 Jan 2003 07:21:29 +0100 (CET) (envelope-from phk@freebsd.org) To: kpeter@melbpc.org.au Cc: freebsd-current@freebsd.org Subject: Re: VOP_STRATEGY on VCHR? From: phk@freebsd.org In-Reply-To: Your message of "Mon, 06 Jan 2003 10:36:55 +1100." <3E18C197.2010107@melbpc.org.au> Date: Mon, 06 Jan 2003 07:21:29 +0100 Message-ID: <3020.1041834089@critter.freebsd.dk> 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 That one should already be fixed. In message <3E18C197.2010107@melbpc.org.au>, Peter Kostouros writes: >Hi > >I received a similar problem during booting into single user mode upon >startup. I hope the following helps: > >mounting root from ufs:/dev/ad2s1a >start_init: trying /sbin/init > >VOP_STRATEGY on VCHR >:0xc189a00: tag none, type VCHR, usecount 5, write count 0, refcount 6, >flags (VV_OBJBUF) > >backtrace >spec_strategy >spec_getpages >ffs_getpages >vnode_pager_getpages >exec_map_first_page >kern_execve >execve >start_init >fork_exit >fork_trampoline > >--- trap 0x1, eip = 0, esp = 0xcbaaed7c, ebp = 0 --- > >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), >>>Sorry, need DDB option to print backtrace >>> >>>That feels like an error message (sort of) but everything seems to be >>>working normally. Is this a real problem or just noise? >>> >> >> >>Well, to you it's just noise, to me it's a real problem :-) >> >>It is probably the same problem as the one I just commited a fix for. >> >>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. >> >> >> > > >-- > >Regards > >Peter > >As always the organisation disavows knowledge of this email > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message