From owner-freebsd-current@FreeBSD.ORG Tue May 13 13:59:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D959237B404 for ; Tue, 13 May 2003 13:59:07 -0700 (PDT) Received: from pfepa.post.tele.dk (pfepa.post.tele.dk [193.162.153.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F80243FBF for ; Tue, 13 May 2003 13:59:06 -0700 (PDT) (envelope-from lists@petri.cc) Received: from lisatorris (unknown [80.164.84.214]) by pfepa.post.tele.dk (Postfix) with SMTP id 935D647FF63; Tue, 13 May 2003 22:59:04 +0200 (CEST) Message-ID: <008001c31992$7d622710$d654a450@lisatorris> From: "Nicolai Petri" To: "Dag-Erling Smorgrav" References: <200305131300.h4DD0Ecd059610@fledge.watson.org> Date: Tue, 13 May 2003 22:59:04 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: current@FreeBSD.org Subject: Re: 5.1-RELEASE TODO X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2003 20:59:08 -0000 From: "Dag-Erling Smorgrav" Subject: Re: 5.1-RELEASE TODO > I'm unable to reproduce this; kldload refuses to load a module which > is already present, and if you try to preload a driver which is > compiled into the kernel, the kernel will refuse to register it. Well.... The problem(s) certainly still exists.. And the most common crash is because under kldload, sysctl_register fails because of a duplicated oid.When unloading the module it fails to unregister the sysctl's, and then sysctl_unregister() causes a panic(). My patches and some thoughts on kld-problems kan be found at http://hobbes.bsd-dk.dk/~npp/ .. We should definately have these patches (or similar) committed before RC1 is released. There is still some not-so-easy to fix crashes when e.g. random is statically compiled into the kernel and then preloaded in the loader. I have some ideas for fixing these but it kills binary compatibility and it will need thorough testing. > > There have been problems with unloading network drivers (due to > interrupts being delivered to a handler which had disappeared into > thin air) but these had nothing to do with whether the driver was > already compiled-in, and I believe they were fixed about a month ago. You are right in some of this.. I think the "interrupt while unload" crashes have been fixed.. > Dag-Erling Smorgrav - des@ofug.org --- Nicolai Petri nicolai@catpipe.net