linux-kernel - 3.4-rc ath9k regression (Re: [ath9k-devel] 3.3.1 ath9k regression)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120409010816.36244f17@xenia.leun.net>
Date:	Mon, 9 Apr 2012 01:08:16 +0200
From:	Michael Leun <lkml20120218@...ton.leun.net>
To:	Ben Greear <greearb@...delatech.com>
Cc:	Mohammed Shafi <shafi.wireless@...il.com>,
	casteyde.christian@...e.fr,
	Kelly Anderson <kelly@...ka.with-linux.com>,
	"ath9k-devel@...ts.ath9k.org" <ath9k-devel@...ema.h4ckr.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Felix Fietkau <nbd@...nwrt.org>,
	linux-wireless Mailing List <linux-wireless@...r.kernel.org>
Subject: 3.4-rc ath9k regression (Re: [ath9k-devel] 3.3.1 ath9k regression)

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/