Date: Sun, 14 May 2000 13:33:14 +0100 (BST) From: Nick Hibma <n_hibma@calcaphon.com> To: phk@freebsd.org Cc: Peter Edwards <peter.edwards@openet-telecom.com>, FreeBSD CURRENT Mailing List <current@freebsd.org>, wc.bulte@chello.nl, Maxim Sobolev <sobomax@altavista.net> Subject: Re: vn.ko load/unload/mount = panic Message-ID: <Pine.BSF.4.20.0005141328380.78621-100000@localhost> In-Reply-To: <39097C24.55671DBE@openet-telecom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Correct me if I am wrong, but I don't think you actually have to
disassociate any dev_t's from the driver (by clearing the si_drv[12]
fields) because we call destroy_dev and cdevsw_remove, so any later uses
of dev_t's get an error because the device has gone away.
Apart from that I don't think we the calls to cdevsw_add/_destroy in the
first place, because we create the cdevsw on demand (with make_dev).
Poul, is this correct?
nick
On Fri, 28 Apr 2000, Peter Edwards wrote:
> I had a longer look at this, and a more complete patch is logged as PR
> kern/18270 (try at your own risk: it works for me).
> I'd appreciate someone more experienced having a look at it and
> commenting.
> Cheers,
> Peter.
>
>
> Wilko Bulte wrote:
> >
> > On Wed, Apr 26, 2000 at 04:25:46PM +0100, Peter Edwards (local) wrote:
> >
> > How about send-pr ing this stuff?
> >
> > Wilko
> >
> > > 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
> >
> > --
> > Wilko Bulte Powered by FreeBSD http://www.freebsd.org
> > http://www.tcja.nl
> >
> > 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
>
--
n_hibma@webweaving.org
n_hibma@freebsd.org USB project
http://www.etla.net/~n_hibma/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.0005141328380.78621-100000>