From owner-freebsd-net@freebsd.org Sun Aug 21 01:29:39 2016 Return-Path: Delivered-To: freebsd-net@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 3CCEBBB9CD1 for ; Sun, 21 Aug 2016 01:29:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 1AFB91534 for ; Sun, 21 Aug 2016 01:29:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 171C3BB9CD0; Sun, 21 Aug 2016 01:29:39 +0000 (UTC) Delivered-To: net@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 14905BB9CCF for ; Sun, 21 Aug 2016 01:29:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (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 CD6D31532; Sun, 21 Aug 2016 01:29:38 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x22f.google.com with SMTP id e63so60556122ith.1; Sat, 20 Aug 2016 18:29:38 -0700 (PDT) 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=I2aUmMvZEz9N9+wcKrmaq3eCKwVrGY8HHGolbI5oVOA=; b=CbXvMrN8CNHYsJF8Rh1lFOiRNc/OBagmtA4EaoXpxXyQIup1AzUH6XRb/klMZHN+jA QDEg1onIS7gcwK5ZbxUYyY9xI//BjQ5iHdTHRzN1APltpb/LvT+Jo/j65pDhJM4ilqzr WcanVXRPy4iqy8DLqOk5+CghJpYt9bVLfKJ3TJxB+IEcrA3EElx7jAR5WiGhQ51B0caV QFy4ZXAju7cmVoRTfFhGLT7VeRWmHjoXXzZ8fnNGqzuJD9RkE9JxtwJqf7GHk3LO1Shr q1L7qgODxIpmvN1H8pxPOzy/d3LXjfFA97E69V1NRlNS8oUltmDxTfDOAF123xx+IaQr Tsjw== 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=I2aUmMvZEz9N9+wcKrmaq3eCKwVrGY8HHGolbI5oVOA=; b=IuM5UYbAu+6zOK60KFtdu1MSpMSB3PQEmYOKF8xWw/31vIHtYWAap8JgTygMmoizo+ G7ERZbYhk6K2ndgPwV68ptYdxQT9Sn7V8091nHXG9/msPR7roZU1eTpVaoCtRH0O9CNu R6he7tmeejai5c+3CLvSpmN1SnvU+hPqrG5o6/ObOC4jtqhy7BsY+Mbr3EhtjC4rUZWd YuDNMSxCYtVp+jL2syo7WR9rXd/mE+JRxT4udna4qfKOhxORCpK7pBsKDI765cGs/n+7 TcFfJRpYxgRNzIckYseu0c45dkTmz6ZrUQuZ5sWoi8/N/SPc/g3LeM/rQyuNepAOhiFv Tr5Q== X-Gm-Message-State: AEkoousR/KCF9Ke4hjlxR92KdBeJqz2x3KmM42sOqWfM14VTySgl5XviA69SnB23MiL+tubtSQ0s/Wk/5pJF6g== X-Received: by 10.36.150.70 with SMTP id z67mr12900460itd.80.1471742978012; Sat, 20 Aug 2016 18:29:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Sat, 20 Aug 2016 18:29:35 -0700 (PDT) Received: by 10.36.141.129 with HTTP; Sat, 20 Aug 2016 18:29:35 -0700 (PDT) In-Reply-To: References: From: Adrian Chadd Date: Sat, 20 Aug 2016 18:29:35 -0700 Message-ID: Subject: Re: iwn(4) association issues in 11-Stable (and maybe RC) To: Kevin Oberman Cc: FreeBSD Net , Andriy Voskoboinyk Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2016 01:29:39 -0000 Hi, There have been some changes to the scan code and iwn scan timeout code. Andriy may have some ideas. Thanks! A On Aug 19, 2016 3:48 PM, "Kevin Oberman" wrote: > Lately I have had serious issues with my system successfully associating. > These were not present with 10.3. > > > uname -a > FreeBSD rogue 11.0-BETA4 FreeBSD 11.0-BETA4 #1 r303806: Sat Aug 6 18:50:50 > PDT 2016 root@rogue:/usr/obj/usr/src/sys/GENERIC.4BSD amd64 > > iwn0@pci0:3:0:0: class=0x028000 card=0x13118086 chip=0x00858086 > rev=0x34 > hdr=0x00 > cap 01[c8] = powerspec 3 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > cap 10[e0] = PCI-Express 1 endpoint max data 128(128) FLR RO NS > link x1(x1) speed 2.5(2.5) ASPM L1(L0s/L1) > ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected > ecap 0003[140] = Serial 1 a088b4ffffc6ad28 > > Once associated, it works fine, but a dropped association is often not > re-established and the network fails to come up at boot time. Kernel is > GENERIC except the 4BSD scheduler. > > I've been using a mobile hotspot this week during travels and it has become > a real pain. With lot of patience and many "netif restart wlan0" > operations, it will come up, but it can be painful. Here is what I see in > messages: > Aug 19 00:13:52 rogue kernel: wlan0: Ethernet address: a0:88:b4:c6:ad:28 > Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN > Aug 19 00:13:52 rogue kernel: iwn0: scan timeout > Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN > Aug 19 00:13:52 rogue kernel: iwn0: scan timeout > Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN > Aug 19 00:13:52 rogue kernel: iwn0: scan timeout > Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN > Aug 19 00:13:52 rogue kernel: iwn0: scan timeout > Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN > Aug 19 00:13:52 rogue kernel: iwn0: scan timeout > Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN > Aug 19 00:13:52 rogue kernel: iwn0: scan timeout > Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN > Aug 19 00:13:52 rogue kernel: iwn0: scan timeout > Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to UP > Aug 19 00:13:52 rogue kernel: ipfw2 (+ipv6) initialized, divert loadable, > nat loadable, default to deny, logging disabled > Aug 19 00:13:52 rogue kernel: wlan0: link state changed to DOWN > Aug 19 00:13:52 rogue kernel: iwn0: scan timeout > Aug 19 00:13:52 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > Aug 19 00:14:17 rogue dhclient[362]: send_packet: Network is down > Aug 19 00:14:37 rogue dhclient[362]: send_packet: Network is down > Aug 19 00:14:39 rogue wpa_supplicant[350]: wlan0: CTRL-EVENT-TERMINATING > Aug 19 00:14:39 rogue dhclient[362]: connection closed > Aug 19 00:14:39 rogue dhclient[362]: exiting. > Aug 19 00:14:39 rogue rtsold[873]: interface > wlan0 removed > Aug 19 00:14:39 rogue kernel: wlan0: Ethernet address: a0:88:b4:c6:ad:28 > Aug 19 00:14:39 rogue wpa_supplicant[1621]: Successfully initialized > wpa_supplicant > Aug 19 00:14:39 rogue wpa_supplicant[1633]: Successfully initialized > wpa_supplicant > Aug 19 00:14:39 rogue root: /etc/rc.d/wpa_supplicant: WARNING: failed to > start wpa_supplicant > Aug 19 00:14:39 rogue kernel: iwn0: iwn_read_firmware: ucode rev=0x12a80601 > Aug 19 00:14:39 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:39 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:40 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:40 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:41 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:41 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:42 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:42 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:43 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:43 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:44 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:44 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:45 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:45 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:46 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:46 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:47 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:47 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:48 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:48 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:49 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:49 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:50 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:50 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:50 rogue root: /etc/rc.d/dhclient: WARNING: failed to start > dhclient > Aug 19 00:14:51 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:51 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:52 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:52 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > Aug 19 00:14:53 rogue wpa_supplicant[1634]: ioctl[SIOCS80211, op=103, > val=0, arg_len=128]: Operation now in progress > Aug 19 00:14:53 rogue wpa_supplicant[1634]: wlan0: CTRL-EVENT-SCAN-FAILED > ret=-1 retry=1 > > Is anyone else seeing this? > > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >