Messages in this thread | | | Date | Thu, 14 Feb 2008 13:27:58 -0800 | From | "Tony Luck" <> | Subject | Re: Strange hang on ia64 with CONFIG_PRINTK_TIME=y |
| |
On Wed, Feb 13, 2008 at 7:47 PM, Roland Dreier <rdreier@cisco.com> wrote: > The strange thing is that Ingo's patch to make cpu_clock() a NOP until > after sched_init() didn't fix things for me...
Very strange. I threw in an output line counter into the printk code() ... if I disable the timestamps for the first 30 lines, then everything is good (so the basic timestamping code does still work on ia64). But I would have thought that Ingo's delay until sched_init() ought to be long enough too. Clearly I need to figure out exactly what needs to be initialized to prevent the hang/crash.
-Tony
| |