From: Michael Leun <lkml20120218@newton.leun.net>
To: Ben Greear <greearb@candelatech.com>
Cc: Mohammed Shafi <shafi.wireless@gmail.com>,
casteyde.christian@free.fr,
Kelly Anderson <kelly@silka.with-linux.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: 3.4-rc ath9k regression (Re: [ath9k-devel] 3.3.1 ath9k regression)
Date: Mon, 9 Apr 2012 01:08:16 +0200 [thread overview]
Message-ID: <20120409010816.36244f17@xenia.leun.net> (raw)
In-Reply-To: <4F7F52BD.7060906@candelatech.com>
After an suspend to disk / resume cycle (in kernel suspend to disk,
openSuSE) with 3.4-rc2 my ath9k wireless does not ping
anymore.
Output of iwconfig wlan0 looks just as usual (associated to AP).
iwconfig wlan0 essid <myssid> fixes this (causes an
deauthenticate/authenticate with AP) - then connectivity is there again.
Guess what: "Of course" does not happen when reverting
c1afdaff90538ef085b756454f12b29575411214 ath9k: fix going to full-sleep
on PS idle.
So, in my opinion it should be seriously considered to revert that patch
until it is fully understood what is going on and why.
It may look theoretically correct (I've no knowledge that would enable
me assess that), but it seems to have caused 3 more or less different
problems to various people.
--
MfG,
Michael Leun
next prev parent reply other threads:[~2012-04-08 23:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 5:46 3.3.1 ath9k regression Kelly Anderson
2012-04-03 6:01 ` Ben Greear
2012-04-03 6:26 ` [ath9k-devel] " 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
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 ` Michael Leun [this message]
2012-04-09 6:28 ` 3.4-rc ath9k regression (Re: [ath9k-devel] 3.3.1 ath9k regression) 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
2012-04-04 10:40 ` Mantas M.
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=20120409010816.36244f17@xenia.leun.net \
--to=lkml20120218@newton.leun.net \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=casteyde.christian@free.fr \
--cc=greearb@candelatech.com \
--cc=kelly@silka.with-linux.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
all inboxes | Powered by JetHome®