From owner-freebsd-current@FreeBSD.ORG Sun Oct 22 17:00:46 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 5C32F16A4D1 for ; Sun, 22 Oct 2006 17:00:46 +0000 (UTC) (envelope-from norgaard@locolomo.org) Received: from strange.daemonsecurity.com (59.Red-81-33-11.staticIP.rima-tde.net [81.33.11.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 323D143DA4 for ; Sun, 22 Oct 2006 17:00:34 +0000 (GMT) (envelope-from norgaard@locolomo.org) Received: from [10.35.4.65] (65.4-35-10-static.chueca.wifi [10.35.4.65]) by strange.daemonsecurity.com (Postfix) with ESMTP id E1AFB2E024; Sun, 22 Oct 2006 19:00:24 +0200 (CEST) Message-ID: <453BA34C.7010504@locolomo.org> Date: Sun, 22 Oct 2006 18:58:52 +0200 From: Erik Norgaard User-Agent: Thunderbird 1.5.0.7 (X11/20061022) MIME-Version: 1.0 To: Jeremie Le Hen References: <20061022064322.GU53114@obiwan.tataz.chchile.org> In-Reply-To: <20061022064322.GU53114@obiwan.tataz.chchile.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org 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 17:00:46 -0000 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): > Any clue how to disable this unwanted behaviour ? Have you tried to bring down the interface first? A possible reason could be that the interface is "busy" or locked so the unload fails, are you running wpa_supplicant? Try stop wpa_supplicant if you use it and bring down the interface first. Also, you may get more info if you set debug.iwi=1. Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org X.509 Certificate: http://www.locolomo.org/crt/8D03551FFCE04F0C.crt Key ID: 69:79:B8:2C:E3:8F:E7:BE:5D:C3:C3:B1:74:62:B8:3F:9F:1F:69:B9