> smp_prepare_cpus > smp: kicking cpu 1 > smp: kicking cpu 2 > smp: kicking cpu 3 That's odd. We should be seeing "Processor x found" or "Processor x is stuck" after each of those "kicking cpu" messages. Or do udbg and printk not work well together?