On Sat, Jul 19, 2008 at 05:54:59PM -0400, Kyle McMartin wrote:
quoted text
> I'm *guessing* that umoddi3 or udivdi3 is doing an xmpyu or something,
> which since this is probably before fpu init, is trapping, which is
> trying to printk, which is recursively exploding.
> 

If my guess is right, this quick fix might work. Can you please test it,
as my a500 decided to have its scsi controller die in the middle of
this...

(Proper fix is probably to bring fpu bringup into head.S, since it will
 be necessary for any printk with CONFIG_PRINTK_TIME on. (Or bring back
 my use embedded libgcc patch, which was buggy on 32-bit. :\ ))

diff --git a/init/main.c b/init/main.c
index edeace0..729b150 100644
--- a/init/main.c
+++ b/init/main.c
@@ -560,9 +560,9 @@ asmlinkage void __init start_kernel(void)
 	tick_init();
 	boot_cpu_init();
 	page_address_init();
+	setup_arch(&command_line);
 	printk(KERN_NOTICE);
 	printk(linux_banner);
-	setup_arch(&command_line);
 	mm_init_owner(&init_mm, &init_task);
 	setup_command_line(command_line);
 	unwind_setup();
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/