From: ebiederm@xmission.com (Eric W. Biederman)
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Andy Pfiffer <andyp@osdl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Suparna Bhattacharya <suparna@in.ibm.com>,
Petr Vandrovec <VANDROVE@vc.cvut.cz>,
fastboot@osdl.org, Werner Almesberger <wa@almesberger.net>
Subject: Re: [Fastboot] [CFT] kexec syscall for 2.5.43 (linux booting linux)
Date: 22 Oct 2002 02:33:04 -0600 [thread overview]
Message-ID: <m1fzuyub3z.fsf@frodo.biederman.org> (raw)
In-Reply-To: <m1ptu3t3ec.fsf@frodo.biederman.org>
Ok as promised kexec-tools-1.3.tar.gz is released.
The new test case it provides is
kexec -debug bzImage
The serial console must be initialized before using this.
[root@p4dp8-0 root]# kexec -debug bzImage-2.4.17.eb-amd768-eepro100-kexec-apic-lb-mtd2 ip=dhcp root=/dev/nfs console=tty0 console=ttyS0,9600 reboot=hard panic=5 ide0=ata66 verbose
setup16_end: 00091ac4
Shutting down devices
kexecing image
a
b
c
d
e
f
g
h
< All above are various points in x86-setup-16.S >
i < Printed from the first callback in setup.S, before protected mode is entered >
j < Printed from the second callback in setup.S, just before the kernel decompresser is run >
I have a very strange node that makes it all of the way to 'j' before rebooting.
The concept that something is dying in protected mode will all of the interrupts
disabled is so novel that I really don't know what to make of it, yet.
But I would be very interested if other people had similar experiences.
Eric
next prev parent reply other threads:[~2002-10-22 8:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 19:59 [CFT] kexec syscall for 2.5.43 (linux booting linux) Eric W. Biederman
[not found] ` <20021018173248.E14894@almesberger.net>
[not found] ` <m1bs5rz1d6.fsf@frodo.biederman.org>
[not found] ` <20021018231540.C7951@almesberger.net>
[not found] ` <20021019025309.A24579@almesberger.net>
[not found] ` <m17kgfyltc.fsf@frodo.biederman.org>
[not found] ` <20021019040600.D7951@almesberger.net>
2002-10-19 9:34 ` Eric W. Biederman
2002-10-19 17:18 ` Werner Almesberger
2002-10-19 17:37 ` Eric W. Biederman
2002-10-21 23:11 ` [Fastboot] " Andy Pfiffer
2002-10-22 4:18 ` Eric W. Biederman
2002-10-22 6:04 ` Eric W. Biederman
2002-10-22 8:33 ` Eric W. Biederman [this message]
2002-10-22 3:57 ` Rob Landley
2002-10-22 14:48 ` Eric W. Biederman
2002-10-22 16:02 ` Eric W. Biederman
2002-10-22 16:27 ` erich
2002-10-23 2:23 ` Eric W. Biederman
2002-10-22 16:30 ` erich
2002-10-22 23:27 ` Andy Pfiffer
2002-10-22 23:32 ` Andy Pfiffer
2002-10-22 8:30 ` Werner Almesberger
2002-10-22 8:55 ` Eric W. Biederman
2002-10-22 23:17 ` Andy Pfiffer
2002-10-23 6:29 ` Eric W. Biederman
2002-10-23 17:11 ` Andy Pfiffer
2002-10-24 17:10 ` Eric W. Biederman
2002-10-28 7:45 ` Kasper Dupont
2002-10-28 8:24 ` Eric W. Biederman
2002-10-28 8:48 ` Kasper Dupont
2002-10-28 17:14 ` Eric W. Biederman
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=m1fzuyub3z.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=VANDROVE@vc.cvut.cz \
--cc=andyp@osdl.org \
--cc=fastboot@osdl.org \
--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