From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 18:10:17 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2AC79106564A; Sun, 5 Dec 2010 18:10:17 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id DC5A78FC0C; Sun, 5 Dec 2010 18:10:16 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.4/8.14.4) with ESMTP id oB5IAGDg066862; Sun, 5 Dec 2010 10:10:16 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.4/8.14.4/Submit) id oB5IAGQ8066861; Sun, 5 Dec 2010 10:10:16 -0800 (PST) (envelope-from sgk) Date: Sun, 5 Dec 2010 10:10:16 -0800 From: Steve Kargl To: Bernhard Schmidt Message-ID: <20101205181016.GA66750@troutmask.apl.washington.edu> References: <20101205062103.GA63430@troutmask.apl.washington.edu> <201012050934.46566.bschmidt@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201012050934.46566.bschmidt@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: wlan0 going UP/DOWN problem 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, 05 Dec 2010 18:10:17 -0000 On Sun, Dec 05, 2010 at 09:34:46AM +0100, Bernhard Schmidt wrote: > On Sunday 05 December 2010 07:21:03 Steve Kargl wrote: > > It seems some recent change (as in the last 7-10 days) > > has caused an instability in wlan0. Just a small > > excerpt from /var/log/messages, > > > > Dec 4 18:54:16 laptop kernel: wlan0: link state changed to UP > > Dec 4 19:11:16 laptop kernel: wlan0: link state changed to DOWN > > Dec 4 19:11:16 laptop kernel: wlan0: link state changed to UP > > Dec 4 19:19:46 laptop kernel: wlan0: link state changed to DOWN > > Dec 4 19:19:46 laptop kernel: wlan0: link state changed to UP > > Dec 4 19:37:01 laptop kernel: wlan0: link state changed to DOWN > > Dec 4 19:37:01 laptop kernel: wlan0: link state changed to UP > > Dec 4 19:45:31 laptop kernel: wlan0: link state changed to DOWN > > Dec 4 19:45:31 laptop kernel: wlan0: link state changed to UP > > Dec 4 19:54:01 laptop kernel: wlan0: link state changed to DOWN > > Dec 4 19:54:01 laptop kernel: wlan0: link state changed to UP > > Dec 4 20:11:16 laptop kernel: wlan0: link state changed to DOWN > > Dec 4 20:11:16 laptop kernel: wlan0: link state changed to UP > > Dec 4 20:19:46 laptop kernel: wlan0: link state changed to DOWN > > Dec 4 20:19:46 laptop kernel: wlan0: link state changed to UP > > Dec 4 20:36:46 laptop kernel: wlan0: link state changed to DOWN > > Dec 4 20:36:46 laptop kernel: wlan0: link state changed to UP > > Dec 4 20:45:16 laptop kernel: wlan0: link state changed to DOWN > > Dec 4 20:45:16 laptop kernel: wlan0: link state changed to UP > > Dec 4 20:53:46 laptop kernel: wlan0: link state changed to DOWN > > Dec 4 20:53:46 laptop kernel: wlan0: link state changed to UP > > > > So, every 18 minutes the devices is going DOWN/UP. :-/ > > More details please. Which driver? wpi0. > How is that stuff configured? laptop:root[204] ifconfig wpi0 wpi0: flags=8843 metric 0 mtu 2290 ether 00:1c:bf:90:ab:44 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated laptop:root[205] ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:1c:bf:90:ab:44 inet 192.168.0.10 netmask 0xffffff00 broadcast 192.168.0.255 media: IEEE 802.11 Wireless Ethernet OFDM/36Mbps mode 11g status: associated ssid SpartanTeepee channel 6 (2437 MHz 11g) bssid 00:18:e7:d4:f2:1b country US authmode OPEN privacy ON deftxkey 1 wepkey 1:40-bit txpower 0 bmiss 7 scanvalid 60 protmode CTS > wpa_supplicant involved? No. > Try running it with debug messages enabled. > > We need to figure out what entity is causing the device to go down/up, this > can either be wpa_supplicant or net80211 (or a cronjob calling ifconfig > down/up every 18 minutes ;). The appropriate debug options enabled (wlandebug > 0xffffffff or wpa_supplicant with -dd) should reveal that. laptop:root[209] wlandebug wlandebug: sysctl-get(net.wlan.0.debug): No such file or directory Looks like I need to rebuild the kernel. -- Steve