Hi, I've spotted the following problem: In function start_kernel() (file init/main.c), there are two calls to printk(), followed by setup_arch(). However, if the kernel is configured to use timing information on calls to printk(), then printk() will call cpu_clock(), which uses per-cpu data. For ia64, the physical address for the per-cpu data is kept in ar.k3, which is only initialized in cpu_init(), which is called by setup_arch(), i.e. AFTER the calls to printk(). Regards, Christian Kandeler -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|