linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
To: "Björn Smedman" <bjorn.smedman@venatech.se>
Cc: Bob Copeland <me@bobcopeland.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	"ath9k-devel@venema.h4ckr.net" <ath9k-devel@venema.h4ckr.net>
Subject: Re: [ath9k-devel] [RFC] ath9k: Insert wmb before linking dma descriptors
Date: Mon, 1 Nov 2010 23:45:33 +0100	[thread overview]
Message-ID: <20101101224533.5647.qmail@stuge.se> (raw)
In-Reply-To: <AANLkTikqw5oVTd66DeQGrPgyPAqh66dm6jCvNFSeHpQi@mail.gmail.com>

Björn Smedman wrote:
> long and unwanted weekend of debugging ath9k DMA errors

Yeah, I've seen those as well, especially with AR5008 but also AR9002.

I have severe intermittent issues with PCI functionality of an AR9280
card. It locks up in a state where it either returns absolute garbage
so severe that the kernel plain rejects it, or just mildly garbage
data so that it reports corrupt PCI ids. It can fix itself in a
running system, so that a later lspci shows the correct device ids
and the driver actually loads and runs.

I typically get PCI fatal interrupts after resurrecting the card
(that takes a couple of power cycles including removing the laptop
battery). I don't suppose anyone can explain *in detail* what causee
these issues and what could be done to fix them?

Finally I've also experienced complete system lockup after a
previously working system was left on but idle overnight.

All this fun with commit 2d10d8737ccdba752d60106abbc6ed4f37404923 but
I believe these problems are nothing new.


//Peter

  parent reply	other threads:[~2010-11-01 22:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 20:55 [RFC] ath9k: Insert wmb before linking dma descriptors Björn Smedman
2010-10-05 13:17 ` John W. Linville
2010-10-05 19:50   ` [ath9k-devel] " Luis R. Rodriguez
2010-10-09 15:19     ` Björn Smedman
2010-10-09 15:23       ` Felix Fietkau
2010-10-28 23:36         ` Ben Greear
2010-10-28 23:45           ` Felix Fietkau
2010-10-29  0:57             ` Luis R. Rodriguez
2010-11-01 15:44               ` Björn Smedman
2010-11-01 17:17                 ` Bob Copeland
2010-11-01 18:49                   ` Björn Smedman
2010-11-01 18:56                     ` Bob Copeland
2010-11-01 22:45                     ` Peter Stuge [this message]
2010-11-01 22:51                       ` Ben Greear

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=20101101224533.5647.qmail@stuge.se \
    --to=peter@stuge.se \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=bjorn.smedman@venatech.se \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=me@bobcopeland.com \
    /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).