From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Dave Hansen <haveblue@us.ibm.com>, Andy Pfiffer <andyp@osdl.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
suparna@in.ibm.com, Werner Almesberger <wa@almesberger.net>
Subject: Re: [PATCH] kexec for 2.5.54
Date: Tue, 07 Jan 2003 15:11:42 -0800 [thread overview]
Message-ID: <29440000.1041981101@titus> (raw)
In-Reply-To: <3E1B5C44.1030302@us.ibm.com>
> ... taking poor Linus off the cc list
> Andy Pfiffer wrote:
>> For those that have had success w/ recent vintage kernels and kexec (>
>> 2.5.48), could I get a roll-call of your machine's hardware? Uniproc,
>> SMP, AGP, chipset, BIOS version, that kind of thing. lspci -v,
>> /cat/proc/cpuinfo, and maybe the boot-up messages would all be
>> appreciated.
>
> I've had it work on 2 IBM x86 boxes.
> 4/8-way SMP
> 1/4/16 GB RAM
> no AGP
> Intel Profusion Chipset and some funky IBM one
>
> It failed on the NUMA-Q's I tried it on. I haven't investigated any more thoroughly.
>
> If you want more details, let me know. But, I've never seen your "Calibrating delay loop..." problem. The last time I saw problems there was when I broke the interrupt stack patches. But, since those aren't in mainline, you shouldn't be seeing it.
Last time I saw calibrating delay loop problems, it just mean the other CPUs
weren't getting / acting upon IPIs. I might expect that on NUMA-Q, but the
INIT, INIT, STARTUP sequence on normal machines should kick the remote proc
pretty damned hard and reset it. You might want to add more APIC resetting
things (I think there are some in there that only NUMA-Q does right now ..
try turning those on).
M.
next prev parent reply other threads:[~2003-01-07 23:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-22 11:07 [PATCH][CFT] kexec (rewrite) for 2.5.52 Eric W. Biederman
2002-12-31 14:35 ` Suparna Bhattacharya
2003-01-03 10:37 ` Eric W. Biederman
2003-01-03 12:41 ` Suparna Bhattacharya
2003-01-04 20:34 ` Eric W. Biederman
2003-01-04 22:42 ` Eric W. Biederman
2003-01-06 5:48 ` [PATCH] kexec for 2.5.54 Eric W. Biederman
2003-01-07 22:46 ` Andy Pfiffer
2003-01-07 23:01 ` Dave Hansen
2003-01-07 23:11 ` Martin J. Bligh [this message]
2003-01-15 19:43 ` [2.5.58][KEXEC] Success! (using 2.5.54 version + kexec tools 1.8) Andy Pfiffer
2003-01-04 0:32 ` 2.5.54: Re: [PATCH][CFT] kexec (rewrite) for 2.5.52 Andy Pfiffer
2003-01-04 18:56 ` Eric W. Biederman
[not found] ` <m11y2w557p.fsf@frodo.biederman.org>
[not found] ` <20030204142426.A1950@in.ibm.com>
[not found] ` <m1d6m81ttu.fsf@frodo.biederman.org>
2003-02-06 15:56 ` [PATCH][WIP] Using kexec for crash dumps in LKCD Suparna Bhattacharya
2003-02-07 15:39 ` Suparna Bhattacharya
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=29440000.1041981101@titus \
--to=mbligh@aracnet.com \
--cc=andyp@osdl.org \
--cc=ebiederm@xmission.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suparna@in.ibm.com \
--cc=wa@almesberger.net \
/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).