From: Sven Eckelmann <sven@narfation.org>
To: Felix Fietkau <nbd@openwrt.org>
Cc: ath9k-devel@lists.ath9k.org, adrian.chadd@gmail.com,
linux-wireless@vger.kernel.org, shafi.wireless@gmail.com,
lindner_marek@yahoo.de,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Subject: Re: Re: [RFC] ath9k: Work around complete stuck of hw
Date: Sun, 23 Sep 2012 12:04:47 +0200 [thread overview]
Message-ID: <1822413.FOnaUoKYHo@sven-desktop.home.narfation.org> (raw)
In-Reply-To: <5053160B.8060908@openwrt.org>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
On Friday 14 September 2012 13:33:31 Felix Fietkau wrote:
[..]
> > ---
> > This check is currently tested. This takes quite a long time and maybe
> > someone with more knowledge of atheros devices can check whether this one
> > is completely and utterly wrong.
> >
> > The type RESET_TYPE_FATAL_INT was chosen in this test to allow us to see
> > whether this condition was already true by reading from
> > /sys/kernel/debug/ieee80211/phy0/ath9k/reset
>
> Your debug patch should not be silent when it resets the hw. We need
> to make sure that this bug gets fixed properly. If my patch below does
> not fix it, then at least add a WARN_ON to ensure that we don't just
> hide the bug and move on.
It is not silent for me and is not a patch that should be applied to the
upstream kernel. Just wanted to ask whether this is the right place and
approach
> Somebody on the openwrt-devel list pointed out that there is some code
> missing in the ar933x wmac reset function. Please try this patch (apply
> it to your kernel tree):
Neither mine nor your patch has an effect. One node is now again dead after ~8
1/2 days. It looks like the check isn't done (correctly). I will investigate
this further tomorrow.
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-09-23 10:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 16:53 AR9330 hornet board stops beaconing after a few days (0xdeadbeef) Simon Wunderlich
2012-08-19 22:04 ` Simon Wunderlich
2012-08-22 5:20 ` Mohammed Shafi
2012-08-22 18:57 ` Adrian Chadd
2012-08-23 9:28 ` Simon Wunderlich
2012-08-23 17:10 ` Gabor Juhos
2012-08-23 19:26 ` Adrian Chadd
2012-08-23 14:59 ` Mohammed Shafi
2012-08-23 15:19 ` Sven Eckelmann
2012-08-23 15:27 ` Sven Eckelmann
2012-09-02 20:01 ` Simon Wunderlich
2012-09-03 13:53 ` Mohammed Shafi
2012-09-03 14:34 ` Sven Eckelmann
2012-09-04 17:12 ` Simon Wunderlich
2012-09-05 5:12 ` Mohammed Shafi
2012-09-05 14:08 ` Adrian Chadd
2012-09-05 14:20 ` Sven Eckelmann
2012-09-13 16:51 ` Simon Wunderlich
2012-09-13 16:59 ` Adrian Chadd
2012-09-13 17:55 ` [OpenWrt-Devel] " Felix Fietkau
2012-09-14 9:47 ` [RFC] ath9k: Work around complete stuck of hw Sven Eckelmann
2012-09-14 11:33 ` Felix Fietkau
2012-09-23 10:04 ` Sven Eckelmann [this message]
2013-11-20 20:57 ` [OpenWrt-Devel] AR9330 hornet board stops beaconing after a few days (0xdeadbeef) Bastian Bittorf
2013-11-20 21:00 ` Sven Eckelmann
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=1822413.FOnaUoKYHo@sven-desktop.home.narfation.org \
--to=sven@narfation.org \
--cc=adrian.chadd@gmail.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=lindner_marek@yahoo.de \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=shafi.wireless@gmail.com \
--cc=siwu@hrz.tu-chemnitz.de \
/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;
as well as URLs for NNTP newsgroup(s).