From: Andy Pfiffer <andyp@osdl.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
suparna@in.ibm.com, Linus Torvalds <torvalds@transmeta.com>,
Dave Hansen <haveblue@us.ibm.com>,
Werner Almesberger <wa@almesberger.net>
Subject: Re: [PATCH] kexec for 2.5.54
Date: 07 Jan 2003 14:46:00 -0800 [thread overview]
Message-ID: <1041979560.12674.93.camel@andyp> (raw)
In-Reply-To: <m1fzs6j0bh.fsf_-_@frodo.biederman.org>
On Sun, 2003-01-05 at 21:48, Eric W. Biederman wrote:
>
> O.k. I have switched to using the init_mm and premapping the reboot
> code buffer.
<snip>
> The code in machine_kexec now takes no locks and is drop dead simple,
> so it should be safe to call from a panic handler.
Eric,
The patch applies cleanly to 2.5.54 for me. Current behavior matches
the version of kexec for 2.5.48 that I carried forward into 2.5.52 and
2.5.54 (and kexec_tools 1.8):
- the kexec-ed kernel starts rebooting and finds all of my system's
memory, so the generic kexec machinery is working as expected.
- the kexec-ed kernel hangs while calibrating the delay loop. The list
of kernels I attempted to reboot includes permutations of 2.5.48 +/-
kexec, 2.5.52 +/- kexec(from 2.5.48), 2.5.54, 2.5.54 + kexec(from
2.5.48), and 2.5.54 + kexec (recent patch from you).
- Whatever it is that SuSE supplies in 8.0 (2.4.x +) panics near/during
frame buffer initialization when rebooted via kexec for 2.5.54:
.
.
.
Initializing CPU#0
Detected 799.665 MHz Processor
Console: colour VGA+ 80x25
invalid operand: 0000
CPU: 0
EIP: 0010[<00000007>] Not tainted
EFLAGS 00010002
.
.
.
Something has definitely changed in the 2.5.5x series, and the symptoms
indicate that at least the clock interrupt is not being received.
kexec for 2.5.48 worked for me (with some limits), so I should be able
to walk the tree forwards and poke at it some more.
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.
Regards,
Andy
next prev parent reply other threads:[~2003-01-07 22:37 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 [this message]
2003-01-07 23:01 ` Dave Hansen
2003-01-07 23:11 ` Martin J. Bligh
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=1041979560.12674.93.camel@andyp \
--to=andyp@osdl.org \
--cc=ebiederm@xmission.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suparna@in.ibm.com \
--cc=torvalds@transmeta.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).