Still happens in current Gutsy after resuming from suspend. Had this several times. The only solution is to kill NetworkManager with -9 parameter and restart it through "sudo /etc/dbus-1/event.d/25NetworkManager restart"
Seems to happen if you suspend shortly after resume. After resume the nm-applet icon still shows a connection and then disables it so a computer with a red triangle is shown. If you suspend in this stage I get the 100% cpu problem after resume.
Oct 13 01:26:14 uber NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
Oct 13 01:26:15 uber gnome-power-manager: (user) Suspending computer because the power button has been pressed
Oct 13 01:26:15 uber NetworkManager: <debug> [1192231575.860382] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/net_00_01_4a_f4_96_7c').
Still happens in current Gutsy after resuming from suspend. Had this several times. The only solution is to kill NetworkManager with -9 parameter and restart it through "sudo /etc/dbus- 1/event. d/25NetworkMana ger restart"
Seems to happen if you suspend shortly after resume. After resume the nm-applet icon still shows a connection and then disables it so a computer with a red triangle is shown. If you suspend in this stage I get the 100% cpu problem after resume.
Oct 13 01:26:14 uber NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started... manager: (user) Suspending computer because the power button has been pressed device_ removed( ): Device removed (hal udi is '/org/freedeskt op/Hal/ devices/ net_00_ 01_4a_f4_ 96_7c') .
Oct 13 01:26:15 uber gnome-power-
Oct 13 01:26:15 uber NetworkManager: <debug> [1192231575.860382] nm_hal_
More information in syslog file.