From: Larry Finger <larry.finger@lwfinger.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: bcm43xx-dev@lists.berlios.de, Michael Buesch <mb@bu3sch.de>,
wireless <linux-wireless@vger.kernel.org>,
linux-wireless@vger.kernel.org,
John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] bcm43xx: Fix loss of association after resume
Date: Sat, 10 Feb 2007 14:33:51 -0600 [thread overview]
Message-ID: <45CE2C2F.8070502@lwfinger.net> (raw)
In-Reply-To: <200702101811.37355.rjw@sisk.pl>
Rafael,
Rafael J. Wysocki wrote:
>
> I'm running with this patch applied right now, but the association is lost
> after the resume anyway. I have to reload bcm43xx to make it associate with
> the AP again (no big deal).
Please send me the output of iwconfig and ifconfig after the resume, but before you reload bcm43xx.
Will the interface recover with any measure less drastic than reloading? Does an ifdown/ifup
sequence do the trick?
Thanks,
Larry
next prev parent reply other threads:[~2007-02-10 20:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 16:18 [PATCH] bcm43xx: Fix loss of association after resume Larry Finger
2007-02-09 16:53 ` Michael Buesch
2007-02-10 17:11 ` Rafael J. Wysocki
2007-02-10 20:33 ` Larry Finger [this message]
2007-02-11 12:56 ` Rafael J. Wysocki
2007-02-11 13:07 ` Michael Buesch
2007-02-11 14:02 ` Rafael J. Wysocki
2007-02-11 14:14 ` Michael Buesch
2007-02-11 14:41 ` Johannes Berg
2007-02-11 14:45 ` Rafael J. Wysocki
2007-02-11 14:48 ` Johannes Berg
2007-02-11 15:59 ` Larry Finger
2007-02-11 16:03 ` Michael Buesch
2007-02-11 16:16 ` Michael Buesch
2007-02-11 16:17 ` Larry Finger
2007-02-12 0:50 ` Rafael J. Wysocki
2007-02-12 1:18 ` Larry Finger
2007-02-12 20:48 ` Rafael J. Wysocki
2007-02-12 22:20 ` Larry Finger
2007-02-12 23:08 ` Rafael J. Wysocki
2007-02-12 23:18 ` Larry Finger
2007-02-12 23:24 ` Michael Buesch
2007-02-13 16:25 ` Rafael J. Wysocki
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=45CE2C2F.8070502@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--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;
as well as URLs for NNTP newsgroup(s).