Public bug reported:
Binary package hint: network-manager
Yet Another Suspend Issue. This is subtle, so I figured I'd file it.
When waking from suspend, NM takes 100% CPU, and needs to be killed. I
haven't found it in /etc/init.d so i'm really not sure how to restart
it, so this requires a reboot. When rebooting after this, I usually get
the "unable to stop HAL" or something similar.
Since I get the HAL issue, I use:
* ipw2200 on a WPA network
* USB 320 GB ext. HD w. Fat32 & ext3 partition
* PreSonus Firebox (uses bebob in jack, when it's working)
* plethora of other ghetto Dell bits in their pre-linux laptops (Dell Inspiron
6000 with an ATi X300 using the OSS driver)
As usual with hardware, it's non deterministic. Fun!
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: hal manager network suspend
** Tags added: hal manager network suspend
--
Busylocks on wake from suspend with ipw2200 on WPA network
https://bugs.launchpad.net/bugs/175921
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
