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.
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.