From owner-freebsd-wireless@FreeBSD.ORG  Sat Jan 12 17:09:01 2013
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 632EA904
 for <freebsd-wireless@freebsd.org>; Sat, 12 Jan 2013 17:09:01 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 by mx1.freebsd.org (Postfix) with ESMTP id 218C5CE
 for <freebsd-wireless@freebsd.org>; Sat, 12 Jan 2013 17:09:01 +0000 (UTC)
Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1Tu4eH-0009Rp-N5; Sat, 12 Jan 2013 21:13:37 +0400
Date: Sat, 12 Jan 2013 21:13:37 +0400
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Adrian Chadd <adrian.chadd@gmail.com>
Subject: Re: Atheros 9220 don't return from S3 state
Message-ID: <20130112171337.GM67643@zxy.spb.ru>
References: <20130112154404.GH67643@zxy.spb.ru>
 <CAJ-Vmomy4jVNs9r0H2XzVO-Q6tq7=O4EzJn-NLCOO=n+SJce_g@mail.gmail.com>
 <20130112162851.GI67643@zxy.spb.ru>
 <CAJ-VmomUdkCtsGfzvd=hoeoNYPVip11nxNFb5z48a0EFWkbCTQ@mail.gmail.com>
 <20130112163712.GJ67643@zxy.spb.ru>
 <CAJ-VmonnDy81joHZ_Z_meMZxdUmSKsQWQ8Mud-42Knremq=Z3A@mail.gmail.com>
 <20130112165235.GK67643@zxy.spb.ru>
 <CAJ-VmomM5z1vjw+3--OYkfb=J5qm1k1egM19Njx660SHdAdJkw@mail.gmail.com>
 <20130112170707.GL67643@zxy.spb.ru>
 <CAJ-Vmo=oKw7HNJvvLu+xN1WSk_i-C-PZMS3zCS8jfvU0BDO0jA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAJ-Vmo=oKw7HNJvvLu+xN1WSk_i-C-PZMS3zCS8jfvU0BDO0jA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
Cc: "freebsd-wireless@freebsd.org" <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." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Jan 2013 17:09:01 -0000

On Sat, Jan 12, 2013 at 09:05:37AM -0800, Adrian Chadd wrote:

> We can't patch pci space if they're all 0xffffffff, that means nothing is there.
> 
> That's the point; the card hasn't come back on from suspend. So we
> need to do something _before_ it suspends. We can't do anything to the
> card after it resumes; we can only do stuff to the PCI bus.

No, patch before suspend. If card don't report support D3 state -- on
sleep card not lost power? Or after resume got full reset?

> Adrian
> 
> On 12 January 2013 09:07, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote:
> > On Sat, Jan 12, 2013 at 08:50:58AM -0800, Adrian Chadd wrote:
> >
> >> I don't know the first thing about ACPI, I'm sorry.
> >
> > OK, what about "patching" pci config space? Remove indication of
> > support D3 state? or system don't suspend after this complete?
> > (sorry for dumb question).
> >
> >> Perhaps ask on the freebsd acpi list?
> >>
> >>
> >>
> >> Adrian
> >>
> >> On 12 January 2013 08:52, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote:
> >> > On Sat, Jan 12, 2013 at 08:38:49AM -0800, Adrian Chadd wrote:
> >> >
> >> >> On 12 January 2013 08:37, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote:
> >> >> > On Sat, Jan 12, 2013 at 08:25:22AM -0800, Adrian Chadd wrote:
> >> >> >
> >> >> >> .. right, try flipping the rf kill switch off/on after suspend, dump
> >> >> >> the config registers.
> >> >> >
> >> >> > don't react -- 255 times 'ff'
> >> >>
> >> >> Okay. Well, I'll see if there's anything that I can do with the PCI
> >> >> glue inside the AR9220, but if it's broken under Windows...
> >> >
> >> > Perhaps if ACPI not found vendor wifi card (intel) not powered slot on
> >> > resume? I am don't know how chek this is acpidump...