Re: suspend/resume wired



On Thu, 2005-06-30 at 09:03 -0400, Bill Moss wrote:

> After an acpi suspend/resume, both e1000 and ipw2200 drivers are loaded 
> but the wired interface is not up. The patch fixes this by bringing up 
> all devices when NM wakes.

Ha!  I spent the CVS outage tracking this down and came up with a nearly
identical patch (see attached).

I'm not 100% sure it is right, because wireless comes up fine without
manually pushing it up.  So that makes me think wired should, too.  Or
maybe wireless isn't obeying the down and this patch is right and
another fix is needed elsewhere.

Not sure.

I do know that it solves my problem and fixes the bug.

	Robert Love

 src/nm-dbus-nm.c |   10 ++++++++++
 1 files changed, 10 insertions(+)

Index: src/nm-dbus-nm.c
===================================================================
RCS file: /cvs/gnome/NetworkManager/src/nm-dbus-nm.c,v
retrieving revision 1.13
diff -u -u -r1.13 nm-dbus-nm.c
--- src/nm-dbus-nm.c	30 Jun 2005 14:29:49 -0000	1.13
+++ src/nm-dbus-nm.c	30 Jun 2005 14:47:04 -0000
@@ -436,6 +436,16 @@
 		nm_info  ("Waking up from sleep.");
 		app_data->asleep = FALSE;
 
+		/* Physically up all devices */
+		nm_lock_mutex (app_data->dev_list_mutex, __FUNCTION__);
+		for (elt = app_data->dev_list; elt; elt = g_slist_next (elt))
+		{
+			NMDevice *dev = (NMDevice *)(elt->data);
+
+			nm_device_bring_up (dev);
+		}
+		nm_unlock_mutex (app_data->dev_list_mutex, __FUNCTION__);
+
 		nm_schedule_state_change_signal_broadcast (app_data);
 		nm_policy_schedule_device_change_check (data->data);
 	}


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]