From: Kelly Anderson <kelly@silka.with-linux.com>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: Ben Greear <greearb@candelatech.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Felix Fietkau <nbd@openwrt.org>,
linux-wireless Mailing List <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] 3.3.1 ath9k regression
Date: Tue, 03 Apr 2012 02:38:22 -0600 [thread overview]
Message-ID: <4F7AB6FE.3080009@silka.with-linux.com> (raw)
In-Reply-To: <CAD2nsn0kogfuMhCN7tNNkiKF4PN-mG2Fa3gu0CGfw01qj-MWyg@mail.gmail.com>
On 04/03/2012 02:04 AM, Mohammed Shafi wrote:
> On Tue, Apr 3, 2012 at 1:22 PM, Mohammed Shafi<shafi.wireless@gmail.com> 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
>
>
next prev parent reply other threads:[~2012-04-03 8:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F7A8EB7.4060200@silka.with-linux.com>
[not found] ` <4F7A923D.5000002@candelatech.com>
2012-04-03 6:26 ` [ath9k-devel] 3.3.1 ath9k regression Mohammed Shafi
2012-04-03 6:49 ` Kelly Anderson
2012-04-03 7:16 ` Mohammed Shafi
2012-04-03 7:46 ` Kelly Anderson
2012-04-03 7:52 ` Mohammed Shafi
2012-04-03 8:04 ` Mohammed Shafi
2012-04-03 8:38 ` Kelly Anderson [this message]
2012-04-03 18:03 ` Michael Leun
2012-04-04 7:29 ` Mohammed Shafi
2012-04-04 15:03 ` Mohammed Shafi
2012-04-04 21:51 ` Michael Leun
2012-04-05 6:16 ` Mohammed Shafi
2012-04-05 13:53 ` Michael Leun
2012-04-05 18:25 ` Ben Greear
2012-04-06 5:11 ` Mohammed Shafi
2012-04-06 20:31 ` Ben Greear
2012-04-08 23:08 ` 3.4-rc ath9k regression (Re: [ath9k-devel] 3.3.1 ath9k regression) Michael Leun
2012-04-09 6:28 ` Mohammed Shafi
2012-04-09 8:45 ` Sergio Correia
2012-04-09 10:25 ` Michael Leun
2012-04-09 14:03 ` Michael Leun
2012-04-09 14:22 ` Mohammed Shafi
2012-04-09 15:29 ` Michael Leun
2012-04-10 5:48 ` Mohammed Shafi
2012-04-10 10:05 ` [ath9k-devel] 3.4-rc ath9k regression (Re: " Mohammed Shafi
2012-04-12 13:46 ` 3.4-rc ath9k regression (Re: [ath9k-devel] " Felix Fietkau
2012-04-12 13:58 ` Felipe Contreras
2012-04-12 15:35 ` Michael Leun
2012-04-12 18:11 ` Felix Fietkau
2012-04-12 19:28 ` Sergio Correia
2012-04-14 21:15 ` Felipe Contreras
2012-04-12 22:01 ` Michael Leun
2012-04-09 19:12 ` [ath9k-devel] 3.4-rc ath9k regression (Re: " Sujith Manoharan
2012-04-09 21:21 ` Michael Leun
2012-04-09 6:52 ` [ath9k-devel] 3.3.1 ath9k regression Mohammed Shafi
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=4F7AB6FE.3080009@silka.with-linux.com \
--to=kelly@silka.with-linux.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
--cc=shafi.wireless@gmail.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).