linux-kernel - Re: 2.6.31-rc5 regression: ath5k broken after suspend-to-ram

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20090809170401.GB16332@sig21.net>
Date:	Sun, 9 Aug 2009 19:04:01 +0200
From:	Johannes Stezenbach <js@...21.net>
To:	Bob Copeland <me@...copeland.com>
Cc:	ath5k-devel@...ts.ath5k.org, linux-wireless@...r.kernel.org,
	linux-kernel@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: 2.6.31-rc5 regression: ath5k broken after suspend-to-ram

On Sun, Aug 09, 2009 at 12:06:03PM -0400, Bob Copeland wrote:
> On Fri, Aug 7, 2009 at 5:51 PM, Johannes Stezenbach<js@...21.net> wrote:
> 
> > If I use nl80211 the second ifup fails with
> > "SIOCSIFFLAGS: Input/output error" messages and the follwing
> > is in dmesg:
> >
> >   ath5k phy0: failed to wakeup the MAC Chip
> >   ath5k phy0: can't reset hardware (-5)
> 
> Ok, does this patch help the above?
> 
> http://patchwork.kernel.org/patch/38550/

Yes, it helps a lot!  The above wakeup error is gone,
and as a result I can switch to use the wpa_supplicant
nl80211 driver.  With the nl80211 driver everything works.

However, with the wpa_supplicant wext driver the issue remains
that only the frst ifup after module load works, the second
ifup shows the association problem most of the time (but not always).
So this turns out to be a mix of two problems, with the wext one
not having anything to do with suspend/resume.

If you want me to test something wext related, let me know.
Otherwise I'm fine with using nl80211.

Thanks,
Johannes
--
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/