From owner-freebsd-wireless@FreeBSD.ORG Sat Apr 23 04:51:04 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1DF11065672 for ; Sat, 23 Apr 2011 04:51:04 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 708098FC1B for ; Sat, 23 Apr 2011 04:51:03 +0000 (UTC) Received: by wwc33 with SMTP id 33so1003894wwc.31 for ; Fri, 22 Apr 2011 21:51:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=YGue0bcN3KDnrxb37sKM7JW8MjE/Dms3eCfou2fe8NE=; b=AkP3P8GfrKLeZ8A8YIP081Ns9LGp7P0fHQgOWeB+dBDEXE85ewp4cLByW9SHR34U8b Q5WIOrEv1JKnmaI6qr0DIrB+hyAiIJKTj3Py7IMWCXP8d3NBU/LUca1HJbRnxfsDQgv8 6NROt25aV4J9ot+/KiewYCLIjsR7IXlpl/iSs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=Hsh4TVxCxIAEv8USe+pXovGbtD6TloCgYx3kcqKLndSfbSOM1dNFSA8T8QldZhNVU7 BcGj+dtcqMC4GSczJAdK+oAPef0gw6Cj2ox/WSp67PuLhJzRwEf4O65eFMqP321vOnzi jwFma5YTpSQn/1z091sxXVKrVuC512SNCXPmg= MIME-Version: 1.0 Received: by 10.227.202.139 with SMTP id fe11mr1671233wbb.169.1303534261606; Fri, 22 Apr 2011 21:51:01 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.227.174.13 with HTTP; Fri, 22 Apr 2011 21:51:01 -0700 (PDT) In-Reply-To: References: <604029735.3207053.1303442079526.JavaMail.root@sz0005a.emeryville.ca.mail.comcast.net> <4DB21FD9.4050503@comcast.net> <4DB24BA8.2040900@comcast.net> Date: Sat, 23 Apr 2011 12:51:01 +0800 X-Google-Sender-Auth: vGgPSP-Bx07hWTAEgXU06LATamE Message-ID: From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Fwd: "Hardware error, resetting" on Atheros AR9285 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Apr 2011 04:51:05 -0000 FYI, since this discussion disappeared off the list.. Adrian ---------- Forwarded message ---------- From: Adrian Chadd Date: 23 April 2011 12:44 Subject: Re: "Hardware error, resetting" on Atheros AR9285 To: Rad Manly Nope, unfortunately. That sync register value is AR_INTR_SYNC_LOCAL_TIMEOUT, which shouldn't be triggering a fatal error. I think there may be some bugs in the interrupt handling code. I'll do some further digging for you. In the meantime, please apply this to sys/dev/ath: Index: if_ath.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- if_ath.c =A0 =A0(revision 220950) +++ if_ath.c =A0 =A0(working copy) @@ -1265,7 +1265,7 @@ =A0 =A0 =A0 =A0struct ath_softc *sc =3D arg; =A0 =A0 =A0 =A0struct ifnet *ifp =3D sc->sc_ifp; =A0 =A0 =A0 =A0struct ath_hal *ah =3D sc->sc_ah; - =A0 =A0 =A0 HAL_INT status; + =A0 =A0 =A0 HAL_INT status =3D 0; =A0 =A0 =A0 =A0if (sc->sc_invalid) { =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/* And see if it has any effect. Thanks, Adrian On 23 April 2011 11:46, Rad Manly wrote: > OK, I'll do that. =A0Is there anything that immediately comes to mind as = a > possibility? =A0Anything I could test or check? > > Thanks, > Rad > > On 04/22/11 21:43, Adrian Chadd wrote: >> Please place all of this in a PR. :) >> >> >> Adrian >> >> On 23 April 2011 08:39, Rad Manly wrote: >>> I checked out and built the latest ath driver from -HEAD. >>> Unfortunately, the problem persists. =A0I turned on all of the debuggin= g >>> flags and saved the log file. =A0Here's what I see when I load the driv= er: >>> >>> Apr 22 18:03:34 ceres kernel: ath0: mem >>> 0xf0100000-0xf010ffff irq 17 at device 0.0 on pci2 >>> Apr 22 18:03:34 ceres kernel: ath0: [ITHREAD] >>> Apr 22 18:03:34 ceres kernel: [ath] AR9285E_20 detected; using XE TX >>> gain tables >>> Apr 22 18:03:34 ceres kernel: [ath] Enabling diversity for Kite >>> Apr 22 18:03:34 ceres kernel: ath0: AR9285 mac 192.2 RF5133 phy 14.0 >>> >>> Here's an example of the error: >>> >>> Apr 22 18:04:24 ceres kernel: ar5416SetInterrupts: 0x800965 =3D> 0xe000= 1071 >>> Apr 22 18:04:24 ceres kernel: ar5416SetInterrupts: new IMR 0x8014b7 >>> Apr 22 18:04:24 ceres kernel: ar5416SetInterrupts: enable IER >>> Apr 22 18:04:24 ceres kernel: ar5212StartTxDma: queue 1 >>> Apr 22 18:04:24 ceres kernel: ar5212StartTxDma: queue 1 >>> Apr 22 18:04:24 ceres kernel: ar5416GetPendingInterrupts: fatal error, >>> ISR_RAC 0x0 SYNC_CAUSE 0x2000 >>> Apr 22 18:04:24 ceres kernel: ar5416SetInterrupts: 0xe0001071 =3D> 0x0 >>> Apr 22 18:04:24 ceres kernel: ar5416SetInterrupts: disable IER >>> Apr 22 18:04:24 ceres kernel: ar5416SetInterrupts: new IMR 0x0 >>> Apr 22 18:04:24 ceres kernel: ath0: hardware error; resetting >>> Apr 22 18:04:24 ceres kernel: ath0: 0x00000000 0x00002000 0x00000000, >>> 0x00000000 0x00000000 0x00000000 >>> Apr 22 18:04:24 ceres kernel: ar5416SetInterrupts: 0x0 =3D> 0x0 >>> Apr 22 18:04:24 ceres kernel: ar5416SetInterrupts: new IMR 0x0 >>> >>> >>> To get this, I executed: >>> >>> ifconfig wlan0 create wlanmode sta wlandev ath0 >>> ifconfig wlan0 up scan >>> >>> Do you know what could cause this error? =A0I think the 0x00002000 mean= s >>> it's a timeout error of some kind but I don't know what's timing out or= why. >>> >>> What can I do to help swat this bug? >>> >>> Thanks, >>> Rad >>> >>> >>> On 04/21/11 23:12, Adrian Chadd wrote: >>>> Try -HEAD. I've fixed a lot of AR9285 related issues in HEAD. >>>> >>>> >>>> >>>> Adrian >>>> >>>> On 22 April 2011 11:14, >>> > wrote: >>>> >>>> =A0 =A0 Hello, >>>> >>>> =A0 =A0 Several of us on the FreeBSD forum are having the same problem >>>> =A0 =A0 with the ath driver on the AR9285 chip. The driver loads fine = but >>>> =A0 =A0 whenever I bring up an interface, I get "Hardware error, >>>> =A0 =A0 resetting" messages on the screen over and over again, roughly= one >>>> =A0 =A0 a second. One user, Claude, reports he upgraded to -STABLE to = no >>>> =A0 =A0 avail. I describe the problem in more detail in this thread: >>>> =A0 =A0 http://forums.freebsd.org/showthread.php?t=3D23297 >>>> >>>> =A0 =A0 Is there anything else I should try before I open a bug report= ? >>>> >>>> =A0 =A0 Thanks, >>>> =A0 =A0 Rad >>>> =A0 =A0 _______________________________________________ >>>> =A0 =A0 freebsd-wireless@freebsd.org >>>> =A0 =A0 mailing list >>>> =A0 =A0 http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>>> =A0 =A0 To unsubscribe, send any mail to >>>> =A0 =A0 "freebsd-wireless-unsubscribe@freebsd.org >>>> =A0 =A0 " >>>> >>>> >>> _______________________________________________ >>> 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" >>> >