Date: Sat, 23 Apr 2011 12:51:01 +0800 From: Adrian Chadd <adrian@freebsd.org> To: freebsd-wireless@freebsd.org Subject: Fwd: "Hardware error, resetting" on Atheros AR9285 Message-ID: <BANLkTim%2Bzgujgbxr725fdDzsL=xfFaG03g@mail.gmail.com> In-Reply-To: <BANLkTimsEgB%2BegPhE8Lm%2BpEj-qGoRNsnRw@mail.gmail.com> References: <604029735.3207053.1303442079526.JavaMail.root@sz0005a.emeryville.ca.mail.comcast.net> <BANLkTimDcKorX5nv56ss3Gp0Lu3SAQXy9Q@mail.gmail.com> <4DB21FD9.4050503@comcast.net> <BANLkTim-3wycxUUnwCR1DnTJ62NTKZMh=Q@mail.gmail.com> <4DB24BA8.2040900@comcast.net> <BANLkTimsEgB%2BegPhE8Lm%2BpEj-qGoRNsnRw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
FYI, since this discussion disappeared off the list..
Adrian
---------- Forwarded message ----------
From: Adrian Chadd <adrian@freebsd.org>
Date: 23 April 2011 12:44
Subject: Re: "Hardware error, resetting" on Atheros AR9285
To: Rad Manly <radmanly@comcast.net>
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 <radmanly@comcast.net> 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 <radmanly@comcast.net> 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: <Atheros 9285> 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, <radmanly@comcast.net
>>>> <mailto:radmanly@comcast.net>> 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 <mailto: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 <mailto:freebsd-wireless-unsubscribe@freebsd.org>"
>>>>
>>>>
>>> _______________________________________________
>>> 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"
>>>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTim%2Bzgujgbxr725fdDzsL=xfFaG03g>