Return-path: Received: from ar100.montanavision.com ([216.146.103.100]:43881 "EHLO silka.with-linux.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751582Ab2DCIjA (ORCPT ); Tue, 3 Apr 2012 04:39:00 -0400 Message-ID: <4F7AB6FE.3080009@silka.with-linux.com> (sfid-20120403_103920_735435_0E5AA395) Date: Tue, 03 Apr 2012 02:38:22 -0600 From: Kelly Anderson MIME-Version: 1.0 To: Mohammed Shafi CC: Ben Greear , "ath9k-devel@lists.ath9k.org" , Linux Kernel Mailing List , Felix Fietkau , linux-wireless Mailing List Subject: Re: [ath9k-devel] 3.3.1 ath9k regression References: <4F7A8EB7.4060200@silka.with-linux.com> <4F7A923D.5000002@candelatech.com> <4F7A9D5C.8040402@silka.with-linux.com> <4F7AAAD9.2040307@silka.with-linux.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 04/03/2012 02:04 AM, Mohammed Shafi wrote: > On Tue, Apr 3, 2012 at 1:22 PM, Mohammed Shafi wrote: >>> I just tried the unpatched kernel with pcie_aspm=off. The device shows up >>> with ifconfig, >>> but it will not connect to the access point. >> oh, ok in addition does disabling power save helps ? Setting ath9k power management off makes no difference. > also please provide the logs sudo modprobe -v ath9k debug=0xe01 when > the STA is not able to connect I'm using systemd with kmod, so I'm not sure that the modprobe -v is giving you anything useful. The output of the modprobe -v is nothing. The systemd journal has these entries (which are truncated due to the way systemd-journal handles piped out) Apr 03 02:26:50 comer.internal kernel: Registered led device: ath9k-phy1 Apr 03 02:26:50 comer.internal kernel: ieee80211 phy1: Atheros AR9280 Rev:2...16 >> -- >> thanks, >> shafi > >