From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 18 00:58:40 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21BE51065670; Sun, 18 Dec 2011 00:58:40 +0000 (UTC) (envelope-from erichfreebsdlist@ovitrap.com) Received: from alogreentechnologies.com (alogreentechnologies.com [67.212.226.44]) by mx1.freebsd.org (Postfix) with ESMTP id C8F6C8FC08; Sun, 18 Dec 2011 00:58:39 +0000 (UTC) Received: from amd620.ovitrap.com ([122.129.201.7]) (authenticated bits=0) by alogreentechnologies.com (8.13.1/8.13.1) with ESMTP id pBI0wbdH009457; Sat, 17 Dec 2011 17:58:38 -0700 From: Erich Dollansky To: PseudoCylon Date: Sun, 18 Dec 2011 07:59:03 +0700 User-Agent: KMail/1.13.7 (FreeBSD/8.2-STABLE; KDE/4.6.5; amd64; ; ) References: <201112171258.56891.erichfreebsdlist@ovitrap.com> <201112171411.05872.bschmidt@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112180759.03722.erichfreebsdlist@ovitrap.com> Cc: freebsd-wireless@freebsd.org, Bernhard Schmidt Subject: Re: Zyxel NWD210N not accepted at boot time but after plugging it in again X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2011 00:58:40 -0000 Hi, On Sunday 18 December 2011 06:45:18 PseudoCylon wrote: > On Sat, Dec 17, 2011 at 6:11 AM, Bernhard Schmidt wrote: > > On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote: > > > > run(4) tries to load the firmware on attach at which point the root > > filesystem isn't yet mounted. Actually I think the prefered behaviour > > is to load it during init, not sure this is possible for run(4) > > though. Someone should check this. :) > > > mmm... It seems "someone" is me. > > At the quick look, the firmware could be loaded during the init. Give > me a few days, I will try to change. > if you need more information, just ask me. Please do not wonder if you do not get them at the spot. I am in a very remote location where electricity is cut off during the day. Erich > > As a workaround you can add runfw_load="YES" to /boot/loader.conf > > > Yep. This should load the firmware during the boot. > > > AK > > From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 18 05:45:32 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 200631065673 for ; Sun, 18 Dec 2011 05:45:32 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm40-vm1.bullet.mail.ne1.yahoo.com (nm40-vm1.bullet.mail.ne1.yahoo.com [98.138.229.177]) by mx1.freebsd.org (Postfix) with SMTP id B64148FC13 for ; Sun, 18 Dec 2011 05:45:31 +0000 (UTC) Received: from [98.138.90.56] by nm40.bullet.mail.ne1.yahoo.com with NNFMP; 18 Dec 2011 05:32:47 -0000 Received: from [98.138.226.56] by tm9.bullet.mail.ne1.yahoo.com with NNFMP; 18 Dec 2011 05:32:47 -0000 Received: from [127.0.0.1] by smtp207.mail.ne1.yahoo.com with NNFMP; 18 Dec 2011 05:32:47 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1324186367; bh=8CNYcE77Po8f47uYMzTY5pzLHP23C2ppW95wp7iFadE=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=00nmnDW6fkdtBePn/xmGrfSldGUVyc8Gv282V1YW4PwfzwO5O4Q+o9Hn/F/kf11BUZqItOClaNUnXo728cwBu/4JxD7IeSQXxfDCl6IPvcGOjQ9EmOt1H824kVKH0NnESY/cX/8A+hj1useXeXIXVSV4+XvUS9O2P6PlzjMcTZ4= X-Yahoo-Newman-Id: 316131.14232.bm@smtp207.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: bbra69AVM1lS5P4IUYHJp.gVF6wCabUOqWOHcvkgaZhyoeL .msenusc9Qoiqz8z4V5STEJU1mGmREZLFSLnhTn9pjC1SRkhnmi2VdNXtGTM e3fujrFS31qTxHvXyVgWHDL8.clIk40ge_qV.xCXVCpoe80CZeOdk0fMqWjU PVs3ojVIyxUDMe9o3SHP_p18x93YB8l3Fiyzw9_f6LOUEVfK2Z26ehPEM..G .691VM143VTIsBOA2NHEnpocujnwi.RcHmYB7gRPuVsQVTPzm9MdD3XVPanJ AdQ_5n8F22AHjd2WhrEhSonJ_snfHTRe1KFsCstK6QX_xBFcC0cRuhWYkpCl CBSa4f_fEs22AQacm6tIhwp3K3yxttZFOf7gCi27TTHppPnurBDZoDseicGC gGu2cp6Lk0Zv8zBohb0BfqWQ7xhuM2lg_nXI- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-iy0-f182.google.com (moonlightakkiy@209.85.210.182 with plain) by smtp207.mail.ne1.yahoo.com with SMTP; 17 Dec 2011 21:32:47 -0800 PST Received: by iadj38 with SMTP id j38so3950189iad.13 for ; Sat, 17 Dec 2011 21:32:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.236.5 with SMTP id uq5mr19685250igc.47.1324186366742; Sat, 17 Dec 2011 21:32:46 -0800 (PST) Received: by 10.231.190.81 with HTTP; Sat, 17 Dec 2011 21:32:46 -0800 (PST) In-Reply-To: <201112180759.03722.erichfreebsdlist@ovitrap.com> References: <201112171258.56891.erichfreebsdlist@ovitrap.com> <201112171411.05872.bschmidt@freebsd.org> <201112180759.03722.erichfreebsdlist@ovitrap.com> Date: Sat, 17 Dec 2011 22:32:46 -0700 Message-ID: From: PseudoCylon To: Erich Dollansky Content-Type: multipart/mixed; boundary=14dae934046101921104b4572a7b X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org, Bernhard Schmidt Subject: Re: Zyxel NWD210N not accepted at boot time but after plugging it in again X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2011 05:45:32 -0000 --14dae934046101921104b4572a7b Content-Type: text/plain; charset=ISO-8859-1 On Sat, Dec 17, 2011 at 5:59 PM, Erich Dollansky wrote: > Hi, > > On Sunday 18 December 2011 06:45:18 PseudoCylon wrote: >> On Sat, Dec 17, 2011 at 6:11 AM, Bernhard Schmidt wrote: >> > On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote: >> > >> > run(4) tries to load the firmware on attach at which point the root >> > filesystem isn't yet mounted. Actually I think the prefered behaviour >> > is to load it during init, not sure this is possible for run(4) >> > though. Someone should check this. :) >> > >> mmm... It seems "someone" is me. >> >> At the quick look, the firmware could be loaded during the init. Give >> me a few days, I will try to change. >> > if you need more information, just ask me. Please do not wonder if you do not get them at the spot. I am in a very remote location where electricity is cut off during the day. > Actually, it was quite straight forward. The patch follows. Also, a tarball is attached which include patch to man.4/run.4 and new firmware. I don't know what has been changed, but I'd appreciate if you try new firmware out. AK ## begin patch ## diff --git a/dev/usb/wlan/if_run.c b/dev/usb/wlan/if_run.c index b2c3c19..ef7c62c 100644 --- a/dev/usb/wlan/if_run.c +++ b/dev/usb/wlan/if_run.c @@ -17,7 +17,7 @@ */ #include -__FBSDID("$FreeBSD: src/sys/dev/usb/wlan/if_run.c,v 1.29 2011/12/17 10:23:17 bschmidt Exp $"); +__FBSDID("$FreeBSD$"); /*- * Ralink Technology RT2700U/RT2800U/RT3000U chipset driver. @@ -600,12 +600,6 @@ run_attach(device_t self) sc->mac_ver, sc->mac_rev, run_get_rf(sc->rf_rev), sc->ntxchains, sc->nrxchains, ether_sprintf(sc->sc_bssid)); - if ((error = run_load_microcode(sc)) != 0) { - device_printf(sc->sc_dev, "could not load 8051 microcode\n"); - RUN_UNLOCK(sc); - goto detach; - } - RUN_UNLOCK(sc); ifp = sc->sc_ifp = if_alloc(IFT_IEEE80211); @@ -1050,8 +1044,9 @@ run_load_microcode(struct run_softc *sc) error = ETIMEDOUT; goto fail; } - device_printf(sc->sc_dev, "firmware %s loaded\n", - (base == fw->data) ? "RT2870" : "RT3071"); + device_printf(sc->sc_dev, "firmware %s ver. %u.%u loaded\n", + (base == fw->data) ? "RT2870" : "RT3071", + *(base + 4092), *(base + 4093)); fail: firmware_put(fw, FIRMWARE_UNLOAD); @@ -4677,6 +4672,11 @@ run_init_locked(struct run_softc *sc) run_stop(sc); + if (run_load_microcode(sc) != 0) { + device_printf(sc->sc_dev, "could not load 8051 microcode\n"); + goto fail; + } + for (ntries = 0; ntries < 100; ntries++) { if (run_read(sc, RT2860_ASIC_VER_ID, &tmp) != 0) goto fail; --14dae934046101921104b4572a7b-- From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 18 09:53:38 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55F47106564A for ; Sun, 18 Dec 2011 09:53:38 +0000 (UTC) (envelope-from bschmidt@techwires.net) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id DF0D88FC15 for ; Sun, 18 Dec 2011 09:53:37 +0000 (UTC) Received: by eekc50 with SMTP id c50so5213845eek.13 for ; Sun, 18 Dec 2011 01:53:36 -0800 (PST) Received: by 10.213.10.145 with SMTP id p17mr1739211ebp.43.1324202016212; Sun, 18 Dec 2011 01:53:36 -0800 (PST) Received: from amy.lab.techwires.net (dslb-178-002-168-014.pools.arcor-ip.net. [178.2.168.14]) by mx.google.com with ESMTPS id 58sm27531193eet.11.2011.12.18.01.53.34 (version=SSLv3 cipher=OTHER); Sun, 18 Dec 2011 01:53:35 -0800 (PST) Sender: Bernhard Schmidt From: Bernhard Schmidt To: PseudoCylon Date: Sun, 18 Dec 2011 10:53:36 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.0-PRERELEASE; KDE/4.7.3; amd64; ; ) References: <201112171258.56891.erichfreebsdlist@ovitrap.com> <201112180759.03722.erichfreebsdlist@ovitrap.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201112181053.36699.bschmidt@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: Zyxel NWD210N not accepted at boot time but after plugging it in again X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2011 09:53:38 -0000 On Sunday 18 December 2011 06:32:46 PseudoCylon wrote: > On Sat, Dec 17, 2011 at 5:59 PM, Erich Dollansky > wrote: > > Hi, > > > > On Sunday 18 December 2011 06:45:18 PseudoCylon wrote: > >> On Sat, Dec 17, 2011 at 6:11 AM, Bernhard Schmidt wrote: > >> > On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote: > >> > > >> > run(4) tries to load the firmware on attach at which point the root > >> > filesystem isn't yet mounted. Actually I think the prefered behaviour > >> > is to load it during init, not sure this is possible for run(4) > >> > though. Someone should check this. :) > >> > > >> mmm... It seems "someone" is me. > >> > >> At the quick look, the firmware could be loaded during the init. Give > >> me a few days, I will try to change. > >> > > if you need more information, just ask me. Please do not wonder if you do not get them at the spot. I am in a very remote location where electricity is cut off during the day. > > > Actually, it was quite straight forward. The patch follows. Fine, thanks, just wasn't sure if the fw has to be loaded on attach to able to obtained whatever information. > Also, a tarball is attached which include patch to man.4/run.4 and new > firmware. I don't know what has been changed, but I'd appreciate if > you try new firmware out. Works for me, the new firmware and the fix. Given positive feedback from Erich I'm going to commit it. -- Bernhard From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 18 16:40:15 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CEEA106566B for ; Sun, 18 Dec 2011 16:40:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 526928FC12 for ; Sun, 18 Dec 2011 16:40:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBIGeFKF055211 for ; Sun, 18 Dec 2011 16:40:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBIGeFYS055210; Sun, 18 Dec 2011 16:40:15 GMT (envelope-from gnats) Date: Sun, 18 Dec 2011 16:40:15 GMT Message-Id: <201112181640.pBIGeFYS055210@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Joel Dahl Cc: Subject: Re: kern/163318: [ath] ath(4) stops working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joel Dahl List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2011 16:40:15 -0000 The following reply was made to PR kern/163318; it has been noted by GNATS. From: Joel Dahl To: bug-followup@freebsd.org Cc: Subject: Re: kern/163318: [ath] ath(4) stops working Date: Sun, 18 Dec 2011 17:35:18 +0100 Disabling bgscan with ifconfig wlan0 -bgscan fixes the problem. The machine has been running for 9 hours now without any problems. -- Joel From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 18 17:16:25 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B717C106564A for ; Sun, 18 Dec 2011 17:16:24 +0000 (UTC) (envelope-from onyx@z-up.ru) Received: from mx.z-up.ru (mx.z-up.ru [92.50.244.44]) by mx1.freebsd.org (Postfix) with ESMTP id 69CCC8FC0C for ; Sun, 18 Dec 2011 17:16:24 +0000 (UTC) Received: from onyx-y550p.loc (unknown [92.241.12.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.z-up.ru (Postfix) with ESMTPSA id 2B6CB1149D for ; Sun, 18 Dec 2011 20:56:33 +0400 (GMT-4) From: Dmitry Kolosov To: freebsd-wireless@freebsd.org Date: Sun, 18 Dec 2011 20:56:49 +0400 User-Agent: KMail/1.13.7 (FreeBSD/9.0-PRERELEASE; KDE/4.7.3; i386; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201112182056.49637.onyx@z-up.ru> Subject: Timeout while waiting for nf to load X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: onyx@z-up.ru List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2011 17:16:25 -0000 Please help! The problem: while watching a movie over NFS over wireless, transmiting and receiving stops for about 10-20 seconds every 5-10 minutes, and i see this in messages: Dec 18 20:28:06 onyx-y550p kernel: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22 Dec 18 20:28:08 onyx-y550p kernel: wlan0: link state changed to DOWN Dec 18 20:28:11 onyx-y550p kernel: wlan0: link state changed to UP Dec 18 20:33:36 onyx-y550p kernel: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22 Dec 18 20:33:38 onyx-y550p kernel: wlan0: link state changed to DOWN Dec 18 20:33:41 onyx-y550p kernel: wlan0: link state changed to UP Dec 18 20:34:36 onyx-y550p kernel: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22 Dec 18 20:34:38 onyx-y550p kernel: wlan0: link state changed to DOWN Dec 18 20:34:41 onyx-y550p kernel: wlan0: link state changed to UP Other wireless operations runs smoothly, without any glitches. I think it happens only on huge wireless load. Station: FreeBSD 9.0-PRERELEASE #5 r228415: Mon Dec 12 23:45:50 MSK 2011 ath0@pci0:6:0:0: class=0x028000 card=0x30a117aa chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR9285 Wireless Network Adapter (PCI-Express)' class = network ath0: mem 0xd7100000-0xd710ffff irq 17 at device 0.0 on pci6 ath0: [HT] enabling HT modes ath0: [HT] 1 RX streams; 1 TX streams ath0: AR9285 mac 192.2 RF5133 phy 14.0 Base: FreeBSD 8.2-STABLE #1: Tue Sep 27 01:22:02 MSD 2011 ath0@pci0:5:0:0: class=0x020000 card=0x2051168c chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = '802.11a/b/g Wireless Adapter (AR2312)' class = network subclass = ethernet Thanks in advance. -- () ascii ribbon campaign - against html mail /\ - against microsoft attachments From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 18 18:15:00 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E61E8106564A for ; Sun, 18 Dec 2011 18:14:59 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9B9438FC13 for ; Sun, 18 Dec 2011 18:14:59 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so6142856vbb.13 for ; Sun, 18 Dec 2011 10:14:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=345LP7KkSxCDXjQH9VYCQ5QiMiejYcOh8RRP7m0UoY4=; b=C3ZZiCQczVHeK6Z9OoN3yT0VU3zU6b/7jmW1YcOsawOZBM/E7LMOHfyXQAu4nbVId1 ElAq6vyuKoDJRejHAEUak1iLTVZ2rs41qU0hWCl6EtTHJNrpZpGTU0nADlMWwu3PleyF gTLQI+lJdM3StJL5LdpcVdlZwFnCapp0W+H/0= MIME-Version: 1.0 Received: by 10.52.90.80 with SMTP id bu16mr9774259vdb.113.1324232098852; Sun, 18 Dec 2011 10:14:58 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.26.50 with HTTP; Sun, 18 Dec 2011 10:14:58 -0800 (PST) In-Reply-To: <201112182056.49637.onyx@z-up.ru> References: <201112182056.49637.onyx@z-up.ru> Date: Sun, 18 Dec 2011 10:14:58 -0800 X-Google-Sender-Auth: Oovi5gER7Bx1wtK_UvqmjMzQnog Message-ID: From: Adrian Chadd To: onyx@z-up.ru Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: Timeout while waiting for nf to load X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2011 18:15:00 -0000 On 18 December 2011 08:56, Dmitry Kolosov wrote: > Please help! > The problem: while watching a movie over NFS over wireless, transmiting a= nd > receiving stops for about 10-20 seconds every 5-10 minutes, and i see thi= s in > messages: > > Dec 18 20:28:06 onyx-y550p kernel: Timeout while waiting for nf to load: > AR_PHY_AGC_CONTROL=3D0x40d22 That's odd; the only reason this occurs is when the RX side is so badly noisy, it can't find a quiet period to complete the noise floor load/update. Please file a PR. I'm a bit snowed under at the moment but I'll see if I can find anything obvious. Can you try with a different base station? I just wonder whether this is a case where the base station is getting angry and transmitting a burst of noise or something.. Adrian > Dec 18 20:28:08 onyx-y550p kernel: wlan0: link state changed to DOWN > Dec 18 20:28:11 onyx-y550p kernel: wlan0: link state changed to UP > Dec 18 20:33:36 onyx-y550p kernel: Timeout while waiting for nf to load: > AR_PHY_AGC_CONTROL=3D0x40d22 > Dec 18 20:33:38 onyx-y550p kernel: wlan0: link state changed to DOWN > Dec 18 20:33:41 onyx-y550p kernel: wlan0: link state changed to UP > Dec 18 20:34:36 onyx-y550p kernel: Timeout while waiting for nf to load: > AR_PHY_AGC_CONTROL=3D0x40d22 > Dec 18 20:34:38 onyx-y550p kernel: wlan0: link state changed to DOWN > Dec 18 20:34:41 onyx-y550p kernel: wlan0: link state changed to UP > > Other wireless operations runs smoothly, without any glitches. I think it > happens only on huge wireless load. > > Station: > FreeBSD 9.0-PRERELEASE #5 r228415: Mon Dec 12 23:45:50 MSK 2011 > ath0@pci0:6:0:0: =A0 =A0 =A0 =A0class=3D0x028000 card=3D0x30a117aa chip= =3D0x002b168c > rev=3D0x01 hdr=3D0x00 > =A0 =A0vendor =A0 =A0 =3D 'Atheros Communications Inc.' > =A0 =A0device =A0 =A0 =3D 'AR9285 Wireless Network Adapter (PCI-Express)' > =A0 =A0class =A0 =A0 =A0=3D network > ath0: mem 0xd7100000-0xd710ffff irq 17 at device 0.0 on pc= i6 > ath0: [HT] enabling HT modes > ath0: [HT] 1 RX streams; 1 TX streams > ath0: AR9285 mac 192.2 RF5133 phy 14.0 > > Base: > FreeBSD 8.2-STABLE #1: Tue Sep 27 01:22:02 MSD 2011 > ath0@pci0:5:0:0: =A0 =A0 =A0 =A0class=3D0x020000 card=3D0x2051168c chip= =3D0x0013168c > rev=3D0x01 hdr=3D0x00 > =A0 =A0vendor =A0 =A0 =3D 'Atheros Communications Inc.' > =A0 =A0device =A0 =A0 =3D '802.11a/b/g Wireless Adapter (AR2312)' > =A0 =A0class =A0 =A0 =A0=3D network > =A0 =A0subclass =A0 =3D ethernet > > Thanks in advance. > > -- > () =A0ascii ribbon campaign =A0 =A0 =A0 - against html mail > /\ =A0 =A0 =A0 =A0 =A0 =A0 =A0 - against microsoft attachments > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 18 18:20:46 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD4851065672; Sun, 18 Dec 2011 18:20:46 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by mx1.freebsd.org (Postfix) with ESMTP id 38AF28FC1E; Sun, 18 Dec 2011 18:20:45 +0000 (UTC) Received: by wgbds13 with SMTP id ds13so6148401wgb.1 for ; Sun, 18 Dec 2011 10:20:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/u3d+om0dbM3xLTd7OAVrW0FY0LsgZR+7sz5OSsuFC8=; b=wZfw9fnG0XtvNcMXUbXTYYLnrrfAZMjhXFivg56ji+Y81V5Okjf8ZFehClENLZzJCl u4Lt3OiCVM5N3OeMnViWVQMMiAOT05NwR8Ji0vVe3LimxHCEpcG/VIfr20HFaUacfAnp TwdnICTYoGr+XaEZZ0VfB3UKKfb0icJy/CeQ0= MIME-Version: 1.0 Received: by 10.180.95.136 with SMTP id dk8mr18233241wib.11.1324231026081; Sun, 18 Dec 2011 09:57:06 -0800 (PST) Received: by 10.223.158.129 with HTTP; Sun, 18 Dec 2011 09:57:06 -0800 (PST) In-Reply-To: <201112181640.pBIGeFYS055210@freefall.freebsd.org> References: <201112181640.pBIGeFYS055210@freefall.freebsd.org> Date: Sun, 18 Dec 2011 09:57:06 -0800 Message-ID: From: Kevin Oberman To: Joel Dahl Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: kern/163318: [ath] ath(4) stops working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2011 18:20:46 -0000 On Sun, Dec 18, 2011 at 8:40 AM, Joel Dahl wrote: > The following reply was made to PR kern/163318; it has been noted by GNAT= S. > > From: Joel Dahl > To: bug-followup@freebsd.org > Cc: > Subject: Re: kern/163318: [ath] ath(4) stops working > Date: Sun, 18 Dec 2011 17:35:18 +0100 > > =A0Disabling bgscan with > > =A0 ifconfig wlan0 -bgscan > > =A0fixes the problem. The machine has been running for 9 hours now withou= t any > =A0problems. I have been recommending that people having problems with wireless cards suddenly losing connectivity turn off bgscan for some time. It certainly fixed my problems with my old ath card, thought I am not sure that it is ath specific. I first reported this several years ago when Sam was still doing the ath work and received a prompt reply that I was wrong and bgscan was completely non-intrusive. I sent Sam details on exactly what I was seeing with the failures always occuring on the 5 minute intervals when background scans are done (though not at nearly every scan) and the conditions that triggered the problem and got a prompt response that what I was reporting was not possible and that whatever was causing the problems I was seeing was not bgscan. I have suggested turning off bgscan to many others reporting similar problems and gotten several responses that it worked. I am still convinced that something is not right about bgscan on FreeBSD, though I don't know if it is ath specific or more generally a wlan issue. I can say that it shows up most often when there are several APs with a common SSID showing up. I had particular problems when I was attending a large conference, such as NANOG, where there were several APs for a large room. I have no expertise on 802.11, so I can't tell much more, but I am convinced that something is wrong with bgscan on FreeBSD, at least with ath. I'd love to see someone get to the bottom of this. It has been showing up for at least 4 years and pre-dates the wlan split going back the the very early days of ath support. --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 18 18:24:39 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D95AB106567C; Sun, 18 Dec 2011 18:24:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8729C8FC18; Sun, 18 Dec 2011 18:24:39 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so6147053vbb.13 for ; Sun, 18 Dec 2011 10:24:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YMeyCupNdzO3pL/DxfCHmAXmyByjiAgSE+ayQDYnkc8=; b=xETiHJabYVCVZAKBk8LBHHG/oilLqFYI123RxzlRQ/PxieIrjRLXtenx8oqlKEhSgZ ayHG5cQfur570g/NqpWkI+9e/2k9sbYpEDMI4g0gnfkqR8zvqaVhycCW7ZoHgswVXfd7 JCg+g60JgxN7NmvVcnHpooUboIiLfselkwQTI= MIME-Version: 1.0 Received: by 10.52.20.165 with SMTP id o5mr9920922vde.79.1324232678790; Sun, 18 Dec 2011 10:24:38 -0800 (PST) Received: by 10.52.26.50 with HTTP; Sun, 18 Dec 2011 10:24:38 -0800 (PST) In-Reply-To: References: <201112181640.pBIGeFYS055210@freefall.freebsd.org> Date: Sun, 18 Dec 2011 10:24:38 -0800 Message-ID: From: Adrian Chadd To: Kevin Oberman Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org, Joel Dahl Subject: Re: kern/163318: [ath] ath(4) stops working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2011 18:24:39 -0000 Don't worry Kevin - "There's something wrong with bgscan" with 802.11n. Even with pre-11n stuff, the code for scanning resets the NIC very often (one per channel change) and this occasionally results in some weird behaviour. Further investigations are on my TODO list because of how sensitive this is with 11n. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 18 21:01:50 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C859C106566B; Sun, 18 Dec 2011 21:01:50 +0000 (UTC) (envelope-from erichfreebsdlist@ovitrap.com) Received: from alogreentechnologies.com (alogreentechnologies.com [67.212.226.44]) by mx1.freebsd.org (Postfix) with ESMTP id 96BC28FC12; Sun, 18 Dec 2011 21:01:50 +0000 (UTC) Received: from amd620.ovitrap.com ([122.129.201.21]) (authenticated bits=0) by alogreentechnologies.com (8.13.1/8.13.1) with ESMTP id pBIL1jNP001586; Sun, 18 Dec 2011 14:01:48 -0700 From: Erich Dollansky To: PseudoCylon Date: Mon, 19 Dec 2011 04:02:06 +0700 User-Agent: KMail/1.13.7 (FreeBSD/8.2-STABLE; KDE/4.6.5; amd64; ; ) References: <201112171258.56891.erichfreebsdlist@ovitrap.com> <201112180759.03722.erichfreebsdlist@ovitrap.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201112190402.07838.erichfreebsdlist@ovitrap.com> Cc: freebsd-wireless@freebsd.org, Bernhard Schmidt Subject: Re: Zyxel NWD210N not accepted at boot time but after plugging it in again X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2011 21:01:51 -0000 hI, On Sunday 18 December 2011 12:32:46 PseudoCylon wrote: > On Sat, Dec 17, 2011 at 5:59 PM, Erich Dollansky > wrote: > > On Sunday 18 December 2011 06:45:18 PseudoCylon wrote: > >> On Sat, Dec 17, 2011 at 6:11 AM, Bernhard Schmidt wrote: > >> > On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote: > >> > > >> > run(4) tries to load the firmware on attach at which point the root > >> > filesystem isn't yet mounted. Actually I think the prefered behaviour > >> > is to load it during init, not sure this is possible for run(4) > >> > though. Someone should check this. :) > >> > > >> mmm... It seems "someone" is me. > >> > >> At the quick look, the firmware could be loaded during the init. Give > >> me a few days, I will try to change. > >> > > if you need more information, just ask me. Please do not wonder if you do not get them at the spot. I am in a very remote location where electricity is cut off during the day. > > > Actually, it was quite straight forward. The patch follows. > > Also, a tarball is attached which include patch to man.4/run.4 and new > firmware. I don't know what has been changed, but I'd appreciate if > you try new firmware out. > where to place it? It would have expected /usr/src/contrib to be the place but there is no entry for run on my 8.2 machine. I compiled the kernel with the batches and will start testing now. Erich > > AK > > ## begin patch ## > > diff --git a/dev/usb/wlan/if_run.c b/dev/usb/wlan/if_run.c > index b2c3c19..ef7c62c 100644 > --- a/dev/usb/wlan/if_run.c > +++ b/dev/usb/wlan/if_run.c > @@ -17,7 +17,7 @@ > */ > > #include > -__FBSDID("$FreeBSD: src/sys/dev/usb/wlan/if_run.c,v 1.29 2011/12/17 > 10:23:17 bschmidt Exp $"); > +__FBSDID("$FreeBSD$"); > > /*- > * Ralink Technology RT2700U/RT2800U/RT3000U chipset driver. > @@ -600,12 +600,6 @@ run_attach(device_t self) > sc->mac_ver, sc->mac_rev, run_get_rf(sc->rf_rev), > sc->ntxchains, sc->nrxchains, ether_sprintf(sc->sc_bssid)); > > - if ((error = run_load_microcode(sc)) != 0) { > - device_printf(sc->sc_dev, "could not load 8051 microcode\n"); > - RUN_UNLOCK(sc); > - goto detach; > - } > - > RUN_UNLOCK(sc); > > ifp = sc->sc_ifp = if_alloc(IFT_IEEE80211); > @@ -1050,8 +1044,9 @@ run_load_microcode(struct run_softc *sc) > error = ETIMEDOUT; > goto fail; > } > - device_printf(sc->sc_dev, "firmware %s loaded\n", > - (base == fw->data) ? "RT2870" : "RT3071"); > + device_printf(sc->sc_dev, "firmware %s ver. %u.%u loaded\n", > + (base == fw->data) ? "RT2870" : "RT3071", > + *(base + 4092), *(base + 4093)); > > fail: > firmware_put(fw, FIRMWARE_UNLOAD); > @@ -4677,6 +4672,11 @@ run_init_locked(struct run_softc *sc) > > run_stop(sc); > > + if (run_load_microcode(sc) != 0) { > + device_printf(sc->sc_dev, "could not load 8051 microcode\n"); > + goto fail; > + } > + > for (ntries = 0; ntries < 100; ntries++) { > if (run_read(sc, RT2860_ASIC_VER_ID, &tmp) != 0) > goto fail; > From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 18 21:11:03 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7DBC8106566B; Sun, 18 Dec 2011 21:11:03 +0000 (UTC) (envelope-from erichfreebsdlist@ovitrap.com) Received: from alogreentechnologies.com (alogreentechnologies.com [67.212.226.44]) by mx1.freebsd.org (Postfix) with ESMTP id 4CE688FC16; Sun, 18 Dec 2011 21:11:03 +0000 (UTC) Received: from amd620.ovitrap.com ([122.129.201.21]) (authenticated bits=0) by alogreentechnologies.com (8.13.1/8.13.1) with ESMTP id pBILB1j2003512; Sun, 18 Dec 2011 14:11:02 -0700 From: Erich Dollansky To: PseudoCylon Date: Mon, 19 Dec 2011 04:11:28 +0700 User-Agent: KMail/1.13.7 (FreeBSD/8.2-STABLE; KDE/4.6.5; amd64; ; ) References: <201112171258.56891.erichfreebsdlist@ovitrap.com> <201112180759.03722.erichfreebsdlist@ovitrap.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201112190411.28991.erichfreebsdlist@ovitrap.com> Cc: freebsd-wireless@freebsd.org, Bernhard Schmidt Subject: Re: Zyxel NWD210N not accepted at boot time but after plugging it in again X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2011 21:11:03 -0000 Hi, On Sunday 18 December 2011 12:32:46 PseudoCylon wrote: > On Sat, Dec 17, 2011 at 5:59 PM, Erich Dollansky > wrote: > > Hi, > > > > On Sunday 18 December 2011 06:45:18 PseudoCylon wrote: > >> On Sat, Dec 17, 2011 at 6:11 AM, Bernhard Schmidt wrote: > >> > On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote: > >> > > >> > run(4) tries to load the firmware on attach at which point the root > >> > filesystem isn't yet mounted. Actually I think the prefered behaviour > >> > is to load it during init, not sure this is possible for run(4) > >> > though. Someone should check this. :) > >> > > >> mmm... It seems "someone" is me. > >> > >> At the quick look, the firmware could be loaded during the init. Give > >> me a few days, I will try to change. > >> > > if you need more information, just ask me. Please do not wonder if you do not get them at the spot. I am in a very remote location where electricity is cut off during the day. > > > Actually, it was quite straight forward. The patch follows. > > Also, a tarball is attached which include patch to man.4/run.4 and new > firmware. I don't know what has been changed, but I'd appreciate if > you try new firmware out. after installing the patch and rebooting the machine, the interface came up as expected. I could not test the new firmware as I did not find the location where to store it. Erich > > > AK > > ## begin patch ## > > diff --git a/dev/usb/wlan/if_run.c b/dev/usb/wlan/if_run.c > index b2c3c19..ef7c62c 100644 > --- a/dev/usb/wlan/if_run.c > +++ b/dev/usb/wlan/if_run.c > @@ -17,7 +17,7 @@ > */ > > #include > -__FBSDID("$FreeBSD: src/sys/dev/usb/wlan/if_run.c,v 1.29 2011/12/17 > 10:23:17 bschmidt Exp $"); > +__FBSDID("$FreeBSD$"); > > /*- > * Ralink Technology RT2700U/RT2800U/RT3000U chipset driver. > @@ -600,12 +600,6 @@ run_attach(device_t self) > sc->mac_ver, sc->mac_rev, run_get_rf(sc->rf_rev), > sc->ntxchains, sc->nrxchains, ether_sprintf(sc->sc_bssid)); > > - if ((error = run_load_microcode(sc)) != 0) { > - device_printf(sc->sc_dev, "could not load 8051 microcode\n"); > - RUN_UNLOCK(sc); > - goto detach; > - } > - > RUN_UNLOCK(sc); > > ifp = sc->sc_ifp = if_alloc(IFT_IEEE80211); > @@ -1050,8 +1044,9 @@ run_load_microcode(struct run_softc *sc) > error = ETIMEDOUT; > goto fail; > } > - device_printf(sc->sc_dev, "firmware %s loaded\n", > - (base == fw->data) ? "RT2870" : "RT3071"); > + device_printf(sc->sc_dev, "firmware %s ver. %u.%u loaded\n", > + (base == fw->data) ? "RT2870" : "RT3071", > + *(base + 4092), *(base + 4093)); > > fail: > firmware_put(fw, FIRMWARE_UNLOAD); > @@ -4677,6 +4672,11 @@ run_init_locked(struct run_softc *sc) > > run_stop(sc); > > + if (run_load_microcode(sc) != 0) { > + device_printf(sc->sc_dev, "could not load 8051 microcode\n"); > + goto fail; > + } > + > for (ntries = 0; ntries < 100; ntries++) { > if (run_read(sc, RT2860_ASIC_VER_ID, &tmp) != 0) > goto fail; > From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 19 04:42:04 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24196106566B for ; Mon, 19 Dec 2011 04:42:04 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from nm15.bullet.mail.sp2.yahoo.com (nm15.bullet.mail.sp2.yahoo.com [98.139.91.85]) by mx1.freebsd.org (Postfix) with SMTP id E967E8FC0A for ; Mon, 19 Dec 2011 04:42:03 +0000 (UTC) Received: from [98.139.91.70] by nm15.bullet.mail.sp2.yahoo.com with NNFMP; 19 Dec 2011 04:42:03 -0000 Received: from [98.136.185.28] by tm10.bullet.mail.sp2.yahoo.com with NNFMP; 19 Dec 2011 04:42:03 -0000 Received: from [127.0.0.1] by smtp109.mail.gq1.yahoo.com with NNFMP; 19 Dec 2011 04:42:03 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1324269723; bh=aQCkhZ8LkF9VEYuvzcHCBJzBGOAnAtwAmQRBtm5MW1M=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Received:MIME-Version:Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=ByiNscWfC+z2351f4qxBTtDXYiXul1cE6WezJ6hJJcRRX2fdsA+Gsvtq9nRclwWFP7lNsM0zB+4Nc5kBqTQuHnjqf+X2abv3LJfkDVr6Y23pF2pySZfpxwF0/HO8U/NRxEm+Ocn0QxbCZ88HE3UUSAWM9pz6wbogMIJg3Ft8Cw8= X-Yahoo-Newman-Id: 725645.92973.bm@smtp109.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: FqaWzrcVM1lt0jq2VTNUoqzbAmq81YmMYbIepcfG8kKofaQ DD_UMbBsDdwAv8QCkaqlLxmRwqa_glZBinNSvx2vcse_mZBVRZJv70JPZaqg YWgdYHirmVnDB7iHKsSCnWN_ecBQWp.79jh9gEa.XUtUAuCYO1NFsqneBjgg XjI09BhxTNHPPOLHODE.p4.yjj4GT0_1X169ST6HWNwMLkJRWbtAxmiTMHiA zTNnhkzCkiJVTdTeKImhb_DVAf8Nj5.AkSZfFAY_Wz25nybzO0iDSLMfIJZt MDY31a0mLdjyWg1DJvw3VzZc4z0B7pGHG15CvERh_P7L9blpyYWo8rY_Zo4l d._4135WmOpi6Nl_NoWO0CKRWJ2loxYMFRT1u0JLdFVctHgEvQpvMkkjTAOj QEDlxzhXUtgBbz8ZPb5aa7rfWiGfFXv7DhzCHeklXZw-- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: from mail-iy0-f182.google.com (moonlightakkiy@209.85.210.182 with plain) by smtp109.mail.gq1.yahoo.com with SMTP; 18 Dec 2011 20:42:03 -0800 PST Received: by iadj38 with SMTP id j38so5724794iad.13 for ; Sun, 18 Dec 2011 20:42:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.219.135 with SMTP id po7mr25912970igc.11.1324269722975; Sun, 18 Dec 2011 20:42:02 -0800 (PST) Received: by 10.231.190.81 with HTTP; Sun, 18 Dec 2011 20:42:02 -0800 (PST) In-Reply-To: <201112190411.28991.erichfreebsdlist@ovitrap.com> References: <201112171258.56891.erichfreebsdlist@ovitrap.com> <201112180759.03722.erichfreebsdlist@ovitrap.com> <201112190411.28991.erichfreebsdlist@ovitrap.com> Date: Sun, 18 Dec 2011 21:42:02 -0700 Message-ID: From: PseudoCylon To: Erich Dollansky Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org, Bernhard Schmidt Subject: Re: Zyxel NWD210N not accepted at boot time but after plugging it in again X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2011 04:42:04 -0000 On Sun, Dec 18, 2011 at 2:11 PM, Erich Dollansky wrote: > Hi, > > On Sunday 18 December 2011 12:32:46 PseudoCylon wrote: >> On Sat, Dec 17, 2011 at 5:59 PM, Erich Dollansky >> wrote: >> > Hi, >> > >> > On Sunday 18 December 2011 06:45:18 PseudoCylon wrote: >> >> On Sat, Dec 17, 2011 at 6:11 AM, Bernhard Schmidt wrote: >> >> > On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote: >> >> > >> >> > run(4) tries to load the firmware on attach at which point the root >> >> > filesystem isn't yet mounted. Actually I think the prefered behaviour >> >> > is to load it during init, not sure this is possible for run(4) >> >> > though. Someone should check this. :) >> >> > >> >> mmm... It seems "someone" is me. >> >> >> >> At the quick look, the firmware could be loaded during the init. Give >> >> me a few days, I will try to change. >> >> >> > if you need more information, just ask me. Please do not wonder if you do not get them at the spot. I am in a very remote location where electricity is cut off during the day. >> > >> Actually, it was quite straight forward. The patch follows. >> >> Also, a tarball is attached which include patch to man.4/run.4 and new >> firmware. I don't know what has been changed, but I'd appreciate if >> you try new firmware out. > > after installing the patch and rebooting the machine, the interface came up as expected. I could not test the new firmware as I did not find the location where to store it. > Good to hear. The original firmware is in /usr/src/sys/contrib/dev/run The easiest way is over write the firmware, cd to /usr/src/sys/modules/runfw, make, and install. The patched if_run will prints out firmware version. Old one is 0.17, new one is 0.236 AK From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 19 11:07:18 2011 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1D15106564A for ; Mon, 19 Dec 2011 11:07:18 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 851428FC16 for ; Mon, 19 Dec 2011 11:07:18 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBJB7I8J011122 for ; Mon, 19 Dec 2011 11:07:18 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBJB7HiM011120 for freebsd-wireless@FreeBSD.org; Mon, 19 Dec 2011 11:07:17 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 19 Dec 2011 11:07:17 GMT Message-Id: <201112191107.pBJB7HiM011120@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2011 11:07:18 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/163318 wireless [ath] ath(4) stops working o kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/162475 wireless [ath] functions with return type HAL_BOOL (might) retu o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o kern/143868 wireless [ath] [patch] [request] allow Atheros watchdog timeout o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 58 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 19 18:41:34 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76B43106566C for ; Mon, 19 Dec 2011 18:41:34 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (secure.freebsdsolutions.net [69.55.234.48]) by mx1.freebsd.org (Postfix) with ESMTP id 4E9998FC13 for ; Mon, 19 Dec 2011 18:41:33 +0000 (UTC) Received: from jnielsen.socialserve.com ([12.249.176.26]) (authenticated bits=0) by ns1.jnielsen.net (8.14.4/8.14.4) with ESMTP id pBJIfTJ5099233 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 19 Dec 2011 13:41:29 -0500 (EST) (envelope-from lists@jnielsen.net) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: John Nielsen In-Reply-To: Date: Mon, 19 Dec 2011 13:41:24 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <40D93FD7-96BC-4A79-B92A-E19831BA9FB5@jnielsen.net> To: Adrian Chadd X-Mailer: Apple Mail (2.1084) X-DCC--Metrics: ns1.jnielsen.net 1282; Body=2 Fuz1=2 Fuz2=2 X-Virus-Scanned: clamav-milter 0.97.2 at ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-wireless@freebsd.org Subject: Re: Is "bssid" parameter to ifconfig supported with ath? X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2011 18:41:34 -0000 On Dec 14, 2011, at 7:46 PM, Adrian Chadd wrote: > Please file another bug and I'll investigate what happened/changed. Submitted as bin/163455. > On 14 December 2011 16:21, John Nielsen wrote: >> I know at some point I was able to do e.g.: >>=20 >> ifconfig wlan0 create wlandev ath0 wlanmode hostap bssid >> ifconfig wlan1 create wlandev ath0 wlanmode hostap bssid >>=20 >> and end up with different MAC addresses on wlan0 and wlan1. Recently = (and possibly for some time) that has not been the case. All wlan = interfaces end up with the MAC address of the parent device, which = (obviously) causes problems if actually using more than one vap. Using = "wlanaddr" and a manual address instead works as expected. >>=20 >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to = "freebsd-wireless-unsubscribe@freebsd.org" >=20 From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 20 08:50:09 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7F6B106564A; Tue, 20 Dec 2011 08:50:08 +0000 (UTC) (envelope-from erichfreebsdlist@ovitrap.com) Received: from alogreentechnologies.com (alogreentechnologies.com [67.212.226.44]) by mx1.freebsd.org (Postfix) with ESMTP id B08648FC12; Tue, 20 Dec 2011 08:50:07 +0000 (UTC) Received: from amd620.ovitrap.com ([122.129.201.13]) (authenticated bits=0) by alogreentechnologies.com (8.13.1/8.13.1) with ESMTP id pBK8o4YY020954; Tue, 20 Dec 2011 01:50:06 -0700 From: Erich Dollansky To: PseudoCylon Date: Tue, 20 Dec 2011 15:49:56 +0700 User-Agent: KMail/1.13.7 (FreeBSD/8.2-STABLE; KDE/4.6.5; amd64; ; ) References: <201112171258.56891.erichfreebsdlist@ovitrap.com> <201112190411.28991.erichfreebsdlist@ovitrap.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112201549.57990.erichfreebsdlist@ovitrap.com> Cc: freebsd-wireless@freebsd.org, Bernhard Schmidt Subject: Re: Zyxel NWD210N not accepted at boot time but after plugging it in again X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2011 08:50:09 -0000 Hi, On Monday 19 December 2011 11:42:02 PseudoCylon wrote: > On Sun, Dec 18, 2011 at 2:11 PM, Erich Dollansky > wrote: > > Hi, > > > > On Sunday 18 December 2011 12:32:46 PseudoCylon wrote: > >> On Sat, Dec 17, 2011 at 5:59 PM, Erich Dollansky > >> wrote: > >> > Hi, > >> > > >> > On Sunday 18 December 2011 06:45:18 PseudoCylon wrote: > >> >> On Sat, Dec 17, 2011 at 6:11 AM, Bernhard Schmidt wrote: > >> >> > On Saturday 17 December 2011 06:58:56 Erich Dollansky wrote: > >> >> > > >> >> > run(4) tries to load the firmware on attach at which point the root > >> >> > filesystem isn't yet mounted. Actually I think the prefered behaviour > >> >> > is to load it during init, not sure this is possible for run(4) > >> >> > though. Someone should check this. :) > >> >> > > >> >> mmm... It seems "someone" is me. > >> >> > >> >> At the quick look, the firmware could be loaded during the init. Give > >> >> me a few days, I will try to change. > >> >> > >> > if you need more information, just ask me. Please do not wonder if you do not get them at the spot. I am in a very remote location where electricity is cut off during the day. > >> > > >> Actually, it was quite straight forward. The patch follows. > >> > >> Also, a tarball is attached which include patch to man.4/run.4 and new > >> firmware. I don't know what has been changed, but I'd appreciate if > >> you try new firmware out. > > > > after installing the patch and rebooting the machine, the interface came up as expected. I could not test the new firmware as I did not find the location where to store it. > > > Good to hear. > > The original firmware is in /usr/src/sys/contrib/dev/run The easiest > way is over write the firmware, cd to /usr/src/sys/modules/runfw, > make, and install. The patched if_run will prints out firmware > version. Old one is 0.17, new one is 0.236 oh, I did not look at the obvious place as it looks like. I just install a new kernel with this firmware. I was off-line for some time for other technical reasons. If you hear nothing from me anymore, it works as expected. Erich From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 20 12:43:45 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73C84106564A; Tue, 20 Dec 2011 12:43:45 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4A1138FC13; Tue, 20 Dec 2011 12:43:45 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBKChjl3076702; Tue, 20 Dec 2011 12:43:45 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBKChjdv076698; Tue, 20 Dec 2011 12:43:45 GMT (envelope-from arundel) Date: Tue, 20 Dec 2011 12:43:45 GMT Message-Id: <201112201243.pBKChjdv076698@freefall.freebsd.org> To: arundel@FreeBSD.org, arundel@FreeBSD.org, freebsd-wireless@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: kern/162475: [ath] functions with return type HAL_BOOL (might) return HAL_STATUS X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2011 12:43:45 -0000 Synopsis: [ath] functions with return type HAL_BOOL (might) return HAL_STATUS State-Changed-From-To: open->patched State-Changed-By: arundel State-Changed-When: Tue Dec 20 12:42:34 UTC 2011 State-Changed-Why: the warnings in my followup mail (dated Sat, 3 Dec 2011), were fixed in r228621 by bschmidt@. the HAL_BOOL/HAL_STATUS issue has not been fixed, yet. http://www.freebsd.org/cgi/query-pr.cgi?pr=162475 From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 20 12:44:32 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88869106568D; Tue, 20 Dec 2011 12:44:32 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5E9A78FC12; Tue, 20 Dec 2011 12:44:32 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBKCiWKX076785; Tue, 20 Dec 2011 12:44:32 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBKCiW8I076781; Tue, 20 Dec 2011 12:44:32 GMT (envelope-from arundel) Date: Tue, 20 Dec 2011 12:44:32 GMT Message-Id: <201112201244.pBKCiW8I076781@freefall.freebsd.org> To: arundel@FreeBSD.org, freebsd-wireless@FreeBSD.org, adrian@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: kern/162475: [ath] functions with return type HAL_BOOL (might) return HAL_STATUS X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2011 12:44:32 -0000 Synopsis: [ath] functions with return type HAL_BOOL (might) return HAL_STATUS Responsible-Changed-From-To: freebsd-wireless->adrian Responsible-Changed-By: arundel Responsible-Changed-When: Tue Dec 20 12:43:56 UTC 2011 Responsible-Changed-Why: Over to adrian@ who volunteered to fix the HAL_BOOL/HAL_STATUS warnings. http://www.freebsd.org/cgi/query-pr.cgi?pr=162475 From owner-freebsd-wireless@FreeBSD.ORG Wed Dec 21 20:35:56 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B69ED106566C for ; Wed, 21 Dec 2011 20:35:56 +0000 (UTC) (envelope-from ml-freebsd-wireless@bettercom.de) Received: from mail.bettermail.de (f0.bettercom.de [95.156.194.53]) by mx1.freebsd.org (Postfix) with ESMTP id 188FA8FC0C for ; Wed, 21 Dec 2011 20:35:55 +0000 (UTC) Received: (qmail 46385 invoked by uid 98); 21 Dec 2011 21:09:13 +0100 Received: from 178.203.181.49 by f0.bettercom.de (envelope-from , uid 82) with qmail-scanner-2.01 (clamdscan: 0.96.3/12172. Clear:RC:1(178.203.181.49):. Processed in 0.019454 secs); 21 Dec 2011 20:09:13 -0000 Received: from ip-178-203-181-49.unitymediagroup.de (HELO [192.168.178.5]) (martin@[178.203.181.49]) (envelope-sender ) by mail.bettermail.de (qmail-ldap-1.03) with CAMELLIA256-SHA encrypted SMTP for ; 21 Dec 2011 21:09:13 +0100 Message-ID: <4EF23CD7.7090402@bettercom.de> Date: Wed, 21 Dec 2011 21:08:55 +0100 From: Martin Lesser User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: stuck beacon with if_ath: old but unresolved issue X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2011 20:35:56 -0000 Hi all, I'm wondering if anyone has an idea how to fix http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/155100 - it's occuring on newer kernels as well as on older ones: [ml@fs ~]$ uname -a FreeBSD fs.bettercom.de 8.2-RELEASE-p3 FreeBSD 8.2-RELEASE-p3 #0: Tue Sep 27 18:07:27 UTC 2011 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 [ml@fs ~]$ ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:1b:11:0d:69:2f inet 192.168.100.1 netmask 0xffffff00 broadcast 192.168.100.255 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid BC_Home2 channel 5 (2432 MHz 11g) bssid 00:1b:11:0d:69:2f regdomain ETSI country DE indoor ecm authmode WPA1+WPA2/802.11i privacy MIXED deftxkey 3 TKIP 2:128-bit TKIP 3:128-bit txpower 30 scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs Extract from /var/log/messages: ath0: mem 0xd4000000-0xd400ffff irq 17 at device 4.0 on pci5 ath0: AR5413 mac 10.5 RF5413 phy 6.1 ... Dec 21 19:43:56 fs kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 21 19:44:12 fs kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 21 19:46:31 fs last message repeated 3 times Dec 21 19:51:09 fs last message repeated 2 times Dec 21 20:04:33 fs kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 21 20:05:01 fs last message repeated 11 times Dec 21 20:07:10 fs last message repeated 32 times Dec 21 20:11:49 fs last message repeated 32 times Extract from /etc/rc.conf: wlans_ath0="wlan0" create_args_wlan0="wlanmode hostap country DE" ifconfig_wlan0="inet 192.168.100.1 netmask 255.255.255.0 up channel 5:g" I'm not living in a crowded area instead my FreeBSD-box has channel 5 "exclusiv"; only 2 or 3 other APs are in range of the box but working on another frequency (channels 1,2 and 11). BUT: The lines above from messages occured when the box sent bytes via another AP on channel 1 to which the BSD-box is connected via ethernet. This other AP has another bssid. So no traffic was sent on wlan0 interface but ath0 was affected by traffic generated nearby as you can see above. Finally the error may crash the box if wireless traffic keeps on a high rate (former postings about this issue state that too). What can I provide to get this bug in if_ath.c fixed? I would really like to use my BSD-box also as AP but in the moment I cannot do that reliable. At the moment I'm concerned whether a 3rd may be able to crash my BSD-box by producing a large amount of wireless traffic... Regards Martin From owner-freebsd-wireless@FreeBSD.ORG Wed Dec 21 21:05:17 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C13441065672 for ; Wed, 21 Dec 2011 21:05:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 793698FC0A for ; Wed, 21 Dec 2011 21:05:17 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so10607879vcb.13 for ; Wed, 21 Dec 2011 13:05:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=8NIdy+f3K17Evd+yK6BdTRrzQZRon+/e7wC4J9BzZAI=; b=iTUoeK5npB3oATemZ8qNetAylDrSI09k+P+KmIaCIZTrtwkl6N1L1eJlRocJltjTxK TVpUE7ueaIFvh7dA+pqHAflwDQVJ3hwuR18X2wbNiDbXbgGjfgwc2ILv6RqItQdxlqUm 3yHtNFk7+wy+OIKk291H5qW+0QH9s2khgzDoQ= MIME-Version: 1.0 Received: by 10.220.232.10 with SMTP id js10mr6060485vcb.22.1324501516614; Wed, 21 Dec 2011 13:05:16 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.158.104 with HTTP; Wed, 21 Dec 2011 13:05:16 -0800 (PST) In-Reply-To: <4EF23CD7.7090402@bettercom.de> References: <4EF23CD7.7090402@bettercom.de> Date: Wed, 21 Dec 2011 13:05:16 -0800 X-Google-Sender-Auth: hojFa5H2OrZIU5VqSd17zxTo-9c Message-ID: From: Adrian Chadd To: Martin Lesser Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: stuck beacon with if_ath: old but unresolved issue X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2011 21:05:17 -0000 Does this happen on -HEAD too? Adrian On 21 December 2011 12:08, Martin Lesser wrote: > Hi all, > > I'm wondering if anyone has an idea how to fix > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/155100 - it's occuring = on > newer kernels as well as on older ones: > > [ml@fs ~]$ uname -a > FreeBSD fs.bettercom.de 8.2-RELEASE-p3 FreeBSD 8.2-RELEASE-p3 #0: Tue Sep= 27 > 18:07:27 UTC 2011 > root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC =A0i386 > > [ml@fs ~]$ ifconfig wlan0 > wlan0: flags=3D8843 metric 0 mtu = 1500 > =A0 =A0 =A0 =A0ether 00:1b:11:0d:69:2f > =A0 =A0 =A0 =A0inet 192.168.100.1 netmask 0xffffff00 broadcast 192.168.10= 0.255 > =A0 =A0 =A0 =A0media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <= hostap> > =A0 =A0 =A0 =A0status: running > =A0 =A0 =A0 =A0ssid BC_Home2 channel 5 (2432 MHz 11g) bssid 00:1b:11:0d:6= 9:2f > =A0 =A0 =A0 =A0regdomain ETSI country DE indoor ecm authmode WPA1+WPA2/80= 2.11i > =A0 =A0 =A0 =A0privacy MIXED deftxkey 3 TKIP 2:128-bit TKIP 3:128-bit txp= ower 30 > =A0 =A0 =A0 =A0scanvalid 60 protmode CTS wme burst dtimperiod 1 -dfs > > Extract from /var/log/messages: > > ath0: mem 0xd4000000-0xd400ffff irq 17 at device 4.0 on pc= i5 > ath0: AR5413 mac 10.5 RF5413 phy 6.1 > ... > Dec 21 19:43:56 fs kernel: ath0: stuck beacon; resetting (bmiss count 4) > Dec 21 19:44:12 fs kernel: ath0: stuck beacon; resetting (bmiss count 4) > Dec 21 19:46:31 fs last message repeated 3 times > Dec 21 19:51:09 fs last message repeated 2 times > Dec 21 20:04:33 fs kernel: ath0: stuck beacon; resetting (bmiss count 4) > Dec 21 20:05:01 fs last message repeated 11 times > Dec 21 20:07:10 fs last message repeated 32 times > Dec 21 20:11:49 fs last message repeated 32 times > > Extract from /etc/rc.conf: > > wlans_ath0=3D"wlan0" > create_args_wlan0=3D"wlanmode hostap country DE" > ifconfig_wlan0=3D"inet 192.168.100.1 netmask 255.255.255.0 up channel 5:g= " > > I'm not living in a crowded area instead my FreeBSD-box has channel 5 > "exclusiv"; only 2 or 3 other APs are in range of the box but working on > another frequency (channels 1,2 and 11). > > BUT: The lines above from messages occured when the box sent bytes via > another AP on channel 1 to which the BSD-box is connected via ethernet. T= his > other AP has another bssid. So no traffic was sent on wlan0 interface but > ath0 was affected by traffic generated nearby as you can see above. Final= ly > the error may crash the box if wireless traffic keeps on a high rate (for= mer > postings about this issue state that too). > > What can I provide to get this bug in if_ath.c fixed? I would really like= to > use my BSD-box also as AP but in the moment I cannot do that reliable. At > the moment I'm concerned whether a 3rd may be able to crash my BSD-box by > producing a large amount of wireless traffic... > > Regards > > Martin > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" From owner-freebsd-wireless@FreeBSD.ORG Wed Dec 21 21:12:46 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76325106564A for ; Wed, 21 Dec 2011 21:12:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2BA908FC16 for ; Wed, 21 Dec 2011 21:12:45 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so10616905vcb.13 for ; Wed, 21 Dec 2011 13:12:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=i/Rr8R60QhptC+T2Uq0tdY3XwYpICwe+Dc3zLFSGJFY=; b=ilFajnrrBTHddCYMby7OS0tuoRikgglfmPMgrKJWD1ANOrPTeB/YLIIi7OPianU/Dj Fbem/Oi5//HPUt7dLm01iUAUCEqoBgQdoJJEXL8/A9cMQeaVYTDliQ2TndUmCPAMTJmo XZBp1/YEdOOYnqJStU6mAzhim2SbGyd4OfinM= MIME-Version: 1.0 Received: by 10.52.94.75 with SMTP id da11mr4705398vdb.111.1324501965391; Wed, 21 Dec 2011 13:12:45 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.158.104 with HTTP; Wed, 21 Dec 2011 13:12:45 -0800 (PST) In-Reply-To: References: <4EF23CD7.7090402@bettercom.de> Date: Wed, 21 Dec 2011 13:12:45 -0800 X-Google-Sender-Auth: X--Fxdn0Zg3wOKR4GAFTMMS4-hs Message-ID: From: Adrian Chadd To: Martin Lesser Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: stuck beacon with if_ath: old but unresolved issue X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2011 21:12:46 -0000 So the background with this kind of issue is that "stuck beacon" can mean a lot of things. It first means "I can't transmit the beacon", which could be (and this isn't an exhaustive list): * due to DMA activity (eg, it can't DMA because the bus is busy); * due to incorrect programming (eg something I found w/ staggered beacons and the content-after-beacon window programming, this upset some of the later generation MACs); * due to busy air (ie the baseband thinks the air is constantly too busy to transmit); * due to incorrect radio programming (eg the ANI code changes the radio parameters in a way that makes things more sensitive to busy air); * due to incorrect antenna selection/programming/design - eg, the noise floor calibration occurs based on a non-attached antenna, but the busy air is received on the attached antenna, causing some very incorrect values to be programmed in. * completely busted hardware - eg, you may find your hardware has noise spurs in the 2.4ghz region. It's sometimes possible to program around these but quite often it isn't. (And who knows what the manufacturer put in their driver to work around this.) The trick is figuring out what is actually going on. The 0th step is to try -HEAD. :-) I fixed a bunch of subtle incorrect programming which hasn't necessarily been backported to -9. So please, try -HEAD out. The first step is to identify whether the bus is busy. Your bus isn't, so I bet it's not that. The next step is to see how busy the hardware thinks the air is. I unfortunately need to backport this work to -HEAD in order to make this easily doable. If it's a "busy air" problem, hopefully we can figure out whether it's just a case of twiddling the ANI parameters to deal with things a bit better. But it could be due to antenna stuff, or noise spurs, or incorrect radio programming. I don't know the pre-11n NICs at all and I haven't yet gone looking for the legacy chipset documentation. So please bear with me whilst I go through this transition into my new job (which is wireless, but not hacking on FreeBSD code during paid hours.) I do have plans to write some more debugging and diagnostic tools but I'm just swamped at the moment. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Dec 21 23:36:49 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B2AF106566C for ; Wed, 21 Dec 2011 23:36:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 028EC8FC17 for ; Wed, 21 Dec 2011 23:36:48 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so10766173vcb.13 for ; Wed, 21 Dec 2011 15:36:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Khbwagx0OA45zYmG2+c13I4+vlKQP+AGjT+sp/6Fs0Q=; b=IczLMOPWDGbVZtLKW6xH5+O08mbQQanFKyPqHUeT3LD8gVWQF0hFLkJso47Lxq/JOl W0U4BdLMFy52diX6br0f4ZLFRKIboiAwsmAN08N2ziy4b6587rfZyTgixaouLddsTPn0 hmJ+sNDTS008VLsKWpNtx6+dbl4pKcpFmAjSE= MIME-Version: 1.0 Received: by 10.220.232.10 with SMTP id js10mr6334312vcb.22.1324510608211; Wed, 21 Dec 2011 15:36:48 -0800 (PST) Received: by 10.52.158.104 with HTTP; Wed, 21 Dec 2011 15:36:48 -0800 (PST) In-Reply-To: References: <3d4d2d249836fafc6acd885693c02198@webmail.entel.upc.edu> <4ECFCDAB.1080407@entel.upc.edu> <4ED3B4D1.3020701@entel.upc.edu> <4EDA4BBA.6010203@entel.upc.edu> <4EDA609F.2080401@entel.upc.edu> <4EDB3A2B.4050503@entel.upc.edu> Date: Wed, 21 Dec 2011 15:36:48 -0800 Message-ID: From: Adrian Chadd To: Gustau Perez Querol Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org Subject: Re: Big delays between an AR5416 AP and its clients X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2011 23:36:49 -0000 Hiya, Just FYI, I've acquired an older IBM Thinkpad which I can use with pccard devices, which include AR5416 based NICs. I'll update the driver on this box to -HEAD and begin doing some testing. Thanks, Adrian On 15 December 2011 00:57, Gustau Perez Querol wrote= : > On Sun, 4 Dec 2011 18:19:29 +0800, Adrian Chadd wrote: >> >> I'll take care of pulling it apart for you. Just give me a week and a >> half to move, ok? :) >> >> >> Adrian > > > =A0Hi Adrian, > > =A0sorry to poke you, but you asked me to do it at Dec 15th (+1UTC it is = 10 in > the morning, I'll guess it is late at night at the west coast of USA). > > =A0I filled a PR (kern/163237) and I added a few info of the tests I did. > > =A0Today I'll try to enable tx loggin and see what it throws me. I'll sen= d the > info to the pr and to the list. > > =A0There's also the possibility of stripping the revision that caused the > regression, but the diff is too large and that blocks me to do the task, > because I guess there would be a lot of dependencies between the differen= t > pieces of the revision. You suggested that you will do the past and provi= de > me with incremental patches to test where the regression is. I just wante= d > to remind you this possibility appart from the tx/rx loggin way. > > =A0Thank you for your help on this! > > =A0Gustau > From owner-freebsd-wireless@FreeBSD.ORG Thu Dec 22 23:19:58 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC0531065670; Thu, 22 Dec 2011 23:19:58 +0000 (UTC) (envelope-from adrian@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AC6878FC08; Thu, 22 Dec 2011 23:19:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBMNJw7q003894; Thu, 22 Dec 2011 23:19:58 GMT (envelope-from adrian@freefall.freebsd.org) Received: (from adrian@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBMNJwJD003890; Thu, 22 Dec 2011 23:19:58 GMT (envelope-from adrian) Date: Thu, 22 Dec 2011 23:19:58 GMT Message-Id: <201112222319.pBMNJwJD003890@freefall.freebsd.org> To: graham@menhennitt.com.au, adrian@FreeBSD.org, freebsd-wireless@FreeBSD.org From: adrian@FreeBSD.org Cc: Subject: Re: kern/143868: [ath] [patch] [request] allow Atheros watchdog timeout to be tunable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2011 23:19:58 -0000 Synopsis: [ath] [patch] [request] allow Atheros watchdog timeout to be tunable State-Changed-From-To: open->closed State-Changed-By: adrian State-Changed-When: Thu Dec 22 23:19:14 UTC 2011 State-Changed-Why: Submitter reports thus: == The Soekris box net5501 I use as my router/WAP/server used to report timeouts every few seconds. I upped that timeout value by changing the code to fix it (well, actually, reduce it to a managable level). It seemed that this should be tunable via a sysctl instead. I've added a second antenna for diversity and that seems to have fixed the problem completely. So, I don't need it any longer. == This is a common problem - if not all antennas are configured, the radio/baseband can incorrectly calibrate things and it shows up as a "stuck beacon". http://www.freebsd.org/cgi/query-pr.cgi?pr=143868 From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 23 02:30:15 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 951431065670 for ; Fri, 23 Dec 2011 02:30:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 662708FC19 for ; Fri, 23 Dec 2011 02:30:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBN2UFJb081310 for ; Fri, 23 Dec 2011 02:30:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBN2UFXU081305; Fri, 23 Dec 2011 02:30:15 GMT (envelope-from gnats) Date: Fri, 23 Dec 2011 02:30:15 GMT Message-Id: <201112230230.pBN2UFXU081305@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/163312: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2011 02:30:15 -0000 The following reply was made to PR kern/163312; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/163312: commit references a PR Date: Fri, 23 Dec 2011 02:21:36 +0000 (UTC) Author: adrian Date: Fri Dec 23 02:21:22 2011 New Revision: 228829 URL: http://svn.freebsd.org/changeset/base/228829 Log: Add a temporary debugging statement in order to try and identify what's going on with the occasional garbage rs_antenna field reported by AR9285 users. I've discovered that the 11n NICs only fill out the entire RX status descriptor on the final descriptor in an aggregate. Some of the fields (notably RSSI) are complete nonsense for A-MPDU subframes. This may be another example of this. The driver doesn't currently toss out statistics for non-final aggregate frames. It's likely that this should be done. If any users hit this particular debugging message they should report it immediately to freebsd-wireless@freebsd.org - please ensure you have ATH_DEBUG enabled so it prints out the full receive descriptor. PR: kern/163312 Modified: head/sys/dev/ath/if_ath.c Modified: head/sys/dev/ath/if_ath.c ============================================================================== --- head/sys/dev/ath/if_ath.c Fri Dec 23 02:13:42 2011 (r228828) +++ head/sys/dev/ath/if_ath.c Fri Dec 23 02:21:22 2011 (r228829) @@ -4111,6 +4111,35 @@ rx_accept: m->m_pkthdr.len = len; } + /* + * Validate rs->rs_antenna. + * + * Some users w/ AR9285 NICs have reported crashes + * here because rs_antenna field is bogusly large. + * Let's enforce the maximum antenna limit of 8 + * (and it shouldn't be hard coded, but that's a + * separate problem) and if there's an issue, print + * out an error and adjust rs_antenna to something + * sensible. + * + * This code should be removed once the actual + * root cause of the issue has been identified. + * For example, it may be that the rs_antenna + * field is only valid for the lsat frame of + * an aggregate and it just happens that it is + * "mostly" right. (This is a general statement - + * the majority of the statistics are only valid + * for the last frame in an aggregate. + */ + if (rs->rs_antenna > 7) { + device_printf(sc->sc_dev, "%s: rs_antenna > 7 (%d)\n", + __func__, rs->rs_antenna); +#ifdef ATH_DEBUG + ath_printrxbuf(sc, bf, 0, status == HAL_OK); +#endif /* ATH_DEBUG */ + rs->rs_antenna = 0; /* XXX better than nothing */ + } + ifp->if_ipackets++; sc->sc_stats.ast_ant_rx[rs->rs_antenna]++; _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 23 04:02:08 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0820A106566B for ; Fri, 23 Dec 2011 04:02:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id B157F8FC14 for ; Fri, 23 Dec 2011 04:02:07 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so12597142vbb.13 for ; Thu, 22 Dec 2011 20:02:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=XmMiamACIlV/9lez/znDgKASBvQvVKw4eqh/QNvx0oI=; b=wVxEoqJnTZAf+fZfkSbP9cJQkjqQVI0a4gr50BA9IbOZVv4hfwN+/7lrDd98qAPBbK az8f6FqJg5NSwZP8uHiYlchfUy4MHdT+5Rfll0IY9g4YeqYF9KQMacUSipZ5oHx7EPwM NxKED3o06UCswCgI9i3/40XtX9FmaotcEKRV0= MIME-Version: 1.0 Received: by 10.52.23.44 with SMTP id j12mr802905vdf.117.1324612926877; Thu, 22 Dec 2011 20:02:06 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Thu, 22 Dec 2011 20:02:06 -0800 (PST) Date: Thu, 22 Dec 2011 20:02:06 -0800 X-Google-Sender-Auth: Pr2YraIXJu-zt-qHmhVyHrraGhA Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: ath updates - please test X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2011 04:02:08 -0000 Hi all, I've added a few patches to the ath driver. I'd appreciate some testing: * I've attempted to mitigate the issue with concurrent reset/channel change which has logged some 'danger!' messages. Let me know if you see anything logged with the word "danger" in it. * I've added a bit of code which logs what the RX completion descriptor contents are if the rs_antenna field is invalid. Those with AR9285's may have seen this - it panics your machine. Please compile with ATH_DEBUG and let me know what it says. I've still got a long list of things to test and fix with the current code so I'm still not yet comfortable flipping on 11n by default. If you're able to test this code (hostap or station mode) then please, flip on ATH_ENABLE_11N and all the debugging options and give it a whirl. Happy holidays! adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 23 08:04:16 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB29F1065670 for ; Fri, 23 Dec 2011 08:04:16 +0000 (UTC) (envelope-from ml-freebsd-wireless@bettercom.de) Received: from mail.bettermail.de (f0.bettercom.de [95.156.194.53]) by mx1.freebsd.org (Postfix) with ESMTP id 1BE158FC13 for ; Fri, 23 Dec 2011 08:04:15 +0000 (UTC) Received: (qmail 25718 invoked by uid 98); 23 Dec 2011 09:04:13 +0100 Received: from 178.203.181.49 by f0.bettercom.de (envelope-from , uid 82) with qmail-scanner-2.01 (clamdscan: 0.96.3/12172. Clear:RC:1(178.203.181.49):. Processed in 0.01862 secs); 23 Dec 2011 08:04:13 -0000 Received: from ip-178-203-181-49.unitymediagroup.de (HELO [192.168.178.5]) (martin@[178.203.181.49]) (envelope-sender ) by mail.bettermail.de (qmail-ldap-1.03) with CAMELLIA256-SHA encrypted SMTP for ; 23 Dec 2011 09:04:13 +0100 Message-ID: <4EF435E8.4070900@bettercom.de> Date: Fri, 23 Dec 2011 09:03:52 +0100 From: Martin Lesser User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15 MIME-Version: 1.0 To: Adrian Chadd References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org Subject: Re: ath updates - please test X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2011 08:04:16 -0000 Hi Adrian, I will do that just in a few days. At the moment I've trouble building world and so the new kernel (it's a few years ago since I did that the last time :-( ) And upcoming christmas consumes also time here... But I promise I'll do the tests this year... Thanks for your work and your massive engagement for wireless in general and this issue. Martin Am 23.12.2011 05:02, schrieb Adrian Chadd: > Hi all, > > I've added a few patches to the ath driver. I'd appreciate some testing: > > * I've attempted to mitigate the issue with concurrent reset/channel > change which has logged some 'danger!' messages. Let me know if you > see anything logged with the word "danger" in it. > * I've added a bit of code which logs what the RX completion > descriptor contents are if the rs_antenna field is invalid. Those with > AR9285's may have seen this - it panics your machine. > Please compile with ATH_DEBUG and let me know what it says. > > I've still got a long list of things to test and fix with the current > code so I'm still not yet comfortable flipping on 11n by default. If > you're able to test this code (hostap or station mode) then please, > flip on ATH_ENABLE_11N and all the debugging options and give it a > whirl. > > Happy holidays! > > > adrian > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 23 09:57:31 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8EBD3106564A for ; Fri, 23 Dec 2011 09:57:31 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4BFE88FC13 for ; Fri, 23 Dec 2011 09:57:30 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so12857124vbb.13 for ; Fri, 23 Dec 2011 01:57:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=ZoLwDIDpeGbFw7ylcFtheAkFlJMI5/eKP1vHhFizKAA=; b=fMbcQf5ET0oSHqBAHQnk/rdTEcyEOD5W3OIuNCSUKtafyddYbLEK0o/Oiu05sYQrd5 dBRTN5/aCp1y/Kw2seBwAoVH6YY64Q9cNMsV0a16r2Xc0jRpWJhllDMS1KSjYrupuj/9 eGFjmTdBEj1TUAJFTTkDNrTJspo5FFo1+jp7Y= MIME-Version: 1.0 Received: by 10.52.29.16 with SMTP id f16mr7413669vdh.45.1324634250490; Fri, 23 Dec 2011 01:57:30 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Fri, 23 Dec 2011 01:57:30 -0800 (PST) Date: Fri, 23 Dec 2011 01:57:30 -0800 X-Google-Sender-Auth: cSx9-632OotEcyq5OzA4c3OaaTE Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: ath updates - AR5416 (and later) LED fixes X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2011 09:57:31 -0000 Hi, I've found some issues with the LED code in the HAL. The short version: we're not programming the LED pins right. The long version: * The GPIO multiplexer wasn't being programmed correctly; * The values being written into AR_MAC_LED (which control what the MAC network state and power LEDs are doing) were wrong; * We're not programming both LEDs - I think we're just programming the network LED. I've fixed things up so the Link LED on my D-Link AR5416 NIC works. I bet that other 11n NICs now work (if they have LEDs, or the LEDs are wired to the board.) I unfortunately don't have anything to test though. No wait, I lie - the onboard AR9280 in this IBM thinkpad has GPIO 1 wired into the wireless lan LED, and that's now happily blinking away when I flip on the right softled configuration. So maybe we'll finally have working wireless LAN LED blinking for the 11n NICs. :) Ok, so if someone would like a bit of a mini-project, I can give you all the relevant documentation and braindump what I've managed to figure out re: LED handling. It's going to be a bit messy as there's a whole load of potential ways that the LEDs can be configured but I think it's worthwhile to get right. Especially if you'd like an introductory project. Adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 23 19:22:57 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00B6B106564A; Fri, 23 Dec 2011 19:22:57 +0000 (UTC) (envelope-from adrian@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CB5418FC12; Fri, 23 Dec 2011 19:22:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBNJMusJ088641; Fri, 23 Dec 2011 19:22:56 GMT (envelope-from adrian@freefall.freebsd.org) Received: (from adrian@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBNJMu94088637; Fri, 23 Dec 2011 19:22:56 GMT (envelope-from adrian) Date: Fri, 23 Dec 2011 19:22:56 GMT Message-Id: <201112231922.pBNJMu94088637@freefall.freebsd.org> To: adrian@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: adrian@FreeBSD.org Cc: Subject: Re: kern/163573: [ath] hostap mode TX buffer hang X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2011 19:22:57 -0000 Synopsis: [ath] hostap mode TX buffer hang Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: adrian Responsible-Changed-When: Fri Dec 23 19:22:34 UTC 2011 Responsible-Changed-Why: Over to -wireless. http://www.freebsd.org/cgi/query-pr.cgi?pr=163573 From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 23 23:13:14 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE6621065675 for ; Fri, 23 Dec 2011 23:13:14 +0000 (UTC) (envelope-from ml-freebsd-wireless@bettercom.de) Received: from mail.bettermail.de (f0.bettercom.de [95.156.194.53]) by mx1.freebsd.org (Postfix) with ESMTP id 51CE88FC22 for ; Fri, 23 Dec 2011 23:13:13 +0000 (UTC) Received: (qmail 91399 invoked by uid 98); 24 Dec 2011 00:13:12 +0100 Received: from 178.203.181.49 by f0.bettercom.de (envelope-from , uid 82) with qmail-scanner-2.01 (clamdscan: 0.96.3/12172. Clear:RC:1(178.203.181.49):. Processed in 0.012235 secs); 23 Dec 2011 23:13:12 -0000 Received: from ip-178-203-181-49.unitymediagroup.de (HELO [192.168.178.5]) (martin@[178.203.181.49]) (envelope-sender ) by mail.bettermail.de (qmail-ldap-1.03) with CAMELLIA256-SHA encrypted SMTP for ; 24 Dec 2011 00:13:12 +0100 Message-ID: <4EF50AF4.3030105@bettercom.de> Date: Sat, 24 Dec 2011 00:12:52 +0100 From: Martin Lesser User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-wireless@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ath updates - please test X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2011 23:13:15 -0000 Hi Adrian, hi all, > I've added a few patches to the ath driver. I'd appreciate some testing: No more ("old" stuck beacon) errors until now with HEAD (r228833). Tested under several different conditions (acting as AP, with and without connected clients, switching between different channels, etc). So it looks good. Thanks again. > I've still got a long list of things to test and fix with the current > code so I'm still not yet comfortable flipping on 11n by default. If > you're able to test this code (hostap or station mode) then please, > flip on ATH_ENABLE_11N and all the debugging options and give it a > whirl. I'll do that. But does it make sense with an -based card? Or only newer chips? Martin From owner-freebsd-wireless@FreeBSD.ORG Fri Dec 23 23:45:58 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72CFC106566C for ; Fri, 23 Dec 2011 23:45:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 30C198FC0A for ; Fri, 23 Dec 2011 23:45:57 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so13544718vbb.13 for ; Fri, 23 Dec 2011 15:45:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=/wQQewzbcuMXCj6/E8EbbMzwMdy6YhmLT6XgEChWfWA=; b=vQuPcUhcArBCHq/R96KeOkW8eStn2iKzLouI/OgqBDyXmY6H1SCdfev4zJs+GB7JMQ Gp9y2igDfnUKy6fwMKME0KSfAgs5iUj4vUizirOoNBt0lyu1is2hwfYF72fh5SBx74Mh WUfZNaUK2ZI7Qb/YyGW2wuGWKIfEGYk0m2xqk= MIME-Version: 1.0 Received: by 10.52.29.16 with SMTP id f16mr8550491vdh.45.1324683957442; Fri, 23 Dec 2011 15:45:57 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Fri, 23 Dec 2011 15:45:57 -0800 (PST) In-Reply-To: <4EF50AF4.3030105@bettercom.de> References: <4EF50AF4.3030105@bettercom.de> Date: Fri, 23 Dec 2011 15:45:57 -0800 X-Google-Sender-Auth: OAhLrRQ9ZS-cR4jEdNxGkF_0StM Message-ID: From: Adrian Chadd To: Martin Lesser Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: ath updates - please test X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Dec 2011 23:45:58 -0000 Hi, Thanks for testing out -HEAD! Sure, you can flip it on just to ensure it compiles, but all it does is enable it. All of the actual TX path changes occur whether you're using 11n or not. (Ie, even the AR5210 NIC goes via the software TX queue these days.) Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 24 01:02:04 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 439661065675; Sat, 24 Dec 2011 01:02:04 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1A4008FC1F; Sat, 24 Dec 2011 01:02:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBO123qU002592; Sat, 24 Dec 2011 01:02:03 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBO123jk002588; Sat, 24 Dec 2011 01:02:03 GMT (envelope-from linimon) Date: Sat, 24 Dec 2011 01:02:03 GMT Message-Id: <201112240102.pBO123jk002588@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/163574: [net80211] overly-frequent HT occupancy changes X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Dec 2011 01:02:04 -0000 Synopsis: [net80211] overly-frequent HT occupancy changes Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sat Dec 24 01:01:31 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=163574 From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 24 08:10:12 2011 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D490A106564A for ; Sat, 24 Dec 2011 08:10:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BE9D18FC13 for ; Sat, 24 Dec 2011 08:10:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pBO8ACW3020984 for ; Sat, 24 Dec 2011 08:10:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pBO8ACqj020983; Sat, 24 Dec 2011 08:10:12 GMT (envelope-from gnats) Date: Sat, 24 Dec 2011 08:10:12 GMT Message-Id: <201112240810.pBO8ACqj020983@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org From: Joel Dahl Cc: Subject: Re: kern/163318: [ath] ath(4) stops working X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joel Dahl List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Dec 2011 08:10:13 -0000 The following reply was made to PR kern/163318; it has been noted by GNATS. From: Joel Dahl To: bug-followup@freebsd.org Cc: Subject: Re: kern/163318: [ath] ath(4) stops working Date: Sat, 24 Dec 2011 09:05:11 +0100 dding more information with the results from a private email conversation between me and adrian@: This is in station mode. It's a very simple setup, the only thing I've really configured is the following in rc.conf: wlans_ath0="wlan0" ifconfig_wlan0="WPA DHCP" And i've created the wpa_supplicant.conf file. ifconfig wlan0 says the following: root@crashbox [~] ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 1c:7e:e5:10:5a:5d inet 10.10.10.238 netmask 0xffffff00 broadcast 10.10.10.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g status: associated ssid DAHL channel 1 (2412 MHz 11g) bssid f8:1e:df:fc:34:2b regdomain ETSI indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 3:128-bit txpower 20 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming MANUAL wlandebug +11n +input +output +rate and some pings from/to the unit: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 562 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 563 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 564 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 565 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 566 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 567 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 568 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 569 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 570 (size 50) no tx bufs (empty list): 0 no tx bufs (was busy): 0 aggr single packet: 0 aggr single packet w/ BAW closed: 0 aggr non-baw packet: 0 aggr aggregate packet: 0 aggr single packet low hwq: 0 aggr sched, no work: 0 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 7: 0 8: 0 9: 0 10: 0 11: 0 12: 0 13: 0 14: 0 15: 0 16: 0 17: 0 18: 0 19: 0 20: 0 21: 0 22: 0 23: 0 24: 0 25: 0 26: 0 27: 0 28: 0 29: 0 30: 0 31: 0 32: 0 33: 0 34: 0 35: 0 36: 0 37: 0 38: 0 39: 0 40: 0 41: 0 42: 0 43: 0 44: 0 45: 0 46: 0 47: 0 48: 0 49: 0 50: 0 51: 0 52: 0 53: 0 54: 0 55: 0 56: 0 57: 0 58: 0 59: 0 60: 0 61: 0 62: 0 63: 0 HW TXQ 0: axq_depth=0, axq_aggr_depth=0 HW TXQ 1: axq_depth=2, axq_aggr_depth=0 HW TXQ 2: axq_depth=0, axq_aggr_depth=0 HW TXQ 3: axq_depth=0, axq_aggr_depth=0 HW TXQ 8: axq_depth=0, axq_aggr_depth=0 Total TX buffers: 198; Total TX buffers busy: 0 no tx bufs (empty list): 0 no tx bufs (was busy): 0 aggr single packet: 0 aggr single packet w/ BAW closed: 0 aggr non-baw packet: 0 aggr aggregate packet: 0 aggr single packet low hwq: 0 aggr sched, no work: 0 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 7: 0 8: 0 9: 0 10: 0 11: 0 12: 0 13: 0 14: 0 15: 0 16: 0 17: 0 18: 0 19: 0 20: 0 21: 0 22: 0 23: 0 24: 0 25: 0 26: 0 27: 0 28: 0 29: 0 30: 0 31: 0 32: 0 33: 0 34: 0 35: 0 36: 0 37: 0 38: 0 39: 0 40: 0 41: 0 42: 0 43: 0 44: 0 45: 0 46: 0 47: 0 48: 0 49: 0 50: 0 51: 0 52: 0 53: 0 54: 0 55: 0 56: 0 57: 0 58: 0 59: 0 60: 0 61: 0 62: 0 63: 0 HW TXQ 0: axq_depth=0, axq_aggr_depth=0 HW TXQ 1: axq_depth=2, axq_aggr_depth=0 HW TXQ 2: axq_depth=0, axq_aggr_depth=0 HW TXQ 3: axq_depth=0, axq_aggr_depth=0 HW TXQ 8: axq_depth=0, axq_aggr_depth=0 Total TX buffers: 198; Total TX buffers busy: 0 no tx bufs (empty list): 0 no tx bufs (was busy): 0 aggr single packet: 0 aggr single packet w/ BAW closed: 0 aggr non-baw packet: 0 aggr aggregate packet: 0 aggr single packet low hwq: 0 aggr sched, no work: 0 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 7: 0 8: 0 9: 0 10: 0 11: 0 12: 0 13: 0 14: 0 15: 0 16: 0 17: 0 18: 0 19: 0 20: 0 21: 0 22: 0 23: 0 24: 0 25: 0 26: 0 27: 0 28: 0 29: 0 30: 0 31: 0 32: 0 33: 0 34: 0 35: 0 36: 0 37: 0 38: 0 39: 0 40: 0 41: 0 42: 0 43: 0 44: 0 45: 0 46: 0 47: 0 48: 0 49: 0 50: 0 51: 0 52: 0 53: 0 54: 0 55: 0 56: 0 57: 0 58: 0 59: 0 60: 0 61: 0 62: 0 63: 0 HW TXQ 0: axq_depth=0, axq_aggr_depth=0 HW TXQ 1: axq_depth=2, axq_aggr_depth=0 HW TXQ 2: axq_depth=0, axq_aggr_depth=0 HW TXQ 3: axq_depth=0, axq_aggr_depth=0 HW TXQ 8: axq_depth=0, axq_aggr_depth=0 Total TX buffers: 198; Total TX buffers busy: 0 no tx bufs (empty list): 0 no tx bufs (was busy): 0 aggr single packet: 0 aggr single packet w/ BAW closed: 0 aggr non-baw packet: 0 aggr aggregate packet: 0 aggr single packet low hwq: 0 aggr sched, no work: 0 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 7: 0 8: 0 9: 0 10: 0 11: 0 12: 0 13: 0 14: 0 15: 0 16: 0 17: 0 18: 0 19: 0 20: 0 21: 0 22: 0 23: 0 24: 0 25: 0 26: 0 27: 0 28: 0 29: 0 30: 0 31: 0 32: 0 33: 0 34: 0 35: 0 36: 0 37: 0 38: 0 39: 0 40: 0 41: 0 42: 0 43: 0 44: 0 45: 0 46: 0 47: 0 48: 0 49: 0 50: 0 51: 0 52: 0 53: 0 54: 0 55: 0 56: 0 57: 0 58: 0 59: 0 60: 0 61: 0 62: 0 63: 0 HW TXQ 0: axq_depth=0, axq_aggr_depth=0 HW TXQ 1: axq_depth=2, axq_aggr_depth=0 HW TXQ 2: axq_depth=0, axq_aggr_depth=0 HW TXQ 3: axq_depth=0, axq_aggr_depth=0 HW TXQ 8: axq_depth=0, axq_aggr_depth=0 Total TX buffers: 198; Total TX buffers busy: 0 wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 571 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 572 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 573 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 574 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 575 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 576 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 577 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 578 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 579 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 580 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 581 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 582 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 583 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 584 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 585 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 586 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 587 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 588 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 589 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 590 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 591 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 592 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 593 (size 50) wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 594 (size 50) Later on, tried doing: wlandebug 0 wlandebug +input +output +rate ping 10.10.10.255 (broadcast ping) The only thing that appear in dmesg after setting the above and doing a broadcast ping is: Dec 24 06:07:56 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 171 (size 50) Dec 24 06:08:07 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 172 (size 50) Dec 24 06:08:22 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 173 (size 50) Dec 24 06:08:43 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 174 (size 50) Dec 24 06:13:45 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 175 (size 50) Dec 24 06:13:50 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 176 (size 50) Dec 24 06:14:01 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 177 (size 50) Dec 24 06:14:14 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 178 (size 50) Dec 24 06:14:28 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 179 (size 50) Dec 24 06:14:36 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 180 (size 50) Dec 24 06:19:46 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 181 (size 50) Dec 24 06:19:54 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 182 (size 50) Dec 24 06:20:05 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 183 (size 50) Dec 24 06:20:23 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 184 (size 50) Dec 24 06:20:33 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 185 (size 50) Dec 24 06:25:47 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 186 (size 50) Dec 24 06:25:50 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 187 (size 50) Dec 24 06:25:58 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 188 (size 50) Dec 24 06:26:08 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 189 (size 50) Dec 24 06:26:19 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 190 (size 50) Dec 24 06:26:39 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 191 (size 50) Dec 24 06:31:48 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 192 (size 50) Dec 24 06:31:56 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 193 (size 50) Dec 24 06:32:06 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 194 (size 50) Dec 24 06:32:22 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 195 (size 50) Dec 24 06:32:39 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 196 (size 50) Dec 24 06:37:49 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 197 (size 50) Dec 24 06:37:57 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 198 (size 50) Dec 24 06:38:08 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 199 (size 50) Dec 24 06:38:15 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 200 (size 50) Dec 24 06:38:33 crashbox kernel: wlan0: [f8:1e:df:fc:34:2b] pwr save q overflow, drops 201 (size 50) FWIW, I rebooted the machine and immediately turned on the wlandebug stuff above (while ath was still working). ath died a few hours later as usual, and the above "pwr save q overflow" messages started appearing in dmesg almost right away. -- Joel