From: Konrad Eisele <konrad@xxxxxxxxxxx> Date: Tue, 17 Apr 2012 08:37:50 +0200 > 2. What happens next > > CPU1 will boot up and execute schedule(). > ... > -> kernel/core.c:__schedule() The stop thread doesn't actually run immediately when it is created, so will need to be woken up to be scheduled and run. At wakeup time, set_task_cpu() should fix things up and make the task have a correct ->cpu in it's thread_info. I wonder if one of the sparc32 global cpu masks isn't being initialized properly. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
