From owner-freebsd-stable Wed Jul 25 15:24:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail8.nc.rr.com (fe8.southeast.rr.com [24.93.67.55]) by hub.freebsd.org (Postfix) with ESMTP id 525E437B403 for ; Wed, 25 Jul 2001 15:24:45 -0700 (PDT) (envelope-from aa8vb@nc.rr.com) Received: from stealth.cary.dummynet ([66.57.28.236]) by mail8.nc.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Wed, 25 Jul 2001 18:24:39 -0400 Received: (from rhh@localhost) by stealth.cary.dummynet (8.11.4/8.11.4) id f6PMO3W17721 for stable@freebsd.org; Wed, 25 Jul 2001 18:24:03 -0400 (EDT) (envelope-from aa8vb@nc.rr.com) X-Authentication-Warning: stealth.cary.dummynet: rhh set sender to aa8vb@nc.rr.com using -f Date: Wed, 25 Jul 2001 18:24:03 -0400 From: Randall Hopper To: stable@freebsd.org Subject: kldunload --> SYSTEM FREEZE Message-ID: <20010725182403.A17617@nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Was experimenting with mods to the DRI modules on -stable, and half to my surprise when I first tried a "kldunload mga.ko" (to then reload the new version) my system locked hard. I know what happened. But I'm wondering, what "should" happen. Would you say: a) Doh! Well of "course" it's going to lock up stupid! Don't do that! b) It really shouldn't lock up. It should flat refuse to unload, but something is apparently broken. c) It should unload, but a pre-unload "cleanup hook" probably isn't implemented. Randall -- Randall Hopper aa8vb@nc.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message