From owner-freebsd-wireless@freebsd.org Mon May 2 12:45: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 77E8DB2AB42 for ; Mon, 2 May 2016 12:45: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 5E6A71439 for ; Mon, 2 May 2016 12:45: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 u42CjBiO033161 for ; Mon, 2 May 2016 12:45:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 209198] iwn sometimes loses link on dhclient start Date: Mon, 02 May 2016 12:45: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-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: david@catwhisker.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: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc attachments.created 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.22 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, 02 May 2016 12:45:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209198 Bug ID: 209198 Summary: iwn sometimes loses link on dhclient start Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: wireless Assignee: freebsd-wireless@FreeBSD.org Reporter: david@catwhisker.org CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Created attachment 169878 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D169878&action= =3Dedit dmesg output after "service netif restart wlan0" and logging in Over the last several months, as I reboot my laptop to the "head" slice for= its daily update-in-place (by source rebuild), I've noticed that while the wlano NIC (using iwn hardware) almost always "Just Works" when I boot stable/10, = in head, it's about a 50% probability that wpa_supplicant will start, bring up wlan0, and keep link up after dhclient starts -- vs. dropping link once dhclient starts, only to have dhclient continue to re-try, even though wlan= 0's link has dropped. In the latter case, I have found a circumvention (of sorts): After dhclient finally times out and gives up, login (as root) on ttyv1, then issue "servi= ce netif restart wlan0". In my experience, this always makes it work again. (= As I use xdm, started via getty out of /etc/ttys, I then also issue "service xdm stop".) Per suggestion, I have augmented /etc/rc.conf with 'wlandebug_wlan0=3D"state+scan+auth+assoc+crypto"' ... and while I did not encounter the above-described issue on the first "head" boot this morning, I did on the second, when the laptop was running: FreeBSD g1-252.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #406=20 r298919M/298920:1100106: Mon May 2 04:42:04 PDT 2016=20=20=20=20 root@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 For each of the "head" boots this morning, I booted verbosely; I have retai= ned a few log files from the second boot (where link was dropped), and managed = to attach one of them. (I didn't see a way to attach multiple files -- other = than concatenating them into one single mess, which seemed a bit counterproducti= ve.) Note that the SSID of interest to me is "lmdhw-net". --=20 You are receiving this mail because: You are the assignee for the bug.=