All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] "Failed to stop Tx DMA" and "Could not stop RX" with AR9485
Date: Thu, 01 Mar 2012 18:22:55 +0100	[thread overview]
Message-ID: <4F4FB06F.6030201@openwrt.org> (raw)
In-Reply-To: <20120301144642.13047.qmail@stuge.se>

On 2012-03-01 3:46 PM, Peter Stuge wrote:
> Mohammed Shafi wrote:
>> disabling power save would be a nice idea,  to see if this issue
>> disappears.
> 
> I can not understand why Atheros insists on recommending "disable
> power saving" in response to this error which has been pouring out
> of ath9k hardware and driver for YEARS!
> 
> It's baffling.
> 
> Work with someone who has hardware clue and just fix the problem.
If you weren't so locked up in your bitching and moaning habit, you
might have noticed that just because the error messages are similar does
not mean that it's just one bug that has been lurking in the driver for
years.

Just because one ore more symptoms are the same does not mean that the
issue has just one cause, or always leads to the same connectivity issues.

I remember at least 5 different issues that I fixed myself, which had
all led to these exact symptoms, but were otherwise unrelated to each
other and had different side effects.

On most chips with recent kernels, these issues tend to not be fatal
anymore, and at least on embedded hardware it's getting much harder to
find people that can still produce connection stability issues.

Sometimes I wonder why you keep wasting your energy on these rants,
which do *nothing* to fix the underlying issues. In fact, while I'm
writing this I wonder why I bother to respond, but I guess my answer is
simply to provide some perspective for people that might stumble upon
one of your mindless rants for the first time.

If your intention really is to improve the situation, then please use
your time to do something useful instead of writing such garbage.

  parent reply	other threads:[~2012-03-01 17:22 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 21:35 [ath9k-devel] "Failed to stop Tx DMA" and "Could not stop RX" with AR9485 Kim Lidström
2012-02-29 21:35 ` Kim Lidström
2012-02-29 21:50 ` [ath9k-devel] " Adrian Chadd
2012-02-29 21:50   ` Adrian Chadd
2012-02-29 23:52 ` [ath9k-devel] " Adrian Chadd
2012-02-29 23:52   ` Adrian Chadd
2012-03-01  5:09 ` [ath9k-devel] " Mohammed Shafi
2012-03-01  5:09   ` Mohammed Shafi
2012-03-01  5:53   ` [ath9k-devel] " Kim Lidström
2012-03-01  5:53     ` Kim Lidström
2012-03-01 16:23     ` [ath9k-devel] " Mieszko Ślusarczyk
2012-03-02  6:21       ` Kim Lidström
2012-03-01 14:46   ` Peter Stuge
2012-03-01 15:04     ` Mohammed Shafi
2012-03-01 17:50       ` Ben Greear
2012-03-01 18:01         ` Peter Stuge
2012-03-01 19:05         ` Sune Mølgaard
2012-03-01 17:02     ` Adrian Chadd
2012-03-01 17:23       ` Peter Stuge
2012-03-01 17:22     ` Felix Fietkau [this message]
2012-03-01 17:53       ` Peter Stuge
2012-03-01 18:13         ` Felix Fietkau
2012-03-01 18:42           ` Peter Stuge
2012-03-01 18:51             ` Peter Stuge
2012-03-01 19:18             ` Felix Fietkau
2012-03-01 19:53               ` Peter Stuge
2012-03-01 20:26                 ` Adrian Chadd
2012-03-01 20:40                 ` Felix Fietkau
2012-03-01 21:27                   ` Peter Stuge
2012-03-02  0:38                     ` Sujith Manoharan
2012-03-02  2:21                       ` Peter Stuge
2012-03-07 17:29 ` Felix Fietkau
2012-03-07 17:29   ` Felix Fietkau
2012-03-07 18:35   ` Paul Farrow
2012-03-07 18:37   ` Paul Farrow
2012-03-07 19:42     ` Felix Fietkau
2012-03-07 19:55       ` Paul Farrow

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=4F4FB06F.6030201@openwrt.org \
    --to=nbd@openwrt.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.