From: Kimio Suganuma <k-suganuma@mvj.biglobe.ne.jp>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: <linux-kernel@vger.kernel.org>,
<large-discuss@lists.sourceforge.net>,
Heiko Carstens <Heiko.Carstens@de.ibm.com>,
Jason McMullan <jmcmullan@linuxcare.com>,
Anton Blanchard <antonb@au1.ibm.com>,
Greg Kroah-Hartman <ghartman@us.ibm.com>, <rusty@rustcorp.com.au>
Subject: Re: [ANNOUNCE] HotPlug CPU patch against 2.5.0
Date: Wed, 19 Dec 2001 16:17:00 -0800 [thread overview]
Message-ID: <20011219160402.3D14.K-SUGANUMA@mvj.biglobe.ne.jp> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0112181748040.20824-100000@dragon.pdx.osdl.net>
In-Reply-To: <20011213132557.5B3E.K-SUGANUMA@mvj.biglobe.ne.jp> <Pine.LNX.4.33L2.0112181748040.20824-100000@dragon.pdx.osdl.net>
Hi,
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>
next prev parent reply other threads:[~2001-12-20 0:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33L2.0112181748040.20824-100000@dragon.pdx.osdl.net>
2001-12-13 21:29 ` [ANNOUNCE] HotPlug CPU patch against 2.5.0 Kimio Suganuma
2001-12-13 22:44 ` Russell King
2001-12-14 0:20 ` Kimio Suganuma
2001-12-14 1:36 ` Dave Jones
2001-12-18 0:21 ` Pavel Machek
2001-12-20 0:17 ` Kimio Suganuma [this message]
2002-01-17 2:21 ` Randy.Dunlap
2002-01-17 7:28 ` Rusty Russell
2001-12-21 21:08 Grover, Andrew
2001-12-22 16:05 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011219160402.3D14.K-SUGANUMA@mvj.biglobe.ne.jp \
--to=k-suganuma@mvj.biglobe.ne.jp \
--cc=Heiko.Carstens@de.ibm.com \
--cc=antonb@au1.ibm.com \
--cc=ghartman@us.ibm.com \
--cc=jmcmullan@linuxcare.com \
--cc=large-discuss@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).