From owner-freebsd-wireless@freebsd.org Sun Dec 4 00:49:18 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87453C5783F for ; Sun, 4 Dec 2016 00:49:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 77328169D for ; Sun, 4 Dec 2016 00:49:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uB40nHwa018509 for ; Sun, 4 Dec 2016 00:49:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 215025] Panic in arptimer Date: Sun, 04 Dec 2016 00:49:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avos@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: see_also Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 04 Dec 2016 00:49:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215025 Andriy Voskoboinyk changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 096 | |82 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Sun Dec 4 00:49:41 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2EF69C578E5 for ; Sun, 4 Dec 2016 00:49:41 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 1CD5617A5 for ; Sun, 4 Dec 2016 00:49:40 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id uB40ndqk030303 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 3 Dec 2016 16:49:39 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me Subject: Re: wpa_supplicant + wpa_gui have troubles when many APs have the same name To: Adrian Chadd References: <264bf419-c97f-a333-167a-5eb13a6bf96a@rawbw.com> <1983541127.1707358.1479779586520@mail.yahoo.com> <3b76a34b-0ac7-dd2e-60f0-e6b0ac811e44@rawbw.com> <7e39e6b6-30a6-9c67-534b-4b8a1b2309e7@rawbw.com> Cc: freebsd-wireless From: Yuri Message-ID: Date: Sat, 3 Dec 2016 16:49:38 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 04 Dec 2016 00:49:41 -0000 On 11/30/2016 17:32, Adrian Chadd wrote: > ping?:) > > > -a Yes, I will do this once I get into such place again. Yuri From owner-freebsd-wireless@freebsd.org Sun Dec 4 21:00:07 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CCB19C67D33 for ; Sun, 4 Dec 2016 21:00:07 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C38FD1745 for ; Sun, 4 Dec 2016 21:00:07 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uB4L018o021875 for ; Sun, 4 Dec 2016 21:00:07 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201612042100.uB4L018o021875@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-wireless@FreeBSD.org Subject: Problem reports for freebsd-wireless@FreeBSD.org that need special attention Date: Sun, 04 Dec 2016 21:00:07 +0000 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 04 Dec 2016 21:00:07 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 206801 | iwn(4) page fault on netif restart Open | 154598 | [ath] Atheros 5424/2424 can't connect to WPA netw Open | 163312 | [panic] [ath] kernel panic: page fault with ath0 Open | 166190 | [ath] TX hangs and frames stuck in TX queue Open | 166357 | [ath] 802.11n TX stall when the first frame in th Open | 169362 | [ath] AR5416: radar pulse PHY errors sometimes in Open | 169433 | [iwn] iwn(4) doesn't support 6235 chip. Open | 211689 | panic with lagg failover wireless ath and iwm 8 problems total for which you should take action. From owner-freebsd-wireless@freebsd.org Sun Dec 4 23:32:45 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0640C673AF for ; Sun, 4 Dec 2016 23:32:45 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 873121D58 for ; Sun, 4 Dec 2016 23:32:45 +0000 (UTC) (envelope-from gonzo@id.bluezbox.com) Received: from [136.179.10.143] (helo=[10.140.230.85]) by id.bluezbox.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cDgGx-000AAv-Il for freebsd-wireless@freebsd.org; Sun, 04 Dec 2016 15:32:44 -0800 From: Oleksandr Tymoshenko Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Problem with Intel Centrino Wireless-N 1000 on ARM Message-Id: <9770367E-AEC9-4849-9F9E-47B4E35F724F@bluezbox.com> Date: Sun, 4 Dec 2016 15:32:12 -0800 To: freebsd-wireless@freebsd.org X-Mailer: Apple Mail (2.3251) Sender: gonzo@id.bluezbox.com X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Hello, I am trying to get Intel Centrino Wireless-N 1000 working on one of my ARM boards. iwn(4) recognizes it but I can’t associate it with AP or get scan results. I am not sure whether it’s an iwn on ARM problem or this card in general. I’d appreciate any hints on how to debug this issue. [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 04 Dec 2016 23:32:45 -0000 Hello, I am trying to get Intel Centrino Wireless-N 1000 working on one of my ARM boards. iwn(4) recognizes it but I can=E2=80=99t associate it = with AP or get scan results. I am not sure whether it=E2=80=99s an iwn on ARM = problem or this card in general. I=E2=80=99d appreciate any hints on how to = debug this issue. My test script: sysctl dev.iwn.0.debug=3D0x8007 ifconfig wlan create wlandev iwn0 wlandebug -i wlan0 +dumppkts+scan+debug ifconfig wlan0 up scan Card=E2=80=99s dmesg: Dec 4 23:25:25 jetson-tk1 kernel: iwn0: irq 104 at device 0.0 on pci1 Dec 4 23:25:25 jetson-tk1 kernel: pcib1: allocated initial memory = window of 0x13100000-0x131fffff Dec 4 23:25:25 jetson-tk1 kernel: pcib1: allocated memory range = (0x13100000-0x13101fff) for rid 10 of iwn0 Dec 4 23:25:25 jetson-tk1 kernel: iwn0: Lazy allocation of 0x2000 bytes = rid 0x10 type 3 at 0x13100000 Dec 4 23:25:25 jetson-tk1 kernel: ofw_pci mapdev: start 13100000, len = 8192 Dec 4 23:25:25 jetson-tk1 kernel: iwn0: attempting to allocate 1 MSI = vectors (1 supported) Dec 4 23:25:25 jetson-tk1 kernel: iwn0: using IRQ 106 for MSI Dec 4 23:25:25 jetson-tk1 kernel: iwn0: MIMO 1T2R, BGS, address = 74:e5:0b:53:04:ec Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps = 11Mbps Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps = 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 1T2R Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 11ng MCS 20MHz Dec 4 23:25:25 jetson-tk1 kernel: iwn0: MCS 0-7: 6.5Mbps - 65Mbps Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 11ng MCS 20MHz SGI Dec 4 23:25:25 jetson-tk1 kernel: iwn0: MCS 0-7: 7Mbps - 72Mbps Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 11ng MCS 40MHz: Dec 4 23:25:25 jetson-tk1 kernel: iwn0: MCS 0-7: 13.5Mbps - 135Mbps Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 11ng MCS 40MHz SGI: Dec 4 23:25:25 jetson-tk1 kernel: iwn0: MCS 0-7: 15Mbps - 150Mbps Dec 4 23:25:25 jetson-tk1 kernel: wlan0: bpf attached Dec 4 23:25:25 jetson-tk1 kernel: wlan0: bpf attached Dec 4 23:25:25 jetson-tk1 kernel: wlan0: Ethernet address: = 74:e5:0b:53:04:ec Dec 4 23:25:25 jetson-tk1 kernel: wlan0: start running, 0 vaps running Dec 4 23:25:25 jetson-tk1 kernel: wlan0: ieee80211_start_locked: up = parent iwn0 Dec 4 23:25:25 jetson-tk1 kernel: iwn0: iwn_read_firmware: ucode = rev=3D0x271f0501 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D0; qid 0 idx 0 = flags 0 type 1(UC_READY) len 36 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D1; qid 4 idx 0 = flags 0 type 90(IWN5000_CMD_WIMAX_COEX) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D2; qid 4 idx 1 = flags 0 type 176(IWN_CMD_PHY_CALIB) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D3; qid 4 idx 2 = flags 0 type 101(IWN5000_CMD_CALIB_CONFIG) len 8 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D4; qid 0 idx 1 = flags 0 type 102(IWN5000_CMD_CALIB_RESULT) len 12 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D5; qid 0 idx 2 = flags 0 type 102(IWN5000_CMD_CALIB_RESULT) len 296 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D6; qid 0 idx 3 = flags 0 type 102(IWN5000_CMD_CALIB_RESULT) len 92 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D7; qid 0 idx 4 = flags 0 type 102(IWN5000_CMD_CALIB_RESULT) len 52 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D8; qid 0 idx 5 = flags 0 type 103(IWN5000_CMD_CALIB_COMPLETE) len 8 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D0; qid 0 idx 0 = flags 0 type 1(UC_READY) len 36 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D1; qid 4 idx 0 = flags 0 type 90(IWN5000_CMD_WIMAX_COEX) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D2; qid 4 idx 1 = flags 0 type 176(IWN_CMD_PHY_CALIB) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D3; qid 4 idx 2 = flags 0 type 176(IWN_CMD_PHY_CALIB) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D4; qid 4 idx 3 = flags 0 type 176(IWN_CMD_PHY_CALIB) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D5; qid 4 idx 4 = flags 0 type 176(IWN_CMD_PHY_CALIB) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D6; qid 4 idx 5 = flags 0 type 176(IWN_CMD_PHY_CALIB) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn_config: configuring valid TX = chains 0x1 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D7; qid 4 idx 6 = flags 0 type 152(IWN5000_CMD_TX_ANT_CONFIG) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D8; qid 4 idx 7 = flags 0 type 155(IWN_CMD_BT_COEX) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn_config: rxchainmask=3D0x3, = nrxchains=3D2 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D9; qid 4 idx 8 = flags 0 type 16(IWN_CMD_RXON) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D10; qid 4 idx 9 = flags 0 type 24(ADD_NODE_DONE) len 8 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D11; qid 4 idx = 10 flags 0 type 78(IWN_CMD_LINK_QUALITY) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn5000_set_txpower: setting TX = power; rev=3D5 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D12; qid 4 idx = 11 flags 0 type 149(IWN_CMD_TXPOWER_DBM) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D13; qid 4 idx = 12 flags 0 type 164(IWN_CMD_SET_CRITICAL_TEMP) len 4 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D14; qid 4 idx = 13 flags 0 type 119(IWN_CMD_SET_POWER_MODE) len 4 Dec 4 23:25:25 jetson-tk1 kernel: wlan0: start running, 1 vaps running Dec 4 23:25:25 jetson-tk1 kernel: iwn_newstate: INIT -> SCAN Than it just goes like this: Dec 4 23:25:25 jetson-tk1 kernel: sending scan command nchan=3D1 Dec 4 23:25:25 jetson-tk1 kernel: wlan0: iwn_notif_intr: cur=3D24; qid = 4 idx 17 flags 0 type 128(IWN_CMD_SCAN) len 8 Dec 4 23:25:25 jetson-tk1 kernel: scan_curchan_task: waiting Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D25; qid 0 idx 8 = flags 0 type 130(START_SCAN) len 24 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: scanning channel 11 = status 1 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D26; qid 0 idx 9 = flags 0 type 131(IWN_CMD_SCAN_RESULTS) len 20 Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D27; qid 0 idx = 10 flags 0 type 132(STOP_SCAN) len 16 Dec 4 23:25:25 jetson-tk1 kernel: scan finished nchan=3D1 status=3D1 = chan=3D11 Dec 4 23:25:25 jetson-tk1 kernel: wlan0: ieee80211_swscan_scan_next: = called Dec 4 23:25:25 jetson-tk1 kernel: wlan0: scan_curchan_task: loop start; = scandone=3D0 Dec 4 23:25:25 jetson-tk1 kernel: wlan0: scan_curchan_task: chan 11g = -> 7g [active, dwell min 20ms max 200ms] Dec 4 23:25:25 jetson-tk1 kernel: iwn_scan: ssid_len=3D0, ssid=3D Dec 4 23:25:25 jetson-tk1 kernel: iwn_scan: chan 7 flags 0x1 rf_gain = 0x28 dsp_gain 0x6e active 33 passive 100 scan_svc_time 16879616 crc = 0xffff isactive=3D0 numssid=3D0 without any RX frames or scan results. Thank you= From owner-freebsd-wireless@freebsd.org Mon Dec 5 02:41:33 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6CBD2C66109 for ; Mon, 5 Dec 2016 02:41:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 36C531D21 for ; Mon, 5 Dec 2016 02:41:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x233.google.com with SMTP id c21so530569335ioj.1 for ; Sun, 04 Dec 2016 18:41:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=DX0TR7BlHGIQiPeim/RCDPum3NLz+Gl061dX31Eo1io=; b=Sg0M2zLzlaYvEl5c32l6oAId19Yaw7cDL3cEfLgwZrS3UEbr0hFegOljgUoh/d7SWA vqmO88qgIDrU1r4zN6zVUJJRfGpok1n/LiKuShlbr8AKRzci1JsGTNgDnSxzodldkOim spP/v4WVR36ZFoAMFmG17I3CaqK8exkTya2vkUKn1KItnI+7Ri/uinjPMt6NBkX9VPrW Qr8lrPwmKOKpDF/tSRwgUYzP9lCvFtARe1BtGwh7ZfPY3H4n/tLEvnYru61b+cVtiwuq 03F2+v2avom4eziuHR/M9Hmm7pw+qYn545ABLG9mKrgpjoEUWTBs7Ls14KhvIrRuxHgY cnnA== 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:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=DX0TR7BlHGIQiPeim/RCDPum3NLz+Gl061dX31Eo1io=; b=YKDrqkP0X9l7DAghLKlcCLBHfJj3CzIaeSKiwoy4FTOksLnfhcQUKkk1xHIMtj4e+/ eXosfYzPYpQwI954g1l2a8i8xfqMpfZO2nSpDwd7pVYYQZiJO2Tk1XD5F4mlb0w+enoQ AyyNMBu3h5d7yil643wyNyYsu+T+sGx09rV00iAr6JsLTkttrvMeixtJBdL+Vh28yeiM tg/Tzxplo+i8siTaLLZReX65mYvjchPKP1QYW4/Na38JJVPQy2Za7foh4m2jSzjoyRmr 9m3F8br23TnIb3cJeoC3xJCpEYMn3pAo5vIITpdLBSVeI4fIWCifo0XTmFauEgRy3wwa 1lqQ== X-Gm-Message-State: AKaTC00Ii+EfqDnnhiPHUpNuv2bZhdI/AbD7EtSTsTlJOlyCFIhb8JCHmOTdVWD7xkT7gY1AIAGu64CZJb6L8g== X-Received: by 10.36.91.134 with SMTP id g128mr6637263itb.78.1480905692486; Sun, 04 Dec 2016 18:41:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.150.129 with HTTP; Sun, 4 Dec 2016 18:41:31 -0800 (PST) In-Reply-To: <9770367E-AEC9-4849-9F9E-47B4E35F724F@bluezbox.com> References: <9770367E-AEC9-4849-9F9E-47B4E35F724F@bluezbox.com> From: Adrian Chadd Date: Sun, 4 Dec 2016 18:41:31 -0800 Message-ID: Subject: Re: Problem with Intel Centrino Wireless-N 1000 on ARM To: Oleksandr Tymoshenko Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 05 Dec 2016 02:41:33 -0000 hiya, it's totally possible some endian clean stuff is missing from the driver :( -adrian On 4 December 2016 at 15:32, Oleksandr Tymoshenko wrot= e: > Hello, > > I am trying to get Intel Centrino Wireless-N 1000 working on one of > my ARM boards. iwn(4) recognizes it but I can=E2=80=99t associate it with > AP or get scan results. I am not sure whether it=E2=80=99s an iwn on ARM = problem > or this card in general. I=E2=80=99d appreciate any hints on how to debug= this > issue. > > My test script: > sysctl dev.iwn.0.debug=3D0x8007 > ifconfig wlan create wlandev iwn0 > wlandebug -i wlan0 +dumppkts+scan+debug > ifconfig wlan0 up scan > > Card=E2=80=99s dmesg: > > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: = irq 104 at device 0.0 on pci1 > Dec 4 23:25:25 jetson-tk1 kernel: pcib1: allocated initial memory window= of 0x13100000-0x131fffff > Dec 4 23:25:25 jetson-tk1 kernel: pcib1: allocated memory range (0x13100= 000-0x13101fff) for rid 10 of iwn0 > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: Lazy allocation of 0x2000 bytes = rid 0x10 type 3 at 0x13100000 > Dec 4 23:25:25 jetson-tk1 kernel: ofw_pci mapdev: start 13100000, len 81= 92 > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: attempting to allocate 1 MSI vec= tors (1 supported) > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: using IRQ 106 for MSI > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: MIMO 1T2R, BGS, address 74:e5:0b= :53:04:ec > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 1= 1Mbps > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 1= 1Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 1T2R > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 11ng MCS 20MHz > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: MCS 0-7: 6.5Mbps - 65Mbps > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 11ng MCS 20MHz SGI > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: MCS 0-7: 7Mbps - 72Mbps > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 11ng MCS 40MHz: > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: MCS 0-7: 13.5Mbps - 135Mbps > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: 11ng MCS 40MHz SGI: > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: MCS 0-7: 15Mbps - 150Mbps > Dec 4 23:25:25 jetson-tk1 kernel: wlan0: bpf attached > Dec 4 23:25:25 jetson-tk1 kernel: wlan0: bpf attached > Dec 4 23:25:25 jetson-tk1 kernel: wlan0: Ethernet address: 74:e5:0b:53:0= 4:ec > Dec 4 23:25:25 jetson-tk1 kernel: wlan0: start running, 0 vaps running > Dec 4 23:25:25 jetson-tk1 kernel: wlan0: ieee80211_start_locked: up pare= nt iwn0 > Dec 4 23:25:25 jetson-tk1 kernel: iwn0: iwn_read_firmware: ucode rev=3D0= x271f0501 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D0; qid 0 idx 0 f= lags 0 type 1(UC_READY) len 36 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D1; qid 4 idx 0 f= lags 0 type 90(IWN5000_CMD_WIMAX_COEX) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D2; qid 4 idx 1 f= lags 0 type 176(IWN_CMD_PHY_CALIB) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D3; qid 4 idx 2 f= lags 0 type 101(IWN5000_CMD_CALIB_CONFIG) len 8 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D4; qid 0 idx 1 f= lags 0 type 102(IWN5000_CMD_CALIB_RESULT) len 12 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D5; qid 0 idx 2 f= lags 0 type 102(IWN5000_CMD_CALIB_RESULT) len 296 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D6; qid 0 idx 3 f= lags 0 type 102(IWN5000_CMD_CALIB_RESULT) len 92 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D7; qid 0 idx 4 f= lags 0 type 102(IWN5000_CMD_CALIB_RESULT) len 52 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D8; qid 0 idx 5 f= lags 0 type 103(IWN5000_CMD_CALIB_COMPLETE) len 8 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D0; qid 0 idx 0 f= lags 0 type 1(UC_READY) len 36 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D1; qid 4 idx 0 f= lags 0 type 90(IWN5000_CMD_WIMAX_COEX) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D2; qid 4 idx 1 f= lags 0 type 176(IWN_CMD_PHY_CALIB) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D3; qid 4 idx 2 f= lags 0 type 176(IWN_CMD_PHY_CALIB) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D4; qid 4 idx 3 f= lags 0 type 176(IWN_CMD_PHY_CALIB) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D5; qid 4 idx 4 f= lags 0 type 176(IWN_CMD_PHY_CALIB) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D6; qid 4 idx 5 f= lags 0 type 176(IWN_CMD_PHY_CALIB) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_config: configuring valid TX chain= s 0x1 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D7; qid 4 idx 6 f= lags 0 type 152(IWN5000_CMD_TX_ANT_CONFIG) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D8; qid 4 idx 7 f= lags 0 type 155(IWN_CMD_BT_COEX) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_config: rxchainmask=3D0x3, nrxchai= ns=3D2 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D9; qid 4 idx 8 f= lags 0 type 16(IWN_CMD_RXON) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D10; qid 4 idx 9 = flags 0 type 24(ADD_NODE_DONE) len 8 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D11; qid 4 idx 10= flags 0 type 78(IWN_CMD_LINK_QUALITY) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn5000_set_txpower: setting TX power;= rev=3D5 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D12; qid 4 idx 11= flags 0 type 149(IWN_CMD_TXPOWER_DBM) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D13; qid 4 idx 12= flags 0 type 164(IWN_CMD_SET_CRITICAL_TEMP) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D14; qid 4 idx 13= flags 0 type 119(IWN_CMD_SET_POWER_MODE) len 4 > Dec 4 23:25:25 jetson-tk1 kernel: wlan0: start running, 1 vaps running > Dec 4 23:25:25 jetson-tk1 kernel: iwn_newstate: INIT -> SCAN > > Than it just goes like this: > > Dec 4 23:25:25 jetson-tk1 kernel: sending scan command nchan=3D1 > Dec 4 23:25:25 jetson-tk1 kernel: wlan0: iwn_notif_intr: cur=3D24; qid 4= idx 17 flags 0 type 128(IWN_CMD_SCAN) len 8 > Dec 4 23:25:25 jetson-tk1 kernel: scan_curchan_task: waiting > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D25; qid 0 idx 8 = flags 0 type 130(START_SCAN) len 24 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: scanning channel 11 st= atus 1 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D26; qid 0 idx 9 = flags 0 type 131(IWN_CMD_SCAN_RESULTS) len 20 > Dec 4 23:25:25 jetson-tk1 kernel: iwn_notif_intr: cur=3D27; qid 0 idx 10= flags 0 type 132(STOP_SCAN) len 16 > Dec 4 23:25:25 jetson-tk1 kernel: scan finished nchan=3D1 status=3D1 cha= n=3D11 > Dec 4 23:25:25 jetson-tk1 kernel: wlan0: ieee80211_swscan_scan_next: cal= led > Dec 4 23:25:25 jetson-tk1 kernel: wlan0: scan_curchan_task: loop start; = scandone=3D0 > Dec 4 23:25:25 jetson-tk1 kernel: wlan0: scan_curchan_task: chan 11g ->= 7g [active, dwell min 20ms max 200ms] > Dec 4 23:25:25 jetson-tk1 kernel: iwn_scan: ssid_len=3D0, ssid=3D > Dec 4 23:25:25 jetson-tk1 kernel: iwn_scan: chan 7 flags 0x1 rf_gain 0x2= 8 dsp_gain 0x6e active 33 passive 100 scan_svc_time 16879616 crc 0xffff isa= ctive=3D0 numssid=3D0 > > without any RX frames or scan results. > > Thank you > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://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 Mon Dec 5 05:26:16 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B346C67F58 for ; Mon, 5 Dec 2016 05:26:16 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2BB47A2F for ; Mon, 5 Dec 2016 05:26:15 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from [127.0.0.1] (helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87 (FreeBSD)) (envelope-from ) id 1cDln4-000Alr-7A for freebsd-wireless@freebsd.org; Sun, 04 Dec 2016 21:26:14 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id uB55QDIO041406 for freebsd-wireless@freebsd.org; Sun, 4 Dec 2016 21:26:13 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Sun, 4 Dec 2016 21:26:13 -0800 From: Oleksandr Tymoshenko To: freebsd-wireless@freebsd.org Subject: Re: Problem with Intel Centrino Wireless-N 1000 on ARM Message-ID: <20161205052613.GA41330@bluezbox.com> References: <9770367E-AEC9-4849-9F9E-47B4E35F724F@bluezbox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9770367E-AEC9-4849-9F9E-47B4E35F724F@bluezbox.com> X-Operating-System: FreeBSD/11.0-RELEASE-p2 (amd64) User-Agent: Mutt/1.6.1 (2016-04-27) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Oleksandr Tymoshenko (gonzo@bluezbox.com) wrote: > Hello, > > I am trying to get Intel Centrino Wireless-N 1000 working on one of > my ARM boards. iwn(4) recognizes it but I can’t associate it with > AP or get scan results. I am not sure whether it’s an iwn on ARM problem > or this card in general. I’d appreciate any hints on how to debug this > issue. > > My test script: > sysctl dev.iwn.0.debug=0x8007 > ifconfig wlan create wlandev iwn0 > wlandebug -i wlan0 +dumppkts+scan+debug > ifconfig wlan0 up scan .. skipped .. > without any RX frames or scan results. [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: bluezbox.com] X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 05 Dec 2016 05:26:16 -0000 Oleksandr Tymoshenko (gonzo@bluezbox.com) wrote: > Hello, > > I am trying to get Intel Centrino Wireless-N 1000 working on one of > my ARM boards. iwn(4) recognizes it but I can’t associate it with > AP or get scan results. I am not sure whether it’s an iwn on ARM problem > or this card in general. I’d appreciate any hints on how to debug this > issue. > > My test script: > sysctl dev.iwn.0.debug=0x8007 > ifconfig wlan create wlandev iwn0 > wlandebug -i wlan0 +dumppkts+scan+debug > ifconfig wlan0 up scan .. skipped .. > without any RX frames or scan results. Never mind, Adrian identified missing link: it was lack of antennas. Once I connected one - card started receiving frames. There is some weird behaviour with scan, but association with non-protected AP seems to work. I'll run more tests later -- gonzo From owner-freebsd-wireless@freebsd.org Mon Dec 5 16:53:11 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E86AC68F38 for ; Mon, 5 Dec 2016 16:53:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 851A018C for ; Mon, 5 Dec 2016 16:53:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uB5GrBb7044802 for ; Mon, 5 Dec 2016 16:53:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 215074] [ath] [panic] (Qualcomm AR9227) nightly panic during periodic runs Date: Mon, 05 Dec 2016 16:53:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: c.kworr@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 05 Dec 2016 16:53:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215074 Bug ID: 215074 Summary: [ath] [panic] (Qualcomm AR9227) nightly panic during periodic runs Product: Base System Version: 11.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: c.kworr@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Hi all. LOR's: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7C068C6870F for ; Mon, 5 Dec 2016 17:15:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6B8A6FBA for ; Mon, 5 Dec 2016 17:15:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uB5HFbEF029719 for ; Mon, 5 Dec 2016 17:15:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 215074] [ath] [panic] (Qualcomm AR9227) nightly panic during periodic runs Date: Mon, 05 Dec 2016 17:15:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 05 Dec 2016 17:15:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215074 Adrian Chadd changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian@freebsd.org --- Comment #1 from Adrian Chadd --- hi, stuck beacons are because of AR9227, and I still need to figure that out ;( we know about the LORs between the wifi drivers and stack; we're slowly chipping away at them. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Mon Dec 5 17:15:58 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 794B5C68757 for ; Mon, 5 Dec 2016 17:15:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6690B1031 for ; Mon, 5 Dec 2016 17:15:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uB5HFwM6030032 for ; Mon, 5 Dec 2016 17:15:58 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 215074] [ath] [panic] (Qualcomm AR9227) nightly panic during periodic runs Date: Mon, 05 Dec 2016 17:15:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 05 Dec 2016 17:15:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215074 --- Comment #2 from Adrian Chadd --- (please file a separate bug for "AR9227 stuck beacon after running a while"= ; as those need to get addressed still!) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Mon Dec 5 19:57:24 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CBCAC68F52 for ; Mon, 5 Dec 2016 19:57:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2C891FE9 for ; Mon, 5 Dec 2016 19:57:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uB5JvNBh085816 for ; Mon, 5 Dec 2016 19:57:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 215079] [ath] [panic] (Qualcomm AR9227) stuck beacon after running a while Date: Mon, 05 Dec 2016 19:57:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: c.kworr@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 05 Dec 2016 19:57:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215079 Bug ID: 215079 Summary: [ath] [panic] (Qualcomm AR9227) stuck beacon after running a while Product: Base System Version: 11.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: c.kworr@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Hello. Dec 5 03:36:49 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 5 03:37:39 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 5 03:38:03 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 5 03:38:11 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 5 03:38:11 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 5 03:38:26 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 5 03:42:29 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) hw.ath.bstuck: 4 hw.ath.txbuf_mgmt: 32 hw.ath.txbuf: 200 hw.ath.rxbuf: 40 hw.ath.anical: 100 hw.ath.resetcal: 1200 hw.ath.shortcal: 100 hw.ath.longcal: 30 wlan0: flags=3D8943 metric = 0 mtu 1500 ether c0:4a:00:eb:4c:17 inet6 fe80::c24a:ff:feeb:4c17%wlan0 prefixlen 64 scopeid 0x4 nd6 options=3D21 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid 42 channel 1 (2412 MHz 11g) bssid c0:4a:00:eb:4c:17 regdomain 32924 country CN indoor ecm authmode OPEN -wps -tsn privacy OFF deftxkey UNDEF powersavemode OFF powersavesleep 100 txpower 20 txpowmax 50.0 -dotd rtsthreshold 2346 fragthreshold 2346 bmiss 7 11a ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6 11b ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6 11g ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6 turboA ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6 turboG ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6 sturbo ucast NONE mgmt 6 Mb/s mcast 6 Mb/s maxretry 6 11na ucast NONE mgmt 12 MCS mcast 12 MCS maxretry 6 11ng ucast NONE mgmt 2 MCS mcast 2 MCS maxretry 6 half ucast NONE mgmt 3 Mb/s mcast 3 Mb/s maxretry 6 quarter ucast NONE mgmt 1 Mb/s mcast 1 Mb/s maxretry 6 scanvalid 60 -bgscan bgscanintvl 300 bgscanidle 250 roam:11a rssi 7dBm rate 12 Mb/s roam:11b rssi 7dBm rate 1 Mb/s roam:11g rssi 7dBm rate 5 Mb/s roam:turboA rssi 7dBm rate 12 Mb/s roam:turboG rssi 7dBm rate 12 Mb/s roam:sturbo rssi 7dBm rate 12 Mb/s roam:11na rssi 7dBm MCS 1 roam:11ng rssi 7dBm MCS 1 roam:half rssi 7dBm rate 6 Mb/s roam:quarter rssi 7dBm rate 3 Mb/s -pureg protmode CTS -ht -htcompat -ampdu ampdulimit 64k ampdudensity 8 -amsdu -shortgi htprotmode RTSCTS -puren smps -rifs -stbc wme burst -dwds -hidessid apbridge dtimperiod 1 doth -dfs ina= ct bintval 100 AC_BE cwmin 4 cwmax 6 aifs 3 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm AC_BK cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm AC_VI cwmin 3 cwmax 4 aifs 1 txopLimit 94 -acm ack cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm AC_VO cwmin 2 cwmax 3 aifs 1 txopLimit 47 -acm ack cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm groups: wlan Would be happy to provide more info/testing if needed. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Mon Dec 5 21:04:49 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1054CC685A2 for ; Mon, 5 Dec 2016 21:04:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F3F0C19BB for ; Mon, 5 Dec 2016 21:04:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uB5L4mPk005152 for ; Mon, 5 Dec 2016 21:04:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 215079] [ath] [panic] (Qualcomm AR9227) stuck beacon after running a while Date: Mon, 05 Dec 2016 21:04:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 05 Dec 2016 21:04:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215079 Adrian Chadd changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian@freebsd.org --- Comment #1 from Adrian Chadd --- Try: sysctl dev.ath.0.hal.force_full_reset=3D1 and then see if it gets stuck less. -adrian --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Tue Dec 6 04:59:36 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9BACC69F58 for ; Tue, 6 Dec 2016 04:59:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A939F61E for ; Tue, 6 Dec 2016 04:59:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uB64xaxZ024998 for ; Tue, 6 Dec 2016 04:59:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 215079] [ath] [panic] (Qualcomm AR9227) stuck beacon after running a while Date: Tue, 06 Dec 2016 04:59:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: c.kworr@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 06 Dec 2016 04:59:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215079 --- Comment #2 from c.kworr@gmail.com --- Added to /etc/sysctl.conf and rebooted (just in case). Not that much differ= ence yet. Dec 6 06:54:45 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:54:50 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:02 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:07 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:09 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:17 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:18 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:45 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:47 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:55:48 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:56:09 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:56:13 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:56:17 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) Dec 6 06:56:25 limbo kernel: ath0: stuck beacon; resetting (bmiss count 4) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Tue Dec 6 05:02:08 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E684C691BE for ; Tue, 6 Dec 2016 05:02:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DF37964 for ; Tue, 6 Dec 2016 05:02:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uB6527r1071162 for ; Tue, 6 Dec 2016 05:02:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 215079] [ath] [panic] (Qualcomm AR9227) stuck beacon after running a while Date: Tue, 06 Dec 2016 05:02:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: adrian@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 06 Dec 2016 05:02:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215079 --- Comment #3 from Adrian Chadd --- It'll happen from time to time depending upon RF conditions. As long as it doesn't go deaf over time then we're okay. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Wed Dec 7 05:47:43 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 980F3C6BCA9 for ; Wed, 7 Dec 2016 05:47:43 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8A9C4E89 for ; Wed, 7 Dec 2016 05:47:43 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id uB75laIl034886 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Tue, 6 Dec 2016 21:47:37 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me To: freebsd-wireless From: Yuri Subject: TP-Link TL-WDN3200 device periodically loses connection on some networks Message-ID: <4e1ec741-6732-49d4-8614-d3583f85eefb@rawbw.com> Date: Tue, 6 Dec 2016 21:47:35 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 07 Dec 2016 05:47:43 -0000 This device ugen3.2: <802.11 n WLAN Ralink> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (450mA) TP-Link TL-WDN3200 idVendor = 0x148f idProduct = 0x5572 works fine with my home router, but periodically loses connection on other networks. For example, I lost connection about 5 times during the day. Pings to the local router get lost while ifconfig says that device stays up and running: wlan0: flags=8843 metric 0 mtu 1500 ether XX:XX:XX:XX:XX:XX inet 10.1.0.216 netmask 0xfffffc00 broadcast 10.1.3.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet OFDM/6Mbps mode 11a status: associated ssid "Xxxxxxx Hotel" channel 44 (5220 MHz 11a) bssid 28:XX:XX:XX:XX:XX regdomain FCC country US authmode OPEN privacy OFF txpower 17 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 wme roaming MANUAL groups: wlan This ssid had about 8 bssids, and a lot of people were using it at the same time, if congestion matters. FreeBSD 11 amd64 Yuri From owner-freebsd-wireless@freebsd.org Wed Dec 7 05:48:58 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 880E8C6BCE1 for ; Wed, 7 Dec 2016 05:48:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 53889EC0 for ; Wed, 7 Dec 2016 05:48:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x233.google.com with SMTP id a124so694355661ioe.2 for ; Tue, 06 Dec 2016 21:48:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5pC/Lp6DHbjqHCa1WDFpbPF5IMhFgQcfs40dKk/lP0g=; b=a5w1BYXwKMd4etkUJYzr2MjbL/+r15OdWnZ3V/+fh/vni9i+3NH1f6OTIRa86gpFFT mLvXGmQYUGdcdxkVPa0ly5r1KCDVK2oWgaeV5UzGYZYyTk9I+q3C3ALuSsvN8rnTGl1x 0O68j5xm0duXEdUdA13TyJ63ZeAgSfYqfVqL+aV4Bd6u7Prb2KqyuVd5bR8okoVFUepO wtmxeUBd+kySF2xGj8XhTK3OpReLC6DRpd4TkrOpugzoifsML8Dpbc5ORtYQvxZTvqed j3qv4L5eUopvngh69v/OhkgygMTrv03mgi46I1aO4PRoEsLx9uoSxWAef9c0FhbYIsLW UhPg== 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:from:date :message-id:subject:to:cc; bh=5pC/Lp6DHbjqHCa1WDFpbPF5IMhFgQcfs40dKk/lP0g=; b=aQWmkaA8mZ+62gMrld38wvvn6pqNKTET8jQESUhEBMxGoT3QHtPmIMEdwQtT9RYeE/ 0YEmfQVDHsoCV+Haq1lkAdo2rU3bnJNsKUiXWIXLP3hyTp5awQ2iqF7qZvUVkb1ICS8s vmvpdf3/JYY6+em2DzlgEFpnBVC/qiqKs9ZJMfGEIQGDCp4VVWtdoI8ExKidapqgNWng TiRE8QkNAETmONYN1xkN18jJtXdZ6X25s6iLC90HqG8kwJy9CxfWG9YANLVCUecFP878 1QF7Z14RLt9M77VtB+kohZUUivR5PWcpxKJ/B0VI4s/EIqGP8AGSGGJ1tHOSXz81QKSK 7Oww== X-Gm-Message-State: AKaTC00aFgt4CBtmyqjk2bgYwyIUxduRIUwz6gU3vNg37EW8kNnmLU/4Qe9b5fq4+zc0iRo8qn8BxbizuOg1LQ== X-Received: by 10.107.192.196 with SMTP id q187mr16548740iof.129.1481089737691; Tue, 06 Dec 2016 21:48:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.150.129 with HTTP; Tue, 6 Dec 2016 21:48:57 -0800 (PST) In-Reply-To: <4e1ec741-6732-49d4-8614-d3583f85eefb@rawbw.com> References: <4e1ec741-6732-49d4-8614-d3583f85eefb@rawbw.com> From: Adrian Chadd Date: Tue, 6 Dec 2016 21:48:57 -0800 Message-ID: Subject: Re: TP-Link TL-WDN3200 device periodically loses connection on some networks To: Yuri Cc: freebsd-wireless Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 07 Dec 2016 05:48:58 -0000 ry compiling with IEEE80211_DEBUG and then wlandebug +crypto +assoc +state let's see if it's something to do with going rx deaf, or RX crypto errors :( -adrian On 6 December 2016 at 21:47, Yuri wrote: > This device > > ugen3.2: <802.11 n WLAN Ralink> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) > pwr=ON (450mA) > > TP-Link TL-WDN3200 idVendor = 0x148f idProduct = 0x5572 > > works fine with my home router, but periodically loses connection on other > networks. For example, I lost connection about 5 times during the day. Pings > to the local router get lost while ifconfig says that device stays up and > running: > > wlan0: flags=8843 metric 0 mtu 1500 > ether XX:XX:XX:XX:XX:XX > inet 10.1.0.216 netmask 0xfffffc00 broadcast 10.1.3.255 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet OFDM/6Mbps mode 11a > status: associated > ssid "Xxxxxxx Hotel" channel 44 (5220 MHz 11a) bssid > 28:XX:XX:XX:XX:XX > regdomain FCC country US authmode OPEN privacy OFF txpower 17 bmiss > 7 > mcastrate 6 mgmtrate 6 scanvalid 60 wme roaming MANUAL > groups: wlan > > > This ssid had about 8 bssids, and a lot of people were using it at the same > time, if congestion matters. > > FreeBSD 11 amd64 > > > Yuri > > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Thu Dec 8 16:26:45 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 181B7C6D799 for ; Thu, 8 Dec 2016 16:26:45 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from mail.opal.com (gw.opal.com [104.247.41.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "opal.com", Issuer "OpalCA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E062D13A7 for ; Thu, 8 Dec 2016 16:26:44 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from shibato (shibato.opal.com [IPv6:2001:470:8cb8:3:721a:4ff:fe77:9dff]) (authenticated bits=0) by homobox.opal.com (8.15.2/8.15.2) with ESMTPSA id uB8EvJsw030429 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 8 Dec 2016 09:57:19 -0500 (EST) (envelope-from fbsd@opal.com) Date: Thu, 8 Dec 2016 09:57:19 -0500 From: "J.R. Oldroyd" To: freebsd-wireless@freebsd.org Subject: Boot freeze 11.0p3 during network initialization Message-ID: <20161208095719.30f3c60e@shibato> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (homobox.opal.com [IPv6:2001:470:8cb8:2::1]); Thu, 08 Dec 2016 09:57:20 -0500 (EST) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_40, RP_MATCHES_RCVD shortcircuit=no autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on homobox.opal.com X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 08 Dec 2016 16:26:45 -0000 I have observed a 11.0p3 freezing during the boot process several times now. It gets as far as running the netif script, displaying the interfaces and then goes on to devd and dhclient at which point it stops dead. No keyboard response. It requires long-press of power to shut it down and restart, at which point it typically boots normally: wlan0: Ethernet address: 70:1a:04:xx:yy:zz Created wlan(4) interfaces: wlan0. Created clone interfaces: lagg0. re0: link state changed to DOWN Starting wpa_supplicant. lagg0: link state changed to DOWN re0: link state changed to UP lagg0: link state changed to UP Starting Network: lo0 re0 wlan0 lagg0. lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 groups: lo re0: flags=8843 metric 0 mtu 1500 options=82098 ether 70:1a:04:xx:yy:zz nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active wlan0: flags=8843 metric 0 mtu 1500 ether 70:1a:04:xx:yy:zz nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 153 (5765 MHz 11a) regdomain FCC country US indoor ecm authmode WPA1+WPA2/802.11i privacy MIXED deftxkey UNDEF txpower 23 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 60 wme burst roaming MANUAL bintval 0 groups: wlan lagg0: flags=8843 metric 0 mtu 1500 ether 70:1a:04:xx:yy:zz inet6 fe80::721a:4ff:fexx:yyzz%lagg0 prefixlen 64 scopeid 0x4 nd6 options=23 media: Ethernet autoselect status: active groups: lagg laggproto failover lagghash l2,l3,l4 laggport: re0 flags=5 laggport: wlan0 flags=0<> Starting devd. Starting dhclient. ----- freezes dead here On a normal boot, the next lines would be: wlan0: link state changed to UP Starting pflog. pflog0: promiscuous mode enabled This is a laptop with its re0 and wlan0 interfaces configured together under lagg using the wlan's MAC as the re's MAC too. The relevant config in rc.conf are these: ether_wlan0="70:1a:04:xx:yy:zz" ifconfig_re0="ether $ether_wlan0 -txcsum -rxcsum up" wlans_ath0=wlan0 create_args_wlan0="regdomain FCC country US" ifconfig_wlan0="WPA" cloned_interfaces="lagg0" ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0 DHCP" # WAN_IF ifconfig_lagg0_ipv6="inet6 accept_rtadv" This boot freeze happens probably 5-10% of the time, so problematic enough. This problem was never observed on 10.x or 9.x or even 8.x on the same laptop. What other info can I provide? -jr From owner-freebsd-wireless@freebsd.org Thu Dec 8 19:29:26 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 469DCC6CB2F for ; Thu, 8 Dec 2016 19:29:26 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA1F8E54 for ; Thu, 8 Dec 2016 19:29:25 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: by mail-wm0-x242.google.com with SMTP id g23so5601574wme.1 for ; Thu, 08 Dec 2016 11:29:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=DKWXViLQ0tw8U1ww1+SmTGdNSQOoP3jX1vnQzQ7RzkM=; b=frU7aowtqaW5VFHbjQFz+0/FR7iwNcz9SuUuJG1jLvrud+YiTi9Jpp50zOo4ASrS+b x0gHg66Fgpxrje/HnwEZwLc6znkZYoTs+1wHG87kBpBDMMAKhiy+lu/hFJE4CBSVGdq3 PLHmgRZvWI+JHRpPcBsAcix+lKsRohq0Qxd3wcIGagh/ZtBMSSLiZahAcR+Opyrodq/g SnYSXMSjipx0CU5jmt+J5QxGd9Z0pd+1quKGIHufmEo7Ze62zEOQkkOx6pYbZIxBlp4r jzpSv0ajwTJGYowYZf1ggozcR3E19IObec8sSckwkpG2kNbO94CZ5Q18rmjqKtf0OFvY jimg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=DKWXViLQ0tw8U1ww1+SmTGdNSQOoP3jX1vnQzQ7RzkM=; b=moklN1IYInm1JwmY+bKuPekrQndAA+spw5SpmHHgYcNPKSi+aURZebXY5VbQzO8saZ KT7XgDWMTfnshL7JUEwv1aiwt0r4xv1kHm0EmQ9xY6Mz94q4f2FP2CyM3fb/J6dxZIPW euiOKxX+z877UZGwsKGyYKJH+usvF7I5obepcnSrhkjxEJREeVWp63easMoXPu0QbIru 5m8AEYTXbd/WbtTSYLLVfrh4i2rsyHnxhGsrwNasqGhEodI/gTqryKlbpIqsRzjxWfne hFHvInHtbZN3yAg6Qm8fcdqm1xrc8suW2SlKQecWG2EypTF3Lkdk+y5dKXYKZ1njFEl1 RZOw== X-Gm-Message-State: AKaTC037ZmYfF0te/mpuJYO2s7LFQaZfIo7HtJC7dJTwJCHmq1+ZYKimxZ0/onCcw06mPw== X-Received: by 10.46.13.9 with SMTP id 9mr15360970ljn.37.1481225362911; Thu, 08 Dec 2016 11:29:22 -0800 (PST) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id d79sm5933115lfd.46.2016.12.08.11.29.21 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 08 Dec 2016 11:29:22 -0800 (PST) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "J.R. Oldroyd" Subject: Re: Boot freeze 11.0p3 during network initialization References: <20161208095719.30f3c60e@shibato> Date: Thu, 08 Dec 2016 21:29:32 +0200 Cc: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: <20161208095719.30f3c60e@shibato> User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 08 Dec 2016 19:29:26 -0000 Thu, 08 Dec 2016 16:57:19 +0200 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE J.R. Oldroyd : Is there any additional output with wlandebug_wlan0=3D"scan+state+auth+assoc" in /etc/rc.conf ? > I have observed a 11.0p3 freezing during the boot process several time= s > now. > > It gets as far as running the netif script, displaying the interfaces = and > then goes on to devd and dhclient at which point it stops dead. No = > keyboard > response. It requires long-press of power to shut it down and restart= , = > at > which point it typically boots normally: > > wlan0: Ethernet address: 70:1a:04:xx:yy:zz > Created wlan(4) interfaces: wlan0. > Created clone interfaces: lagg0. > re0: link state changed to DOWN > Starting wpa_supplicant. > lagg0: link state changed to DOWN > re0: link state changed to UP > lagg0: link state changed to UP > Starting Network: lo0 re0 wlan0 lagg0. > lo0: flags=3D8049 metric 0 mtu 16384 > options=3D600003 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > inet 127.0.0.1 netmask 0xff000000 > nd6 options=3D21 > groups: lo > re0: flags=3D8843 metric 0 mtu= 1500 > options=3D82098 > ether 70:1a:04:xx:yy:zz > nd6 options=3D29 > media: Ethernet autoselect (100baseTX ) > status: active > wlan0: flags=3D8843 metric 0 m= tu = > 1500 > ether 70:1a:04:xx:yy:zz > nd6 options=3D29 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid "" channel 153 (5765 MHz 11a) > regdomain FCC country US indoor ecm authmode WPA1+WPA2/802.11i= > privacy MIXED deftxkey UNDEF txpower 23 bmiss 7 mcastrate 6 = > mgmtrate 6 > scanvalid 60 wme burst roaming MANUAL bintval 0 > groups: wlan > lagg0: flags=3D8843 metric 0 m= tu = > 1500 > ether 70:1a:04:xx:yy:zz > inet6 fe80::721a:4ff:fexx:yyzz%lagg0 prefixlen 64 scopeid 0x4 > nd6 options=3D23 > media: Ethernet autoselect > status: active > groups: lagg > laggproto failover lagghash l2,l3,l4 > laggport: re0 flags=3D5 > laggport: wlan0 flags=3D0<> > Starting devd. > Starting dhclient. > ----- freezes dead here > > On a normal boot, the next lines would be: > wlan0: link state changed to UP > Starting pflog. > pflog0: promiscuous mode enabled > > This is a laptop with its re0 and wlan0 interfaces configured together= > under lagg using the wlan's MAC as the re's MAC too. > > The relevant config in rc.conf are these: > > ether_wlan0=3D"70:1a:04:xx:yy:zz" > ifconfig_re0=3D"ether $ether_wlan0 -txcsum -rxcsum up" > wlans_ath0=3Dwlan0 > create_args_wlan0=3D"regdomain FCC country US" > ifconfig_wlan0=3D"WPA" > cloned_interfaces=3D"lagg0" > ifconfig_lagg0=3D"laggproto failover laggport re0 laggport wlan0 DHCP"= = > # WAN_IF > ifconfig_lagg0_ipv6=3D"inet6 accept_rtadv" > > This boot freeze happens probably 5-10% of the time, so problematic > enough. > > This problem was never observed on 10.x or 9.x or even 8.x on the same= > laptop. > > What other info can I provide? > > -jr > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to = > "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Thu Dec 8 22:19:29 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF8B5C6D265 for ; Thu, 8 Dec 2016 22:19:29 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from mail.opal.com (gw.opal.com [104.247.41.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "opal.com", Issuer "OpalCA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BD1D411DE for ; Thu, 8 Dec 2016 22:19:29 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from shibato (shibato.opal.com [IPv6:2001:470:8cb8:3:721a:4ff:fe77:9dff]) (authenticated bits=0) by mail.opal.com (8.15.2/8.15.2) with ESMTPSA id uB8MJQiZ034523 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Dec 2016 17:19:26 -0500 (EST) (envelope-from fbsd@opal.com) Date: Thu, 8 Dec 2016 17:19:26 -0500 From: "J.R. Oldroyd" To: "Andriy Voskoboinyk" Cc: freebsd-wireless@freebsd.org Subject: Re: Boot freeze 11.0p3 during network initialization Message-ID: <20161208171926.7e182754@shibato> In-Reply-To: References: <20161208095719.30f3c60e@shibato> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.opal.com [IPv6:2001:470:8cb8:2::1]); Thu, 08 Dec 2016 17:19:26 -0500 (EST) X-Spam-Status: No, score=-1.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_50, RP_MATCHES_RCVD shortcircuit=no autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on homobox.opal.com X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 08 Dec 2016 22:19:30 -0000 On Thu, 08 Dec 2016 21:29:32 +0200 "Andriy Voskoboinyk" = wrote: > > Thu, 08 Dec 2016 16:57:19 +0200 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE J.R. Oldroyd : >=20 > Is there any additional output with > wlandebug_wlan0=3D"scan+state+auth+assoc" > in /etc/rc.conf ? >=20 I have put that in and rebooted several times, all times OK. I will report back again in due course when it next hangs. -jr From owner-freebsd-wireless@freebsd.org Sat Dec 10 03:25:38 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A914C6F3CE for ; Sat, 10 Dec 2016 03:25:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2A4151BB2 for ; Sat, 10 Dec 2016 03:25:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uBA3Pc62033967 for ; Sat, 10 Dec 2016 03:25:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 215025] Panic in arptimer Date: Sat, 10 Dec 2016 03:25:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc keywords Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Dec 2016 03:25:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215025 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- CC|freebsd-amd64@FreeBSD.org | Keywords| |regression --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Sat Dec 10 09:28:47 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B216CC706D4 for ; Sat, 10 Dec 2016 09:28:47 +0000 (UTC) (envelope-from vbotka@gmail.com) Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 478441076 for ; Sat, 10 Dec 2016 09:28:47 +0000 (UTC) (envelope-from vbotka@gmail.com) Received: by mail-wm0-x242.google.com with SMTP id m203so1231297wma.3 for ; Sat, 10 Dec 2016 01:28:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:organization:mime-version; bh=LUuiNxOmTb/9FZtNUyo+4RENgQZlGSsqxRhIGWf/kzc=; b=diMWZQ1yn0SQMW1oCuZnacfnnOkhtvJwGTihwgyV651RCEoByP/Tdjxyj1Oj2Q1WVN St9RI7BLH4o6aFaNmfQLy+FAr6k62LeFV8bhdeZ5fTV5CDzgWnwyp66L/nkGJceSYdHq oMXfshf5F05Mm3goYNd5YCSBPkZYgZdcQ7ZFDPrDjTJdqx0c3ePv+3GxRNFGMpi43AA8 qCRLG7IpI28UUZy/1aWJlQONuMka2iIkIhTQV5y4sS4bYeN4q90t1OkfSNu/W8LZt7pq OW9yPDPlCIY2x8IINijB9xyjYx+JGd3vVo+9zBy8HU6q+Fo47xYFOpKZNWQp9ryhHmeW afuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:organization :mime-version; bh=LUuiNxOmTb/9FZtNUyo+4RENgQZlGSsqxRhIGWf/kzc=; b=QCjSXBZE7NFHFQpozuZb91r6U6qYoVx1qZDYaCr+eg04bkcwAl2gSu/OVd9CaUXJkP blVv5rMAV+LFQhkG2CDjbYsmZh2/xOZzFZ1PI6ruQHj6WAlSFJyZG/ba0Mezi8ZdL/qy 4pmAk/IFBbt7tQFXWk6hOciTErDE+3wNYvbgsbqBr8Iav1bu6e7Z43+jAO6Z6wfZKCuw ZB6lzTSKitYxgt6gRydzZUW/05yOK8qNb56bZCyffldbN3VHs7CFoolLoCZGQMphFfeO lNJYZ/4kg11sJeIePqJXzadrH586llRUaG7bxr4dc1m0zrMt+wHMsV+1JPvKj8cyAOwo g4XQ== X-Gm-Message-State: AKaTC03PyUXSlHk42BXqdQfGeBeSkAuyBzR/9cwZRpsNYRc6a2MzzZhRF8oLVe35VIkDsw== X-Received: by 10.28.94.205 with SMTP id s196mr9861726wmb.1.1481362125706; Sat, 10 Dec 2016 01:28:45 -0800 (PST) Received: from planb.netng.org (85-237-234-149.dynamic.orange.sk. [85.237.234.149]) by smtp.gmail.com with ESMTPSA id d17sm46628114wjr.14.2016.12.10.01.28.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 10 Dec 2016 01:28:45 -0800 (PST) Date: Sat, 10 Dec 2016 10:28:40 +0100 From: Vladimir Botka To: laszlo , freebsd-wireless@freebsd.org Subject: Fw: stuck beacon Message-ID: <20161210102840.135f20be@planb.netng.org> Organization: na X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/DDYJIKimEoQ.iHYBg9+mVku"; protocol="application/pgp-signature" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Dec 2016 09:28:47 -0000 --Sig_/DDYJIKimEoQ.iHYBg9+mVku Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi! Let's forward it to wireless. -vlado Begin forwarded message: Date: Fri, 9 Dec 2016 21:12:13 -0500 From: laszlo To: freebsd-questions@freebsd.org Subject: stuck beacon running 11.0 on a mini ITX as a router in hostap mode getting error messages in log usually once i start seeing these errors things go down hill fast, like=20 start not getting ipaddresses and then not authenticating or connection=20 goes up and down etc. i believe this has been a big issue long time ago but has anyone ever=20 found a fix for it.? is there another brand/model of wireless card that can do hostap mode=20 with some power output. kernel: ath0: ath_tx_aggr_comp_aggr: AR5416 bug: hasba=3D0; txok=3D1, isaggr=3D1, seq_st=3D1306 Dec 9 20:25:13 gatekeeper kernel: ath0: stuck beacon; resetting (bmiss count 4) ath0: mem 0x91200000-0x9121ffff irq 19 at device 0.0 on pci2 ar9300_attach: calling ar9300_hw_attach ar9300_hw_attach: calling ar9300_eeprom_attach ar9300_flash_map: unimplemented for now Restoring Cal data from DRAM Restoring Cal data from EEPROM Restoring Cal data from Flash Restoring Cal data from Flash Restoring Cal data from OTP ar9300_hw_attach: ar9300_eeprom_attach returned 0 ath0: [HT] enabling HT modes ath0: [HT] enabling short-GI in 20MHz mode ath0: [HT] 1 stream STBC receive enabled ath0: [HT] 1 stream STBC transmit enabled ath0: [HT] LDPC transmit/receive enabled ath0: [HT] 2 RX streams; 2 TX streams ath0: AR9580 mac 448.4 RF5110 phy 0.0 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000 _______________________________________________ freebsd-questions@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" --=20 Vladim=C3=ADr Botka +420 603.282.699 =C5=A0meralova 13, Praha 17000 --Sig_/DDYJIKimEoQ.iHYBg9+mVku Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJYS8rJAAoJEJDRmRKO1E8BSfkIAJaxX7BQI4SJVQjx3kq2k9rM nJNbeY1bIpjJWm+m6p0AH9/sUYhCeGaINJNnuX1cKLtMXVakuD8rqCO6JcdvFUjJ qdONtCIsAMx/0pA14/aPHW9rBD4qFhSde+v9HBP94kIoo4/V3mqIqaBZXzygFTW9 hsaWW/icqt3TKRDfq6uAzDad31mxEwP6w3Ls6I+Cl78aygNHSd7ziDuKd2PO9DZJ EMgKSlO4M3TVQdWkk8V4VCe7DFVvIqRJJou3X3mrL2gJiWSzsKRrSJG6g0TtTcrU ERuErx6AxyS4DX47TIXjLz1iY5MP9VJLYeYcEDYFI/9833g+UGKF6VSq48UmxSU= =Ub7M -----END PGP SIGNATURE----- --Sig_/DDYJIKimEoQ.iHYBg9+mVku-- From owner-freebsd-wireless@freebsd.org Sat Dec 10 18:10:39 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E3CEC70812; Sat, 10 Dec 2016 18:10:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 59F5A1246; Sat, 10 Dec 2016 18:10:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x22d.google.com with SMTP id d9so108526998ioe.0; Sat, 10 Dec 2016 10:10:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=OtWHXWm1ayraGlJSl9qh+wp/LA5+t6nVuemOuInoQDE=; b=hjj9R/1yaz6QiG6uqvTdQ68H8zPMi9rr6c7S9mnKJiWlu9aPrqIIYUPhReOzH409wZ rOx98pvlLEkwB+rxHFkMlaP2DqznraTLV7PclKP/Wih50JIktOM+DyQ7D10NW+UAL7YU 6O/B+L1jjAsNGLNhi6chGhzBB/huF+vFu0Ln44RU7Q9R1wh82/BvEoQ1ZTPjZOE/2yMD SPJgU8FwXL6Gqe/KYUD9nY64q5t80W1YmFsAgAR8oCMGwarrUAo33iDhcnViv9OT7vvL VJlyqT9D8d00kSfuJX48qnVuw2nwi89vPBGRYIedxVrZvZjnqEW5bNrFHt5qbCS2iOAU FLiw== 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:from:date :message-id:subject:to:cc; bh=OtWHXWm1ayraGlJSl9qh+wp/LA5+t6nVuemOuInoQDE=; b=AX9OLjw/J7Z4+MNpY0qHMT3D0Z1qpa+aWPqmVMwCOefQSGlT5FOvqfPDkVvsYq5Sgn A9Ey8LUOOELILWAQlUAGuKJ5axgvZAvGmtvIvJ/6k0qJl4pO2ltXiolYkTxWppLqZaQk yqlCsJXvkMXgqG7XqsAIE11F8LYziNCVAtg1SiCsv5JeHibgQZiVb4vQoTg9q218GXWP rs5N2pmNVljV1IuF6K7zvGNCcP33ItzWilc4t9krfHJ5pKH7aB4uHwr1p+bFkI0wh5tq d5WD3HpSKJlDneX3iqkZ74qYRTxM4MdmJJLgBdNYQZ4irrnHMJc4nyLYmz6SEJIIF0lW ZFWA== X-Gm-Message-State: AKaTC013bCLTPSQDHi4LIiO6LJVdIKTrghVPIt+GCdHGln89fmogbvGj2/dMnAK8TNdzErxfWtHBojjly8b4Og== X-Received: by 10.36.91.134 with SMTP id g128mr12139800itb.78.1481393438751; Sat, 10 Dec 2016 10:10:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.150.129 with HTTP; Sat, 10 Dec 2016 10:10:38 -0800 (PST) In-Reply-To: <04f4451e-df26-8775-a0d9-3212ea0e9c60@vagner.com> References: <04f4451e-df26-8775-a0d9-3212ea0e9c60@vagner.com> From: Adrian Chadd Date: Sat, 10 Dec 2016 10:10:38 -0800 Message-ID: Subject: Re: stuck beacon To: laszlo , "freebsd-wireless@freebsd.org" Cc: FreeBSD Questions Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Dec 2016 18:10:39 -0000 hiya, You're using the AR9580 in hostap mode? -adrian On 9 December 2016 at 18:12, laszlo wrote: > running 11.0 on a mini ITX as a router in hostap mode > > getting error messages in log > > usually once i start seeing these errors things go down hill fast, like > start not getting ipaddresses and then not authenticating or connection goes > up and down etc. > > > i believe this has been a big issue long time ago but has anyone ever found > a fix for it.? > > is there another brand/model of wireless card that can do hostap mode with > some power output. > > > > kernel: ath0: ath_tx_aggr_comp_aggr: AR5416 bug: hasba=0; txok=1, isaggr=1, > seq_st=1306 > Dec 9 20:25:13 gatekeeper kernel: ath0: stuck beacon; resetting (bmiss > count 4) > > > ath0: mem 0x91200000-0x9121ffff irq 19 at device 0.0 on > pci2 > ar9300_attach: calling ar9300_hw_attach > ar9300_hw_attach: calling ar9300_eeprom_attach > ar9300_flash_map: unimplemented for now > Restoring Cal data from DRAM > Restoring Cal data from EEPROM > Restoring Cal data from Flash > Restoring Cal data from Flash > Restoring Cal data from OTP > ar9300_hw_attach: ar9300_eeprom_attach returned 0 > ath0: [HT] enabling HT modes > ath0: [HT] enabling short-GI in 20MHz mode > ath0: [HT] 1 stream STBC receive enabled > ath0: [HT] 1 stream STBC transmit enabled > ath0: [HT] LDPC transmit/receive enabled > ath0: [HT] 2 RX streams; 2 TX streams > ath0: AR9580 mac 448.4 RF5110 phy 0.0 > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000 > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"