I had this when turning on and off the Wireless option from Network Manager manually. I attached gdb to the process and got the attached stack trace. I then continued execution, saw the CPU usage go up again, interrupted and got exactly the same stack trace. So this should represent at least some of what's going on in this situation.
** Attachment added: "stacktrace from gdb attaching to the busy process" http://launchpadlibrarian.net/39212253/ntop-461141-stacktrace.log -- ntop produces 100% CPU load after suspend https://bugs.launchpad.net/bugs/461141 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
