Bug 300289

Summary:	Main-menu uses 100% when unsuspending
Product:	[openSUSE] openSUSE 10.3	Reporter:	Federico Mena Quintero <federico>
Component:	Network	Assignee:	James Krehl <jimmyk>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	coolo, florin
Version:	Alpha 7	Flags:	coolo: SHIP_STOPPER-
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Federico Mena Quintero 2007-08-14 15:02:56 UTC

This seems to be the same as bug #191903, but for 10.3.  Main-menu uses 100% CPU when unsuspending.  I think NetworkManager is sending it thousands of notifications while it reconnects (it shouldn't!), and then main-menu wants to regenerate its icons or something.

Comment 1 Mark Gordon 2007-08-14 18:42:54 UTC

Any evidence of such notifications? What network hardware/driver do you have?

Comment 2 Federico Mena Quintero 2007-08-14 20:50:58 UTC

Just a Thinkpad T42p with the Intel ProWireless stuff.

If you get a stack trace of the code while it is spinning, you'll see that the only way that code can execute is through a NM notification.  Actually, the NetworkManager daemon shares the CPU load with main-menu:  about 30% NM, and about 70% main-menu (though of course it varies).

Comment 3 Petr Baudis 2007-09-11 12:56:23 UTC

*** Bug 309478 has been marked as a duplicate of this bug. ***

Comment 4 Petr Baudis 2007-09-11 15:02:25 UTC

This can make the system quite unusable for the portion of users not skilled enough to kill mainmenu manually in large portion of suspend/resume cases. I think this should be marked critical.

Comment 5 Stephan Kulow 2007-09-18 06:11:56 UTC

*** Bug 252043 has been marked as a duplicate of this bug. ***

Comment 6 James Krehl 2007-09-18 17:52:16 UTC


*** This bug has been marked as a duplicate of bug 307862 ***