From: Frans Pop <elendil@planet.nl>
To: linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Bob Copeland <me@bobcopeland.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [SOLVED][.32-rc1/2] ath5k: has become unreliable with .32-rc1
Date: Thu, 1 Oct 2009 02:35:27 +0200 [thread overview]
Message-ID: <200910010235.28904.elendil@planet.nl> (raw)
In-Reply-To: <200909300952.29106.elendil@planet.nl>
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
next prev parent reply other threads:[~2009-10-01 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 7:52 [.32-rc1/2] ath5k: has become unreliable with .32-rc1 Frans Pop
2009-09-30 12:24 ` Bob Copeland
2009-09-30 21:49 ` Frans Pop
2009-09-30 22:27 ` Rafael J. Wysocki
2009-10-01 0:35 ` Frans Pop [this message]
2009-10-01 8:52 ` [SOLVED][.32-rc1/2] " Johannes Berg
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=200910010235.28904.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=rjw@sisk.pl \
/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