From owner-freebsd-current@FreeBSD.ORG Sun Oct 22 21:27:33 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org 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 8701316A412; Sun, 22 Oct 2006 21:27:33 +0000 (UTC) (envelope-from mime@traveller.cz) Received: from nxm.secservers.com (nxm.secservers.com [193.85.228.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id E682A43D4C; Sun, 22 Oct 2006 21:27:32 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from [127.0.0.1] (nxm.secservers.com. [193.85.228.22]) by nxm.secservers.com (8.13.4/8.13.4) with ESMTP id k9MLRUqK012050; Sun, 22 Oct 2006 23:27:30 +0200 (CEST) (envelope-from mime@traveller.cz) From: Michal Mertl To: Florent Thoumie In-Reply-To: <1161512742.71755.9.camel@localhost> References: <20061022064322.GU53114@obiwan.tataz.chchile.org> <1161512742.71755.9.camel@localhost> Content-Type: text/plain Date: Sun, 22 Oct 2006 23:27:23 +0200 Message-Id: <1161552443.41580.26.camel@genius.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, Jeremie Le Hen Subject: Re: Cannot unload if_iwi module X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 22 Oct 2006 21:27:33 -0000 Florent Thoumie wrote: > On Sun, 2006-10-22 at 08:43 +0200, Jeremie Le Hen wrote: > > Hi, > > > > when I try to unload if_iwi module, here is what happens: > > > > % jarjarbinks:/<3>dev/iwi:118# kldunload if_iwi > > % iwi0: detached > > % jarjarbinks:/<3>dev/iwi:119# iwi0: mem 0xc8218000-0xc8218fff irq 11 at device 3.0 on pci6 > > % iwi0: Ethernet address: 00:12:f0:2c:f3:6e > > % iwi0: [GIANT-LOCKED] > > > > The kld is reloaded automatically (I am sure it is reloaded because > > the id showed in kldstat(8) changes each time): > > > > % jarjarbinks:/<1>share/mk:137# kldstat > > % Id Refs Address Size Name > > % 1 20 0xc0400000 4ef910 kernel > > % 2 1 0xc08f0000 e5dc if_bge.ko > > % 3 1 0xc08ff000 4ce4 ums.ko > > % 4 1 0xc0904000 b180 umass.ko > > % 5 2 0xc382e000 25000 linux.ko > > % 6 1 0xc38cb000 2000 rtc.ko > > % 9 1 0xc3acf000 e000 if_iwi.ko > > % 10 2 0xc3add000 3000 firmware.ko > > > > % jarjarbinks:/<3>dev/iwi:122# kldstat > > % Id Refs Address Size Name > > % 1 19 0xc0400000 4ef910 kernel > > % 2 1 0xc08f0000 e5dc if_bge.ko > > % 3 1 0xc08ff000 4ce4 ums.ko > > % 4 1 0xc0904000 b180 umass.ko > > % 5 2 0xc382e000 25000 linux.ko > > % 6 1 0xc38cb000 2000 rtc.ko > > % 11 1 0xc3acf000 e000 if_iwi.ko > > % 12 1 0xc3add000 3000 firmware.ko > > > > Any clue how to disable this unwanted behaviour ? > > No idea, but the same behavior can be seen with ipw(4) and experimental > wpi(4). I seem to recall this didn't happen before the the support for > firmware(9) was added. It also happens with em(4) to me. I found out it doesn't happen when devd is not running. I find it rather strange that the 'pciconf -l' command shows driver name (e.g. em0@pci...) even after (successfully and permanently) unloading the module for a device. The 'devinfo' command does not. Michal