From owner-freebsd-stable  Sat Sep  9 12:43: 8 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from db.wireless.net (adsl-gte-la-216-86-194-70.mminternet.com [216.86.194.70])
	by hub.freebsd.org (Postfix) with ESMTP
	id 15DA937B422; Sat,  9 Sep 2000 12:43:01 -0700 (PDT)
Received: from db.wireless.net (dbm.wireless.net [192.168.0.2])
	by db.wireless.net (8.9.3/8.9.3) with ESMTP id MAA12100;
	Sat, 9 Sep 2000 12:30:55 -0700 (PDT)
	(envelope-from dbutter@db.wireless.net)
Message-ID: <39BA92BF.D0632472@db.wireless.net>
Date: Sat, 09 Sep 2000 12:42:55 -0700
From: Devin Butterfield <dbutter@db.wireless.net>
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: hackers@FreeBSD.ORG
Cc: freebsd-stable@FreeBSD.ORG, buaas@wireless.net
Subject: Panics from trying to open dev after kldunload
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi all,

I'm working on a device driver for FreeBSD for a VoIP telephony card and
I stumbled upon a serious problem. If I "kldunload" my driver and
subsequently try to open the device, the kernel panics. I found that the
vn device suffers from this same bug. For example:

Before kldload vn:

[root@dbm]# echo -n>/dev/vn0
su: /dev/vn0: Device not configured
[root@dbm]#

This of course is the expected behavior. We then can do this...

[root@dbm]# kldload vn
[root@dbm]# echo -n>/dev/vn0
[root@dbm]# 

Again, expected behavior...

But if we then do this...

[root@dbm]# kldunload vn
[root@dbm]# echo -n>/dev/vn0

we get an instant panic.

It seems that there is already a pr open for this (kern/18270) which
includes a patch to correctly cleanup after "kldunload". Is this the
correct fix for this...why hasn't this been committed??
--
Regards, Devin.


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