From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 19:45:45 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 51D1BC6 for ; Sun, 13 Jan 2013 19:45:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id E13D583D for ; Sun, 13 Jan 2013 19:45:44 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id o1so845497wic.11 for ; Sun, 13 Jan 2013 11:45:38 -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=9sbkDTs+aCo7FLo5njTP9fN2bZGdoE6UacPZhzSdpZA=; b=EwaeThR/YZJYq3HtJWMGhCkRWB5TUOlG4pmmU70Wc+Ahnz4eDcs0d4aBAojMl60oaZ usV8dbuh+dBf4Xwzx49f9C/2CFhAQiT6G1UXp8Ftssl8qiQC4+lEn7dzXLOnfxYOKvjH hqPT3Fm+AUMjvBTl99PANuOqDkeukhbQOoG2k+faoJExQ7YgZsrSRHnhQ6KZ/vRpxcwV FHhbIWSk7YO+SPWJOOz8hZ1rJPA/j7uOLQ++iFQVX/qmSjF/rraj/Qk7xSHxg73gsH+M NdJtq32/sLEIaDkL7RCei8uLYlBxdGvzXS8I7yCIEbboi/XXp2T0UwZjiWQHyzAY4ZlU KrbQ== MIME-Version: 1.0 Received: by 10.194.179.34 with SMTP id dd2mr131538103wjc.1.1358106338390; Sun, 13 Jan 2013 11:45:38 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sun, 13 Jan 2013 11:45:38 -0800 (PST) In-Reply-To: References: <20130112162851.GI67643@zxy.spb.ru> <20130112163712.GJ67643@zxy.spb.ru> <20130112165235.GK67643@zxy.spb.ru> <20130112170707.GL67643@zxy.spb.ru> <20130114050646.O62930@sola.nimnet.asn.au> <20130113194033.GQ67643@zxy.spb.ru> Date: Sun, 13 Jan 2013 11:45:38 -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" , Ian Smith 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: Sun, 13 Jan 2013 19:45:45 -0000 .. and it may not be the slot power. It could also be the PCI bridge (re) programming. It needs to have the right BAR and such programmed into it, or it won't "route" things correctly to child slots. I had this problem with cardbus a few months ago. After a resume, not all of the relevant PCI config space registers were being restored.. Adrian