linux-kernel - Re: [SOLVED][.32-rc1/2] ath5k: has become unreliable with .32-rc1

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: <200910010235.28904.elendil@planet.nl>
Date:	Thu, 1 Oct 2009 02:35:27 +0200
From:	Frans Pop <elendil@...net.nl>
To:	linux-wireless@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, Bob Copeland <me@...copeland.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [SOLVED][.32-rc1/2] ath5k: has become unreliable with .32-rc1

On Wednesday 30 September 2009, Frans Pop wrote:
> The first time I booted .32-rc1 (reboot from .31-rc5), wireless came up
> without problems, but failed to come back after suspend to RAM. I could
> only get wireless back by ejecting and re-inserting the PCMCIA card.
>
> The second and third time I booted .32-rc1 (to write this report; a cold
> boot and a ".32 to .32" reboot), wireless did not come up at all.
> See attached dmesg. The last part is after 'ifup ath0'. It seems to
> associate, but then for some reason immediately deauthenticates again.

Both issues are solved with current mainline. Probably the resume issue by 
Rafael's PCMCIA patch (the "late" config restore messages for ath5k are 
back too), the boot issue by one of Johannes' patches (I'd guess either 
4be3bd8c 'cfg80211: don't set privacy w/o key' or maybe 8bb89485
'cfg80211: always get BSS').

Still strange that iwlagn continued to work. Although, come to think of it, 
I have not cold booted that laptop recently.

Cheers,
FJP
--
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/