From owner-freebsd-stable@FreeBSD.ORG Sun Sep 27 11:19:25 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBC56106566C for ; Sun, 27 Sep 2009 11:19:25 +0000 (UTC) (envelope-from lambert@lambertfam.org) Received: from sysmon.tcworks.net (sysmon.tcworks.net [65.66.76.4]) by mx1.freebsd.org (Postfix) with ESMTP id 9B1518FC17 for ; Sun, 27 Sep 2009 11:19:25 +0000 (UTC) Received: from sysmon.tcworks.net (localhost [127.0.0.1]) by sysmon.tcworks.net (8.13.1/8.13.1) with ESMTP id n8RBJOAq048803 for ; Sun, 27 Sep 2009 06:19:24 -0500 (CDT) (envelope-from lambert@lambertfam.org) Received: (from lambert@localhost) by sysmon.tcworks.net (8.13.1/8.13.1/Submit) id n8RBJODj048802 for freebsd-stable@freebsd.org; Sun, 27 Sep 2009 06:19:24 -0500 (CDT) (envelope-from lambert@lambertfam.org) X-Authentication-Warning: sysmon.tcworks.net: lambert set sender to lambert@lambertfam.org using -f Date: Sun, 27 Sep 2009 06:19:24 -0500 From: Scott Lambert To: freebsd-stable@freebsd.org Message-ID: <20090927111924.GG4858@sysmon.tcworks.net> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Subject: 8-RC1: iwn0 suspend/resume issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Sep 2009 11:19:25 -0000 Threading broken to avoid potential takover of ral0 thread. On Sat, Sep 26, 2009 at 02:33:26AM +0000, Brandon Gooch wrote: > On Fri, Sep 25, 2009 at 11:29 PM, Scott Lambert wrote: > > iwn does not function after resume so I've actually run ethernet cables > > to where I use the laptop now. > > I have to unload the if_iwn module on suspend, and reload it on resume > (via /etc/rc.[suspend|resume], of course). > > Have you tried that? I am glad to hear that it works for somebody. There is hope! I have: kldunload if_iwn in /etc/rc.suspend and: kldload if_iwn in /etc/rc.resume. On resume there are lots of iwn0: iwn_mem_lock: could not lock memory and iwn0: iwn_transfer_microcode: could not load boot firmware iwn0: iwn_transfer_firmware: could not load boot firmware, error 60 iwn0: iwn_init_locked: could not load firmware, error 60 I did just notice: iwn0: Reg Domain: \M^?\M^?\M^?\M^?iwn0: iwn_mem_lock: could not lock memory Maybe I should set the regulatory domain? But having just spent a few minutes trying, it doesn't seem to be interested... lambert@slambert:~> sudo ifconfig wlan0 regdomain FCC ifconfig: SIOCS80211: Device busy Exit 1 lambert@slambert:~> sudo ifconfig iwn0 regdomain FCC ifconfig: unable to get regulatory domain info: Invalid argument Exit 1 Same result with the other regulatory domains. Maybe iwn just doesn't support it? lambert@slambert:~> sudo ifconfig wlan0 list regdomain :regdomain 0 country US anywhere -ecm http://www.lambertfam.org/~lambert/laptop/TravelMate_5720-6911 has my rc.[suspend|resume] and dmesg.[boot|resume] showing the issues. Other stuff in there that might be relevant too, if anyone is interested. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org