From: Sven Eckelmann <sven@narfation.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCHv2] ath9k_hw: Handle AR_INTR_SYNC_HOST1_FATAL on AR9003
Date: Fri, 05 Oct 2012 13:08:32 +0200 [thread overview]
Message-ID: <2629427.e28b8DS3gI@bentobox> (raw)
In-Reply-To: <CAJ-Vmo=bu=j+=z_TAeE3--Sn5oAEbkEG-HDqK=6okR8xmmWpSQ@mail.gmail.com>
On Wednesday 03 October 2012 07:51:28 Adrian Chadd wrote:
> On 2 October 2012 08:20, Felix Fietkau <nbd@openwrt.org> wrote:
> >> This sync cause 0x20 isn't handled anywhere and may be the cause of the
> >> hang/crash. At least this is the symptom which can be fixed without
> >> crashing the system.
> >
> > I checked the AR933x datasheet, and it says that cause 0x20 is tx
> > descriptor corruption.
>
> Ah hey, for Hornet they redefined those bits:
>
> 5: MAC_TXC_CORRUPTION_FLAG_SYNC (TX descriptor integrity flag)
> 6: INVALID_ADDRESS_ACCESS (invalid register access)
>
> Good catch. That's definitely something in the right direction.
Ok, I've just created a dirty hack to trace some of the register reads/writes.
I used following test setup: Two Hornets, one is the "internet gateway" (just
attached using ethernet to a test server) and is running one AP vif with
standard OpenWRT settings. The other Hornet is placed next to it (only some
centimeter far away) and is connected to the AP using WiFi.
The client device is just trying to download a large file using HTTP. The
serial consoles on both devices will now print the "same" log. I already
searched for the interesting section. It is started in ath_ani_calibrate and
contains ~42 register access operations.
My best guess is the REG_RMW_FIELD for ATH9K_ANI_MRC_CCK in
ar9003_hw_ani_control (just checked sync_cause before and after the access).
So, now I need some input again from the guis with the spec. :)
Kind regards,
Sven
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 999-debug_reg_write.patch
Type: text/x-patch
Size: 11457 bytes
Desc: not available
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20121005/b98046b7/attachment-0002.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invalid_register_access.log
Type: text/x-log
Size: 27233 bytes
Desc: not available
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20121005/b98046b7/attachment-0003.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20121005/b98046b7/attachment-0001.pgp
next prev parent reply other threads:[~2012-10-05 11:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 14:41 [ath9k-devel] [PATCH] ath9k_hw: Handle AR_INTR_SYNC_HOST1_(FATAL|PERR) on AR9003 Sven Eckelmann
2012-10-02 10:33 ` [ath9k-devel] [PATCHv2] ath9k_hw: Handle AR_INTR_SYNC_HOST1_FATAL " Sven Eckelmann
2012-10-02 13:13 ` Adrian Chadd
2012-10-02 13:33 ` Felix Fietkau
2012-10-02 13:35 ` Simon Wunderlich
2012-10-02 14:06 ` Adrian Chadd
2012-10-02 15:02 ` Sven Eckelmann
2012-10-02 15:20 ` Felix Fietkau
2012-10-03 14:51 ` Adrian Chadd
2012-10-05 11:08 ` Sven Eckelmann [this message]
2012-10-05 12:34 ` Felix Fietkau
2012-10-05 13:07 ` Sven Eckelmann
2012-10-05 13:24 ` Felix Fietkau
2012-10-05 15:03 ` Sven Eckelmann
2012-10-05 15:15 ` Felix Fietkau
2012-10-05 16:05 ` Sven Eckelmann
2012-10-05 16:21 ` Adrian Chadd
2012-10-05 16:51 ` Sven Eckelmann
2012-10-05 23:48 ` Adrian Chadd
2012-10-06 9:03 ` Felix Fietkau
2013-02-21 11:14 ` Felix Liao
2013-02-21 20:38 ` Adrian Chadd
2013-02-22 1:19 ` Felix Liao
2013-02-22 5:16 ` Adrian Chadd
2013-02-22 6:43 ` Felix Liao
2013-02-22 7:18 ` Adrian Chadd
2013-02-22 7:31 ` Felix Liao
2013-02-22 8:08 ` Felix Liao
2013-02-22 1:33 ` Felix Liao
2013-02-22 2:22 ` Felix Liao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2629427.e28b8DS3gI@bentobox \
--to=sven@narfation.org \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox