lkml.org 
[lkml]   [2008]   [Feb]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: Strange hang on ia64 with CONFIG_PRINTK_TIME=y
From
From: Ingo Molnar <mingo@elte.hu>
Date: Wed, 20 Feb 2008 09:12:28 +0100

>
> * Tony Luck <tony.luck@gmail.com> 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 <davem@davemloft.net>


\
 
 \ /
  Last update: 2008-02-20 09:17    [W:0.048 / U:0.548 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site