As you mentioned, CPU online caused panic when MTRR was on
on my system. I've only tested with no MTRR configuration. :-(
I'll investigate the problem but I'm not sure I can find
a resolution. (I know nothing about MTRR... )
Does anybody have an idea for the problem?
Thanks,
Kimi
On Tue, 18 Dec 2001 18:29:30 -0800 (PST)
"Randy.Dunlap" <rddunlap@osdl.org> wrote:
> Hi,
>
> I applied this patch to Linux 2.5.0 and tried to use it on
> a 2-way x86 system with dual Intel Pentium III's (1 GHz).
> Results:
> echo 0 > /proc/sys/kernel/cpu/1/online
> seems to work: "top" stops reporting about the second CPU.
>
> However,
> echo 1 > /proc/sys/kernel/cpu/1/online
> results in an Oops in set_mtrr_var_range_testing().
>
> (same oops that I had encountered when I ported the 2.4.5
> patch to 2.4.13)
>
> Does this work for you? I can connect a serial console to
> it and provide you with a complete oops report if you want
> that, and I'm available to help work on it.
>
> In linux/arch/i386/kernel/mtrr.c, the functions
> set_mtrr_var_range_testing() and
> set_mtrr_fixed_testing()
> need to have the "__init" removed from them, but this
> doesn't fix the oops problem.
>
> Thanks,
> --
> ~Randy
-- Kimio Suganuma <k-suganuma@mvj.biglobe.ne.jp>- 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/