From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 16:25:24 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 557B6A40 for ; Sat, 12 Jan 2013 16:25:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x229.google.com (wg-in-x0229.1e100.net [IPv6:2a00:1450:400c:c00::229]) by mx1.freebsd.org (Postfix) with ESMTP id B5F68EFA for ; Sat, 12 Jan 2013 16:25:23 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id ds1so404114wgb.0 for ; Sat, 12 Jan 2013 08:25:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MqaWtR9y9IJ4ujouvNeif+IRUMXVnYEUk5B9NOpXSDU=; b=d5C242utTxMDeek5LPDPEpq+ZwWHNDynY60jPhyihq/qtDuOBJwoUYKPLaVhR9BlbI sOBc7BQIelSjfrSAp05ZLfdvqPssoixGMz+o3l0KcbgXQoNTL+iIlPhvxI1Be6colRip x11lptjCiEIq84BSSkDjVWE2gSNxP3f2o+d7/2asEez1/O46fhlSJrDbNZ+pDY70/DtA gde6vEcDO9gLAmzynCBjZBCXmKRPEbTkLss6RFENL4TQ863s3UWgxQ9kDweyPY9eKAO5 qjHXnqxDK3CenVcGdOTq1bI6SYm/kWCDjreCaCT0QPxnMQ+bigmfLKPuczYOTVlJH5EQ xVYA== MIME-Version: 1.0 Received: by 10.180.88.40 with SMTP id bd8mr4437680wib.33.1358007922159; Sat, 12 Jan 2013 08:25:22 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sat, 12 Jan 2013 08:25:22 -0800 (PST) In-Reply-To: <20130112162851.GI67643@zxy.spb.ru> References: <20130109121613.GO1967@zxy.spb.ru> <50edf68e.ec05320a.6ea9.ffff8ee4@mx.google.com> <20130110080729.GQ1967@zxy.spb.ru> <20130111075136.GA67643@zxy.spb.ru> <20130112105245.GF67643@zxy.spb.ru> <20130112154404.GH67643@zxy.spb.ru> <20130112162851.GI67643@zxy.spb.ru> Date: Sat, 12 Jan 2013 08:25:22 -0800 Message-ID: Subject: Re: Atheros 9220 don't return from S3 state From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 12 Jan 2013 16:25:24 -0000 .. right, try flipping the rf kill switch off/on after suspend, dump the config registers. Adrian On 12 January 2013 08:28, Slawa Olhovchenkov wrote: > On Sat, Jan 12, 2013 at 07:52:19AM -0800, Adrian Chadd wrote: > >> Ah, is it perhaps rfkill related? >> >> I've seen issues with rfkill before, where it is implemented as >> "disable the power to the entire slot" rather than assert the RF kill >> line to the device. >> It's possible this is how it has to happen with the intel NICs? >> >> do you have an rfkill button on the keyboard to enable/disable wireless? >> Try toggling that, then do pciconf -lv again? >> >> You can read the entire set of pci configuration registers: >> >> pciconf -rb pciX.X.X.X 0:255 >> >> If they show up as 0xffffffff then the NIC is disconnected/powered >> off/hung. Try toggling the RF kill key on your keyboard, then re-read >> those config registers. > > No rfkill button on the keyboard, but have hardware rf switch. This > switch now work only for bluetooth (switching off don't relay to > atheros card). > > Fresh boot, driver working > Switch off: # pciconf -rb pci0:6:5:0 0:255 > 8c 16 29 00 16 01 b0 02 01 00 80 02 08 a8 00 00 > 00 00 20 b0 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 8c 16 91 20 > 00 00 00 00 44 00 00 00 00 00 00 00 12 01 00 00 > 80 00 00 00 01 00 82 48 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > Switch on: # pciconf -rb pci0:6:5:0 0:255 > 8c 16 29 00 16 01 b0 02 01 00 80 02 08 a8 00 00 > 00 00 20 b0 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 8c 16 91 20 > 00 00 00 00 44 00 00 00 00 00 00 00 12 01 00 00 > 80 00 00 00 01 00 82 48 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > go to sleep, resume (switch still on): # pciconf -rb pci0:6:5:0 0:255 > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > >> Adrian >> >> >> >> On 12 January 2013 07:44, Slawa Olhovchenkov wrote: >> > On Sat, Jan 12, 2013 at 07:27:02AM -0800, Adrian Chadd wrote: >> > >> >> Hi, >> >> >> >> There's no firmware for the AR9220 .. it's all in the driver/HAL. >> >> >> >> If XP restore isn't working; maybe there's something in the ACPI/BIOS >> >> that's screwing things up? >> > >> > I am use last available BIOS. >> > After restore don't working only this card and this card don't have >> > tab 'Power manager' in windows device manager. >> > >> > I found in the internet information about other issuse with this >> > wn861n (and windows) (for example -- >> > http://www.nothingbuttablets.com/forum/showthread.php?p=80851), but >> > using last driver don't help for me.