From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 19:22: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 15A644AF for ; Sun, 13 Jan 2013 19:22:00 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 240D3708 for ; Sun, 13 Jan 2013 19:21:58 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id r0DJLs7T022561; Mon, 14 Jan 2013 06:21:55 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 14 Jan 2013 06:21:54 +1100 (EST) From: Ian Smith To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state In-Reply-To: Message-ID: <20130114050646.O62930@sola.nimnet.asn.au> 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> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: "freebsd-wireless@freebsd.org" , Slawa Olhovchenkov X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 19:22:00 -0000 On Sat, 12 Jan 2013 09:05:37 -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. > > > > 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. And here was me thinking you were across The Whole Thing :) > > 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). Not dumb .. I don't know but suspect suspend would proceed regardless with perhaps some noise. Maybe worth doing that acpidump per recipe? > > > >> Perhaps ask on the freebsd acpi list? Good idea, or perhaps current@ ? Somewhere both bus and ACPI people congregate anyway. One could point to this thread or compact its contents into a new message, but there may be something Slawa could do before the whole acpi debug palava, which is just to: a) boot verbose, maybe with kern.msgbufsize=98304 (say) in loader.conf b) suspend then resume c) dmesg # head to post somewhere, tail for the susp/res bit. Even without any ACPI debugging enabled, there should be clues as to acpi powering down then later (trying to) resume all devices, which might indicate whether that tunnel is worth diving deeper into .. Since I'm so pleased that suspend/resume finally works without drama out of the box on my T23 at 9.1-R, I include below one such cycle from /var/log/messages. There are logged ACPI errors I don't understand about \_SB_.PCI0.PCI1.CBS[01] that don't seem to affect functionality, but you can see the ACPI and PCI view of things, and it's old and small enough a box (single CPU, with no wireless :) If it helps, Ian > >> > >> > >> 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... ======= Jan 3 04:42:05 t234ma-s2 acpi: suspend at 20130103 04:42:05 Jan 3 04:42:05 t234ma-s2 kernel: acpi_button0: sleep button pressed Jan 3 04:42:10 t234ma-s2 kernel: (ada0:ata0:0:0:0): spin-down Jan 5 00:57:52 t234ma-s2 kernel: acpi_lid0: wake_prep enabled for \_SB_.LID_ (S3) Jan 5 00:57:52 t234ma-s2 kernel: acpi_button0: wake_prep enabled for \_SB_.SLPB (S3) Jan 5 00:57:52 t234ma-s2 kernel: vga0: saving 3780 bytes of video state Jan 5 00:57:52 t234ma-s2 kernel: vga0: saving color palette Jan 5 00:57:52 t234ma-s2 kernel: pci0:1:0:0: Transition from D0 to D3 Jan 5 00:57:52 t234ma-s2 kernel: pci1: set ACPI power state D3 on \_SB_.PCI0.AGP_.VID_ Jan 5 00:57:52 t234ma-s2 kernel: uhub2: at usbus0, port 1, addr 1 (disconnected) Jan 5 00:57:52 t234ma-s2 kernel: uhub0: at usbus1, port 1, addr 1 (disconnected) Jan 5 00:57:52 t234ma-s2 kernel: uhub1: at usbus2, port 1, addr 1 (disconnected) Jan 5 00:57:52 t234ma-s2 kernel: fxp0: link state changed to DOWN Jan 5 00:57:52 t234ma-s2 kernel: pci0:2:0:0: Transition from D0 to D2 Jan 5 00:57:52 t234ma-s2 kernel: pci2: failed to set ACPI power state D2 on \_SB_.PCI0.PCI1.CBS0: AE_BAD_PARAMETER Jan 5 00:57:52 t234ma-s2 kernel: pci0:2:0:1: Transition from D0 to D2 Jan 5 00:57:52 t234ma-s2 kernel: pci2: failed to set ACPI power state D2 on \_SB_.PCI0.PCI1.CBS1: AE_BAD_PARAMETER Jan 5 00:57:52 t234ma-s2 kernel: pci0:2:8:0: Transition from D0 to D2 (resume, above kept for logging after resume despite timestamp) Jan 5 00:57:52 t234ma-s2 kernel: acpi_lid0: run_prep cleaned up for \_SB_.LID_ Jan 5 00:57:52 t234ma-s2 kernel: acpi_button0: run_prep cleaned up for \_SB_.SLPB Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.AGP_ Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.USB0 Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.USB1 Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.USB2 Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.PCI1 Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.LPC_ Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.IDE0 Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.AGP_ Jan 5 00:57:52 t234ma-s2 kernel: pci1: set ACPI power state D0 on \_SB_.PCI0.AGP_.VID_ Jan 5 00:57:52 t234ma-s2 kernel: pci0:1:0:0: Transition from D3 to D0 Jan 5 00:57:52 t234ma-s2 kernel: vgapci0: calling BIOS POST Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.PCI1 Jan 5 00:57:52 t234ma-s2 kernel: pci2: set ACPI power state D0 on \_SB_.PCI0.PCI1.CBS0 Jan 5 00:57:52 t234ma-s2 kernel: pci0:2:0:0: Transition from D2 to D0 Jan 5 00:57:52 t234ma-s2 kernel: pci2: set ACPI power state D0 on \_SB_.PCI0.PCI1.CBS1 Jan 5 00:57:52 t234ma-s2 kernel: pci0:2:0:1: Transition from D2 to D0 Jan 5 00:57:52 t234ma-s2 kernel: wakeup from sleeping state (slept 44:15:36) Jan 5 00:57:52 t234ma-s2 kernel: ata0: reset tp1 mask=03 ostat0=80 ostat1=00 Jan 5 00:57:52 t234ma-s2 kernel: ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 Jan 5 00:57:52 t234ma-s2 last message repeated 9 times (while spinning up) Jan 5 00:57:52 t234ma-s2 kernel: ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 Jan 5 00:57:52 t234ma-s2 kernel: ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 Jan 5 00:57:52 t234ma-s2 kernel: ata0: reset tp2 stat0=50 stat1=00 devices=0x1 Jan 5 00:57:52 t234ma-s2 kernel: ata1: reset tp1 mask=03 ostat0=00 ostat1=00 Jan 5 00:57:52 t234ma-s2 kernel: ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb Jan 5 00:57:52 t234ma-s2 kernel: ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 Jan 5 00:57:52 t234ma-s2 kernel: ata1: reset tp2 stat0=00 stat1=00 devices=0x10000 Jan 5 00:57:52 t234ma-s2 kernel: atkbd: the current kbd controller command byte 0047 Jan 5 00:57:52 t234ma-s2 kernel: atkbd: keyboard ID 0x54ab (2) Jan 5 00:57:52 t234ma-s2 kernel: kbdc: RESET_KBD return code:00fa Jan 5 00:57:52 t234ma-s2 kernel: kbdc: RESET_KBD status:00aa Jan 5 00:57:52 t234ma-s2 kernel: kbdc: TEST_AUX_PORT status:0000 Jan 5 00:57:52 t234ma-s2 kernel: kbdc: RESET_AUX return code:00fa Jan 5 00:57:52 t234ma-s2 kernel: kbdc: RESET_AUX status:00aa Jan 5 00:57:52 t234ma-s2 kernel: kbdc: RESET_AUX ID:0000 Jan 5 00:57:52 t234ma-s2 kernel: fxp0: link state changed to UP Jan 5 00:57:52 t234ma-s2 kernel: battery0: battery initialization start Jan 5 00:57:52 t234ma-s2 kernel: uhub0: on usbus1 Jan 5 00:57:52 t234ma-s2 kernel: uhub1: on usbus2 Jan 5 00:57:52 t234ma-s2 kernel: uhub2: on usbus0 Jan 5 00:57:52 t234ma-s2 kernel: battery0: battery initialization done, tried 1 times Jan 5 00:57:52 t234ma-s2 kernel: uhub0: 2 ports with 2 removable, self powered Jan 5 00:57:52 t234ma-s2 kernel: uhub1: 2 ports with 2 removable, self powered Jan 5 00:57:52 t234ma-s2 kernel: uhub2: 2 ports with 2 removable, self powered Jan 5 00:57:52 t234ma-s2 kernel: (ada0:ata0:0:0:0): resume Jan 5 00:57:52 t234ma-s2 kernel: fxp0: link state changed to DOWN Jan 5 00:57:52 t234ma-s2 acpi: resumed at 20130105 00:57:52 Jan 5 00:57:54 t234ma-s2 kernel: fxp0: link state changed to UP Jan 5 00:57:57 t234ma-s2 dhclient: New IP Address (fxp0): 10.1.1.3 Jan 5 00:57:57 t234ma-s2 kernel: fxp0: link state changed to DOWN Jan 5 00:57:57 t234ma-s2 dhclient: New Subnet Mask (fxp0): 255.0.0.0 Jan 5 00:57:57 t234ma-s2 dhclient: New Broadcast Address (fxp0): 10.255.255.255 Jan 5 00:57:57 t234ma-s2 dhclient: New Routers (fxp0): 10.1.1.1 Jan 5 00:57:59 t234ma-s2 kernel: fxp0: link state changed to UP ======= From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 19:25:39 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 8A4D1571 for ; Sun, 13 Jan 2013 19:25:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53]) by mx1.freebsd.org (Postfix) with ESMTP id 0BFC3746 for ; Sun, 13 Jan 2013 19:25:38 +0000 (UTC) Received: by mail-wg0-f53.google.com with SMTP id fn15so1732415wgb.32 for ; Sun, 13 Jan 2013 11:25:37 -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=L/CvhXlee89wErOWPDzH0zF0a3xuSBmM1eK0oJSntLw=; b=g+aIT+YqkNf2IuR/SQy35P7voUulv8ciInzf2y0qZkIRDhbevEZQWvDlX1Fj3u+0YL 4no6zs9vlBVWuBhAGUVBBzG9NwZuoOskhQgoRNYH2TUYfNFg4qESSXXzKTNaRGCDWqKD pfyvAs/r7cvx0MoDAi700dUHSfye/5uJdk/uVsWgLGuTNuB9TEObCd6XAJAdZ8GQnWU9 zXELTed0WEUC4iflc+gmfpZt2Gm1OINupyFF0cxuQ3Bt3uPW+REY8OyQtqii0gnXRD5g vgpDLk2v7kV43abye32AmJupxdycchh4xZM00L0ts5IftAdN/p2+a335e2rUg4bXELUs 8qCg== MIME-Version: 1.0 Received: by 10.194.109.10 with SMTP id ho10mr40953124wjb.16.1358105137521; Sun, 13 Jan 2013 11:25:37 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sun, 13 Jan 2013 11:25:37 -0800 (PST) In-Reply-To: <20130114050646.O62930@sola.nimnet.asn.au> 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> <20130114050646.O62930@sola.nimnet.asn.au> Date: Sun, 13 Jan 2013 11:25:37 -0800 Message-ID: Subject: Re: Atheros 9220 don't return from S3 state From: Adrian Chadd To: Ian Smith Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" , Slawa Olhovchenkov X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 19:25:39 -0000 The problem here is I can't easily test this. We detach and re-attach cardbus devices during suspend/resume, so although I have AR9220 mini-PCI NICs, they don't stay connected the normal way. The slot gets fully powered down and reset upon power up. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 19:32:34 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 DAD8895A for ; Sun, 13 Jan 2013 19:32:34 +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 5F4AE7A9 for ; Sun, 13 Jan 2013 19:32:34 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1TuTMk-000Hbx-7b; Sun, 13 Jan 2013 23:37:10 +0400 Date: Sun, 13 Jan 2013 23:37:10 +0400 From: Slawa Olhovchenkov To: Ian Smith Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130113193710.GP67643@zxy.spb.ru> References: <20130112162851.GI67643@zxy.spb.ru> <20130112163712.GJ67643@zxy.spb.ru> <20130112165235.GK67643@zxy.spb.ru> <20130112170707.GL67643@zxy.spb.ru> <20130114050646.O62930@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130114050646.O62930@sola.nimnet.asn.au> 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: Sun, 13 Jan 2013 19:32:34 -0000 On Mon, Jan 14, 2013 at 06:21:54AM +1100, Ian Smith wrote: > On Sat, 12 Jan 2013 09:05:37 -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. > > > > > > > > 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. > > And here was me thinking you were across The Whole Thing :) > > > > 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). > > Not dumb .. I don't know but suspect suspend would proceed regardless > with perhaps some noise. Maybe worth doing that acpidump per recipe? > > > > > > >> Perhaps ask on the freebsd acpi list? > > Good idea, or perhaps current@ ? Somewhere both bus and ACPI people > congregate anyway. One could point to this thread or compact its This is not new problem, this card in this notebook never resume. With old freebsd resume work badly with other devices. Now resume work nice (exclude this card) > contents into a new message, but there may be something Slawa could do > before the whole acpi debug palava, which is just to: > > a) boot verbose, maybe with kern.msgbufsize=98304 (say) in loader.conf > b) suspend then resume > c) dmesg # head to post somewhere, tail for the susp/res bit. I am attach this dmesg to first message to Adrian (not to list). > Even without any ACPI debugging enabled, there should be clues as to > acpi powering down then later (trying to) resume all devices, which > might indicate whether that tunnel is worth diving deeper into .. > > Since I'm so pleased that suspend/resume finally works without drama out > of the box on my T23 at 9.1-R, I include below one such cycle from > /var/log/messages. There are logged ACPI errors I don't understand > about \_SB_.PCI0.PCI1.CBS[01] that don't seem to affect functionality, > but you can see the ACPI and PCI view of things, and it's old and small > enough a box (single CPU, with no wireless :) > > If it helps, > > Ian > > > >> > > >> > > >> 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... > > ======= > Jan 3 04:42:05 t234ma-s2 acpi: suspend at 20130103 04:42:05 > Jan 3 04:42:05 t234ma-s2 kernel: acpi_button0: sleep button pressed > Jan 3 04:42:10 t234ma-s2 kernel: (ada0:ata0:0:0:0): spin-down > Jan 5 00:57:52 t234ma-s2 kernel: acpi_lid0: wake_prep enabled for \_SB_.LID_ (S3) > Jan 5 00:57:52 t234ma-s2 kernel: acpi_button0: wake_prep enabled for \_SB_.SLPB (S3) > Jan 5 00:57:52 t234ma-s2 kernel: vga0: saving 3780 bytes of video state > Jan 5 00:57:52 t234ma-s2 kernel: vga0: saving color palette > Jan 5 00:57:52 t234ma-s2 kernel: pci0:1:0:0: Transition from D0 to D3 > Jan 5 00:57:52 t234ma-s2 kernel: pci1: set ACPI power state D3 on \_SB_.PCI0.AGP_.VID_ > Jan 5 00:57:52 t234ma-s2 kernel: uhub2: at usbus0, port 1, addr 1 (disconnected) > Jan 5 00:57:52 t234ma-s2 kernel: uhub0: at usbus1, port 1, addr 1 (disconnected) > Jan 5 00:57:52 t234ma-s2 kernel: uhub1: at usbus2, port 1, addr 1 (disconnected) > Jan 5 00:57:52 t234ma-s2 kernel: fxp0: link state changed to DOWN > Jan 5 00:57:52 t234ma-s2 kernel: pci0:2:0:0: Transition from D0 to D2 > Jan 5 00:57:52 t234ma-s2 kernel: pci2: failed to set ACPI power state D2 on \_SB_.PCI0.PCI1.CBS0: AE_BAD_PARAMETER > Jan 5 00:57:52 t234ma-s2 kernel: pci0:2:0:1: Transition from D0 to D2 > Jan 5 00:57:52 t234ma-s2 kernel: pci2: failed to set ACPI power state D2 on \_SB_.PCI0.PCI1.CBS1: AE_BAD_PARAMETER > Jan 5 00:57:52 t234ma-s2 kernel: pci0:2:8:0: Transition from D0 to D2 > (resume, above kept for logging after resume despite timestamp) > Jan 5 00:57:52 t234ma-s2 kernel: acpi_lid0: run_prep cleaned up for \_SB_.LID_ > Jan 5 00:57:52 t234ma-s2 kernel: acpi_button0: run_prep cleaned up for \_SB_.SLPB > Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.AGP_ > Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.USB0 > Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.USB1 > Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.USB2 > Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.PCI1 > Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.LPC_ > Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.IDE0 > Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.AGP_ > Jan 5 00:57:52 t234ma-s2 kernel: pci1: set ACPI power state D0 on \_SB_.PCI0.AGP_.VID_ > Jan 5 00:57:52 t234ma-s2 kernel: pci0:1:0:0: Transition from D3 to D0 > Jan 5 00:57:52 t234ma-s2 kernel: vgapci0: calling BIOS POST > Jan 5 00:57:52 t234ma-s2 kernel: pci0: set ACPI power state D0 on \_SB_.PCI0.PCI1 > Jan 5 00:57:52 t234ma-s2 kernel: pci2: set ACPI power state D0 on \_SB_.PCI0.PCI1.CBS0 > Jan 5 00:57:52 t234ma-s2 kernel: pci0:2:0:0: Transition from D2 to D0 > Jan 5 00:57:52 t234ma-s2 kernel: pci2: set ACPI power state D0 on \_SB_.PCI0.PCI1.CBS1 > Jan 5 00:57:52 t234ma-s2 kernel: pci0:2:0:1: Transition from D2 to D0 > Jan 5 00:57:52 t234ma-s2 kernel: wakeup from sleeping state (slept 44:15:36) > Jan 5 00:57:52 t234ma-s2 kernel: ata0: reset tp1 mask=03 ostat0=80 ostat1=00 > Jan 5 00:57:52 t234ma-s2 kernel: ata0: stat0=0x80 err=0x80 lsb=0x80 msb=0x80 > Jan 5 00:57:52 t234ma-s2 last message repeated 9 times > (while spinning up) > Jan 5 00:57:52 t234ma-s2 kernel: ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 > Jan 5 00:57:52 t234ma-s2 kernel: ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 > Jan 5 00:57:52 t234ma-s2 kernel: ata0: reset tp2 stat0=50 stat1=00 devices=0x1 > Jan 5 00:57:52 t234ma-s2 kernel: ata1: reset tp1 mask=03 ostat0=00 ostat1=00 > Jan 5 00:57:52 t234ma-s2 kernel: ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb > Jan 5 00:57:52 t234ma-s2 kernel: ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 > Jan 5 00:57:52 t234ma-s2 kernel: ata1: reset tp2 stat0=00 stat1=00 devices=0x10000 > Jan 5 00:57:52 t234ma-s2 kernel: atkbd: the current kbd controller command byte 0047 > Jan 5 00:57:52 t234ma-s2 kernel: atkbd: keyboard ID 0x54ab (2) > Jan 5 00:57:52 t234ma-s2 kernel: kbdc: RESET_KBD return code:00fa > Jan 5 00:57:52 t234ma-s2 kernel: kbdc: RESET_KBD status:00aa > Jan 5 00:57:52 t234ma-s2 kernel: kbdc: TEST_AUX_PORT status:0000 > Jan 5 00:57:52 t234ma-s2 kernel: kbdc: RESET_AUX return code:00fa > Jan 5 00:57:52 t234ma-s2 kernel: kbdc: RESET_AUX status:00aa > Jan 5 00:57:52 t234ma-s2 kernel: kbdc: RESET_AUX ID:0000 > Jan 5 00:57:52 t234ma-s2 kernel: fxp0: link state changed to UP > Jan 5 00:57:52 t234ma-s2 kernel: battery0: battery initialization start > Jan 5 00:57:52 t234ma-s2 kernel: uhub0: on usbus1 > Jan 5 00:57:52 t234ma-s2 kernel: uhub1: on usbus2 > Jan 5 00:57:52 t234ma-s2 kernel: uhub2: on usbus0 > Jan 5 00:57:52 t234ma-s2 kernel: battery0: battery initialization done, tried 1 times > Jan 5 00:57:52 t234ma-s2 kernel: uhub0: 2 ports with 2 removable, self powered > Jan 5 00:57:52 t234ma-s2 kernel: uhub1: 2 ports with 2 removable, self powered > Jan 5 00:57:52 t234ma-s2 kernel: uhub2: 2 ports with 2 removable, self powered > Jan 5 00:57:52 t234ma-s2 kernel: (ada0:ata0:0:0:0): resume > Jan 5 00:57:52 t234ma-s2 kernel: fxp0: link state changed to DOWN > Jan 5 00:57:52 t234ma-s2 acpi: resumed at 20130105 00:57:52 > Jan 5 00:57:54 t234ma-s2 kernel: fxp0: link state changed to UP > Jan 5 00:57:57 t234ma-s2 dhclient: New IP Address (fxp0): 10.1.1.3 > Jan 5 00:57:57 t234ma-s2 kernel: fxp0: link state changed to DOWN > Jan 5 00:57:57 t234ma-s2 dhclient: New Subnet Mask (fxp0): 255.0.0.0 > Jan 5 00:57:57 t234ma-s2 dhclient: New Broadcast Address (fxp0): 10.255.255.255 > Jan 5 00:57:57 t234ma-s2 dhclient: New Routers (fxp0): 10.1.1.1 > Jan 5 00:57:59 t234ma-s2 kernel: fxp0: link state changed to UP > ======= From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 19:35:56 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 D4E84A61 for ; Sun, 13 Jan 2013 19:35:56 +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 8140B7CC for ; Sun, 13 Jan 2013 19:35:56 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1TuTQ1-000Hcl-79; Sun, 13 Jan 2013 23:40:33 +0400 Date: Sun, 13 Jan 2013 23:40:33 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130113194033.GQ67643@zxy.spb.ru> References: <20130112162851.GI67643@zxy.spb.ru> <20130112163712.GJ67643@zxy.spb.ru> <20130112165235.GK67643@zxy.spb.ru> <20130112170707.GL67643@zxy.spb.ru> <20130114050646.O62930@sola.nimnet.asn.au> 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" , Ian Smith X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 19:35:56 -0000 On Sun, Jan 13, 2013 at 11:25:37AM -0800, Adrian Chadd wrote: > The problem here is I can't easily test this. We detach and re-attach > cardbus devices during suspend/resume, so although I have AR9220 > mini-PCI NICs, they don't stay connected the normal way. The slot gets > fully powered down and reset upon power up. I can touch (by my finger) this card after resume, for test temperature change. I think if slot not powered after resume temperature of card should reduced. From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 19:43:57 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 9620377 for ; Sun, 13 Jan 2013 19:43:57 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f179.google.com (mail-we0-f179.google.com [74.125.82.179]) by mx1.freebsd.org (Postfix) with ESMTP id 03AE282E for ; Sun, 13 Jan 2013 19:43:56 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id r6so1671552wey.38 for ; Sun, 13 Jan 2013 11:43:55 -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=clUCOWEsM3qOi2Fwe4O2tqiXHDXXJSw4w6HJ9EAFjmQ=; b=pfUBUQ6PhPBe9wTd3TwcmZZuh60qNAJLwVRf/SYsbquM5rai/hhCiCrBx3X1bRJVIm wki0eCbi+NlR3TXsl2RPq5Y+1+sT6J/oKXFkHz6OReTfAoGApy8eYvGOSPY4ppVEI87T ISZoOcYfOH8wvufeVs45FhXSoGwHEIpkXZ7bHTqdYDk+JQirV3e9S1SwokYf7OrZ6B7B SgCg40TZvl7sVAZoFfkxzS3V9O0BZKEcnIF4y0sIcqtZSIxdDUaQsphFi1faiaT0VlLE ILAkUJUikmEacAR357S7gW3dXCw5jq4I1A8WZ6Nxzdq05oGwlF2Iul0H+OuZK6qSEJQP NKRA== MIME-Version: 1.0 Received: by 10.180.88.40 with SMTP id bd8mr8702859wib.33.1358106235912; Sun, 13 Jan 2013 11:43:55 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sun, 13 Jan 2013 11:43:55 -0800 (PST) In-Reply-To: <20130113194033.GQ67643@zxy.spb.ru> References: <20130112162851.GI67643@zxy.spb.ru> <20130112163712.GJ67643@zxy.spb.ru> <20130112165235.GK67643@zxy.spb.ru> <20130112170707.GL67643@zxy.spb.ru> <20130114050646.O62930@sola.nimnet.asn.au> <20130113194033.GQ67643@zxy.spb.ru> Date: Sun, 13 Jan 2013 11:43:55 -0800 Message-ID: Subject: Re: Atheros 9220 don't return from S3 state From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" , Ian Smith X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 19:43:57 -0000 Right. That should be a good indication. It's a shame you can't just get a multimeter and measure the relevant pins. :) Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 19:45:45 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 51D1BC6 for ; Sun, 13 Jan 2013 19:45:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id E13D583D for ; Sun, 13 Jan 2013 19:45:44 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id o1so845497wic.11 for ; Sun, 13 Jan 2013 11:45:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9sbkDTs+aCo7FLo5njTP9fN2bZGdoE6UacPZhzSdpZA=; b=EwaeThR/YZJYq3HtJWMGhCkRWB5TUOlG4pmmU70Wc+Ahnz4eDcs0d4aBAojMl60oaZ usV8dbuh+dBf4Xwzx49f9C/2CFhAQiT6G1UXp8Ftssl8qiQC4+lEn7dzXLOnfxYOKvjH hqPT3Fm+AUMjvBTl99PANuOqDkeukhbQOoG2k+faoJExQ7YgZsrSRHnhQ6KZ/vRpxcwV FHhbIWSk7YO+SPWJOOz8hZ1rJPA/j7uOLQ++iFQVX/qmSjF/rraj/Qk7xSHxg73gsH+M NdJtq32/sLEIaDkL7RCei8uLYlBxdGvzXS8I7yCIEbboi/XXp2T0UwZjiWQHyzAY4ZlU KrbQ== MIME-Version: 1.0 Received: by 10.194.179.34 with SMTP id dd2mr131538103wjc.1.1358106338390; Sun, 13 Jan 2013 11:45:38 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sun, 13 Jan 2013 11:45:38 -0800 (PST) In-Reply-To: References: <20130112162851.GI67643@zxy.spb.ru> <20130112163712.GJ67643@zxy.spb.ru> <20130112165235.GK67643@zxy.spb.ru> <20130112170707.GL67643@zxy.spb.ru> <20130114050646.O62930@sola.nimnet.asn.au> <20130113194033.GQ67643@zxy.spb.ru> Date: Sun, 13 Jan 2013 11:45:38 -0800 Message-ID: Subject: Re: Atheros 9220 don't return from S3 state From: Adrian Chadd To: Slawa Olhovchenkov Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" , Ian Smith X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 19:45:45 -0000 .. and it may not be the slot power. It could also be the PCI bridge (re) programming. It needs to have the right BAR and such programmed into it, or it won't "route" things correctly to child slots. I had this problem with cardbus a few months ago. After a resume, not all of the relevant PCI config space registers were being restored.. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 20:00:14 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 50854266; Sun, 13 Jan 2013 20:00:14 +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 00C3B8AE; Sun, 13 Jan 2013 20:00:13 +0000 (UTC) Received: from [10.0.0.16] (77-64-237-200.dynamic.primacom.net [77.64.237.200]) by starbug.ugh.net.au (Postfix) with ESMTPSA id D197E386C57; Mon, 14 Jan 2013 08:30:00 +1100 (EST) Subject: Re: Debugging Stalls with ath(4) Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Andrew In-Reply-To: Date: Sun, 13 Jan 2013 20:59:52 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Adrian Chadd X-Mailer: Apple Mail (2.1085) 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: Sun, 13 Jan 2013 20:00:14 -0000 On 12 Jan 2013, at 01:00, Adrian Chadd wrote: > 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.) Hi Adrian, I've been away for the weekend and just got back home planning to try = this out but the problem seems to have cleared itself up whilst I was = out. I'm not sure how, or if it is likely to come back. I have just = powered on the FreeBSD box after a few days switched off - but I had = earlier rebooted it several times which didn't clear the problem so I'm = not sure its that. I have tested from multiple clients. I guess all I can do now is wait and see if the problem reoccurs and if = so try and determine the triggering factor. Maybe a specific client = being associated? I don't see anywhere near the number of power save = on/off messages that I was before. Thanks for your help. I'll repost if I get a reproduction. If there is = anything you would like me to try anyway to aid debugging I'm happy to = do it. Thanks again, Andrew= From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 20:02:47 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 28C5F2BB for ; Sun, 13 Jan 2013 20:02:47 +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 D7EE38DD for ; Sun, 13 Jan 2013 20:02:46 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1TuTpx-000HkT-U9; Mon, 14 Jan 2013 00:07:21 +0400 Date: Mon, 14 Jan 2013 00:07:21 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130113200721.GR67643@zxy.spb.ru> References: <20130112163712.GJ67643@zxy.spb.ru> <20130112165235.GK67643@zxy.spb.ru> <20130112170707.GL67643@zxy.spb.ru> <20130114050646.O62930@sola.nimnet.asn.au> <20130113194033.GQ67643@zxy.spb.ru> 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" , Ian Smith X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 20:02:47 -0000 On Sun, Jan 13, 2013 at 11:43:55AM -0800, Adrian Chadd wrote: > Right. That should be a good indication. After 10 min card still hot. > It's a shame you can't just get a multimeter and measure the relevant pins. :) I am can get multimeter but I can't get so thin probe :) From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 20:19:23 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 E4D34977 for ; Sun, 13 Jan 2013 20:19:23 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f176.google.com (mail-we0-f176.google.com [74.125.82.176]) by mx1.freebsd.org (Postfix) with ESMTP id 526E69A1 for ; Sun, 13 Jan 2013 20:19:22 +0000 (UTC) Received: by mail-we0-f176.google.com with SMTP id r5so1668626wey.21 for ; Sun, 13 Jan 2013 12:19: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=AnLQ3Q9POixgUQJ53z7uZWltADaBhsUaj7OjiPtsr88=; b=uHR8LZDD9nqpco506rOWeqDSJq0mnAKxyA1d0dFBzEZfrNYme0j1EFMk+dR8dQ8ACW wcjxA1Iomn3276UAMtZ+2t4y8U1IoYymhvewpBRPccgi8PvQ3QaaBWZeTj2dNdVnvweS M/5my+4FhmnFJ7zgf41AqAu/XOunNvjhiTpYivpWpjuauxr3ZBl5/A+J4jNLCOt3zGAi /WNPC/WMTgMPwkhoWIqNoklyj2NVi3SK0zxO5tG2QN8Jy8/M5GabRbotRLSMTWzJM0Ge xmdXBL4Vj/ewt0ITi0GLmb9od+CfqQhYY3ktIlxXVfCVZQY9kBY5awYKvvXJTRjZYja0 UU+w== MIME-Version: 1.0 Received: by 10.194.179.34 with SMTP id dd2mr131642622wjc.1.1358108362175; Sun, 13 Jan 2013 12:19:22 -0800 (PST) Received: by 10.217.57.9 with HTTP; Sun, 13 Jan 2013 12:19:22 -0800 (PST) In-Reply-To: <20130113200721.GR67643@zxy.spb.ru> References: <20130112163712.GJ67643@zxy.spb.ru> <20130112165235.GK67643@zxy.spb.ru> <20130112170707.GL67643@zxy.spb.ru> <20130114050646.O62930@sola.nimnet.asn.au> <20130113194033.GQ67643@zxy.spb.ru> <20130113200721.GR67643@zxy.spb.ru> Date: Sun, 13 Jan 2013 12:19: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" , Ian Smith X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 20:19:24 -0000 On 13 January 2013 12:07, Slawa Olhovchenkov wrote: > On Sun, Jan 13, 2013 at 11:43:55AM -0800, Adrian Chadd wrote: > >> Right. That should be a good indication. > > After 10 min card still hot. Ok, so that means the basic power lines are up and working. Ah, I did add in the force-wakeup hack code; it's just not enabled by default. Try editing sys/dev/ath/if_ath_pci.c ; look for: #ifdef ATH_PCI_WAKEUP_WAR .. and change that to #if 1 Then recompile if_ath_pci and try that. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 20:21:20 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 55A939AA for ; Sun, 13 Jan 2013 20:21:20 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f45.google.com (mail-wg0-f45.google.com [74.125.82.45]) by mx1.freebsd.org (Postfix) with ESMTP id EA1CE9B3 for ; Sun, 13 Jan 2013 20:21:19 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id dq12so1745830wgb.24 for ; Sun, 13 Jan 2013 12:21:18 -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=0geIAO8cJolhIZZ2QLLN640X4+rWy6Te51A2mFMLMQY=; b=eCBbGfBScotSBELuRJ6e+V018AIh0jlwKAsSujDDg9Qu0/9O5RmSJ66dXlxpykMD4g vRnfKAl0mjNMemmpYrf5zkXyznI3+glysBaaDljr2+mKT1CNoAQczBT5n5TDclCcwaAe 2APi/r2khg0p4FZxdesQg0Q0R8MXUqyGldzhU8pLH4jop+cLO425d9Cak8oPijlbF8dh I0W/86VdABUqQMnLQVLcmi/B/gddgPVoEQVpUaiICouwkKUsYBKf+uXR742V44uq1XfG RpuSaUfjqckO+VVNp4wcjLo33vBHejfXX4Yxl/B8LfkbcthErDB5jYOXDLVUgWylzNH+ sw/Q== MIME-Version: 1.0 X-Received: by 10.180.33.44 with SMTP id o12mr9099059wii.28.1358108478804; Sun, 13 Jan 2013 12:21:18 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sun, 13 Jan 2013 12:21:18 -0800 (PST) In-Reply-To: References: Date: Sun, 13 Jan 2013 12:21:18 -0800 X-Google-Sender-Auth: qPZ-jfa2IMC_Pz56I7VMzJjVAcI 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: Sun, 13 Jan 2013 20:21:20 -0000 It was likely a specific client. Traffic levels can affect things - the macosx wifi stuff will do background scans if traffic is under a certain threshold and stop it otherwise. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 20:31:57 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 ADDF4DD4 for ; Sun, 13 Jan 2013 20:31:57 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-f175.google.com (mail-we0-f175.google.com [74.125.82.175]) by mx1.freebsd.org (Postfix) with ESMTP id 4E6FBA1F for ; Sun, 13 Jan 2013 20:31:56 +0000 (UTC) Received: by mail-we0-f175.google.com with SMTP id z53so1738801wey.20 for ; Sun, 13 Jan 2013 12:31:50 -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=ynT7LNwlBFnj0sDI5ULnVaKiJk2gMdZZVF3KvQtfqSY=; b=Rh5eSc6QQhxGZn7JPVjZcwDd7mJ7Yu/D2H+TJYZJ9J+o7yhAp9Xf3lFu8JzaDEwzl8 rIumSYbcNY65yQKzaF3Pa4c2dFmgsn0ZaCMFaha+RHJCqbM1nW9e9E17ZdDzE3qrDtQI 0jlZFeB0OTs2omrWEqCFJTPCzlqIyTLJBoxNAw9OLN7N8W3kjnrHQV4w7LXxBchW0BCR FpltVk3gLiqIVayAi/2GPvWWfMWqutMSywBMZCLZcumkRcGXWkPIHAs8RdRA24rNFrKO Rc8FOXzmUiOpboTRwk4FX5f53u4ptsxkffhb40XH1JkMzHfWMQNIxBW1wdOfwnfqOXIf lCYg== MIME-Version: 1.0 Received: by 10.194.179.34 with SMTP id dd2mr131681333wjc.1.1358109110591; Sun, 13 Jan 2013 12:31:50 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Sun, 13 Jan 2013 12:31:50 -0800 (PST) In-Reply-To: References: Date: Sun, 13 Jan 2013 12:31:50 -0800 X-Google-Sender-Auth: PVqsdEsmrXYpmq_M-uccW1rIFRg 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: Sun, 13 Jan 2013 20:31:57 -0000 Hi, The reason I haven't (yet) written any particular directions up on this is because I'm still trying to come up with relevant workarounds for spectral scan on the AR9280, when it's active with traffic. Since some of you will likely enable it with traffic and then discover that things hang (and frequently), I'd like to make sure the general case recoverable. What I've discovered thus far: * In STA mode, the beacon timer programming doesn't happen after a watchdog reset. * In STA mode, a beacon miss event can be indicative of RX deafness, so the right thing to do there is a no-loss reset. A reset does fix the RX deafness hang issue, but it doesn't reprogram the beacon timers, so subsequent beacon miss interrupts don't occur. * If I overflow the RX queue, the recovery doesn't .. recover. This may be a failure mode that's very specific to "RX queue overflow with PHY errors" rather than "RX queue overflow with data." At this stage, the RX just totally hangs until a reset occurs. I've fixed #1 and #2, and #3 is an interesting side-case. Once #2 was fixed, #3 immediately results in missed beacons, which results in a reset. But if too many missed beacons occur due to deafness, the association session is reset. So what I may do is: * Add the code to -HEAD to correctly reprogram the beacon timer after a missed beacon -> hardware reset; * Always reset the hardware after a beacon miss, in case it's a hang that we haven't yet detected; * Add the spectral scan related signatures to the HAL, so the ath_bmiss_proc() code doesn't call ieee80211_beacon_miss() and thus disassociate things. I'll also see if a full reset rather than a warm reset fixes whatever the bad PHY hardware state is that's causing things to continuously get stuck. Once that's done, I'll release some updated instructions so people can tinker with it, along with "this can hang all kinds of things and decrease performance, be careful" warnings. I may even wrap the code up in a github project or something and make a port. Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 21:25: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 C9BAB272 for ; Sun, 13 Jan 2013 21:25:09 +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 7583AD7B for ; Sun, 13 Jan 2013 21:25:09 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1TuV7b-000I9c-Dw; Mon, 14 Jan 2013 01:29:39 +0400 Date: Mon, 14 Jan 2013 01:29:39 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130113212939.GS67643@zxy.spb.ru> References: <20130112165235.GK67643@zxy.spb.ru> <20130112170707.GL67643@zxy.spb.ru> <20130114050646.O62930@sola.nimnet.asn.au> <20130113194033.GQ67643@zxy.spb.ru> <20130113200721.GR67643@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" , Ian Smith X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 21:25:09 -0000 On Sun, Jan 13, 2013 at 12:19:22PM -0800, Adrian Chadd wrote: > On 13 January 2013 12:07, Slawa Olhovchenkov wrote: > > On Sun, Jan 13, 2013 at 11:43:55AM -0800, Adrian Chadd wrote: > > > >> Right. That should be a good indication. > > > > After 10 min card still hot. > > Ok, so that means the basic power lines are up and working. > > Ah, I did add in the force-wakeup hack code; it's just not enabled by default. > > Try editing sys/dev/ath/if_ath_pci.c ; look for: > > #ifdef ATH_PCI_WAKEUP_WAR > > .. and change that to > > #if 1 > > Then recompile if_ath_pci and try that. After reboot not working: [228] ath0: device timeout [236] ath0: device timeout [245] ath0: device timeout PS: card more hot. From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 21:29: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 B9A018D3 for ; Sun, 13 Jan 2013 21:29: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 757C8DD1 for ; Sun, 13 Jan 2013 21:29:33 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1TuVBx-000IBD-Aa; Mon, 14 Jan 2013 01:34:09 +0400 Date: Mon, 14 Jan 2013 01:34:09 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130113213409.GT67643@zxy.spb.ru> References: <20130112170707.GL67643@zxy.spb.ru> <20130114050646.O62930@sola.nimnet.asn.au> <20130113194033.GQ67643@zxy.spb.ru> <20130113200721.GR67643@zxy.spb.ru> <20130113212939.GS67643@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130113212939.GS67643@zxy.spb.ru> 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" , Ian Smith X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 21:29:33 -0000 On Mon, Jan 14, 2013 at 01:29:39AM +0400, Slawa Olhovchenkov wrote: > On Sun, Jan 13, 2013 at 12:19:22PM -0800, Adrian Chadd wrote: > > > On 13 January 2013 12:07, Slawa Olhovchenkov wrote: > > > On Sun, Jan 13, 2013 at 11:43:55AM -0800, Adrian Chadd wrote: > > > > > >> Right. That should be a good indication. > > > > > > After 10 min card still hot. > > > > Ok, so that means the basic power lines are up and working. > > > > Ah, I did add in the force-wakeup hack code; it's just not enabled by default. > > > > Try editing sys/dev/ath/if_ath_pci.c ; look for: > > > > #ifdef ATH_PCI_WAKEUP_WAR > > > > .. and change that to > > > > #if 1 > > > > Then recompile if_ath_pci and try that. > > After reboot not working: > > [228] ath0: device timeout > [236] ath0: device timeout > [245] ath0: device timeout > > PS: card more hot. And different output from pciconf -rb pci0:6:5:0 0:255 8c 16 29 00 02 00 b0 02 01 00 80 02 08 a8 00 00 old value: 8c 16 29 00 16 01 b0 02 01 00 80 02 08 a8 00 00 From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 21:31:59 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 21B579F2 for ; Sun, 13 Jan 2013 21:31:59 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) by mx1.freebsd.org (Postfix) with ESMTP id E8EB9DF3 for ; Sun, 13 Jan 2013 21:31:58 +0000 (UTC) Received: by mail-ie0-f176.google.com with SMTP id 13so4290940iea.21 for ; Sun, 13 Jan 2013 13:31:58 -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=sLDcPE2bGK96usmH9QryzDG4Jwti+qS/cXtt7/ZsGGE=; b=Jid+AfqhzVPdFPZn0mbAn7t7871mBGiSNAqw8V4LYr5iGQgmxmRGCztyhy/6Z4Xfuz dbINQdMXwNF6nQRZHT1THqgjQa7sCU8iWnZEqOt/j+u4y7gqcYbIoy5W2x6rxatEEi9h ti5PVg3QTpJoMfJCKuMOowstswYSXA9Yai6ePQ/6jj9bDcM86c2/MAs0w8waFmTU+luF QhwqWItvo7UB1PGdNK0aFNatBIQLo+gMbe/9xYuXLVReyWppgTCnqYiss/7ZY971eywB K/eUlA73j4YTFpkhS5zofQ52gEeuImHCsA32g4BUCzgQp2LmE/P+OnQ8RqkqcuqkyVg0 8xIA== X-Received: by 10.50.194.167 with SMTP id hx7mr5122670igc.99.1358112718353; Sun, 13 Jan 2013 13:31:58 -0800 (PST) Received: from www.palm.com ([32.167.173.243]) by mx.google.com with ESMTPS id aa6sm4899595igc.14.2013.01.13.13.31.53 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 13 Jan 2013 13:31:57 -0800 (PST) Message-ID: <50f327cd.06a9320a.3870.ffffb408@mx.google.com> Date: Sun, 13 Jan 2013 16:32:16 -0500 From: "Adrian Chadd" To: "Slawa Olhovchenkov" Subject: Re: Atheros 9220 don't return from S3 state In-Reply-To: <20130113212939.GS67643@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 Cc: "freebsd-wireless@freebsd.org" , Ian Smith 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: Sun, 13 Jan 2013 21:31:59 -0000 Ok. So don't use that :) I'll dig up the pci hostif registers and see what I can find. But, hm. We= should dump and compare the pci conf registers for the bridge that device= is on.  Adrian Adrian Sent from my Palm Pre on AT&T On Jan 13, 2013 4:25 PM, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote:=20 On Sun, Jan 13, 2013 at 12:19:22PM -0800, Adrian Chadd wrote: > On 13 January 2013 12:07, Slawa Olhovchenkov <slw@zxy.spb.ru> wr= ote: > > On Sun, Jan 13, 2013 at 11:43:55AM -0800, Adrian Chadd wrote: > > > >> Right. That should be a good indication. > > > > After 10 min card still hot. >=20 > Ok, so that means the basic power lines are up and working. >=20 > Ah, I did add in the force-wakeup hack code; it's just not enabled by= default. >=20 > Try editing sys/dev/ath/if_ath_pci.c ; look for: >=20 > #ifdef ATH_PCI_WAKEUP_WAR >=20 > .. and change that to >=20 > #if 1 >=20 > Then recompile if_ath_pci and try that. After reboot not working: [228] ath0: device timeout [236] ath0: device timeout [245] ath0: device timeout PS: card more hot. From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 21:40:13 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 0583EE7F for ; Sun, 13 Jan 2013 21:40:13 +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 B8B81E3C for ; Sun, 13 Jan 2013 21:40:12 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1TuVMH-000IDt-2D; Mon, 14 Jan 2013 01:44:49 +0400 Date: Mon, 14 Jan 2013 01:44:49 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state Message-ID: <20130113214448.GU67643@zxy.spb.ru> References: <20130113212939.GS67643@zxy.spb.ru> <50f327cd.06a9320a.3870.ffffb408@mx.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50f327cd.06a9320a.3870.ffffb408@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" , Ian Smith X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jan 2013 21:40:13 -0000 On Sun, Jan 13, 2013 at 04:32:16PM -0500, Adrian Chadd wrote: > Ok. So don't use that :) > > I'll dig up the pci hostif registers and see what I can find. But, hm. We should dump and compare the pci conf registers for the bridge that device is on.  > If it is pcib3@pci0:0:30:0: class=0x060401 card=0x12e310cf chip=0x24488086 rev=0xd4 hdr=0x01 vendor = 'Intel Corporation' device = '82801 Mobile PCI Bridge' class = bridge subclass = PCI-PCI (other bridge is PCI Express) -- I don't find difference between 'boot' and 'resume'. > Adrian > > Adrian > > > > Sent from my Palm Pre on AT&T > On Jan 13, 2013 4:25 PM, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote: > > On Sun, Jan 13, 2013 at 12:19:22PM -0800, Adrian Chadd wrote: > > > > > On 13 January 2013 12:07, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote: > > > > On Sun, Jan 13, 2013 at 11:43:55AM -0800, Adrian Chadd wrote: > > > > > > > >> Right. That should be a good indication. > > > > > > > > After 10 min card still hot. > > > > > > Ok, so that means the basic power lines are up and working. > > > > > > Ah, I did add in the force-wakeup hack code; it's just not enabled by default. > > > > > > Try editing sys/dev/ath/if_ath_pci.c ; look for: > > > > > > #ifdef ATH_PCI_WAKEUP_WAR > > > > > > .. and change that to > > > > > > #if 1 > > > > > > Then recompile if_ath_pci and try that. > > > > After reboot not working: > > > > [228] ath0: device timeout > > [236] ath0: device timeout > > [245] ath0: device timeout > > > > PS: card more hot. > > From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 13 23:57:12 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 C45E17C6 for ; Sun, 13 Jan 2013 23:57:12 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ia0-f176.google.com (mail-ia0-f176.google.com [209.85.210.176]) by mx1.freebsd.org (Postfix) with ESMTP id 715D272F for ; Sun, 13 Jan 2013 23:57:12 +0000 (UTC) Received: by mail-ia0-f176.google.com with SMTP id y26so3114669iab.35 for ; Sun, 13 Jan 2013 15:57:06 -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=eVT9KmpgzkBBz8mCWxT+qtDnIpYKbrADgHEQ9Tnl1JQ=; b=qnseQ8E3PlS3wZS5Ycajuupd1m/TC4fR5jU6SJkFuoeJoB+S7SX7ojgBTCOUZm7gUu sj7OhktsE4p4jTlBg9btWnhc131DANULAjxwF63fJsPtwi0fSh+s5SH7nspw3MJ2fZMt vpNJ878dZYv4ZkrfCSAKHHO24Mljdan7p9QrREBV0g3gnsVK1TDElfUmFIRCI/sc4EO/ FeVeKeAwWptWpx8HWE42ikQsbZkvdWBBhH9FqGeCwsROjootmK6mwxnJptYCiMIKHapg 0d1bK1bC6jjjxKkD3R8d/ONY/hYVfDSmdGMz6SNhTLRZToA1xmZ7c9ubpx3pMEEwCOkn x0WA== X-Received: by 10.43.110.132 with SMTP id ek4mr62295739icc.32.1358121426453; Sun, 13 Jan 2013 15:57:06 -0800 (PST) Received: from www.palm.com ([32.167.173.243]) by mx.google.com with ESMTPS id x7sm5721015igk.8.2013.01.13.15.57.01 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 13 Jan 2013 15:57:05 -0800 (PST) Message-ID: <50f349d1.8728320a.6ff7.ffffc0f5@mx.google.com> Date: Sun, 13 Jan 2013 18:56:47 -0500 From: "Adrian Chadd" To: "Slawa Olhovchenkov" Subject: Re: Atheros 9220 don't return from S3 state In-Reply-To: <20130113214448.GU67643@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 Cc: "freebsd-wireless@freebsd.org" , Ian Smith 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: Sun, 13 Jan 2013 23:57:12 -0000 Well. Compare the other bridges too, out of interest. Adrian Sent from my Palm Pre on AT&T On Jan 13, 2013 4:40 PM, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote:=20 On Sun, Jan 13, 2013 at 04:32:16PM -0500, Adrian Chadd wrote: > Ok. So don't use that :) >=20 > I'll dig up the pci hostif registers and see what I can find. But, hm.= We should dump and compare the pci conf registers for the bridge that devi= ce is on.&nbsp; >=20 If it is pcib3@pci0:0:30:0: class=3D0x060401 card=3D0x12e310cf chip=3D0x2448808= 6 rev=3D0xd4 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D '82801 Mobile PCI Bridge' class =3D bridge subclass =3D PCI-PCI (other bridge is PCI Express) -- I don't find difference between 'boot' and 'resume'. > Adrian >=20 > Adrian >=20 >=20 >=20 > Sent from my Palm Pre on AT&amp;T > On Jan 13, 2013 4:25 PM, Slawa Olhovchenkov &lt;slw@zxy.spb.ru&= ;gt; wrote:=20 >=20 > On Sun, Jan 13, 2013 at 12:19:22PM -0800, Adrian Chadd wrote: >=20 >=20 >=20 > &gt; On 13 January 2013 12:07, Slawa Olhovchenkov &lt;slw@zxy.= spb.ru&gt; wrote: >=20 > &gt; &gt; On Sun, Jan 13, 2013 at 11:43:55AM -0800, Adrian Cha= dd wrote: >=20 > &gt; &gt; >=20 > &gt; &gt;&gt; Right. That should be a good indication. >=20 > &gt; &gt; >=20 > &gt; &gt; After 10 min card still hot. >=20 > &gt;=20 >=20 > &gt; Ok, so that means the basic power lines are up and working. >=20 > &gt;=20 >=20 > &gt; Ah, I did add in the force-wakeup hack code; it's just not en= abled by default. >=20 > &gt;=20 >=20 > &gt; Try editing sys/dev/ath/if_ath_pci.c ; look for: >=20 > &gt;=20 >=20 > &gt; #ifdef ATH_PCI_WAKEUP_WAR >=20 > &gt;=20 >=20 > &gt; .. and change that to >=20 > &gt;=20 >=20 > &gt; #if 1 >=20 > &gt;=20 >=20 > &gt; Then recompile if_ath_pci and try that. >=20 >=20 >=20 > After reboot not working: >=20 >=20 >=20 > [228] ath0: device timeout >=20 > [236] ath0: device timeout >=20 > [245] ath0: device timeout >=20 >=20 >=20 > PS: card more hot. >=20 >=20 From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 14 11:06:57 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 7B7DA609 for ; Mon, 14 Jan 2013 11:06:57 +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 E9A39665 for ; Mon, 14 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 r0EB6u7c086587 for ; Mon, 14 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 r0EB6uph086585 for freebsd-wireless@FreeBSD.org; Mon, 14 Jan 2013 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 Jan 2013 11:06:56 GMT Message-Id: <201301141106.r0EB6uph086585@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, 14 Jan 2013 11:06:57 -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/175227 wireless [ath] beacon timers aren't necessarily reprogrammed af o kern/175183 wireless [iwn] iwn(4) becomes unresponsive during initial confi 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 146 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 14 11:49: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 BAD35E33 for ; Mon, 14 Jan 2013 11:49:44 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 368ABC06 for ; Mon, 14 Jan 2013 11:49:43 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id r0EBnehK056594; Mon, 14 Jan 2013 22:49:40 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 14 Jan 2013 22:49:40 +1100 (EST) From: Ian Smith To: Adrian Chadd Subject: Re: Atheros 9220 don't return from S3 state In-Reply-To: Message-ID: <20130114221708.X62930@sola.nimnet.asn.au> 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> <20130114050646.O62930@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: "freebsd-wireless@freebsd.org" , Slawa Olhovchenkov 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, 14 Jan 2013 11:49:44 -0000 On Sun, 13 Jan 2013 11:25:37 -0800, Adrian Chadd wrote: > The problem here is I can't easily test this. We detach and re-attach > cardbus devices during suspend/resume, so although I have AR9220 > mini-PCI NICs, they don't stay connected the normal way. The slot gets > fully powered down and reset upon power up. Ah, of course, cardbus .. I was wondering what *CBS[01] in my dmesg were that indicated apparently not being able to go from D0 -> D2, though on resume they seemed to do D2 -> D0 ok (well, perhaps from D3 really?) Um, are you saying that mini-PCI devices are treated as if cardbus? My only wireless card is an old Cabletron RoamAbout 11b, pccard not cardbus, that used to work on (AFAIR) 4.8-REL but on 9.1-REL causes an interrupt storm on IRQ 11, throttled. I'm uninterested in pursing it. And I haven't managed to get a cardbus USB 2 card working properly either yet, to the extent that suspend/resume _sometimes_ but not with any apparent consistency panics, so I'm no help here. cheers, Ian From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 14 23:59: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 EEFFEA5F for ; Mon, 14 Jan 2013 23:59:52 +0000 (UTC) (envelope-from jakub_lach@mailplus.pl) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id D6C0F665 for ; Mon, 14 Jan 2013 23:59:52 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TutwQ-0001Vd-9b for freebsd-wireless@freebsd.org; Mon, 14 Jan 2013 15:59:46 -0800 Date: Mon, 14 Jan 2013 15:59:46 -0800 (PST) From: Jakub Lach To: freebsd-wireless@freebsd.org Message-ID: <1358207986273-5777695.post@n5.nabble.com> Subject: 9-STABLE kernel ath build problem, probably related to r245429 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, 14 Jan 2013 23:59:53 -0000 Have dependencies changed? I've only have ath and ath_pci, they always gave me everything I needed for my card. /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ar9002/ar9285_attach.c:144:35: error: use of undeclared identifier 'ath_hal_EepromDataRead' AH_PRIVATE(ah)->ah_eepromRead = ath_hal_EepromDataRead; ^ 1 error generated. *** [ar9285_attach.o] Error code 1 -- View this message in context: http://freebsd.1045724.n5.nabble.com/9-STABLE-kernel-ath-build-problem-probably-related-to-r245429-tp5777695.html Sent from the freebsd-wireless mailing list archive at Nabble.com. From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 15 00:56:58 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 91D9110C for ; Tue, 15 Jan 2013 00:56:58 +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 1CC328FC for ; Tue, 15 Jan 2013 00:56:57 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id hm11so1788274wib.14 for ; Mon, 14 Jan 2013 16:56:56 -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=H0UKPhEk2teDkD9A1Pe+s6qoOo3BxXo1jygK/lBEAHY=; b=g/stbcLCB8zPfcYKxA8fTqW+g2trGdelUJTAxXcU+S1un1uB6JZpJevVO6S5XlCsur b0/YW8ToGTtKgu54iJIoDqau9e+HUHkeepY/40NTasIDVI5bFuH+UH5vKYt3YsYpfn0g zOIwOGVqaC2pKz1pmvsblaKTYQegz0J69/COuH6WN0+DX+YnqAwJn62Gp5kUBiA/Vbm5 J2W4WRrhze3aM27/To8N51uO8zwgcYSPnPnvGcvtFFw8KRjJD8ME1unWkwlZoX++r6up rIMOCo+WlVGNNruRfEnaa5I4ZtUXsM26cY8dwVBQcbwwnTNNDtLHZAUf7K2bpK8efqme K8Sg== MIME-Version: 1.0 Received: by 10.194.109.10 with SMTP id ho10mr47969370wjb.16.1358211416921; Mon, 14 Jan 2013 16:56:56 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Mon, 14 Jan 2013 16:56:56 -0800 (PST) In-Reply-To: <1358207986273-5777695.post@n5.nabble.com> References: <1358207986273-5777695.post@n5.nabble.com> Date: Mon, 14 Jan 2013 16:56:56 -0800 X-Google-Sender-Auth: McJZ0UR3dyH1uXFfTdtZ-HSyMSQ Message-ID: Subject: Re: 9-STABLE kernel ath build problem, probably related to r245429 From: Adrian Chadd To: Jakub Lach 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: Tue, 15 Jan 2013 00:56:58 -0000 -HEAD or -9 ? Adrian On 14 January 2013 15:59, Jakub Lach wrote: > Have dependencies changed? > > I've only have ath and ath_pci, they always gave me everything I needed > for my card. > > /usr/src/sys/modules/ath/../../dev/ath/ath_hal/ar9002/ar9285_attach.c:144:35: > error: > use of undeclared identifier 'ath_hal_EepromDataRead' > AH_PRIVATE(ah)->ah_eepromRead = ath_hal_EepromDataRead; > ^ > 1 error generated. > *** [ar9285_attach.o] Error code 1 > > > > > -- > View this message in context: http://freebsd.1045724.n5.nabble.com/9-STABLE-kernel-ath-build-problem-probably-related-to-r245429-tp5777695.html > Sent from the freebsd-wireless mailing list archive at Nabble.com. > _______________________________________________ > 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 Tue Jan 15 00:58:12 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 2B74113D for ; Tue, 15 Jan 2013 00:58:12 +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 B9F1B90F for ; Tue, 15 Jan 2013 00:58:10 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id dq11so2460088wgb.14 for ; Mon, 14 Jan 2013 16:58:04 -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=awE5fu00suqL0z8k/mcVHKDYnRWUAK3cm4KKw/dAipo=; b=c2UG0il5+vIjW5/dIJY91KTpjOwy76jjm9lPt1YLtKdMx2iYBoyimqu4mcyRTYn5na lKlwsydZ/7xWd90sb74DzNx3QWIOZXZ9OXm6zG74ASTNCOvwLrdFmki92KsfeWqBGgzZ 2CtFynSUQQza7EoCmCldKyaLnuJk7ra5BxGDve30Z+xp/nVIn5duX1iG14k4BDKQJ/7f NnAftNmpQsp6qP60wWJVpTmjIjeYIVR72tmYeaVzhnfYWiHTPDcAQWAu+PlTxgh9BbNz x14g8nCKqnrVHGVYEU3baNTKhETXP5s/k1jx5TouhQYDaVD5D160JQblcdu6Z/+sjlrz 3QGA== MIME-Version: 1.0 Received: by 10.194.109.10 with SMTP id ho10mr47972709wjb.16.1358211484439; Mon, 14 Jan 2013 16:58:04 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Mon, 14 Jan 2013 16:58:04 -0800 (PST) In-Reply-To: References: <1358207986273-5777695.post@n5.nabble.com> Date: Mon, 14 Jan 2013 16:58:04 -0800 X-Google-Sender-Auth: C5w6EAivDHZV7Xlzttdd8u3Gdw0 Message-ID: Subject: Re: 9-STABLE kernel ath build problem, probably related to r245429 From: Adrian Chadd To: Jakub Lach 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: Tue, 15 Jan 2013 00:58:12 -0000 Duh, 9-STABLE. Guess it wasn't build tested before commit? Odd... Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 17 16:50:01 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 1408E1E0 for ; Thu, 17 Jan 2013 16:50:01 +0000 (UTC) (envelope-from gnats@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 04523E7F for ; Thu, 17 Jan 2013 16:50:01 +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 r0HGo06F096787 for ; Thu, 17 Jan 2013 16:50:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r0HGo02e096786; Thu, 17 Jan 2013 16:50:00 GMT (envelope-from gnats) Date: Thu, 17 Jan 2013 16:50:00 GMT Message-Id: <201301171650.r0HGo02e096786@freefall.freebsd.org> To: freebsd-wireless@FreeBSD.org Cc: From: dfilter@FreeBSD.ORG (dfilter service) Subject: Re: kern/175227: commit references a PR X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: dfilter service 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, 17 Jan 2013 16:50:01 -0000 The following reply was made to PR kern/175227; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/175227: commit references a PR Date: Thu, 17 Jan 2013 16:44:12 +0000 (UTC) Author: adrian Date: Thu Jan 17 16:43:59 2013 New Revision: 245556 URL: http://svnweb.freebsd.org/changeset/base/245556 Log: Fix hangs (exposed by spectral scan activity) in STA mode when the chip hangs. * Always do a reset in ath_bmiss_proc(), regardless of whether the hardware is "hung" or not. Specifically, for spectral scan, there's likely a whole bunch of potential hangs that we don't (yet) recognise in the HAL. So to avoid staying RX deaf persisting until the station disassociates, just do a no-loss reset. * Set sc_beacons=1 in STA mode. During a reset, the beacon programming isn't done. (It's likely I need to set sc_syncbeacons during a hang reset, but I digress.) Thus after a reset, there's no beacon timer programming to send a BMISS interrupt if beacons aren't heard .. thus if the AP disappears, you won't get notified and you'll have to reset your interface. This hasn't yet fixed all of the hangs that I've seen when debugging spectral scan, but it's certainly reduced the hang frequency and it should improve general STA stability in very noisy environments. Tested: * AR9280, STA mode, spectral scan off/on PR: kern/175227 Modified: head/sys/dev/ath/if_ath.c Modified: head/sys/dev/ath/if_ath.c ============================================================================== --- head/sys/dev/ath/if_ath.c Thu Jan 17 16:39:21 2013 (r245555) +++ head/sys/dev/ath/if_ath.c Thu Jan 17 16:43:59 2013 (r245556) @@ -1883,11 +1883,19 @@ ath_bmiss_proc(void *arg, int pending) DPRINTF(sc, ATH_DEBUG_ANY, "%s: pending %u\n", __func__, pending); + /* + * Do a reset upon any becaon miss event. + * + * It may be a non-recognised RX clear hang which needs a reset + * to clear. + */ if (ath_hal_gethangstate(sc->sc_ah, 0xff, &hangs) && hangs != 0) { + ath_reset(ifp, ATH_RESET_NOLOSS); if_printf(ifp, "bb hang detected (0x%x), resetting\n", hangs); + } else { ath_reset(ifp, ATH_RESET_NOLOSS); - } else ieee80211_beacon_miss(ifp->if_l2com); + } } /* @@ -5056,6 +5064,7 @@ ath_newstate(struct ieee80211vap *vap, e int i, error, stamode; u_int32_t rfilt; int csa_run_transition = 0; + static const HAL_LED_STATE leds[] = { HAL_LED_INIT, /* IEEE80211_S_INIT */ HAL_LED_SCAN, /* IEEE80211_S_SCAN */ @@ -5200,10 +5209,32 @@ ath_newstate(struct ieee80211vap *vap, e * force a beacon update so we pick up a lack of * beacons from an AP in CAC and thus force a * scan. + * + * And, there's also corner cases here where + * after a scan, the AP may have disappeared. + * In that case, we may not receive an actual + * beacon to update the beacon timer and thus we + * won't get notified of the missing beacons. */ sc->sc_syncbeacon = 1; +#if 0 if (csa_run_transition) +#endif ath_beacon_config(sc, vap); + + /* + * PR: kern/175227 + * + * Reconfigure beacons during reset; as otherwise + * we won't get the beacon timers reprogrammed + * after a reset and thus we won't pick up a + * beacon miss interrupt. + * + * Hopefully we'll see a beacon before the BMISS + * timer fires (too often), leading to a STA + * disassociation. + */ + sc->sc_beacons = 1; break; case IEEE80211_M_MONITOR: /* _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 19 23:49:07 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 0F517FFB for ; Sat, 19 Jan 2013 23:49:07 +0000 (UTC) (envelope-from hoptoa@gmail.com) Received: from mail-vc0-f173.google.com (mail-vc0-f173.google.com [209.85.220.173]) by mx1.freebsd.org (Postfix) with ESMTP id A2179659 for ; Sat, 19 Jan 2013 23:49:06 +0000 (UTC) Received: by mail-vc0-f173.google.com with SMTP id fy7so1578472vcb.18 for ; Sat, 19 Jan 2013 15:48:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=NaXLAP1B17J5LSfZcByDlZYv9aCkuDg/49gsQwNuer8=; b=VGd13f4LiEuoa5VpyZ/GFHhLaYG9aeVYcWtn2ffmws8+jvI+haNgSx2ktd/40Lm8bD UVRPNXQOy6JwAZXz4DEpSRq5EzqpCp9Z1rmd6RucND8d9KpXljNtra4DFFT96+qTKH85 AObdnLxJljt2WvKnCFKxfV0SZPcXU36Zs3i6VfdyMR7mGIZXfd99Jw/kU8dAeng4p9uE 535MyIaoBVkGD1MtSu0LAslCwTZMPv24WqqWY8IkZCXlX4vHRgaRrxZGiahOW3X6d4N5 BViAwlne4/KVVwhr669e70usCXbx+u2Wlpu9ETS1HLeGZByVPp0gLUOIUYfBkDYX0iAr qhPg== MIME-Version: 1.0 X-Received: by 10.52.94.113 with SMTP id db17mr13068888vdb.27.1358638889453; Sat, 19 Jan 2013 15:41:29 -0800 (PST) Received: by 10.220.104.82 with HTTP; Sat, 19 Jan 2013 15:41:29 -0800 (PST) Date: Sun, 20 Jan 2013 01:41:29 +0200 Message-ID: Subject: From: =?KOI8-R?B?4dLUo80g7c/Sz9rP1w==?= To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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, 19 Jan 2013 23:49:07 -0000 D-link DWA-525 I'm trying to find solution for a long time, i want to lead this wireless NIC to work. NIC works on chipset rt3060 which support on Free BSD from 2012.05, but in spite of that NIC doesn't work. I setting up it without any errors, but when I settings it in client mode card cannot find any works access point. And when I settings card in access point mode, I cannot find even this access point. LED indicator on the NIC show, that card is works and transmit data, but really, it doesn't work.