public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Jean Delvare <khali@linux-fr.org>, 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 06:38:14 +0530	[thread overview]
Message-ID: <20061221010814.GA30299@in.ibm.com> (raw)
In-Reply-To: <m164c5pmim.fsf@ebiederm.dsl.xmission.com>

On Thu, Dec 21, 2006 at 03:32:33AM -0700, Eric W. Biederman wrote:
> Jean Delvare <khali@linux-fr.org> writes:
> 
> > On Thu, 21 Dec 2006 10:12:40 +0100, Jean Delvare wrote:
> >> On Wed, 20 Dec 2006 15:22:20 -0700, Eric W. Biederman wrote:
> >> > Ok.  Here is a small diff that inserts the infinite loops, between
> >> > each section of code in head.S  Procedurally please trying booting
> >> > this unmodified and see if it boots, then remove the infinite loop
> >> > until you come to the one where the system reboots instead of hangs.
> >> >
> >> > That should at least give me a good idea of where to look.
> >> > If 20 hangs and 21 still reboots we are into misc.c and the
> >> > decompressor.  And I will have to ask something different.
> >>
> >> OK, I'll start the tests now, I'll let you know the outcome when I'm
> >> done.
> >
> > Hm, that was quick... Even with your unmodified patch, the machine
> > still reboots. Does that make any sense to you?
> >
> > I can try installing a more recent system on the same hardware if it
> > helps.
> 
> 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 am using grub 0.97. So any dependency on lilo can be ruled out in this
case.

Following is my software environment.

gcc version 4.1.1 20061130 (Red Hat 4.1.1-43)
GNU ld version 2.17.50.0.6-2.el5 20061020

I got Intel Xeon machine.

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 4
model name      : Intel(R) Xeon(TM) CPU 3.40GHz
stepping        : 3
cpu MHz         : 3400.483
cache size      : 2048 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 1
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 5
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr
bogomips        : 6805.59
clflush size    : 64

Thanks
Vivek

  reply	other threads:[~2006-12-21 11:39 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 [this message]
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
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=20061221010814.GA30299@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