Date: Tue, 28 Sep 2004 00:08:35 +0800 (CST) From: tjs <tjs@cdpa.nsysu.edu.tw> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/72131: panic when starting vinum on system boot Message-ID: <200409271608.i8RG8ZEu003487@Pluto.CDPA.nsysu.edu.tw> Resent-Message-ID: <200409271610.i8RGAMdN061128@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 72131
>Category: kern
>Synopsis: panic when starting vinum on system boot
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Sep 27 16:10:21 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator: Jin-Shan Tseng
>Release: FreeBSD 5.3-BETA6 i386
>Organization:
NSYSU-CDPA
>Environment:
System: FreeBSD Pluto.CDPA.nsysu.edu.tw 5.3-BETA6 FreeBSD 5.3-BETA6 #0: Mon Sep 27 21:07:29 CST 2004 tjs@Pluto.CDPA.nsysu.edu.tw:/usr/obj/usr/src/sys/Pluto i386
>Description:
When setting start_vinum="YES" in /etc/rc.conf, system will panic on boot.
There are some messages.
<messages>
SMP: AP CPU #1 Launched!
Mounting root from ufs:/dev/da0s1a
Pre-seeding PRNG: kickstart.
Loading configuration files.
Entropy harvesting: interrupts ethernet point_to_point kickstart.
vinum: loaded
panic: umount: dangling vnode
cpuid = 1;
Uptime: 19s
Cannot dump. No dump device defined.
Automatic reboot in 15 secounds - press a key on the console to abort
</messages>
But, if I start vinum at prompt, it would not.
>How-To-Repeat:
Set start_vinum="YES" in /etc/rc.conf and reboot.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409271608.i8RG8ZEu003487>