After nearly two months with the fixed version, I think I identified a case were NetworkManager still use 100% CPU and needs to be killed. Here is the step to reproduce :
- hit the Fn+F4 key (= suspend-to-ram shortcut on my thinkpad X40)
- while the computer is suspending (blinking 'moon' led), close the lid (= closing the lid is configured to initiate a suspend-to-ram)
=> upon resume, NetworkManager will hang with 100% cpu.
Once hanged, NetworkManager needs to be killed with 'kill -9' and could be restarted (sudo /etc/dbus-1/event.d/25NetworkManager restart), but it will hang again at each subsequent resume from suspend-to-ram.
After nearly two months with the fixed version, I think I identified a case were NetworkManager still use 100% CPU and needs to be killed. Here is the step to reproduce :
- hit the Fn+F4 key (= suspend-to-ram shortcut on my thinkpad X40)
- while the computer is suspending (blinking 'moon' led), close the lid (= closing the lid is configured to initiate a suspend-to-ram)
=> upon resume, NetworkManager will hang with 100% cpu.
Once hanged, NetworkManager needs to be killed with 'kill -9' and could be restarted (sudo /etc/dbus- 1/event. d/25NetworkMana ger restart), but it will hang again at each subsequent resume from suspend-to-ram.
Hope it helps.