From: Ingo Molnar <[EMAIL PROTECTED]> Date: Wed, 20 Feb 2008 09:12:28 +0100
> > * Tony Luck <[EMAIL PROTECTED]> wrote: > > > > Perhaps what is happening is that cpu0 comes online ... safely skips > > > over the early printk calls. Calls cpu_init() which sets up the > > > resources *it* needs (ar.k3 points to per-cpu space), and then > > > executes sched_init() which marks it safe for all printk's. Then > > > cpu1 comes up and does a printk before it gets to cpu_init(). > > > > I just tried Ingo's patch[1] on a 2.6.25-rc2 kernel with printk > > timestamps turned on ... and it booted just fine on my tiger4. The > > default path for non-boot cpus is from head.S to start_secondary(), > > and that calls cpu_init() pretty quickly. There shouldn't normally[2] > > be any printk() calls on the non-boot cpu before it is safe to do so. > > ok. I've queued up the patch again in sched.git, as a .25 fix. Can i add > your Tested-by and Acked-by tags? Acked-by: David S. Miller <[EMAIL PROTECTED]> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
