From: ebiederm@xmission.com (Eric W. Biederman)
To: landley@trommello.org
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 08:48:43 -0600 [thread overview]
Message-ID: <m17kgattpw.fsf@frodo.biederman.org> (raw)
In-Reply-To: <200210212257.40050.landley@trommello.org>
Rob Landley <landley@trommello.org> writes:
> On Tuesday 22 October 2002 03:33, Eric W. Biederman wrote:
>
> > 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.
>
> It would almost have to be the MMU. Any way to dump the page tables?
I don't know yet. I need to find a way to install some additional hooks
at run time so I can narrow down where the failure is occuring. I
will have to look, but I should be able to set up an interrupt
descriptor table and single step through the code.
What has me very puzzled is that I can boot that same kernel if I run
a substitute for setup.S that makes a similar set of BIOS calls.
The kernel I am having problems with is an old 2.4.17 kernel. But
more than anything my goal is to make the boot process debuggable
without requiring a recompile. So I can ask users to throw a switch
and I can find out where things are failing.
I may be able to recompile that 2.4.17 kernel and then edit the build
so I can get more debug information. But if it is my preference to
attempt to track down what is happening without doing that.
Especially as it is more useful if that does not happen.
The compressor in misc.c runs without a page table enabled, so it may
be something before the page tables are enabled.
Eric
next prev parent reply other threads:[~2002-10-22 14:44 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
2002-10-22 3:57 ` Rob Landley
2002-10-22 14:48 ` Eric W. Biederman [this message]
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=m17kgattpw.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=VANDROVE@vc.cvut.cz \
--cc=andyp@osdl.org \
--cc=fastboot@osdl.org \
--cc=landley@trommello.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