From: Meelis Roos <mroos@xxxxx> Date: Thu, 21 Aug 2008 12:13:21 +0300 (EEST) > Some it seems something is causing the CPU to get stuck in either after > libata detection or during ohci detection and then even sysrq does not > work. It's getting hung in the setup of some module it seems. I did some looking again, and it turns out that "initcall_debug" does work for modules, rejoice! Please add "initcall_debug" to the kernel boot command line, that will print the last module initialization function that gets called right before it hangs. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
