From owner-freebsd-current  Wed Apr 26  8:26: 2 2000
Delivered-To: freebsd-current@freebsd.org
Received: from Mail.Openet-Telecom.COM (opentisdn.isdn.dublin.esat.net [193.120.50.79])
	by hub.freebsd.org (Postfix) with ESMTP id D58B137BF29
	for <current@FreeBSD.ORG>; Wed, 26 Apr 2000 08:25:53 -0700 (PDT)
	(envelope-from peter.edwards@openet-telecom.com)
Received: from openet-telecom.com (rocklobster.openet-telecom.lan [10.0.0.40])
	by Mail.Openet-Telecom.COM (8.9.3/8.9.3) with ESMTP id QAA95049;
	Wed, 26 Apr 2000 16:33:10 +0100 (IST)
	(envelope-from peter.edwards@openet-telecom.com)
Message-ID: <39070A7A.A2766B32@openet-telecom.com>
Date: Wed, 26 Apr 2000 16:25:46 +0100
From: "Peter Edwards (local)" <peter.edwards@openet-telecom.com>
Organization: Openet Telecom
X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Maxim Sobolev <sobomax@altavista.net>
Cc: current@FreeBSD.ORG
Subject: Re: vn.ko load/unload/mount = panic
References: <390702C6.BCC0CA88@altavista.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,
After a (very) quick look at the source it looks like there's a missing
cdevsw_remove() missing from the MOD_UNLOAD/MOD_SHUTDOWN event handling
I haven't time to test it, but try this:

*** vn.c.old    Wed Apr 26 16:23:03 2000
--- vn.c        Wed Apr 26 16:24:06 2000
***************
*** 762,767 ****
--- 762,768 ----
        case MOD_UNLOAD:
                /* fall through */
        case MOD_SHUTDOWN:
+               cdevsw_remove(&vn_cdevsw);
                for (;;) {
                        vn = SLIST_FIRST(&vn_list);
                        if (!vn)


Maxim Sobolev wrote:
> 
> Hi,
> 
> I've already submitted this crash report earlier but it seems that developers
> in -current list are too busy discussing whether Matt allowed to commit his SMP
> work into 4.0 to pay attention to "ordinary" panic reports :-(. Following is
> slightly simplified course of actions which is known to produce kernel panic on
> both 4.0 and 5.0:
> 
> root@notebook# kldstat
> Id Refs Address    Size     Name
>  1    2 0xc0100000 1c2f48   kernel
>  2    1 0xc02c3000 30c8     splash_bmp.ko
> root@notebook# mount /dev/vn0c /mnt
> mount: Device not configured
> root@notebook# kldload /modules/vn.ko
> root@notebook# kldstat
> Id Refs Address    Size     Name
>  1    3 0xc0100000 1c2f48   kernel
>  2    1 0xc02c3000 30c8     splash_bmp.ko
>  3    1 0xc0823000 3000     vn.ko
> root@notebook# kldunload -i 3
> root@notebook# mount /dev/vn0c /mnt
> [BINGO]
> Fatal trap 12: page fault while in kernel mode
> [...]
> 
> -Maxim
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message