From owner-freebsd-stable Wed Jul 25 15:38:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from exchangech.dunnsys.com (unknown [208.178.202.11]) by hub.freebsd.org (Postfix) with ESMTP id 9E2C137B419 for ; Wed, 25 Jul 2001 15:38:22 -0700 (PDT) (envelope-from DavidLa@dunnsolutions.com) Received: by exchangech.dunnsys.com with Internet Mail Service (5.5.2650.21) id ; Wed, 25 Jul 2001 17:37:38 -0500 Message-ID: <132A7BCD951DD511B33F00105AE55CA00B6C35@MARTIN> From: David La Croix To: 'Randall Hopper' , stable@freebsd.org Subject: RE: kldunload --> SYSTEM FREEZE Date: Wed, 25 Jul 2001 17:44:19 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" 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 I had the same thing happen with a 4.3R box with the if_tun kld. (Machine is in a remote location -- and according to the on-site help -- it rebooted itself) -----Original Message----- From: Randall Hopper [mailto:aa8vb@nc.rr.com] Sent: Wednesday, July 25, 2001 5:24 PM To: stable@freebsd.org Subject: kldunload --> SYSTEM FREEZE 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message