Return-path: Received: from mail.candelatech.com ([208.74.158.172]:58044 "EHLO ns3.lanforge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750966Ab0KAWvq (ORCPT ); Mon, 1 Nov 2010 18:51:46 -0400 Message-ID: <4CCF4457.9040703@candelatech.com> Date: Mon, 01 Nov 2010 15:51:03 -0700 From: Ben Greear MIME-Version: 1.0 To: Peter Stuge CC: =?UTF-8?B?QmrDtnJuIFNtZWRtYW4=?= , linux-wireless , "ath9k-devel@venema.h4ckr.net" , Bob Copeland , "John W. Linville" Subject: Re: [ath9k-devel] [RFC] ath9k: Insert wmb before linking dma descriptors References: <20101005131744.GB4074@tuxdriver.com> <20101005195039.GD11831@tux> <4CB0890D.3050208@openwrt.org> <4CCA0908.6000105@candelatech.com> <4CCA0B26.5010008@openwrt.org> <20101101224533.5647.qmail@stuge.se> In-Reply-To: <20101101224533.5647.qmail@stuge.se> Content-Type: text/plain; charset=UTF-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 11/01/2010 03:45 PM, Peter Stuge wrote: > 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. I think at least some of that DEADBEAF stuff was related to the DMA bugs. Since we applied all of those patches, we haven't seen those problems..but we also haven't been testing a whole lot lately..waiting for wireless-testing to finish merging in those tx-dma patches before we continue... Thanks, Ben > > > //Peter > _______________________________________________ > ath9k-devel mailing list > ath9k-devel@lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel -- Ben Greear Candela Technologies Inc http://www.candelatech.com