public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Jean Delvare <khali@linux-fr.org>
Cc: Vivek Goyal <vgoyal@in.ibm.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 03:32:33 -0700	[thread overview]
Message-ID: <m164c5pmim.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20061221102232.5a10bece.khali@linux-fr.org> (Jean Delvare's message of "Thu, 21 Dec 2006 10:22:32 +0100")

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.


Eric

diff --git a/arch/i386/boot/setup.S b/arch/i386/boot/setup.S
index 06edf1c..2868020 100644
--- a/arch/i386/boot/setup.S
+++ b/arch/i386/boot/setup.S
@@ -795,6 +795,7 @@ a20_done:
 
 #endif /* CONFIG_X86_VOYAGER */
 # set up gdt and idt and 32bit start address
+10: jmp	10b
 	lidt	idt_48				# load idt with 0,0
 	xorl	%eax, %eax			# Compute gdt_base
 	movw	%ds, %ax			# (Convert %ds:gdt to a linear ptr)
@@ -846,6 +847,7 @@ flush_instr:
 	subw	$DELTA_INITSEG, %si
 	shll	$4, %esi			# Convert to 32-bit pointer
 
+11: jmp	11b
 # jump to startup_32 in arch/i386/boot/compressed/head.S
 #	
 # NOTE: For high loaded big kernels we need a
@@ -862,6 +864,7 @@ code32:	.long	startup_32			# will be set to %cs+startup_32
 	.word	__BOOT_CS
 .code32
 startup_32:
+12: jmp	12b
 	movl $(__BOOT_DS), %eax
 	movl %eax, %ds
 	movl %eax, %es
@@ -869,12 +872,14 @@ startup_32:
 	movl %eax, %gs
 	movl %eax, %ss
 
+13: jmp	13b
 	xorl %eax, %eax
 1:	incl %eax				# check that A20 really IS enabled
 	movl %eax, 0x00000000			# loop forever if it isn't
 	cmpl %eax, 0x00100000
 	je 1b
 
+14: jmp	14b
 	# Jump to the 32bit entry point
 	jmpl *(code32_start - start + (DELTA_INITSEG << 4))(%esi)
 .code16

  parent reply	other threads:[~2006-12-21 10:33 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 [this message]
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
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=m164c5pmim.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=ak@suse.de \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@in.ibm.com \
    /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