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: Tue, 02 Oct 2012 17:02:30 +0200 [thread overview]
Message-ID: <7670031.sYFb4t8Iqn@bentobox> (raw)
In-Reply-To: <CAJ-VmomddCMRxx6Vh_i8AJsqYMUCyguUwFt_PQHpDY7-+Gs88A@mail.gmail.com>
On Tuesday 02 October 2012 07:06:03 Adrian Chadd wrote:
> Hm, there are still issues on Hornet?
Yes, we still have problems with hornet. The issue I am trying to "fix" with
this patch is an interrupt storm on AR9330 devices with sta interface(s).
Random devices crash after getting a stacktrace reporting __report_bad_irq.
The crash either results in a reboot or hang of the device
[ 952.950000] irq 2: nobody cared (try booting with the "irqpoll" option)
[ 952.950000] Call Trace:
[ 952.950000] [<8026ade8>] dump_stack+0x8/0x34
[ 952.950000] [<800a75d0>] __report_bad_irq+0x44/0xf4
[ 952.950000] [<800a78ec>] note_interrupt+0x200/0x2a4
[ 952.950000] [<800a58c8>] handle_irq_event_percpu+0x19c/0x1e0
[ 952.950000] [<800a86cc>] handle_percpu_irq+0x54/0x88
[ 952.950000] [<800a501c>] generic_handle_irq+0x3c/0x4c
[ 952.950000] [<80064748>] do_IRQ+0x1c/0x34
[ 952.950000] [<80062d6c>] ret_from_irq+0x0/0x4
[ 952.950000] [<8007673c>] tasklet_action+0xb8/0xd4
[ 952.950000] [<80076c24>] __do_softirq+0xa0/0x154
[ 952.950000] [<80076e30>] do_softirq+0x48/0x68
[ 952.950000] [<80076f94>] local_bh_enable+0x94/0xb0
[ 952.950000] [<83406d60>] cfg80211_scan_done+0x670/0x6d0 [cfg80211]
[ 952.950000]
[ 952.950000] handlers:
[ 952.950000] [<83564d48>] ath_isr
[ 952.950000] Disabling IRQ #2
The test setup is using 30 AR9330 devices running OpenWRT 32727/33559. 32727
is using compat-wireless-2012-04-17 (+ many OpenWRT patches) and 33559 is
running compat-wireless-2012-09-07 (+many more patches from Felix). 1 device
is running an open AP device (standard OpenWRT settings) and 29 devices are
trying to connect. Random devices will now fail. To debug this problem, I used
one devices with 8 vif devices and restarted the network script again and
again to force the recreation of the vif and reconnect.
The stack trace doesn't seem to be very helpful. Therefore, I checked ath_isr
and noticed that the interrupts right before the device crash get the status 0
from ar9003_hw_get_isr. Digging a little but further also revealed that the
interrupts in the interrupt storm also have async_cause 0 and sync_cause 0x20.
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 hope that helps to track down the problem.
Kind regards,
Sven
-------------- 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/20121002/aba09566/attachment.pgp
WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven@narfation.org>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
linville@tuxdriver.com, mcgrof@qca.qualcomm.com,
lindner_marek@yahoo.de
Subject: Re: [PATCHv2] ath9k_hw: Handle AR_INTR_SYNC_HOST1_FATAL on AR9003
Date: Tue, 02 Oct 2012 17:02:30 +0200 [thread overview]
Message-ID: <7670031.sYFb4t8Iqn@bentobox> (raw)
In-Reply-To: <CAJ-VmomddCMRxx6Vh_i8AJsqYMUCyguUwFt_PQHpDY7-+Gs88A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2378 bytes --]
On Tuesday 02 October 2012 07:06:03 Adrian Chadd wrote:
> Hm, there are still issues on Hornet?
Yes, we still have problems with hornet. The issue I am trying to "fix" with
this patch is an interrupt storm on AR9330 devices with sta interface(s).
Random devices crash after getting a stacktrace reporting __report_bad_irq.
The crash either results in a reboot or hang of the device
[ 952.950000] irq 2: nobody cared (try booting with the "irqpoll" option)
[ 952.950000] Call Trace:
[ 952.950000] [<8026ade8>] dump_stack+0x8/0x34
[ 952.950000] [<800a75d0>] __report_bad_irq+0x44/0xf4
[ 952.950000] [<800a78ec>] note_interrupt+0x200/0x2a4
[ 952.950000] [<800a58c8>] handle_irq_event_percpu+0x19c/0x1e0
[ 952.950000] [<800a86cc>] handle_percpu_irq+0x54/0x88
[ 952.950000] [<800a501c>] generic_handle_irq+0x3c/0x4c
[ 952.950000] [<80064748>] do_IRQ+0x1c/0x34
[ 952.950000] [<80062d6c>] ret_from_irq+0x0/0x4
[ 952.950000] [<8007673c>] tasklet_action+0xb8/0xd4
[ 952.950000] [<80076c24>] __do_softirq+0xa0/0x154
[ 952.950000] [<80076e30>] do_softirq+0x48/0x68
[ 952.950000] [<80076f94>] local_bh_enable+0x94/0xb0
[ 952.950000] [<83406d60>] cfg80211_scan_done+0x670/0x6d0 [cfg80211]
[ 952.950000]
[ 952.950000] handlers:
[ 952.950000] [<83564d48>] ath_isr
[ 952.950000] Disabling IRQ #2
The test setup is using 30 AR9330 devices running OpenWRT 32727/33559. 32727
is using compat-wireless-2012-04-17 (+ many OpenWRT patches) and 33559 is
running compat-wireless-2012-09-07 (+many more patches from Felix). 1 device
is running an open AP device (standard OpenWRT settings) and 29 devices are
trying to connect. Random devices will now fail. To debug this problem, I used
one devices with 8 vif devices and restarted the network script again and
again to force the recreation of the vif and reconnect.
The stack trace doesn't seem to be very helpful. Therefore, I checked ath_isr
and noticed that the interrupts right before the device crash get the status 0
from ar9003_hw_get_isr. Digging a little but further also revealed that the
interrupts in the interrupt storm also have async_cause 0 and sync_cause 0x20.
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 hope that helps to track down the problem.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-10-02 15:02 UTC|newest]
Thread overview: 51+ 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-09-27 14:41 ` Sven Eckelmann
2012-10-02 10:33 ` [ath9k-devel] [PATCHv2] ath9k_hw: Handle AR_INTR_SYNC_HOST1_FATAL " Sven Eckelmann
2012-10-02 10:33 ` Sven Eckelmann
2012-10-02 13:13 ` [ath9k-devel] " Adrian Chadd
2012-10-02 13:13 ` Adrian Chadd
2012-10-02 13:33 ` [ath9k-devel] " Felix Fietkau
2012-10-02 13:33 ` Felix Fietkau
2012-10-02 13:35 ` Simon Wunderlich
2012-10-02 13:35 ` Simon Wunderlich
2012-10-02 14:06 ` [ath9k-devel] " Adrian Chadd
2012-10-02 14:06 ` Adrian Chadd
2012-10-02 15:02 ` Sven Eckelmann [this message]
2012-10-02 15:02 ` Sven Eckelmann
2012-10-02 15:20 ` [ath9k-devel] " Felix Fietkau
2012-10-02 15:20 ` Felix Fietkau
2012-10-03 14:51 ` Adrian Chadd
2012-10-03 14:51 ` Adrian Chadd
2012-10-05 11:08 ` Sven Eckelmann
2012-10-05 11:08 ` Sven Eckelmann
2012-10-05 12:34 ` Felix Fietkau
2012-10-05 12:34 ` Felix Fietkau
2012-10-05 13:07 ` Sven Eckelmann
2012-10-05 13:07 ` Sven Eckelmann
2012-10-05 13:24 ` Felix Fietkau
2012-10-05 13:24 ` Felix Fietkau
2012-10-05 15:03 ` Sven Eckelmann
2012-10-05 15:03 ` Sven Eckelmann
2012-10-05 15:15 ` Felix Fietkau
2012-10-05 15:15 ` Felix Fietkau
2012-10-05 16:05 ` Sven Eckelmann
2012-10-05 16:05 ` Sven Eckelmann
2012-10-05 16:21 ` Adrian Chadd
2012-10-05 16:21 ` Adrian Chadd
2012-10-05 16:51 ` Sven Eckelmann
2012-10-05 16:51 ` Sven Eckelmann
2012-10-05 23:48 ` Adrian Chadd
2012-10-05 23:48 ` Adrian Chadd
2012-10-06 9:03 ` Felix Fietkau
2012-10-06 9:03 ` Felix Fietkau
2013-02-21 11:14 ` Felix Liao
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=7670031.sYFb4t8Iqn@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.