Return-path: Received: from mail-bw0-f46.google.com ([209.85.214.46]:51020 "EHLO mail-bw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752828Ab0FUUQ5 (ORCPT ); Mon, 21 Jun 2010 16:16:57 -0400 Subject: Re: [ath5k-devel] [PATCH v2] ath5k: disable ASPM From: Maxim Levitsky To: "Luis R. Rodriguez" Cc: David Quan , Bob Copeland , "Luis R. Rodriguez" , Jussi Kivilinna , ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org, linux-kernel In-Reply-To: References: <20100528100901.14580.1322.stgit@fate.lan> <1276806785.20754.8.camel@maxim-laptop> <20100618112026.17623g6uhdjk8hts@naisho.dyndns.info> <1276856142.9114.1.camel@maxim-laptop> <20100618134930.124225d4fsi8w1fk@naisho.dyndns.info> <1276859156.19554.2.camel@maxim-laptop> <1276870309.23783.3.camel@maxim-laptop> <1276933774.16697.11.camel@maxim-laptop> <1277032723.9555.12.camel@maxim-laptop> Content-Type: text/plain; charset="UTF-8" Date: Mon, 21 Jun 2010 23:16:50 +0300 Message-ID: <1277151410.5409.33.camel@maxim-laptop> Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: Luis, let me explain again, exactly the situation: First of all AR5001 and AR5001X devices (former was usualy listed as AR2425, and I have it, later I don't know about much), don't work well with ASPM L0s enabled. I told that many times, but I tell again. As soon as card it put on medium to high transmit load (for example even if transmission consists mostly of TCP ACK packets), it dies. Usualy it will stop transmitting, and then after few seconds it will send RXORN intrrupt to the host, even though the channel was idle. (Tested by sending a stream of UDP packets on channel that is neighbor free). I didn't see it, but some users reported seeing jumbo frames at this time as well. Overall it doesn't matter because card just goes south. A reset sometimes brings card to life, sometimes causes another storm of RXORN and sometimes just results in quiet dead card. A next reset might bring it to life, or not. Card (at least mine) advertises its as a 'pre pci 1.1 device'. Therefore if I enable CONFIG_PCIEASPM, the pci core will automaticly disable ASPM (both L0s and L1) on this card. I won't be surprised that windows does the same. Therefore the patch I sent it useless because it only works when CONFIG_PCIEASPM is enabled. In addition to that using the original version of this patch from Jussi Kivilinna contains code that disables ASPM (I modified it to disable only L0s) with or without CONFIG_PCIEASPM. But without CONFIG_PCIEASPM it uses open coded function that should belong to pci core. And it is also copied from e1000 which shouldn't do that too. Best regards, Maxim Levitsky