From: Marcel Holtmann <marcel@holtmann.org>
To: Bob Copeland <me@bobcopeland.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Dan Williams <dcbw@redhat.com>,
linux-wireless@vger.kernel.org, mabbaswireless@gmail.com
Subject: Re: [PATCH v2 0/3] mac80211 suspend/resume
Date: Wed, 24 Dec 2008 08:16:29 +0100 [thread overview]
Message-ID: <1230102989.16960.14.camel@californication> (raw)
In-Reply-To: <20081224054951.GA32398@hash.localnet>
Hi Bob,
> > > Running pm-suspend from pm-utils directly also triggers the problem,
> > > so that would seem to excuse gnome-power-manager at least.
> >
> > What's the status of this? Should I look into things a bit?
>
> Well, I guess I should have noticed this a lot earlier, but anyway the
> problem was pm-utils on Fedora 10:
>
> /usr/lib/pm-utils/sleep.d/55NetworkManager:
>
> suspend_nm()
> {
> # Tell NetworkManager to shut down networking
> dbus-send --system \
> --dest=org.freedesktop.NetworkManager \
> /org/freedesktop/NetworkManager \
> org.freedesktop.NetworkManager.sleep
> }
>
> I really don't think this is necessary (g-p-m will also do it if you
> set the proper gconf setting.)
this should not be needed at all. I have systems running wpa_supplicant
and not any of the pm-utils scripts messing with it. During suspend and
later resume it indicates normally just only a new handshake with the AP
or a disconnect if the AP got out of range.
I think Network Manager is perfectly capable of handling state changes
from wpa_supplicant. I really do think that this hack only exists of
some broken drivers from really old kernels or for the 0.6 version of
Network Manager. Remember that Ubuntu's suspend/resume solution used to
be to unload all networking drivers on suspend.
Regards
Marcel
next prev parent reply other threads:[~2008-12-24 7:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 3:50 [PATCH v2 0/3] mac80211 suspend/resume Bob Copeland
2008-12-15 10:14 ` Johannes Berg
2008-12-15 15:22 ` Dan Williams
2008-12-15 9:28 ` Luis R. Rodriguez
2008-12-17 18:21 ` Bob Copeland
2008-12-23 20:30 ` Johannes Berg
2008-12-24 5:49 ` Bob Copeland
2008-12-24 7:16 ` Marcel Holtmann [this message]
2009-01-06 16:45 ` Dan Williams
2009-01-06 17:07 ` Bob Copeland
2009-01-06 17:14 ` Johannes Berg
2009-01-06 17:35 ` Bob Copeland
2009-01-06 17:43 ` Johannes Berg
2009-01-06 18:01 ` Bob Copeland
2009-01-06 18:16 ` Johannes Berg
2009-01-06 17:12 ` Marcel Holtmann
2009-01-06 18:52 ` Dan Williams
2009-01-06 19:36 ` Marcel Holtmann
2009-01-06 20:05 ` Johannes Berg
2009-01-09 23:53 ` Tomas Winkler
2009-01-10 9:27 ` Johannes Berg
2009-01-11 11:11 ` Tomas Winkler
2009-01-11 14:40 ` Bob Copeland
2009-01-08 16:39 ` Dan Williams
2009-01-09 7:55 ` Kalle Valo
2009-01-09 16:35 ` Dan Williams
2009-01-09 16:44 ` Kalle Valo
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=1230102989.16960.14.camel@californication \
--to=marcel@holtmann.org \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mabbaswireless@gmail.com \
--cc=me@bobcopeland.com \
/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