From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 6 00:08:00 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 D9BA2F7C for ; Sun, 6 Jan 2013 00:08:00 +0000 (UTC) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [IPv6:2001:470:f0fd:0:2e0:81ff:fe2b:acbc]) by mx1.freebsd.org (Postfix) with ESMTP id A64EDAF4 for ; Sun, 6 Jan 2013 00:07:59 +0000 (UTC) Received: from jill.exit.com (jill.exit.com [IPv6:2001:470:f0fd:0:2e0:81ff:febc:fdcc]) by tinker.exit.com (8.14.5/8.14.5) with ESMTP id r0607vlL010598 for ; Sat, 5 Jan 2013 16:07:57 -0800 (PST) (envelope-from frank@exit.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=exit.com; s=tinker; t=1357430877; bh=KlisKq0qVcwO6YLBxMPpAOFzpMsdKQzUAeBPphXJWQw=; h=Subject:From:Reply-To:To:Date; b=XatWrbM5a6YUuSO7aoDolGM+zxHgxWFxv4UKdxLFg4mRJYIzd24Qm7yhNRaJi0L0Q xzVzVZNJEOxl+crV6BtF9PSsmib6iA4uZbWzvimbIjc9/RIDuxpR1SRw8SrWpo04Nf noQ1ieeQx/m3C0y8Ni4pV2BslWNZ+eIzr4V2fnIg= Received: from jill.exit.com (localhost [127.0.0.1]) by jill.exit.com (8.14.5/8.14.5) with ESMTP id r0607YvK067080 for ; Sat, 5 Jan 2013 16:07:34 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by jill.exit.com (8.14.5/8.14.5/Submit) id r0607Ysu067079 for freebsd-wireless@freebsd.org; Sat, 5 Jan 2013 16:07:34 -0800 (PST) (envelope-from frank@exit.com) X-Authentication-Warning: jill.exit.com: frank set sender to frank@exit.com using -f Subject: Reliable wireless card for 9-stable? From: Frank Mayhar To: freebsd-wireless Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Organization: Exit Consulting Date: Sat, 05 Jan 2013 16:07:34 -0800 Message-ID: <1357430854.50885.4.camel@jill.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: frank@exit.com 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, 06 Jan 2013 00:08:00 -0000 Seeing as the Intel Ultimate-N 6300 that's in my new Dell doesn't work in 9-stable (see related email here), I'm looking for a card that _does_ work. Can anyone recommend a decent 11a/g/n card that works well? At least for 11a and 11g, I realize that 11n is still under heavy development, thanks, Adrian! It obviously needs to be a mini-pcie card. Suggestions greatly appreciated. Links even more appreciated. :-) Thanks! --=20 Frank Mayhar frank@exit.com From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 6 03:15:55 2013 Return-Path: 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 2A89A381 for ; Sun, 6 Jan 2013 03:15:55 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id DDBFDFE6 for ; Sun, 6 Jan 2013 03:15:54 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.6/8.14.6) with ESMTP id r063Fjhj017934; Sat, 5 Jan 2013 20:15:45 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.6/8.14.6/Submit) with ESMTP id r063FiM3017931; Sat, 5 Jan 2013 20:15:45 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sat, 5 Jan 2013 20:15:44 -0700 (MST) From: Warren Block To: Frank Mayhar Subject: Re: Reliable wireless card for 9-stable? In-Reply-To: <1357430854.50885.4.camel@jill.exit.com> Message-ID: References: <1357430854.50885.4.camel@jill.exit.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Sat, 05 Jan 2013 20:15:45 -0700 (MST) Cc: freebsd-wireless 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, 06 Jan 2013 03:15:55 -0000 On Sat, 5 Jan 2013, Frank Mayhar wrote: > Seeing as the Intel Ultimate-N 6300 that's in my new Dell doesn't work > in 9-stable (see related email here), I'm looking for a card that _does_ > work. Can anyone recommend a decent 11a/g/n card that works well? At > least for 11a and 11g, I realize that 11n is still under heavy > development, thanks, Adrian! It obviously needs to be a mini-pcie card. Careful, there are two sizes of mini-PCIe cards, full- and half-, and between one and three antenna connections. Another important consideration is that Lenovo and HP machines have BIOS whitelists that only allow certain cards to work. > Suggestions greatly appreciated. Links even more appreciated. :-) > Thanks! There's a page on the wiki with Atheros hardware support, but the wiki is down right now. From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 6 03:42:22 2013 Return-Path: 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 3E87475D for ; Sun, 6 Jan 2013 03:42:22 +0000 (UTC) (envelope-from frank@exit.com) Received: from tinker.exit.com (unknown [IPv6:2001:470:f0fd:0:2e0:81ff:fe2b:acbc]) by mx1.freebsd.org (Postfix) with ESMTP id D7984EB for ; Sun, 6 Jan 2013 03:42:21 +0000 (UTC) Received: from jill.exit.com (jill.exit.com [IPv6:2001:470:f0fd:0:2e0:81ff:febc:fdcc]) by tinker.exit.com (8.14.5/8.14.5) with ESMTP id r063gK9p011632; Sat, 5 Jan 2013 19:42:20 -0800 (PST) (envelope-from frank@exit.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=exit.com; s=tinker; t=1357443741; bh=wMkziV5cUwKAlkNdioI1CW2axhUzvfG6kFythciQt+Y=; h=Subject:From:Reply-To:To:Cc:In-Reply-To:References:Date; b=KD8G476li837RAzBVoGSzxaAYgau08VoggyU0jvwOsq1CEEvGVeirHIO9ZW9EhhhK BuJpVHUGgf46eqMRH98lJhESI9iAbVHglUlEYwpexuk0agX6UTtSefOpVYrThGuczP sxomcVPwt27WrjzYxtDX0j11wV6Lk6PJCHCQJGNY= Received: from jill.exit.com (localhost [127.0.0.1]) by jill.exit.com (8.14.5/8.14.5) with ESMTP id r063fvqY068059; Sat, 5 Jan 2013 19:41:57 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by jill.exit.com (8.14.5/8.14.5/Submit) id r063fvpv068058; Sat, 5 Jan 2013 19:41:57 -0800 (PST) (envelope-from frank@exit.com) X-Authentication-Warning: jill.exit.com: frank set sender to frank@exit.com using -f Subject: Re: Reliable wireless card for 9-stable? From: Frank Mayhar To: Warren Block In-Reply-To: References: <1357430854.50885.4.camel@jill.exit.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Organization: Exit Consulting Date: Sat, 05 Jan 2013 19:41:57 -0800 Message-ID: <1357443717.50885.10.camel@jill.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Cc: freebsd-wireless X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: frank@exit.com 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, 06 Jan 2013 03:42:22 -0000 On Sat, 2013-01-05 at 20:15 -0700, Warren Block wrote: > On Sat, 5 Jan 2013, Frank Mayhar wrote: > > Seeing as the Intel Ultimate-N 6300 that's in my new Dell doesn't work > > in 9-stable (see related email here), I'm looking for a card that _does= _ > > work. Can anyone recommend a decent 11a/g/n card that works well? At > > least for 11a and 11g, I realize that 11n is still under heavy > > development, thanks, Adrian! It obviously needs to be a mini-pcie card= . > Careful, there are two sizes of mini-PCIe cards, full- and half-, and=20 > between one and three antenna connections. Yeah, I'm planning on picking up a half-size card. I don't know how many antenna connections the current card has bit it's at least two and quite likely three. =46rom reading lists and comments here and there it looks like and Atheros-based card is the way to go but I was hoping for a concrete recommendation. I'm currently using an AR5413-based card in another laptop but it suffers from regular device timeouts and poor performance. > Another important consideration is that Lenovo and HP machines have BIOS= =20 > whitelists that only allow certain cards to work. Not an issue for me, this is a Dell Latitude E6530. > > Suggestions greatly appreciated. Links even more appreciated. :-) > > Thanks! > There's a page on the wiki with Atheros hardware support, but the wiki= =20 > is down right now. Yeah, I tried that. Thanks. --=20 Frank Mayhar frank@exit.com From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 6 04:53:18 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 A8132DEB for ; Sun, 6 Jan 2013 04:53:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by mx1.freebsd.org (Postfix) with ESMTP id 29E3B209 for ; Sun, 6 Jan 2013 04:53:17 +0000 (UTC) Received: by mail-wg0-f43.google.com with SMTP id e12so8395480wge.34 for ; Sat, 05 Jan 2013 20:53:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=BHams3Q7qaI3MB3bM+UyJ0HNqu/C50VzERTlf9G2hrw=; b=FGoD6bzRaYHEud/CnpAbLBk4EJ4dAhorVRZra9XKKSTdzFrXIjNFSixK+5JfkbcBoG pQpypvTahaouoP8fvDimTMk6GOqOU3KOZrvSL0hbInirR8y+EtIxdeCysonxRq88THWM /6DGcvHsGcptgnsqLlM/m4/qE/tewYnRUD0mG1+FrpOPRllkxXj7P1973jcof9TA/1/1 BAFN2HdpFoP2gKItGmAeDN86wkIJnskEzpKQ0EGcEQ2H1YqFKf64pZhzKB0CYW/VI3JK A+6Z1YlfIVxK/RFbkWfamPaIsAgX3N7eoHedSRoR6ChIg4FldjiH5v3y9bZbECkpLDO4 kj8g== MIME-Version: 1.0 Received: by 10.180.8.130 with SMTP id r2mr3943284wia.28.1357447996704; Sat, 05 Jan 2013 20:53:16 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sat, 5 Jan 2013 20:53:16 -0800 (PST) Date: Sat, 5 Jan 2013 20:53:16 -0800 X-Google-Sender-Auth: PSxoxXdyC7W1U1p7vTzP3C8H_lo Message-ID: Subject: [CFT] ath(4) migration to if_transmit() and a transmit tasklet, rather than direct dispatch From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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, 06 Jan 2013 04:53:18 -0000 Hi, I've written up a replacement ath(4) TX path that does a bunch of things. The patch I'd like everyone to try: http://people.freebsd.org/~adrian/ath/20130105-if_transmit_txfrag_2.diff What it does: * It implements a driver staging queue for frames from if_start and if_transmit(); * It populates that staging queue with ath_buf's, that contain the mbuf and node ref; * The actual TX occurs in a taskqueue (the default ath taskqueue for now, but I'll move it to another one soon) in order to serialise things; * The tx fragment list is populated correctly (but doesn't quite work, see below); * the reliance on "peeking" at the next mbuf in a fragment list is gone - instead, I now store the data length of the next fragment in the current buffer and fire that across. Now, in station mode I get exactly the same throughput as before - 150-180mbit TCP iperf tests. It's great. I need to do some more (single core) MIPS testing - if it drops in throughput there, it'll likely be the ridiculously huge calls to taskqueue_enqueue() and/or some lock contention. I'd like to commit this to -HEAD and then begin next the next phase, which is: * Figure out why TX fragments are transmitted but dropped by (some) receivers. FreeBSD -> FreeBSD works fine, but FreeBSD -> (some random 11g cable modem router) just plain drops the fragments in question. Sigh; * Tidy up some more of the locking, which likely involves separating out the TX queue lock from the TX taskqueue lock; * Push raw xmit frames into the same queue mechanism, so they are queued in the same fashion and obey the same sequence number / CCMP IV allocation ordering that data frames do (which is important as things like EAPOL frames are encrypted and have sequence numbers, but come in the raw xmit path. Grr.) * Finish tidying up when things are called - specifically, I'd like to make sure all the buffer completions occur outside of the locks behind held, so I can finally avoid a bunch of potential LORs when doing things like transmitting BAR frames from the TX completion path. I'd really appreciate any testing that can be done for this. It doesn't matter which mode you're in - adhoc, hostap, mesh, sta, 11n or non-11n - all ath(4) chips share the same TX path code and this all happens before the software TX queue and aggregation handling. Once this is all verified and working, I'll work on migrating the net80211 TX path to actually use if_transmit() itself and use a TX taskqueue to serialise all TX. That should fix a whole bunch of subtle, niggling little TX side bugs that have been the bane of my existence since I took this code on a couple years ago. Finally - although I'd like to _fix_ TX fragment handling, it still has its .. quirks. I'm still worried that a very active STA or AP with multiple traffic sessions will end up with TX fragments in the software queue that aren't kept 100% in order (ie, other frames from other sessions get interspersed with other session traffic. For now it won't happen - the TX lock is held for the duration of running the TX queuing and so (in theory!) nothing should appear in the TX queue in between TX fragments. But I don't trust it. Chances are the correct fix is a lot more nasty than the current net80211 way of "just do fragmentation in the net80211 layer and the driver will figure it out" lets me do cleanly. (Ie, I think the clean way is to do fragmentation at the point where you're about to queue it to the actual hardware and not in net80211, but I digress.) Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 6 07:34:07 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 74A0CACB; Sun, 6 Jan 2013 07:34:07 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 40A576C6; Sun, 6 Jan 2013 07:34:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id r067Y76s057204; Sun, 6 Jan 2013 07:34:07 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id r067Y7n5057200; Sun, 6 Jan 2013 07:34:07 GMT (envelope-from linimon) Date: Sun, 6 Jan 2013 07:34:07 GMT Message-Id: <201301060734.r067Y7n5057200@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/175053: [iwn] iwn firmware error on 9-stable with Ultimate-N 6300 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, 06 Jan 2013 07:34:07 -0000 Old Synopsis: iwn firmware error on 9-stable with Ultimate-N 6300 New Synopsis: [iwn] iwn firmware error on 9-stable with Ultimate-N 6300 Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jan 6 07:33:50 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=175053 From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 7 11:06:56 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 ACA2A10D for ; Mon, 7 Jan 2013 11:06:56 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 901BDFA7 for ; Mon, 7 Jan 2013 11:06:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r07B6urR088084 for ; Mon, 7 Jan 2013 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r07B6uEE088082 for freebsd-wireless@FreeBSD.org; Mon, 7 Jan 2013 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 7 Jan 2013 11:06:56 GMT Message-Id: <201301071106.r07B6uEE088082@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Subject: Current problem reports assigned to 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: Mon, 07 Jan 2013 11:06:56 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/175053 wireless [iwn] iwn firmware error on 9-stable with Ultimate-N 6 o kern/174722 wireless [wlan] can't use channel 12 and 13 (14) with my wifi i o kern/174661 wireless [wlan] lost alias on wlan interface o kern/174283 wireless [net80211] panics in ieee80211_ff_age() and ieee80211_ o kern/174276 wireless [ath] if_ath memory modified after free o kern/174273 wireless [net80211] taking down a net80211 node with active fas o kern/173917 wireless [iwn] wpa-supplicant issues on iwn o kern/173883 wireless [ath] ath0: unable to attach - pci issue? o kern/173711 wireless [ath] powerd kills ath on the Asus EeePC 1005HA o kern/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff handling o o kern/172955 wireless [ath] 11n does not work in adhoc mode o kern/172706 wireless [wpi] wpi0 fails to load firmware when using country o kern/172672 wireless [ubt] Bluetooth device recognised but not working o kern/172661 wireless hostapd(8) securing wireless adapter in HostAP mode is o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170904 wireless [ath] ath driver: configure related parameters when ra o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o kern/121061 wireless [ath] [panic] panic while ejecting ath(4)-adapter duri o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 144 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 7 19:40:33 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 5E9CFF0E for ; Mon, 7 Jan 2013 19:40:33 +0000 (UTC) (envelope-from marko.cupac@gmail.com) Received: from mail-bk0-f45.google.com (mail-bk0-f45.google.com [209.85.214.45]) by mx1.freebsd.org (Postfix) with ESMTP id DA18D1C9 for ; Mon, 7 Jan 2013 19:40:32 +0000 (UTC) Received: by mail-bk0-f45.google.com with SMTP id jk13so8658981bkc.18 for ; Mon, 07 Jan 2013 11:40:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:subject:message-id:in-reply-to:references :x-mailer:mime-version:content-type:content-transfer-encoding; bh=2ir+355AdNSsDtkpDUZi3WJev+q3yNdVJmwCqQOQkAA=; b=D6cO6qgX32MXcsJZDPK5cDgBosY0HUPKAJYIgFh8JgErc3O7Aswl/y/zTmMPF8h6Ro GJ+6+RHNhjhvDCj9IVXaiBUCEQ8fbXGrthynpKQRo5XpLXX8/CWF1UaH463VKMDZ/LOZ AdqxHLVi0JiCnfk5I/6tksx4ahzjfbJknpLkXHdme8J1IwQQ2eke9JTChNnSEwevm7Lf 7/zMTwrpwVNOVZqkyG9x6SuqiXXrkSD+rqXnnLUZzXTGGtzJcNTFpNSIo/XYERwh2jSS nOIikRcAtNLIXAl283Et/UpCe9CZ2619CkUy42ofs0dkPSsMemGXe6yw4QQYumuvxqw6 1t9A== X-Received: by 10.204.148.154 with SMTP id p26mr30465405bkv.31.1357587626035; Mon, 07 Jan 2013 11:40:26 -0800 (PST) Received: from kaa.mimar.rs (79-101-90-2.dynamic.isp.telekom.rs. [79.101.90.2]) by mx.google.com with ESMTPS id u3sm43585002bkw.9.2013.01.07.11.40.24 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 07 Jan 2013 11:40:24 -0800 (PST) Date: Mon, 7 Jan 2013 20:40:22 +0100 From: "marko.cupac" To: freebsd-wireless@freebsd.org Subject: 9.1 solved my ath problem Message-ID: <20130107204022.67509693@kaa.mimar.rs> In-Reply-To: References: X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Mon, 07 Jan 2013 19:40:33 -0000 I just wanted to say that since I upgraded to 9.1-RELEASE my problems with random freezes of AR9285 and consequent system restarts are gone. I guess my PR kern/171235 can be closed. Thanks to developers for fixing it. From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 8 23:51:06 2013 Return-Path: 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 A61AFACB for ; Tue, 8 Jan 2013 23:51:06 +0000 (UTC) (envelope-from andrew@ugh.net.au) Received: from starbug.ugh.net.au (starbug.ugh.net.au [202.3.36.37]) by mx1.freebsd.org (Postfix) with ESMTP id 61C783FB for ; Tue, 8 Jan 2013 23:51:06 +0000 (UTC) Received: from [10.0.0.11] (77-64-236-30.dynamic.primacom.net [77.64.236.30]) by starbug.ugh.net.au (Postfix) with ESMTPSA id 8E6A8386C57 for ; Wed, 9 Jan 2013 12:20:27 +1100 (EST) From: Andrew Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Debugging Stalls with ath(4) Date: Wed, 9 Jan 2013 00:50:57 +0100 Message-Id: To: freebsd-wireless@freebsd.org Mime-Version: 1.0 (Apple Message framework v1085) X-Mailer: Apple Mail (2.1085) 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: Tue, 08 Jan 2013 23:51:06 -0000 Hi, I just installed a TP-Link TL-WN851ND PCI wireless card into my = 9.1-STABLE (r244942) box. It shows up in dmesg as Atheros 9287 mac 384.2 = RF5133. I am running it in hostap mode, 11g. Things seem to work OK but there = are occasionally stalls in traffic across the network. e.g. PING 10.0.0.1 (10.0.0.1): 56 data bytes 64 bytes from 10.0.0.1: icmp_seq=3D0 ttl=3D64 time=3D13.134 ms 64 bytes from 10.0.0.1: icmp_seq=3D1 ttl=3D64 time=3D77.776 ms 64 bytes from 10.0.0.1: icmp_seq=3D2 ttl=3D64 time=3D246.675 ms Request timeout for icmp_seq 3 64 bytes from 10.0.0.1: icmp_seq=3D3 ttl=3D64 time=3D1037.327 ms 64 bytes from 10.0.0.1: icmp_seq=3D4 ttl=3D64 time=3D37.481 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev =3D 13.134/282.479/1037.327/386.148 ms I was wondering how I would go about debugging the issue? I have been playing with wlandebug and I can see that the client I am = testing with (though it doesn't appear to be client specific) is listed = as going in and out of PS mode once or twice a second. Not sure that = that is a problem. Using "wlandebug rate" I see: Jan 9 00:45:25 sanna kernel: wlan0: [00:17:f2:e9:04:b0] = ath_rate_tx_complete: size 1600 (1167 bytes) OK rate/try 48 Mb /0/1 Jan 9 00:45:25 sanna kernel: wlan0: [00:17:f2:e9:04:b0] = ath_rate_tx_complete: size 1600 (1554 bytes) OK rate/try 48 Mb /0/1 Jan 9 00:45:25 sanna kernel: wlan0: [00:17:f2:e9:04:b0] = ath_rate_tx_complete: size 1600 (1554 bytes) OK rate/try 48 Mb /0/1 Jan 9 00:45:25 sanna kernel: wlan0: [7c:c5:37:6d:4c:7e] = ath_rate_tx_complete: size 250 (30 bytes) FAIL rate/try 1 Mb /0/7 Jan 9 00:45:25 sanna kernel: wlan0: [00:17:f2:e9:04:b0] = ath_rate_tx_complete: size 250 (106 bytes) OK rate/try 11 Mb /0/1 Jan 9 00:45:25 sanna kernel: wlan0: [00:17:f2:e9:04:b0] = ath_rate_tx_complete: size 250 (122 bytes) OK rate/try 11 Mb /0/1 Jan 9 00:45:26 sanna kernel: wlan0: [00:17:f2:e9:04:b0] = ath_rate_tx_complete: size 250 (138 bytes) OK rate/try 11 Mb /0/1 Jan 9 00:45:26 sanna kernel: wlan0: [00:23:14:98:15:b4] = ath_rate_findrate: size 250 switch rate 48 (1129/690) -> 54 (736/682) = after 2 packets mrr 0 Jan 9 00:45:26 sanna kernel: wlan0: [64:70:02:f0:c8:03] = ath_rate_tx_complete: size 250 FAIL rate/try 0/5 no rates yet Jan 9 00:45:26 sanna kernel: wlan0: [00:17:f2:e9:04:b0] = ath_rate_tx_complete: size 250 (94 bytes) OK rate/try 11 Mb /0/1 Jan 9 00:45:26 sanna last message repeated 2 times Jan 9 00:45:26 sanna kernel: wlan0: [00:23:14:98:15:b4] = ath_rate_tx_complete: size 250 (163 bytes) OK rate/try 54 Mb /0/2 Jan 9 00:45:26 sanna kernel: wlan0: [00:17:f2:e9:04:b0] = ath_rate_tx_complete: size 250 (137 bytes) OK rate/try 11 Mb /0/1 Given the proximity of the clients and the FreeBSD box I would have = expected it to not have had any trouble maintaing a high connection rate = - but perhaps this is a symptom of the stalls. Can anyone suggest where to go from here? Thanks, Andrew= From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 9 00:07:09 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 9C3453C6 for ; Wed, 9 Jan 2013 00:07:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 1BA726EB for ; Wed, 9 Jan 2013 00:07:08 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id dr1so896118wgb.5 for ; Tue, 08 Jan 2013 16:07:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=E/ccKejMcJT+R/bWPCiwlM0tUzlgzfyC/BG+WRC2OPo=; b=yvziMHyZ2kKfJYBM509yQvgY+4BEvvBUQzSdP2rdFk5/cscUSCpolxbYn5Sz+YRGk5 r06kMVpXQzuiTaYVYYSZBf8o7XtqCVfH3HgyP7U+ciFFup3Xpz57A7vvdIx/k3j41vAJ /gCT8CarY/NNEmtJQoWd+l8Vh1UpWhqBl30fxO0GB69jDvNpdre8OuXpDMzZ7TV1QwtI eQNrR2axTZLp67KjyqkTrW8fc2lBvr5FX3mBhD82RDamR8xQacPWIGzGu0DCGS+2Eedg IjI8HWpXeBgC+W2InTUdNzgye1YUtZpFZ9KdxnvAZ6GAT09tKdo3Mg9A4BDdz8nNhAJ1 zJ8g== MIME-Version: 1.0 Received: by 10.195.13.67 with SMTP id ew3mr17229676wjd.59.1357690027241; Tue, 08 Jan 2013 16:07:07 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Tue, 8 Jan 2013 16:07:07 -0800 (PST) Date: Tue, 8 Jan 2013 16:07:07 -0800 X-Google-Sender-Auth: UpEYzNGbk57RPwpTgCgB0kkpISc Message-ID: Subject: freebsd-head and spectral scan From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Wed, 09 Jan 2013 00:07:09 -0000 I hereby give you, AR9280 doing spectral + channel scanning: http://people.freebsd.org/~adrian/ath/fft_snapshot_5ghz.7.png adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 9 15:11:42 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 4213A68B; Wed, 9 Jan 2013 15:11:42 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id DDBC0764; Wed, 9 Jan 2013 15:11:40 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.6/8.14.6) with ESMTP id r09FBdQC008156; Wed, 9 Jan 2013 08:11:39 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.6/8.14.6/Submit) with ESMTP id r09FBd3g008153; Wed, 9 Jan 2013 08:11:39 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 9 Jan 2013 08:11:39 -0700 (MST) From: Warren Block To: Adrian Chadd Subject: Re: freebsd-head and spectral scan In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Wed, 09 Jan 2013 08:11:39 -0700 (MST) 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: Wed, 09 Jan 2013 15:11:42 -0000 On Tue, 8 Jan 2013, Adrian Chadd wrote: > I hereby give you, AR9280 doing spectral + channel scanning: > > http://people.freebsd.org/~adrian/ath/fft_snapshot_5ghz.7.png Nice! From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 9 15:59: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 07F169F3; Wed, 9 Jan 2013 15:59:24 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7BD4DA24; Wed, 9 Jan 2013 15:59:21 +0000 (UTC) Received: from vhoffman.lon.namesco.net (lon.namesco.net [195.7.254.102]) (authenticated bits=0) by unsane.co.uk (8.14.5/8.14.5) with ESMTP id r09FxJka039935 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 9 Jan 2013 15:59:19 GMT (envelope-from vince@unsane.co.uk) Message-ID: <50ED93D7.1030701@unsane.co.uk> Date: Wed, 09 Jan 2013 15:59:19 +0000 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: freebsd-head and spectral scan References: In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: Wed, 09 Jan 2013 15:59:24 -0000 On 09/01/2013 00:07, Adrian Chadd wrote: > I hereby give you, AR9280 doing spectral + channel scanning: > > http://people.freebsd.org/~adrian/ath/fft_snapshot_5ghz.7.png > This looks pretty :) as a bit of a clueless end user, what can I use this for? :) > > adrian > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 9 22:56:48 2013 Return-Path: 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 BD87C100; Wed, 9 Jan 2013 22:56:48 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ia0-f173.google.com (mail-ia0-f173.google.com [209.85.210.173]) by mx1.freebsd.org (Postfix) with ESMTP id 7303C289; Wed, 9 Jan 2013 22:56:48 +0000 (UTC) Received: by mail-ia0-f173.google.com with SMTP id w21so2032721iac.32 for ; Wed, 09 Jan 2013 14:56:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:to:cc:reply-to:subject:in-reply-to :x-mailer:mime-version:content-type; bh=1G6Kx+thAC1R5dWshu/PW20Ho3BLpK5kDxk1khYThLA=; b=oQoHhLdkL724ga8doxqGNpW+zHDnSxBV77e8ZO8G5kEwelCF+vpQML2z11tFLC9GBu lIvRwSG1QzeJ0V66VyatW1clP9UxsQj53QFD9IZ+hNiWcxT9jzMvcVzVCPJuJELtRc4c 3dLjpNg83mZMp6Pof8Bbhy3fj9tkSC8/fJOl3oVjfwZfkN+TYCnazfPjzByZ0CEbHlHv nVjceAzwFTZ9zUadbiUOwHoNpU7VAhSdYeR2jCS0T+7lxKHPBJW0zdDocnVLZ+5RkAjO zapCgxKeSpC+GltH/5AOykcfD53qHWErz+x7ISHBtryAuFofSDP8Ekj0EjPSQGHVHhe7 xOjA== X-Received: by 10.50.106.227 with SMTP id gx3mr3152089igb.10.1357772207614; Wed, 09 Jan 2013 14:56:47 -0800 (PST) Received: from www.palm.com ([166.197.237.98]) by mx.google.com with ESMTPS id bh3sm3128059igc.0.2013.01.09.14.56.42 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 09 Jan 2013 14:56:46 -0800 (PST) Message-ID: <50edf5ae.23ad320a.4d4f.ffff9018@mx.google.com> Date: Wed, 9 Jan 2013 17:56:36 -0500 From: "Adrian Chadd" To: "Vincent Hoffman" , "Adrian Chadd" Subject: Re: freebsd-head and spectral scan In-Reply-To: <50ED93D7.1030701@unsane.co.uk> X-Mailer: Palm webOS v1.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Adrian Chadd 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: Wed, 09 Jan 2013 22:56:48 -0000 Primarily- to look at inteference sources. Adrian Sent from my Palm Pre on AT&T On Jan 9, 2013 10:59 AM, Vincent Hoffman <vince@unsane.co.uk> wrote:= On 09/01/2013 00:07, Adrian Chadd wrote: > I hereby give you, AR9280 doing spectral + channel scanning: > > http://people.freebsd.org/~adrian/ath/fft_snapshot_5ghz.7.png > This looks pretty :) as a bit of a clueless end user, what can I use this for? :) > > adrian > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd= =2Eorg" > From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 9 23:00:33 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 6E34223D; Wed, 9 Jan 2013 23:00:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) by mx1.freebsd.org (Postfix) with ESMTP id 073E82AD; Wed, 9 Jan 2013 23:00:32 +0000 (UTC) Received: by mail-ie0-f178.google.com with SMTP id c12so2898771ieb.9 for ; Wed, 09 Jan 2013 15:00:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:to:reply-to:subject:in-reply-to :x-mailer:mime-version:content-type; bh=buIuOwpbWyn5Lo5L4JjefaZ9s1eM4nbfekMNGBaMB0w=; b=CjFu6/upf1H6eoaGjaAz2noW/2WmcG3P55hbwlieRYwIWWDk1etHdTDgWxfzgsmcrA Xx/AYt9YIcdGqMghbrPQ5IjvA11W1Kq00bINZwNlZWGt52r/D5pIFGp8AS7bAqSEx3KZ S2KpYKCReuf+50JHmYT2GFlDBC8adnrLuUDnYAoW3skdI7GxI12JTG1jIgK3VuJTmscx QEoitu9xcRMnbnRGUA+yKg4g1ync/6fi3ZwPPjkrrSI7odc07MTpY7FJxqoa90LITnkz HZ2uv1yyZ/ajWZLJyEyaW/Axj/icC7r/U4l1mlKHG/nWM3op4NQt29Pa+/Ft+FPzlfT2 lm8g== X-Received: by 10.50.222.226 with SMTP id qp2mr3216735igc.103.1357772432214; Wed, 09 Jan 2013 15:00:32 -0800 (PST) Received: from www.palm.com ([166.197.237.98]) by mx.google.com with ESMTPS id v12sm3421669igv.3.2013.01.09.15.00.25 (version=SSLv3 cipher=OTHER); Wed, 09 Jan 2013 15:00:30 -0800 (PST) Message-ID: <50edf68e.ec05320a.6ea9.ffff8ee4@mx.google.com> Date: Wed, 9 Jan 2013 18:00:21 -0500 From: "Adrian Chadd" To: "Slawa Olhovchenkov" , "Adrian Chadd" , "freebsd-wireless@freebsd.org" Subject: Re: Atheros 9220 don't return from S3 state In-Reply-To: <20130109121613.GO1967@zxy.spb.ru> X-Mailer: Palm webOS v1.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Adrian Chadd 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: Wed, 09 Jan 2013 23:00:33 -0000 Does it happen every time? Which version of freebsd is it? Adrian Sent from my Palm Pre on AT&T On Jan 9, 2013 7:11 AM, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote:=20 I am try play with suspend resume and see Atheros 9220 don't return from s3 state: [833] ath0: unable to reset hardware; hal status 3 try to unload/load module: [873] ath0: detached [873] pci6: <network> at device 5.0 (no driver attached) [882] pci0: driver added [882] found-> vendor=3D0x8086, dev=3D0x266a, revid=3D0x04 [882] domain=3D0, bus=3D0, slot=3D31, func=3D3 [882] class=3D0c-05-00, hdrtype=3D0x00, mfdev=3D0 [882] cmdreg=3D0x0101, statreg=3D0x0280, cachelnsz=3D0 (dwords) [882] lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) [882] intpin=3Db, irq=3D19 [882] pci0:0:31:3: reprobing on driver added [882] pci2: driver added [882] found-> vendor=3D0x14e4, dev=3D0x167d, revid=3D0x21 [882] domain=3D0, bus=3D2, slot=3D0, func=3D0 [882] class=3D02-00-00, hdrtype=3D0x00, mfdev=3D0 [882] cmdreg=3D0x0106, statreg=3D0x0010, cachelnsz=3D8 (dwords) [882] lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) [882] intpin=3Da, irq=3D16 [882] powerspec 2 supports D0 D3 current D0 [882] MSI supports 8 messages, 64 bit [882] pci0:2:0:0: reprobing on driver added [882] pci3: driver added [882] pci6: driver added [882] found-> vendor=3D0xffff, dev=3D0xffff, revid=3D0xff [882] domain=3D0, bus=3D6, slot=3D5, func=3D0 [882] class=3Dff-ff-ff, hdrtype=3D0x00, mfdev=3D0 [882] cmdreg=3D0xffff, statreg=3D0x02b0, cachelnsz=3D255 (dwords) [882] lattimer=3D0xff (7650 ns), mingnt=3D0xff (63750 ns), maxlat=3D0xff= (63750 ns) [882] intpin=3D_, irq=3D255 [882] powerspec 2 supports D0 D3 current D3 [882] pci0:6:5:0: reprobing on driver added [882] pci0:6:5:0: Transition from D3 to D0 [965] pci0: driver added [965] found-> vendor=3D0x8086, dev=3D0x266a, revid=3D0x04 [965] domain=3D0, bus=3D0, slot=3D31, func=3D3 [965] class=3D0c-05-00, hdrtype=3D0x00, mfdev=3D0 [965] cmdreg=3D0x0101, statreg=3D0x0280, cachelnsz=3D0 (dwords) [965] lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) [965] intpin=3Db, irq=3D19 [965] pci0:0:31:3: reprobing on driver added [965] pci2: driver added [965] found-> vendor=3D0x14e4, dev=3D0x167d, revid=3D0x21 [965] domain=3D0, bus=3D2, slot=3D0, func=3D0 [965] class=3D02-00-00, hdrtype=3D0x00, mfdev=3D0 [965] cmdreg=3D0x0106, statreg=3D0x0010, cachelnsz=3D8 (dwords) [965] lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) [965] intpin=3Da, irq=3D16 [965] powerspec 2 supports D0 D3 current D0 [965] MSI supports 8 messages, 64 bit [965] pci0:2:0:0: reprobing on driver added [965] pci3: driver added [965] pci6: driver added [965] found-> vendor=3D0xffff, dev=3D0xffff, revid=3D0xff [965] domain=3D0, bus=3D6, slot=3D5, func=3D0 [965] class=3Dff-ff-ff, hdrtype=3D0x00, mfdev=3D0 [965] cmdreg=3D0xffff, statreg=3D0x02b0, cachelnsz=3D255 (dwords) [965] lattimer=3D0xff (7650 ns), mingnt=3D0xff (63750 ns), maxlat=3D0xff= (63750 ns) [965] intpin=3D_, irq=3D255 [965] powerspec 2 supports D0 D3 current D3 [965] pci0:6:5:0: reprobing on driver added [965] pci0:6:5:0: Transition from D3 to D0 driver don't attached card detected after boot as pci0:6:5:0 From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 10 08:02:55 2013 Return-Path: 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 224A34D8; Thu, 10 Jan 2013 08:02:55 +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 AECFD88C; Thu, 10 Jan 2013 08:02:54 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1TtDAf-000DWy-Vy; Thu, 10 Jan 2013 12:07:29 +0400 Date: Thu, 10 Jan 2013 12:07:29 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130110080729.GQ1967@zxy.spb.ru> References: <20130109121613.GO1967@zxy.spb.ru> <50edf68e.ec05320a.6ea9.ffff8ee4@mx.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50edf68e.ec05320a.6ea9.ffff8ee4@mx.google.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 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" 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: Thu, 10 Jan 2013 08:02:55 -0000 On Wed, Jan 09, 2013 at 06:00:21PM -0500, Adrian Chadd wrote: > Does it happen every time? Yes. > Which version of freebsd is it? Last -current > > > Adrian > > > Sent from my Palm Pre on AT&T > On Jan 9, 2013 7:11 AM, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote: > > I am try play with suspend resume and see Atheros 9220 don't return > > from s3 state: > > > > > > [833] ath0: unable to reset hardware; hal status 3 > > > > try to unload/load module: > > > > [873] ath0: detached > > [873] pci6: <network> at device 5.0 (no driver attached) > > [882] pci0: driver added > > [882] found-> vendor=0x8086, dev=0x266a, revid=0x04 > > [882] domain=0, bus=0, slot=31, func=3 > > [882] class=0c-05-00, hdrtype=0x00, mfdev=0 > > [882] cmdreg=0x0101, statreg=0x0280, cachelnsz=0 (dwords) > > [882] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > > [882] intpin=b, irq=19 > > [882] pci0:0:31:3: reprobing on driver added > > [882] pci2: driver added > > [882] found-> vendor=0x14e4, dev=0x167d, revid=0x21 > > [882] domain=0, bus=2, slot=0, func=0 > > [882] class=02-00-00, hdrtype=0x00, mfdev=0 > > [882] cmdreg=0x0106, statreg=0x0010, cachelnsz=8 (dwords) > > [882] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > > [882] intpin=a, irq=16 > > [882] powerspec 2 supports D0 D3 current D0 > > [882] MSI supports 8 messages, 64 bit > > [882] pci0:2:0:0: reprobing on driver added > > [882] pci3: driver added > > [882] pci6: driver added > > [882] found-> vendor=0xffff, dev=0xffff, revid=0xff > > [882] domain=0, bus=6, slot=5, func=0 > > [882] class=ff-ff-ff, hdrtype=0x00, mfdev=0 > > [882] cmdreg=0xffff, statreg=0x02b0, cachelnsz=255 (dwords) > > [882] lattimer=0xff (7650 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns) > > [882] intpin=_, irq=255 > > [882] powerspec 2 supports D0 D3 current D3 > > [882] pci0:6:5:0: reprobing on driver added > > [882] pci0:6:5:0: Transition from D3 to D0 > > [965] pci0: driver added > > [965] found-> vendor=0x8086, dev=0x266a, revid=0x04 > > [965] domain=0, bus=0, slot=31, func=3 > > [965] class=0c-05-00, hdrtype=0x00, mfdev=0 > > [965] cmdreg=0x0101, statreg=0x0280, cachelnsz=0 (dwords) > > [965] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > > [965] intpin=b, irq=19 > > [965] pci0:0:31:3: reprobing on driver added > > [965] pci2: driver added > > [965] found-> vendor=0x14e4, dev=0x167d, revid=0x21 > > [965] domain=0, bus=2, slot=0, func=0 > > [965] class=02-00-00, hdrtype=0x00, mfdev=0 > > [965] cmdreg=0x0106, statreg=0x0010, cachelnsz=8 (dwords) > > [965] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > > [965] intpin=a, irq=16 > > [965] powerspec 2 supports D0 D3 current D0 > > [965] MSI supports 8 messages, 64 bit > > [965] pci0:2:0:0: reprobing on driver added > > [965] pci3: driver added > > [965] pci6: driver added > > [965] found-> vendor=0xffff, dev=0xffff, revid=0xff > > [965] domain=0, bus=6, slot=5, func=0 > > [965] class=ff-ff-ff, hdrtype=0x00, mfdev=0 > > [965] cmdreg=0xffff, statreg=0x02b0, cachelnsz=255 (dwords) > > [965] lattimer=0xff (7650 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns) > > [965] intpin=_, irq=255 > > [965] powerspec 2 supports D0 D3 current D3 > > [965] pci0:6:5:0: reprobing on driver added > > [965] pci0:6:5:0: Transition from D3 to D0 > > > > driver don't attached > > card detected after boot as pci0:6:5:0 > > From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 10 15:23:11 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 4AAC343C for ; Thu, 10 Jan 2013 15:23:11 +0000 (UTC) (envelope-from sven@hazejager.nl) Received: from mail-qa0-f42.google.com (mail-qa0-f42.google.com [209.85.216.42]) by mx1.freebsd.org (Postfix) with ESMTP id 03F512B6 for ; Thu, 10 Jan 2013 15:23:10 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id hg5so1750588qab.1 for ; Thu, 10 Jan 2013 07:23:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=ZK+xaGIwLp6MKxRLbufkPmYlgEv7Dq7cgcuiohtafBM=; b=GkYunsO5rmdSARwq+X9Ztg/BXs9+jtnK0b1DWakxzmLFh7h00ZVkUIDpUqtQoWTYzo NsQ2GfJZuQtUTcdEiVfKdgcQERxDXg3RewDt+UGWUrn0BN2u8lllGavmiQniXOHRIvsN gK7aUAGBTWG2a3Rf7VkmoUMI9MAr+nwRDIaoY0sxbJPwEo0pRt56uXLXC6ceiHs98zyt WwH0mBx50lbD4sJ0HmLJxhOm2xLEi+NPu039nZLgIk5b+uijPDSWN+0l0ndK5fgiu6DC +XX4wpc04xRPTjtj+7QFiDzS1G3+84aDZpii8S/lhYl8czLWS13Y6YDt4891L7Sl1Xn8 eFNg== MIME-Version: 1.0 Received: by 10.224.179.75 with SMTP id bp11mr49052290qab.22.1357831389874; Thu, 10 Jan 2013 07:23:09 -0800 (PST) Received: by 10.49.104.208 with HTTP; Thu, 10 Jan 2013 07:23:09 -0800 (PST) X-Originating-IP: [212.123.177.47] In-Reply-To: References: Date: Thu, 10 Jan 2013 16:23:09 +0100 Message-ID: Subject: Re: freebsd-head and spectral scan From: Sven Hazejager To: Adrian Chadd , freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnRSHSopzNVe5geDfOmH7OWK8XVU9zNmXS66B3MZWzqeTOyIsNCdToCVwdPeY4UH7gqdbTe 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: Thu, 10 Jan 2013 15:23:11 -0000 On Wed, Jan 9, 2013 at 1:07 AM, Adrian Chadd wrote: > I hereby give you, AR9280 doing spectral + channel scanning: Much appreciated, Adrian. That is great functionality, and exactly what I was looking for. Is there a HOWTO to get this to work? I'm cranking up my buildworld cycle as we speak. Sven From owner-freebsd-wireless@FreeBSD.ORG Fri Jan 11 01:58:11 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 86C0084D; Fri, 11 Jan 2013 01:58:11 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 62A2F7C1; Fri, 11 Jan 2013 01:58:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r0B1wB60058989; Fri, 11 Jan 2013 01:58:11 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r0B1wBc4058985; Fri, 11 Jan 2013 01:58:11 GMT (envelope-from linimon) Date: Fri, 11 Jan 2013 01:58:11 GMT Message-Id: <201301110158.r0B1wBc4058985@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/175183: [iwn] iwn(4) becomes unresponsive during initial configuration 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: Fri, 11 Jan 2013 01:58:11 -0000 Old Synopsis: iwn(4) becomes unresponsive during initial configuration New Synopsis: [iwn] iwn(4) becomes unresponsive during initial configuration Responsible-Changed-From-To: freebsd-amd64->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Fri Jan 11 01:57:46 UTC 2013 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=175183 From owner-freebsd-wireless@FreeBSD.ORG Fri Jan 11 04:08:09 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 3E69B72 for ; Fri, 11 Jan 2013 04:08:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by mx1.freebsd.org (Postfix) with ESMTP id CDB75D6D for ; Fri, 11 Jan 2013 04:08:08 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id hj13so777783wib.13 for ; Thu, 10 Jan 2013 20:08:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=AYh/aHRhog7cRNZiD3FQHdVlJim5SJPdisIPyV/1qPo=; b=s6jLiMKwYjOO6kY+HWUNYXNfl9DyMJ+UtJsO4V77Pdrly0qPSS4deaIUZ+ApVyM6N/ X9NeIdaXBFe5TXsbK1+7qv3E0KdQY8e345wGvlEfXNhXxqwlzkyT2tOzTXuRSqu78jSw s7N7UUgZ9hwefPjw38hB7ZsBIfbi2wq+AkQo9ipcKmbHbHMJmFCWLtwHty1Wg37i0F9A 3ScJvzfvu1X6IEvzw+Z0rxdWz4ZUPJ8fyHvkHwc/y9Yrbn/g0gqMToOsI4yUFfz1kUjD yENxjkNOYlZlmXs1EgsUM8ikEJK/3inAVCLyDvFfuxinaPHGXsOXsMpZtld6/7+aYYKb kzMg== MIME-Version: 1.0 X-Received: by 10.180.93.133 with SMTP id cu5mr12790883wib.32.1357877287540; Thu, 10 Jan 2013 20:08:07 -0800 (PST) Received: by 10.217.57.9 with HTTP; Thu, 10 Jan 2013 20:08:07 -0800 (PST) In-Reply-To: <20130110080729.GQ1967@zxy.spb.ru> References: <20130109121613.GO1967@zxy.spb.ru> <50edf68e.ec05320a.6ea9.ffff8ee4@mx.google.com> <20130110080729.GQ1967@zxy.spb.ru> Date: Thu, 10 Jan 2013 20:08:07 -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: Fri, 11 Jan 2013 04:08:09 -0000 .. odd. Is anything else behind that PCI bridge? I can do some digging in a couple weeks; I don't have any AR9220's on me at the moment. Adrian On 10 January 2013 00:07, Slawa Olhovchenkov wrote: > On Wed, Jan 09, 2013 at 06:00:21PM -0500, Adrian Chadd wrote: > > >> Does it happen every time? > > Yes. > >> Which version of freebsd is it? > > Last -current > >> >> >> Adrian >> >> >> Sent from my Palm Pre on AT&T >> On Jan 9, 2013 7:11 AM, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote: >> >> I am try play with suspend resume and see Atheros 9220 don't return >> >> from s3 state: >> >> >> >> >> >> [833] ath0: unable to reset hardware; hal status 3 >> >> >> >> try to unload/load module: >> >> >> >> [873] ath0: detached >> >> [873] pci6: <network> at device 5.0 (no driver attached) >> >> [882] pci0: driver added >> >> [882] found-> vendor=0x8086, dev=0x266a, revid=0x04 >> >> [882] domain=0, bus=0, slot=31, func=3 >> >> [882] class=0c-05-00, hdrtype=0x00, mfdev=0 >> >> [882] cmdreg=0x0101, statreg=0x0280, cachelnsz=0 (dwords) >> >> [882] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) >> >> [882] intpin=b, irq=19 >> >> [882] pci0:0:31:3: reprobing on driver added >> >> [882] pci2: driver added >> >> [882] found-> vendor=0x14e4, dev=0x167d, revid=0x21 >> >> [882] domain=0, bus=2, slot=0, func=0 >> >> [882] class=02-00-00, hdrtype=0x00, mfdev=0 >> >> [882] cmdreg=0x0106, statreg=0x0010, cachelnsz=8 (dwords) >> >> [882] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) >> >> [882] intpin=a, irq=16 >> >> [882] powerspec 2 supports D0 D3 current D0 >> >> [882] MSI supports 8 messages, 64 bit >> >> [882] pci0:2:0:0: reprobing on driver added >> >> [882] pci3: driver added >> >> [882] pci6: driver added >> >> [882] found-> vendor=0xffff, dev=0xffff, revid=0xff >> >> [882] domain=0, bus=6, slot=5, func=0 >> >> [882] class=ff-ff-ff, hdrtype=0x00, mfdev=0 >> >> [882] cmdreg=0xffff, statreg=0x02b0, cachelnsz=255 (dwords) >> >> [882] lattimer=0xff (7650 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns) >> >> [882] intpin=_, irq=255 >> >> [882] powerspec 2 supports D0 D3 current D3 >> >> [882] pci0:6:5:0: reprobing on driver added >> >> [882] pci0:6:5:0: Transition from D3 to D0 >> >> [965] pci0: driver added >> >> [965] found-> vendor=0x8086, dev=0x266a, revid=0x04 >> >> [965] domain=0, bus=0, slot=31, func=3 >> >> [965] class=0c-05-00, hdrtype=0x00, mfdev=0 >> >> [965] cmdreg=0x0101, statreg=0x0280, cachelnsz=0 (dwords) >> >> [965] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) >> >> [965] intpin=b, irq=19 >> >> [965] pci0:0:31:3: reprobing on driver added >> >> [965] pci2: driver added >> >> [965] found-> vendor=0x14e4, dev=0x167d, revid=0x21 >> >> [965] domain=0, bus=2, slot=0, func=0 >> >> [965] class=02-00-00, hdrtype=0x00, mfdev=0 >> >> [965] cmdreg=0x0106, statreg=0x0010, cachelnsz=8 (dwords) >> >> [965] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) >> >> [965] intpin=a, irq=16 >> >> [965] powerspec 2 supports D0 D3 current D0 >> >> [965] MSI supports 8 messages, 64 bit >> >> [965] pci0:2:0:0: reprobing on driver added >> >> [965] pci3: driver added >> >> [965] pci6: driver added >> >> [965] found-> vendor=0xffff, dev=0xffff, revid=0xff >> >> [965] domain=0, bus=6, slot=5, func=0 >> >> [965] class=ff-ff-ff, hdrtype=0x00, mfdev=0 >> >> [965] cmdreg=0xffff, statreg=0x02b0, cachelnsz=255 (dwords) >> >> [965] lattimer=0xff (7650 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns) >> >> [965] intpin=_, irq=255 >> >> [965] powerspec 2 supports D0 D3 current D3 >> >> [965] pci0:6:5:0: reprobing on driver added >> >> [965] pci0:6:5:0: Transition from D3 to D0 >> >> >> >> driver don't attached >> >> card detected after boot as pci0:6:5:0 >> >> From owner-freebsd-wireless@FreeBSD.ORG Fri Jan 11 07:45:52 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 C0667F41 for ; Fri, 11 Jan 2013 07:45:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id 5F69F780 for ; Fri, 11 Jan 2013 07:45:51 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id hn3so844292wib.5 for ; Thu, 10 Jan 2013 23:45:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Mvsjxvp4i8RSvJcHZyqq4//ETYpWDwk4skZsInYWinE=; b=hKTzQ+KMv3h1UzXG19uZTNTif0EHmW7zmly7TV9bn8qosXdtCFiIWfyEvXyivFEwho IKK2nh4rKT2+eQoUxqFiqlel6dvK1y0FlMynX5FSIbVp6l1+MGqF4IIFrNJyBZR0agmL vGBkehzbc738l8fsO6V0H4SLcDeNvZL66l7IB5Tyi+gw5AudfYUzY9lR8eSHSJuxLYS+ vfCO0yo8XYohp3w3cdJZwCyfvEKa3HWTPVFLDcynszN53hy9rpZ2e/EjwH7WB6vT1Wft h1r+wH03uQ9yLwjt631zxJh7vD1Pq+V1G2VXkbFLDc+xfav6F6nwNiWu10O/Vqx9M0WG Ev6A== MIME-Version: 1.0 Received: by 10.180.88.40 with SMTP id bd8mr13398840wib.33.1357890351061; Thu, 10 Jan 2013 23:45:51 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Thu, 10 Jan 2013 23:45:50 -0800 (PST) In-Reply-To: References: Date: Thu, 10 Jan 2013 23:45:50 -0800 X-Google-Sender-Auth: B8BmtowXCnbnSBYrf37KpZGqEK0 Message-ID: Subject: Re: freebsd-head and spectral scan From: Adrian Chadd To: Sven Hazejager 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: Fri, 11 Jan 2013 07:45:52 -0000 i'll write up something in the next few days. Adrian On 10 January 2013 07:23, Sven Hazejager wrote: > On Wed, Jan 9, 2013 at 1:07 AM, Adrian Chadd wrote: >> I hereby give you, AR9280 doing spectral + channel scanning: > > Much appreciated, Adrian. That is great functionality, and exactly > what I was looking for. Is there a HOWTO to get this to work? I'm > cranking up my buildworld cycle as we speak. > > Sven From owner-freebsd-wireless@FreeBSD.ORG Fri Jan 11 07:47:02 2013 Return-Path: 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 3693AF6C for ; Fri, 11 Jan 2013 07:47:02 +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 C278878B for ; Fri, 11 Jan 2013 07:47:01 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1TtZOq-000LVm-OE; Fri, 11 Jan 2013 11:51:36 +0400 Date: Fri, 11 Jan 2013 11:51:36 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130111075136.GA67643@zxy.spb.ru> References: <20130109121613.GO1967@zxy.spb.ru> <50edf68e.ec05320a.6ea9.ffff8ee4@mx.google.com> <20130110080729.GQ1967@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 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" 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: Fri, 11 Jan 2013 07:47:02 -0000 On Thu, Jan 10, 2013 at 08:08:07PM -0800, Adrian Chadd wrote: > .. odd. Is anything else behind that PCI bridge? bge0@pci0:2:0:0 work fine (work after resume). fwohci0@pci0:6:6:0 report working > I can do some digging in a couple weeks; I don't have any AR9220's on > me at the moment. > > > > Adrian > > > On 10 January 2013 00:07, Slawa Olhovchenkov wrote: > > On Wed, Jan 09, 2013 at 06:00:21PM -0500, Adrian Chadd wrote: > > > > > >> Does it happen every time? > > > > Yes. > > > >> Which version of freebsd is it? > > > > Last -current > > > >> > >> > >> Adrian > >> > >> > >> Sent from my Palm Pre on AT&T > >> On Jan 9, 2013 7:11 AM, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote: > >> > >> I am try play with suspend resume and see Atheros 9220 don't return > >> > >> from s3 state: > >> > >> > >> > >> > >> > >> [833] ath0: unable to reset hardware; hal status 3 > >> > >> > >> > >> try to unload/load module: > >> > >> > >> > >> [873] ath0: detached > >> > >> [873] pci6: <network> at device 5.0 (no driver attached) > >> > >> [882] pci0: driver added > >> > >> [882] found-> vendor=0x8086, dev=0x266a, revid=0x04 > >> > >> [882] domain=0, bus=0, slot=31, func=3 > >> > >> [882] class=0c-05-00, hdrtype=0x00, mfdev=0 > >> > >> [882] cmdreg=0x0101, statreg=0x0280, cachelnsz=0 (dwords) > >> > >> [882] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > >> > >> [882] intpin=b, irq=19 > >> > >> [882] pci0:0:31:3: reprobing on driver added > >> > >> [882] pci2: driver added > >> > >> [882] found-> vendor=0x14e4, dev=0x167d, revid=0x21 > >> > >> [882] domain=0, bus=2, slot=0, func=0 > >> > >> [882] class=02-00-00, hdrtype=0x00, mfdev=0 > >> > >> [882] cmdreg=0x0106, statreg=0x0010, cachelnsz=8 (dwords) > >> > >> [882] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > >> > >> [882] intpin=a, irq=16 > >> > >> [882] powerspec 2 supports D0 D3 current D0 > >> > >> [882] MSI supports 8 messages, 64 bit > >> > >> [882] pci0:2:0:0: reprobing on driver added > >> > >> [882] pci3: driver added > >> > >> [882] pci6: driver added > >> > >> [882] found-> vendor=0xffff, dev=0xffff, revid=0xff > >> > >> [882] domain=0, bus=6, slot=5, func=0 > >> > >> [882] class=ff-ff-ff, hdrtype=0x00, mfdev=0 > >> > >> [882] cmdreg=0xffff, statreg=0x02b0, cachelnsz=255 (dwords) > >> > >> [882] lattimer=0xff (7650 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns) > >> > >> [882] intpin=_, irq=255 > >> > >> [882] powerspec 2 supports D0 D3 current D3 > >> > >> [882] pci0:6:5:0: reprobing on driver added > >> > >> [882] pci0:6:5:0: Transition from D3 to D0 > >> > >> [965] pci0: driver added > >> > >> [965] found-> vendor=0x8086, dev=0x266a, revid=0x04 > >> > >> [965] domain=0, bus=0, slot=31, func=3 > >> > >> [965] class=0c-05-00, hdrtype=0x00, mfdev=0 > >> > >> [965] cmdreg=0x0101, statreg=0x0280, cachelnsz=0 (dwords) > >> > >> [965] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > >> > >> [965] intpin=b, irq=19 > >> > >> [965] pci0:0:31:3: reprobing on driver added > >> > >> [965] pci2: driver added > >> > >> [965] found-> vendor=0x14e4, dev=0x167d, revid=0x21 > >> > >> [965] domain=0, bus=2, slot=0, func=0 > >> > >> [965] class=02-00-00, hdrtype=0x00, mfdev=0 > >> > >> [965] cmdreg=0x0106, statreg=0x0010, cachelnsz=8 (dwords) > >> > >> [965] lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > >> > >> [965] intpin=a, irq=16 > >> > >> [965] powerspec 2 supports D0 D3 current D0 > >> > >> [965] MSI supports 8 messages, 64 bit > >> > >> [965] pci0:2:0:0: reprobing on driver added > >> > >> [965] pci3: driver added > >> > >> [965] pci6: driver added > >> > >> [965] found-> vendor=0xffff, dev=0xffff, revid=0xff > >> > >> [965] domain=0, bus=6, slot=5, func=0 > >> > >> [965] class=ff-ff-ff, hdrtype=0x00, mfdev=0 > >> > >> [965] cmdreg=0xffff, statreg=0x02b0, cachelnsz=255 (dwords) > >> > >> [965] lattimer=0xff (7650 ns), mingnt=0xff (63750 ns), maxlat=0xff (63750 ns) > >> > >> [965] intpin=_, irq=255 > >> > >> [965] powerspec 2 supports D0 D3 current D3 > >> > >> [965] pci0:6:5:0: reprobing on driver added > >> > >> [965] pci0:6:5:0: Transition from D3 to D0 > >> > >> > >> > >> driver don't attached > >> > >> card detected after boot as pci0:6:5:0 > >> > >> From owner-freebsd-wireless@FreeBSD.ORG Fri Jan 11 22:19:45 2013 Return-Path: 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 D37DFEE0 for ; Fri, 11 Jan 2013 22:19:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by mx1.freebsd.org (Postfix) with ESMTP id 59A5A69B for ; Fri, 11 Jan 2013 22:19:44 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hq4so146078wib.1 for ; Fri, 11 Jan 2013 14:19: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=UGXVae2hnQpw5Yc8Pyjth/b7+4XjsfJ15+1dG4y4Bys=; b=J564oJJZcoTCYjfrcqeo/MppB82cuLo1fJCmv5rNMJx2/R/7m63I8ETfTfl4KbYsAl rXnCmkkD3lANAi8+QoR0YVYwCNm697niUdIY5OCUXKOawJHDuIW+uwXMAmZ+PbtPfP03 nSjF4l8fwbT2GZk8CXn3/FA6LWcIq4nPcSqFuxamqnC8vaTBJ3wq58jR9xixAmYeW1ir Teh4VJekFibtZIUcPOt5uq/pFHmJzFLSELYggfzhV4K2kyGGoVPMVHDqI7qKS/fKr9fx uKYwkxKIK/EkVh+sOVIBtlPs2RC+BMY92sTnJtjWmQBJMUgqYABrTZWetqzNQDflEdo0 mvDA== MIME-Version: 1.0 Received: by 10.180.100.163 with SMTP id ez3mr651278wib.32.1357942778699; Fri, 11 Jan 2013 14:19:38 -0800 (PST) Received: by 10.217.57.9 with HTTP; Fri, 11 Jan 2013 14:19:38 -0800 (PST) In-Reply-To: <20130111075136.GA67643@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> Date: Fri, 11 Jan 2013 14:19: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" 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: Fri, 11 Jan 2013 22:19:45 -0000 .. so there's no _specific_ code being run when it goes to sleep or comes back from sleep for the 11n PCI NICs (AR5416, AR9160, AR9220, AR9227..) .. there's some code to tinker with the internal reset line(s) that force the hardware to re-initialise, but that's not appropriate for you. The problem here is: * it probe/attches fine; * you go to sleep; * you come back from sleep; * the PCI registers seem to be all 0xffffffff; which means the slot or the card is entirely asleep. So it's not something I can do when the NIC comes back - there's likely something that needs to happen to the PCI interface inside the AR9220 before you put the chip to sleep. And I don't (yet) have anything like that in the driver(s) that I've seen internally. But we need to first eliminate that it's the specific slot in question.. does Linux work right? adrian From owner-freebsd-wireless@FreeBSD.ORG Fri Jan 11 22:55:54 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 41D078CA for ; Fri, 11 Jan 2013 22:55:54 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f169.google.com (mail-we0-f169.google.com [74.125.82.169]) by mx1.freebsd.org (Postfix) with ESMTP id C8667818 for ; Fri, 11 Jan 2013 22:55:53 +0000 (UTC) Received: by mail-we0-f169.google.com with SMTP id t49so1123233wey.0 for ; Fri, 11 Jan 2013 14:55:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=tBVESbCS4xCm6PIukBhBigTYOqMEzLQrLz/po3YUiEQ=; b=R5umWuUuuNNdfFjUHdr985txBx4pAQo7CbqEnxYlqoi1NYIE6nztUGYEilx0R+GqJm tstqQ182XnnD9KoOv7Q0JMcoLrG61ucTi7a50zt7CLXqf2xDfod0GXQgnSidTyuHWXx4 FMvFOWfe+MUf2k2LLWPsFJ/Q7d6Nv8r4AEbV7dpXuQoB6Pc6Ha5GGLXbRtppfvtxsbfq OeLFvvrJqrKOYmxxdiknW5DOqteqZp0nqfdou2WUTvfPjsEmV7jIoqqoLs4fNU5gkA7Y SAj9QYQPHntSLGMl1vkTJ0D4UHrouNUZywZvZjO8DK6ry7ynb7lShLXtrMa5XySA9Jsp Iu3w== MIME-Version: 1.0 Received: by 10.194.179.34 with SMTP id dd2mr123677507wjc.1.1357944947202; Fri, 11 Jan 2013 14:55:47 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Fri, 11 Jan 2013 14:55:47 -0800 (PST) In-Reply-To: References: Date: Fri, 11 Jan 2013 14:55:47 -0800 X-Google-Sender-Auth: 1F7o25c1SOCHgcOP76Jlq3xAOE4 Message-ID: Subject: Re: Debugging Stalls with ath(4) From: Adrian Chadd To: Andrew Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: Fri, 11 Jan 2013 22:55:54 -0000 ... oh this is kind of strange. Hm, it's interesting that it's delaying that much; I wonder if the air is really busy and the transmitter just can't squeeze a frame out into the air. How close is it? What's the RSSI? adrian On 8 January 2013 15:50, Andrew wrote: > Hi, > > I just installed a TP-Link TL-WN851ND PCI wireless card into my 9.1-STABL= E (r244942) box. It shows up in dmesg as Atheros 9287 mac 384.2 RF5133. > > I am running it in hostap mode, 11g. Things seem to work OK but there are= occasionally stalls in traffic across the network. e.g. > > PING 10.0.0.1 (10.0.0.1): 56 data bytes > 64 bytes from 10.0.0.1: icmp_seq=3D0 ttl=3D64 time=3D13.134 ms > 64 bytes from 10.0.0.1: icmp_seq=3D1 ttl=3D64 time=3D77.776 ms > 64 bytes from 10.0.0.1: icmp_seq=3D2 ttl=3D64 time=3D246.675 ms > Request timeout for icmp_seq 3 > 64 bytes from 10.0.0.1: icmp_seq=3D3 ttl=3D64 time=3D1037.327 ms > 64 bytes from 10.0.0.1: icmp_seq=3D4 ttl=3D64 time=3D37.481 ms > > --- 10.0.0.1 ping statistics --- > 5 packets transmitted, 5 packets received, 0.0% packet loss > round-trip min/avg/max/stddev =3D 13.134/282.479/1037.327/386.148 ms > > I was wondering how I would go about debugging the issue? > > I have been playing with wlandebug and I can see that the client I am tes= ting with (though it doesn't appear to be client specific) is listed as goi= ng in and out of PS mode once or twice a second. Not sure that that is a pr= oblem. Using "wlandebug rate" I see: > > Jan 9 00:45:25 sanna kernel: wlan0: [00:17:f2:e9:04:b0] ath_rate_tx_comp= lete: size 1600 (1167 bytes) OK rate/try 48 Mb /0/1 > Jan 9 00:45:25 sanna kernel: wlan0: [00:17:f2:e9:04:b0] ath_rate_tx_comp= lete: size 1600 (1554 bytes) OK rate/try 48 Mb /0/1 > Jan 9 00:45:25 sanna kernel: wlan0: [00:17:f2:e9:04:b0] ath_rate_tx_comp= lete: size 1600 (1554 bytes) OK rate/try 48 Mb /0/1 > Jan 9 00:45:25 sanna kernel: wlan0: [7c:c5:37:6d:4c:7e] ath_rate_tx_comp= lete: size 250 (30 bytes) FAIL rate/try 1 Mb /0/7 > Jan 9 00:45:25 sanna kernel: wlan0: [00:17:f2:e9:04:b0] ath_rate_tx_comp= lete: size 250 (106 bytes) OK rate/try 11 Mb /0/1 > Jan 9 00:45:25 sanna kernel: wlan0: [00:17:f2:e9:04:b0] ath_rate_tx_comp= lete: size 250 (122 bytes) OK rate/try 11 Mb /0/1 > Jan 9 00:45:26 sanna kernel: wlan0: [00:17:f2:e9:04:b0] ath_rate_tx_comp= lete: size 250 (138 bytes) OK rate/try 11 Mb /0/1 > Jan 9 00:45:26 sanna kernel: wlan0: [00:23:14:98:15:b4] ath_rate_findrat= e: size 250 switch rate 48 (1129/690) -> 54 (736/682) after 2 packets mrr 0 > Jan 9 00:45:26 sanna kernel: wlan0: [64:70:02:f0:c8:03] ath_rate_tx_comp= lete: size 250 FAIL rate/try 0/5 no rates yet > Jan 9 00:45:26 sanna kernel: wlan0: [00:17:f2:e9:04:b0] ath_rate_tx_comp= lete: size 250 (94 bytes) OK rate/try 11 Mb /0/1 > Jan 9 00:45:26 sanna last message repeated 2 times > Jan 9 00:45:26 sanna kernel: wlan0: [00:23:14:98:15:b4] ath_rate_tx_comp= lete: size 250 (163 bytes) OK rate/try 54 Mb /0/2 > Jan 9 00:45:26 sanna kernel: wlan0: [00:17:f2:e9:04:b0] ath_rate_tx_comp= lete: size 250 (137 bytes) OK rate/try 11 Mb /0/1 > > Given the proximity of the clients and the FreeBSD box I would have expec= ted it to not have had any trouble maintaing a high connection rate - but p= erhaps this is a symptom of the stalls. > > Can anyone suggest where to go from here? > > Thanks, > > Andrew > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 00:00:44 2013 Return-Path: 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 86704F59 for ; Sat, 12 Jan 2013 00:00:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49]) by mx1.freebsd.org (Postfix) with ESMTP id 26422A76 for ; Sat, 12 Jan 2013 00:00:43 +0000 (UTC) Received: by mail-wg0-f49.google.com with SMTP id 15so1128082wgd.16 for ; Fri, 11 Jan 2013 16:00:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UZMYLWtg45XCK72IjJBsFQ+nYhUNv0GxBmTrCaYyP7U=; b=PAHrR1ixt/ss64ibeYQhhXv5TMN7MQGb9ee3bimX5nseYvgJNP+qEneMaDEElbx1dC sYGGDEPLMDBtX4naKHNYbyLp8LqinA9fDa5qL29aMrzgJJWbYyDVhZcWRAOOqVM+KfSC tYCRb1m9Z+V9BuIZ4ypiB8nsJYZKvtDD6KB5MyD0/8L2mRDmA8Gg/vzns8TVJ4KTH4bC K1AT5tg5NMPsu7kJHk/Y+8W9EuKWTdvrysNQIcaDhIQG931Jpa7Vlya4mX7FxJLzXJ8e g5EBAjjW+CDFOeU9wdfptTCzIRADxcROrz7fmCCL0zQsDOT7d/wUWu0COlMm+SScHVYN Mfog== MIME-Version: 1.0 X-Received: by 10.180.33.44 with SMTP id o12mr1472946wii.28.1357948836917; Fri, 11 Jan 2013 16:00:36 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Fri, 11 Jan 2013 16:00:36 -0800 (PST) In-Reply-To: References: Date: Fri, 11 Jan 2013 16:00:36 -0800 X-Google-Sender-Auth: DuHA-UK_Lt6xYeuz9BDvxDtYKcc Message-ID: Subject: Re: Debugging Stalls with ath(4) From: Adrian Chadd To: Andrew 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 00:00:44 -0000 .. ok, so reading about this a bit more. Going in and out of power save state could be it. Having it wait for a second is possible when you're in power save, because it's quite possible that the device is _in_ power save state for that long. Enable power state debugging in net80211 and see what's happening. You'll see it come in and out of power save, as well as it queuing up frames (and if the node power save queue overflows.) It'll also log whether it receives ps-poll frames (which I know handling of is broken in various ways in -HEAD and will be for a few more weeks) or whether it's just coming in and out of power save frames. Thanks, Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 07:53:49 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.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 314BBD12; Sat, 12 Jan 2013 07:53:49 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 09A509B2; Sat, 12 Jan 2013 07:53:49 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r0C7rmxd000545; Sat, 12 Jan 2013 07:53:48 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r0C7rmIZ000541; Sat, 12 Jan 2013 07:53:48 GMT (envelope-from linimon) Date: Sat, 12 Jan 2013 07:53:48 GMT Message-Id: <201301120753.r0C7rmIZ000541@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/175227: [ath] beacon timers aren't necessarily reprogrammed after a chip reset 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 07:53:49 -0000 Synopsis: [ath] beacon timers aren't necessarily reprogrammed after a chip reset Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Sat Jan 12 07:53:39 UTC 2013 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=175227 From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 10:48:10 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 85324B84 for ; Sat, 12 Jan 2013 10:48:10 +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 362ABFA8 for ; Sat, 12 Jan 2013 10:48:09 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Ttyhh-0007Wt-8b; Sat, 12 Jan 2013 14:52:45 +0400 Date: Sat, 12 Jan 2013 14:52:45 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130112105245.GF67643@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 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" 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 10:48:10 -0000 On Fri, Jan 11, 2013 at 02:19:38PM -0800, Adrian Chadd wrote: > .. so there's no _specific_ code being run when it goes to sleep or > comes back from sleep for the 11n PCI NICs (AR5416, AR9160, AR9220, > AR9227..) .. there's some code to tinker with the internal reset > line(s) that force the hardware to re-initialise, but that's not > appropriate for you. > > The problem here is: > > * it probe/attches fine; > * you go to sleep; > * you come back from sleep; > * the PCI registers seem to be all 0xffffffff; which means the slot or > the card is entirely asleep. Yes. > So it's not something I can do when the NIC comes back - there's > likely something that needs to happen to the PCI interface inside the > AR9220 before you put the chip to sleep. And I don't (yet) have > anything like that in the driver(s) that I've seen internally. May be need to do something in firmware code? > But we need to first eliminate that it's the specific slot in > question.. does Linux work right? I can't try linux -- no space to install. Now I try Windows XP and under windows don't work after resume also, strange. But I don't sure about rigth driver -- card vendor is TP-Link, driver is just atheros driver. Before installed this card in this slot was installed intel wifi, need to test with intel card and windows? From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 15:27:09 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 D66579E for ; Sat, 12 Jan 2013 15:27:09 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f47.google.com (mail-wg0-f47.google.com [74.125.82.47]) by mx1.freebsd.org (Postfix) with ESMTP id 62C57C3F for ; Sat, 12 Jan 2013 15:27:08 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id dq11so1332758wgb.14 for ; Sat, 12 Jan 2013 07:27:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=RNKPf3sKEOwcVoVUXRpzafe9lkGPVlEosV5yVPiu8cE=; b=wiKZwM1GvmViKSAcLHv289TxJ8hjRtiFgGnFRbKv24324UUKklBVTsrZGjpf2Nx/MK nEuUyQjLnDz7f2E6ZS6cWXf1p/d9mlI/hXws5ednnmDC4ILeP/iuw59eFMf9VEMrZDCW GtQKhQbhbkyahu2t3uc4iDOc2t0R38bS7OSzriGAwZuEp2YDdFzxBiIDPS18AONMYnxU yFYMC1gYLfJdjeTTkmuqNOA8Z9fZvIskF/2AY85SVEr0kwlk3f3L4k18UQdNkSVn+NWd GAIDi3pPPOBHAMCLnS7aFXexYRFm6IHNgDozXt2ZoalyEIkoVoOG3IeVyAONqhyesnpj XXJw== MIME-Version: 1.0 X-Received: by 10.180.93.133 with SMTP id cu5mr4253208wib.32.1358004422648; Sat, 12 Jan 2013 07:27:02 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sat, 12 Jan 2013 07:27:02 -0800 (PST) In-Reply-To: <20130112105245.GF67643@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> Date: Sat, 12 Jan 2013 07:27:02 -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 15:27:09 -0000 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? Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 15:39:29 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 DD40B4AA for ; Sat, 12 Jan 2013 15:39:29 +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 9CBB3D53 for ; Sat, 12 Jan 2013 15:39:29 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Tu3Fc-0008m5-IU; Sat, 12 Jan 2013 19:44:04 +0400 Date: Sat, 12 Jan 2013 19:44:04 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130112154404.GH67643@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 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" 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 15:39:29 -0000 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. From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 15:52:27 2013 Return-Path: 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 6E93FA63 for ; Sat, 12 Jan 2013 15:52:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by mx1.freebsd.org (Postfix) with ESMTP id D93D7DDA for ; Sat, 12 Jan 2013 15:52:26 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id hm11so428509wib.2 for ; Sat, 12 Jan 2013 07:52:20 -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=jILWEkW07gOGZJJgxnQMhfypQ7vG0D4OWx46T86gFcs=; b=A2N0ND+8MxFjhEIEOl/WS7JJZoA16H9agT5stBQZU8WaXBlbJ9wXrCi5AlXMdq3NDJ ke3KbR74ZsMc4vC7ohttoRs1NGc09B+oJuPuV2aFhKB2JKV/MKptrdz+vI31e5jO8z/F /N1GI2SCau3rW7iOvgldallSfK7kVb1AWRKW9BTTeVlnRyiwXYYwTKiYIuBnOahJOL1s t8DMJ2IuqGyA2nvFw9qx59Uy3ducoHliTKX19gRc+NFQg9gVf61An/eqGplflgY/1U+o wp+VOcWPfYl7HpEJM4tZTOQ9IjbPmnmRtc79GqJ407KUoUHQtD/wXEP7kbxwS3SB7Zzf 2+qw== MIME-Version: 1.0 Received: by 10.194.179.34 with SMTP id dd2mr126945333wjc.1.1358005940081; Sat, 12 Jan 2013 07:52:20 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sat, 12 Jan 2013 07:52:19 -0800 (PST) In-Reply-To: <20130112154404.GH67643@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> Date: Sat, 12 Jan 2013 07:52:19 -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 15:52:27 -0000 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. Thanks, 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. From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 16:24:15 2013 Return-Path: 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 CCBBEA28 for ; Sat, 12 Jan 2013 16:24:15 +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 6AE37EF3 for ; Sat, 12 Jan 2013 16:24:15 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Tu3wx-00096S-IF; Sat, 12 Jan 2013 20:28:51 +0400 Date: Sat, 12 Jan 2013 20:28:51 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 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" 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:24:15 -0000 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. 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. From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 16:32:36 2013 Return-Path: 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 D557F105 for ; Sat, 12 Jan 2013 16:32:36 +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 6F8BEF5E for ; Sat, 12 Jan 2013 16:32:36 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Tu452-0009JV-Fd; Sat, 12 Jan 2013 20:37:12 +0400 Date: Sat, 12 Jan 2013 20:37:12 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130112163712.GJ67643@zxy.spb.ru> References: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 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" 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:32:36 -0000 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' > 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. From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 16:38:57 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 5EC37211 for ; Sat, 12 Jan 2013 16:38:57 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by mx1.freebsd.org (Postfix) with ESMTP id D2BECF8A for ; Sat, 12 Jan 2013 16:38:56 +0000 (UTC) Received: by mail-wi0-f173.google.com with SMTP id hn17so443069wib.6 for ; Sat, 12 Jan 2013 08:38:49 -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=1ZMXlscPev/Z5S6WszMEeevHC99c13c16tG5sBxwWWo=; b=HexK6BMY7bxW5BhztXAIc0Cl27hNGOF+zwIy7f9tA9mnFhlztKGA4IUUfoPfqj9NSO eM979W5qUI8gNKrLCHq8gOYtpFTRYtQYA5jDWmkNQfKcYEfsdurEJ2Edj4oSphnGgj0X 8o+3MGWPlpmKgw66RvWX5vWD8ECiGpZXclsMJYKWr8a8RW4gs+uISQLJ3ivHaMGUtaPA Cebxqpuk+C5u16tAoJ16WgKg6SBi9qRf8mAcgA8wCibwlViq7vmz7kPG7IHALen96Gk3 DHsc0jUQCeE2Qgrk5F9WLpwZHPhe70lRiGOdiicGShN5ChTCDyXpQVobovaxMxREhEAr VQmg== MIME-Version: 1.0 Received: by 10.180.88.40 with SMTP id bd8mr4480546wib.33.1358008729754; Sat, 12 Jan 2013 08:38:49 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sat, 12 Jan 2013 08:38:49 -0800 (PST) In-Reply-To: <20130112163712.GJ67643@zxy.spb.ru> References: <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> <20130112163712.GJ67643@zxy.spb.ru> Date: Sat, 12 Jan 2013 08:38:49 -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:38:57 -0000 On 12 January 2013 08:37, Slawa Olhovchenkov 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... Adrian From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 16:48:00 2013 Return-Path: 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 BA9A7308 for ; Sat, 12 Jan 2013 16:48:00 +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 78779FC4 for ; Sat, 12 Jan 2013 16:48:00 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Tu4Jv-0009MW-61; Sat, 12 Jan 2013 20:52:35 +0400 Date: Sat, 12 Jan 2013 20:52:35 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130112165235.GK67643@zxy.spb.ru> References: <20130111075136.GA67643@zxy.spb.ru> <20130112105245.GF67643@zxy.spb.ru> <20130112154404.GH67643@zxy.spb.ru> <20130112162851.GI67643@zxy.spb.ru> <20130112163712.GJ67643@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 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" 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:48:00 -0000 On Sat, Jan 12, 2013 at 08:38:49AM -0800, Adrian Chadd wrote: > On 12 January 2013 08:37, Slawa Olhovchenkov 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... From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 16:51:00 2013 Return-Path: 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 3884E337 for ; Sat, 12 Jan 2013 16:51:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by mx1.freebsd.org (Postfix) with ESMTP id 96A46FD7 for ; Sat, 12 Jan 2013 16:50:59 +0000 (UTC) Received: by mail-wg0-f44.google.com with SMTP id dr12so1289899wgb.23 for ; Sat, 12 Jan 2013 08:50:58 -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=L94u00YGm7mUDLSy20BnV3ciIMK3kcCjh246XMCPPuY=; b=faZPE8ECyLowH+yl1hCtaHYxE2dxbyUAR432YCJMt0fQaqtM4Fx3Mp6zcI71erzH13 235ODHxveNpX6TCYI5YZrrBEMFQOgV5JOoU8l0mOl+wKrSZt3qZNq/6AsO1F2sbzz+QM 4e48yIPqScU5U68vfylizGRi035tjN44KX6LPYzjjXxsYwIdC3kR3crvqY5TJzxtCwMj c0ZaO67DKMSmRo2Sd2du5g0rxvi3qlGCorSPdYu2sWQqXjNUjZ7kOtoZrS2Ef7JgxZQl cMn2t92QWiQOo+voxpVTvH+i8ofGyDe0UGK4P5qxxfNmn1qAonq6dvB+TGHVowzbRSs9 hG4g== MIME-Version: 1.0 Received: by 10.180.8.130 with SMTP id r2mr4677667wia.28.1358009458419; Sat, 12 Jan 2013 08:50:58 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sat, 12 Jan 2013 08:50:58 -0800 (PST) In-Reply-To: <20130112165235.GK67643@zxy.spb.ru> References: <20130111075136.GA67643@zxy.spb.ru> <20130112105245.GF67643@zxy.spb.ru> <20130112154404.GH67643@zxy.spb.ru> <20130112162851.GI67643@zxy.spb.ru> <20130112163712.GJ67643@zxy.spb.ru> <20130112165235.GK67643@zxy.spb.ru> Date: Sat, 12 Jan 2013 08:50:58 -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:51:00 -0000 I don't know the first thing about ACPI, I'm sorry. Perhaps ask on the freebsd acpi list? Adrian On 12 January 2013 08:52, Slawa Olhovchenkov wrote: > On Sat, Jan 12, 2013 at 08:38:49AM -0800, Adrian Chadd wrote: > >> On 12 January 2013 08:37, Slawa Olhovchenkov 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... From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 17:02:33 2013 Return-Path: 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 DDC4B79C for ; Sat, 12 Jan 2013 17:02:33 +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 8B2ABA2 for ; Sat, 12 Jan 2013 17:02:32 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Tu4Y0-0009QS-0P; Sat, 12 Jan 2013 21:07:08 +0400 Date: Sat, 12 Jan 2013 21:07:07 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130112170707.GL67643@zxy.spb.ru> References: <20130112105245.GF67643@zxy.spb.ru> <20130112154404.GH67643@zxy.spb.ru> <20130112162851.GI67643@zxy.spb.ru> <20130112163712.GJ67643@zxy.spb.ru> <20130112165235.GK67643@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 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" 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 17:02:33 -0000 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 wrote: > > On Sat, Jan 12, 2013 at 08:38:49AM -0800, Adrian Chadd wrote: > > > >> On 12 January 2013 08:37, Slawa Olhovchenkov 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... From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 17:05:44 2013 Return-Path: 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 929557C6 for ; Sat, 12 Jan 2013 17:05:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1A596B3 for ; Sat, 12 Jan 2013 17:05:43 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id hn14so452763wib.3 for ; Sat, 12 Jan 2013 09:05:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=6aQ9gDvxtNu7gaEtqxwBP54BVNJf2ev3JhRTzL/SN+Y=; b=TKC4+a7J2egiORLdMUN+J0kSouMuxj6yla+NzzAVIDN1aXtxCbAhxQ7e8tQ53etHiB 0DmUyCRLJMunTKGDDA3j+SOCujDGqZMx3VZ4Iw/d+jdfrYeiShopZCKkRT6Xptld5daw PxTB+MSE4ppPbbmAzLqCGqYHuL/c5TFFfpzEPwtC8JAy/roQxupSz95Urm8wyKuPcKSH Ut/Z26tiw6RfVUHc5q4XFnnb0xOPalxeKvjK9idOzodYYhD4M4kreJrjOfX1ynnOfzwf hSF2PUwpmov0NU7H6mzatYsPdOy8lvJ9u5IT4YGrEzZ7u5r0rhbKXTjM8IxZljf8E+/x RakQ== MIME-Version: 1.0 X-Received: by 10.180.72.146 with SMTP id d18mr4570590wiv.33.1358010337148; Sat, 12 Jan 2013 09:05:37 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sat, 12 Jan 2013 09:05:37 -0800 (PST) In-Reply-To: <20130112170707.GL67643@zxy.spb.ru> References: <20130112105245.GF67643@zxy.spb.ru> <20130112154404.GH67643@zxy.spb.ru> <20130112162851.GI67643@zxy.spb.ru> <20130112163712.GJ67643@zxy.spb.ru> <20130112165235.GK67643@zxy.spb.ru> <20130112170707.GL67643@zxy.spb.ru> Date: Sat, 12 Jan 2013 09:05:37 -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 17:05:44 -0000 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. Adrian On 12 January 2013 09:07, Slawa Olhovchenkov 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 wrote: >> > On Sat, Jan 12, 2013 at 08:38:49AM -0800, Adrian Chadd wrote: >> > >> >> On 12 January 2013 08:37, Slawa Olhovchenkov 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... From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 17:09:01 2013 Return-Path: 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 ; 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 ; Sat, 12 Jan 2013 17:09:01 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Tu4eH-0009Rp-N5; Sat, 12 Jan 2013 21:13:37 +0400 Date: Sat, 12 Jan 2013 21:13:37 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130112171337.GM67643@zxy.spb.ru> References: <20130112154404.GH67643@zxy.spb.ru> <20130112162851.GI67643@zxy.spb.ru> <20130112163712.GJ67643@zxy.spb.ru> <20130112165235.GK67643@zxy.spb.ru> <20130112170707.GL67643@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: 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" 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 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 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 wrote: > >> > On Sat, Jan 12, 2013 at 08:38:49AM -0800, Adrian Chadd wrote: > >> > > >> >> On 12 January 2013 08:37, Slawa Olhovchenkov 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... From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 12 17:59:26 2013 Return-Path: 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 5E87A201 for ; Sat, 12 Jan 2013 17:59:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by mx1.freebsd.org (Postfix) with ESMTP id C8A01222 for ; Sat, 12 Jan 2013 17:59:25 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id hj13so467545wib.7 for ; Sat, 12 Jan 2013 09:59:19 -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=G7LcTMOOfXO6Iv92HC6UrRrt04Q244HqZ15zLpypBnw=; b=QqNOawJDJGAdsCw4HE6QC4F4aZL9WpAS1sBFjoA24RuZUiT/xyW632VjrsrcybGbxX dMCwYlqDIgnorW47ccNXJKJgucAIc6l8ZDqD5LGukBlM6rI0/IKUnvfyd86aPn4XC7Rb 2/A4Pm9FaXY/myqgW0H3nUY6nFG2l6+IImWQ2AxnWvq2fVkV7t+ksMH7NFIUO+Ikzqwd P7T3zOsDQrS6dl5HxmYfxcUFDgciwhrAqqAKboWLSKjD0KzhOWYdQ7q9H/AukJu1SrT2 bKbpfOW0527j5Y5DYfck9ndFXj3ifEqW0K9gvrKDOs2jxNxJMO9JFrKa5APxoVmIXXML 8lgQ== MIME-Version: 1.0 Received: by 10.180.8.130 with SMTP id r2mr4900836wia.28.1358013558965; Sat, 12 Jan 2013 09:59:18 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sat, 12 Jan 2013 09:59:18 -0800 (PST) In-Reply-To: <20130112171337.GM67643@zxy.spb.ru> References: <20130112154404.GH67643@zxy.spb.ru> <20130112162851.GI67643@zxy.spb.ru> <20130112163712.GJ67643@zxy.spb.ru> <20130112165235.GK67643@zxy.spb.ru> <20130112170707.GL67643@zxy.spb.ru> <20130112171337.GM67643@zxy.spb.ru> Date: Sat, 12 Jan 2013 09:59:18 -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 17:59:26 -0000 On 12 January 2013 09:13, Slawa Olhovchenkov wrote: > 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? Well, I think there's more to it than that. I could program the card, sure, but what about the PCI bus and the ACPI code that fiddles with the PCI slot. I'm not at all clued up on how PCI sleep/resume works, so I'm scratching in the dark here. I think there's some code in the windows driver to put some older cards into some very specific PCI sleep states (and force them to not enter deep deep sleep?) but I'd have to re-review it. Adrian