All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
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 09:50:14 -0800	[thread overview]
Message-ID: <4F4FB6D6.9040606@candelatech.com> (raw)
In-Reply-To: <CAD2nsn2siQGmfs02uva8_cgQjt+WfSFTf8qsT7Dwft6cS5zP7w@mail.gmail.com>

On 03/01/2012 07:04 AM, Mohammed Shafi wrote:
>> Work with someone who has hardware clue and just fix the problem.
>
> completely agree, we got to fix it.
>

There are folks with machines that can reproduce this very easily.

Maybe offer to rent their system for some short time to
see if you can reproduce it in your lab?

I tried just getting their NICs and putting them in my own
systems, but though I could occassionally get the error to print (maybe once
every 2 days under full load) nothing locked up.  It must be exacerbated by some
interaction with other system components and/or the environment...

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2012-03-01 17:50 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 [this message]
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
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=4F4FB6D6.9040606@candelatech.com \
    --to=greearb@candelatech.com \
    --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.