From owner-freebsd-wireless@FreeBSD.ORG Mon Dec 15 22:43:32 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4BEFD91B for ; Mon, 15 Dec 2014 22:43:32 +0000 (UTC) Received: from mail-yh0-f46.google.com (mail-yh0-f46.google.com [209.85.213.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 082577C0 for ; Mon, 15 Dec 2014 22:43:31 +0000 (UTC) Received: by mail-yh0-f46.google.com with SMTP id t59so5589381yho.5 for ; Mon, 15 Dec 2014 14:43:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=mSm0us5J1MPXUvUxj9y1lxxiGlccB1NIuhvkIVDaerQ=; b=ICX62IO0HBnwopxg86gWdT0B8/t2BDHgeuC5HLT5/JC55G38VVL0LAH+jDvyuKQqai QpZagf/Hwt3PqSNfeiVAPxiM355ajIednTMyr1oAlgFxi3sVP+FTY9+LZWfcaccxE4Ur o436s550BssBQs7Pu3ALe8LbtCyVLM2DYameIS+JMzY5MuUs5AvcBbiaoytQROCZO/hY pJG4dat5eXaY/9YtyM1ZZtg6aKLgqvua/5qpsn4vv9ofTTd+EVg+qouUOnK5S1jlV/rz gdZ3BAonjU2efjdvOXintDe+p0fYkv5PHZdNd+J9K73d6ztb9pOTOdmY1w+bX9F2CyX1 pYqQ== X-Gm-Message-State: ALoCoQnnoPIpiZQ7aMhDLAyO811vs5D1LZdLYb1rpu+9y4OnE+JGJEQSKnV14cFeKQ9rzBxM+gBf MIME-Version: 1.0 X-Received: by 10.236.203.34 with SMTP id e22mr9498530yho.47.1418683405360; Mon, 15 Dec 2014 14:43:25 -0800 (PST) Received: by 10.170.156.197 with HTTP; Mon, 15 Dec 2014 14:43:25 -0800 (PST) In-Reply-To: References: Date: Mon, 15 Dec 2014 17:43:25 -0500 Message-ID: Subject: Re: Problem with Atheros adapter (TP-LINK TL-WDN4800, AR9380) From: David Blewett To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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, 15 Dec 2014 22:43:32 -0000 I haven't hit a kernel panic, but several times I get to the point where the wifi connection from Macbook no longer functions. The icon says it's connected, but no network traffic passes. I see this in dmesg on the FreeBSD box: ath0: ath_tx_default_comp: bf 0xfffffe004e7a3b98: seqno 1873: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e78aec0: seqno 1874: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e7787e8: seqno 1875: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e795fa8: seqno 1876: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e786f00: seqno 1877: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e791190: seqno 1878: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e787560: seqno 1879: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e7a9b38: seqno 1880: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e77f910: seqno 1881: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e79e720: seqno 1882: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e777990: seqno 1883: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e7a8e78: seqno 1884: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e792180: seqno 1885: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e7a2878: seqno 1886: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e78f9a8: seqno 1887: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e7a3208: seqno 1888: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e7893a8: seqno 1889: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e7a2218: seqno 1890: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e782f40: seqno 1891: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e77b620: seqno 1892: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e78d368: seqno 1893: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e783738: seqno 1894: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e782748: seqno 1895: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e7a5518: seqno 1896: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e7a79c0: seqno 1897: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e786d68: seqno 1898: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e77d2d0: seqno 1899: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e78b1f0: seqno 1900: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e7a1090: seqno 1901: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e77ac90: seqno 1902: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e77c7a8: seqno 1903: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e786240: seqno 1905: bf_next not NULL! ath0: ath_tx_default_comp: bf 0xfffffe004e79f578: seqno 1906: bf_next not NULL! wlan0: [28:cf:e9:12:ed:bb] pwr save q overflow, drops 179 (size 50) wlan0: [28:cf:e9:12:ed:bb] pwr save q overflow, drops 180 (size 50) wlan0: [28:cf:e9:12:ed:bb] pwr save q overflow, drops 181 (size 50) wlan0: [28:cf:e9:12:ed:bb] pwr save q overflow, drops 182 (size 50) wlan0: [28:cf:e9:12:ed:bb] pwr save q overflow, drops 183 (size 50) wlan0: [28:cf:e9:12:ed:bb] pwr save q overflow, drops 184 (size 50) wlan0: [28:cf:e9:12:ed:bb] pwr save q overflow, drops 185 (size 50) Thanks, David Blewett On Sun, Dec 14, 2014 at 9:29 PM, David Blewett wrote: > > =E2=80=8BOkay, I've built a custom kernel with if_ath_pci as a module, re= booted > into the new kernel and got it running. I also enabled AH_DEBUG. Will let > you know how things go this week.=E2=80=8B > > Thanks, > > David Blewett > > On Sun, Dec 14, 2014 at 2:58 PM, David Blewett > wrote: >> >> Okay, I can try to give that a go. Will take me a bit. I use ZFS on >> encrypted geli devices, and haven't tried building a custom kernel yet w= ith >> this config. >> >> Thanks, >> >> David Blewett >> >> On Sun, Dec 14, 2014 at 2:55 PM, Adrian Chadd wrote= : >>> >>> Aha! Listen time is 0. Hm! >>> >>> >>> Just add this at line 1179 and recompile: >>> >>> >>> if (ani_state->listen_time =3D=3D 0) >>> return; >>> >>> it's possible that it'll happen; it shoud be bailing out sooner rather >>> than later. >>> >>> >>> >>> -adrian >>> >>> >>> On 14 December 2014 at 11:53, David Blewett >>> wrote: >>> > If this would be easier on IRC, I'm BlueAidan on Freenode. >>> > >>> > Output: >>> > >>> > (kgdb) list *0xffffffff8045161d >>> > 0xffffffff8045161d is in ar9300_ani_ar_poll >>> > (/usr/src/sys/contrib/dev/ath/ath_hal/ar9300/ar9300_ani.c:1180). >>> > 1175 */ >>> > 1176 if (!DO_ANI(ah)) { >>> > 1177 return; >>> > 1178 } >>> > 1179 >>> > 1180 ofdm_phy_err_rate =3D >>> > 1181 ani_state->ofdm_phy_err_count * 1000 / >>> > ani_state->listen_time; >>> > 1182 cck_phy_err_rate =3D >>> > 1183 ani_state->cck_phy_err_count * 1000 / >>> > ani_state->listen_time; >>> > 1184 >>> > >>> > Thanks, >>> > >>> > David Blewett >>> > >>> > On Sun, Dec 14, 2014 at 2:39 PM, Adrian Chadd >>> wrote: >>> >> >>> >> Hi! >>> >> >>> >> Hm, an integer divide by zero fault. Tsk. >>> >> >>> >> can you do this: >>> >> >>> >> kgdb /boot/kernel/kernel >>> >> list *0xffffffff8045161d >>> >> >>> >> Thanks! >>> >> >>> >> >>> >> >>> >> -adrian >>> >> >>> >> >>> >> On 14 December 2014 at 11:24, David Blewett >>> >> wrote: >>> >> > Hi All: >>> >> > >>> >> > I've been having issues with a TP-LINK TL-WDN4800 PCI Express >>> adapter >>> >> > [1] >>> >> > that seem to have become worse since upgrading to 10.1-RELEASE. >>> Since >>> >> > then, >>> >> > I've had a couple of kernel panics. I use the adapter in hostapd >>> mode as >>> >> > my >>> >> > main WiFi access point. I would appreciate any help in making my >>> setup >>> >> > more >>> >> > reliable, and am open to trying to just about anything to help >>> >> > troubleshoot. >>> >> > >>> >> > The problems that I see are regular disconnections from a Macbook >>> Pro >>> >> > client. When this happens, sometimes the wifi icon says it is >>> connected, >>> >> > but I cannot actually transmit anything to the host (i.e., pings >>> fail). >>> >> > The >>> >> > only recourse is to turn the mbp's wifi off, then back on. This >>> >> > *usually* >>> >> > succeeds, but sometimes does not. I also have an iPad that has >>> similar >>> >> > issues; turning wifi off and back on is usually sufficient to >>> restore >>> >> > connectivity. >>> >> > >>> >> > This is my /etc/rc.conf: >>> >> > >>> >> > wlans_ath0=3D"wlan0" >>> >> > create_args_wlan0=3D"wlanmode hostap bssid" >>> >> > ifconfig_wlan0=3D"HOSTAP ssid MiddleEarth mode 11ng channel 2" >>> >> > >>> >> > and /etc/hostapd-wlan0.conf: >>> >> > >>> >> > interface=3Dwlan0 >>> >> > debug=3D2 >>> >> > ctrl_interface=3D/var/run/hostapd >>> >> > ctrl_interface_group=3Dwheel >>> >> > ssid=3DMiddleEarth >>> >> > wpa=3D2 >>> >> > wpa_passphrase=3Dxxxx >>> >> > wpa_key_mgmt=3DWPA-PSK >>> >> > wpa_pairwise=3DCCMP >>> >> > >>> >> > I see a lot of this in the logs: >>> >> > >>> >> > ath0: stuck beacon; resetting (bmiss count 8) >>> >> > >>> >> > However, from what I've read these are due to channel congestion >>> and are >>> >> > to >>> >> > be expected. The kernel panics look like this: >>> >> > >>> >> > Fatal trap 18: integer divide fault while in kernel mode >>> >> > cpuid =3D 1; apic id =3D 11 >>> >> > instruction pointer =3D 0x20:0xffffffff8045161d >>> >> > stack pointer =3D 0x28:0xfffffe00e43bb760 >>> >> > frame pointer =3D 0x28:0xfffffe00e43bb7b0 >>> >> > code segment =3D base 0x0, limit 0xfffff, type 0x1b >>> >> > =3D DPL 0, pres 1, long 1, def32 0, gran 1 >>> >> > processor eflags =3D interrupt enabled, ath0: stuck beacon; >>> resetting >>> >> > (bmiss count 8) >>> >> > resume, IOPL =3D 0 >>> >> > current process =3D 12 (swi4: clock) >>> >> > trap number =3D 18 >>> >> > panic: integer divide fault >>> >> > cpuid =3D 0 >>> >> > KDB: stack backtrace: >>> >> > #0 0xffffffff80963000 at kdb_backtrace+0x60 >>> >> > #1 0xffffffff80928125 at panic+0x155 >>> >> > #2 0xffffffff80d24f1f at trap_fatal+0x38f >>> >> > #3 0xffffffff80d24b7c at trap+0x75c >>> >> > #4 0xffffffff80d0a782 at calltrap+0x8 >>> >> > #5 0xffffffff8045b248 at ar9300_ani_poll_freebsd+0x48 >>> >> > #6 0xffffffff804093d6 at ath_calibrate+0xf6 >>> >> > #7 0xffffffff8093d557 at softclock_call_cc+0x177 >>> >> > #8 0xffffffff8093d994 at softclock+0x94 >>> >> > #9 0xffffffff808faf4b at intr_event_execute_handlers+0xab >>> >> > #10 0xffffffff808fb396 at ithread_loop+0x96 >>> >> > #11 0xffffffff808f8b6a at fork_exit+0x9a >>> >> > >>> >> > Here is the pciconf output: >>> >> > >>> >> > ath0@pci0:2:0:0: class=3D0x028000 card=3D0x3112168c chip=3D0x00= 30168c >>> >> > rev=3D0x01 >>> >> > hdr=3D0x00 >>> >> > vendor =3D 'Atheros Communications Inc.' >>> >> > device =3D 'AR9300 Wireless LAN adaptor' >>> >> > class =3D network >>> >> > >>> >> > 1. http://www.tp-link.com/lk/products/details/?model=3DTL-WDN4800 >>> >> > >>> >> > Thanks, >>> >> > >>> >> > David Blewett >>> >> > _______________________________________________ >>> >> > 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" >>> >>