From owner-freebsd-wireless@freebsd.org Thu Oct 13 16:33:59 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 834B3C106E4 for ; Thu, 13 Oct 2016 16:33:59 +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 5A3601DC for ; Thu, 13 Oct 2016 16:33:59 +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 u9DGXxau063939 for ; Thu, 13 Oct 2016 16:33:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 213444] iwn Wi-Fi not working after suspend/resume, after upgrading to 11.0 Date: Thu, 13 Oct 2016 16:33:59 +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 Many People 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: 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: Thu, 13 Oct 2016 16:33:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213444 david@catwhisker.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david@catwhisker.org --- Comment #3 from david@catwhisker.org --- My hardware and experience are both different; whether one has a significant effect on the other, I don't know. Summary: I don't see the problem. More details: Information on my laptop may be found at . As noted there, I field-replaced the Broadcom wireless/Bluetooth card (whi= ch was apparently not supported) with the Intel WiFi Link 5100 that I pulled o= ut of my previous laptop (Dell M4400). Further, I have (also) been tracking head on the same laptop (on a different slice of the boot drive). Once stable/11 was branched, I copied the head slice's / and /usr file systems to a 3rd slice, then used "svn switch" to update that slice's /usr/src from head to stable/11; I have been tracking h= ead, stable/11, and stable/10 daily on the m4800 since. While I have had issues with suspend/resume (e.g., a recent update to x11/nvidia/driver appears to have broken resume for me until I switched from x11/nvidia-driver to x11/nvidia-driver-340), I do not recall ever having an issue with iwn/wlan0 failing to work on resume. (And yes, I do exercise suspend/resume: I suspend the laptop before getting on my bike to get to the shuttle stop, resume once on shuttle (and use wireless to access the Intern= et), then suspend again once we reach work (before I stuff the laptop back in my backpack), then resume again once I'm at my desk.) And for the past 3 weeks or so, I've been running stable/11 on the laptop Monday - Friday. --=20 You are receiving this mail because: You are the assignee for the bug.=