From: Vivek Goyal <vgoyal@in.ibm.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Andi Kleen <ak@suse.de>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Patch "i386: Relocatable kernel support" causes instant reboot
Date: Thu, 21 Dec 2006 08:43:26 +0530 [thread overview]
Message-ID: <20061221031326.GC30299@in.ibm.com> (raw)
In-Reply-To: <20061221141354.6d9ec3e6.khali@linux-fr.org>
On Thu, Dec 21, 2006 at 02:13:54PM +0100, Jean Delvare wrote:
> On Thu, 21 Dec 2006 06:38:14 +0530, Vivek Goyal wrote:
> > On Thu, Dec 21, 2006 at 03:32:33AM -0700, Eric W. Biederman wrote:
> > > Grr. I guessed the problem was to late in the game it seems the problem
> > > is in setup.S Before we switch to 32bit mode.
> > >
> > > Ok. There is almost enough for inference but here is a patch of stops
> > > for setup.S let's see if one of those will stop the reboots.
> > >
> > > I have a strong feeling that we are going to find a tool chain issue,
> > > but I'd like to find where we ware having problems before we declare
> > > that to be the case.
> >
> > Looks like it might be a tool chain issue. I took Jean's config file and
> > built my own kernel and I am able to boot the kernel. But I can't boot
> > his bzImage. I observed the same behaviour as jean is experiencing. It jumps
> > back to BIOS.
>
> I can only confirm that. I installed a more recent system on the same
> hardware, rebuilt a kernel from the same config file, and now it boots
> OK. So it's not related to the hardware. It has to be a compilation-time
> issue.
>
Hi Jean,
Looks like you have already trashed your setup. If not, is it possible to
upload the output of "objdump -D arch/i386/boot/setup.o"? This will give
some info regarding what assembler is doing.
Thanks
Vivek
next prev parent reply other threads:[~2006-12-21 13:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061220141808.e4b8c0ea.khali@linux-fr.org>
2006-12-20 14:00 ` Patch "i386: Relocatable kernel support" causes instant reboot Eric W. Biederman
[not found] ` <20061220214340.f6b037b1.khali@linux-fr.org>
2006-12-20 22:22 ` Eric W. Biederman
[not found] ` <20061221101240.f7e8f107.khali@linux-fr.org>
[not found] ` <20061221102232.5a10bece.khali@linux-fr.org>
2006-12-21 10:32 ` Eric W. Biederman
2006-12-21 1:08 ` Vivek Goyal
2006-12-21 12:32 ` Eric W. Biederman
2006-12-21 2:26 ` Vivek Goyal
2006-12-21 3:54 ` Vivek Goyal
2006-12-21 13:13 ` Jean Delvare
2006-12-21 3:13 ` Vivek Goyal [this message]
2006-12-21 13:59 ` Jean Delvare
2006-12-21 17:45 ` Alexander van Heukelum
2006-12-21 20:44 ` Vivek Goyal
2006-12-22 8:08 ` Jean Delvare
2006-12-22 10:40 ` Vivek Goyal
2006-12-22 22:22 ` Jean Delvare
2006-12-22 22:37 ` Eric W. Biederman
2006-12-26 12:43 ` Segher Boessenkool
2006-12-26 14:03 ` Jean Delvare
2006-12-27 4:00 ` Vivek Goyal
2006-12-27 4:25 ` Segher Boessenkool
2007-01-01 21:39 ` Jean Delvare
2007-01-02 6:11 ` Vivek Goyal
2007-01-02 9:29 ` Jean Delvare
2007-01-02 13:44 ` Segher Boessenkool
[not found] ` <20061221145401.07bfe408.khali@linux-fr.org>
2006-12-21 3:40 ` Vivek Goyal
2006-12-21 14:22 ` Jean Delvare
2006-12-21 4:41 ` Vivek Goyal
2006-12-21 8:55 ` Jean Delvare
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=20061221031326.GC30299@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
/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