NetworkManager causes high CPU-usage after suspend
Bug #154254 reported by
Stephan Sailer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
After upgrading to Gutsy, NetworkManager starts a second process after wakeup from suspend-to-RAM. One process causes up to 100% CPU-usage and is only killable with "kill -9" - HUP doesn't work. The other process of NetworkManager seems to work perfectly.
My System is a "IBM Thinkpad T41" with an Intel Gigabit LAN-Adaptor ("e1000") and an Intel IPW2915ABG WLAN-Card ("ipw2200"). I'm running Linux-kernel 2.6.22-14-generic without any patches on the network-drivers.
To post a comment you must log in.
I have the same symptoms. I can kill -9 NetworkManager and restart it and everything seems to be fine at that point.
lspci says my wireless is this: 8139C/8139C+ (rev 10)
Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)
and my wire (which I don't use) is this:
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/