From: Mikael Pettersson <mikpe@it.uu.se>
To: linux-kernel@vger.kernel.org
Cc: hpa@zytor.com, mingo@redhat.com, tglx@linutronix.de
Subject: [PATCH] fix i486 boot failure due to stale %ds
Date: Sun, 4 Nov 2007 17:44:04 +0100 (MET) [thread overview]
Message-ID: <200711041644.lA4Gi4Ms013028@harpo.it.uu.se> (raw)
On Mon, 29 Oct 2007 01:05:58 +0100 (MET), Mikael Pettersson wrote:
>My old 486 fails to boot with the 2.6.24-rc1 kernel.
>Grub loads it, 4 lines of text appear but not the kernel's
>"Linux version <blah> greet", and the machine reboots.
>Double-checked with a serial console: nothing appears
>before it reboots.
>
>All 2.6 kernels up to 2.6.23 worked fine on this machine.
Problem identified and solved.
The last good kernel was 2.6.23-git17. The change in 2.6.23-git18
that broke my 486 was a24e785111a32ccb7cebafd24b1b1cb474ea8e5d,
which included the following:
>--- a/arch/x86/boot/compressed/head_32.S
>+++ b/arch/x86/boot/compressed/head_32.S
>@@ -27,13 +27,22 @@
> #include <asm/segment.h>
> #include <asm/page.h>
> #include <asm/boot.h>
>+#include <asm/asm-offsets.h>
>
> .section ".text.head","ax",@progbits
> .globl startup_32
>
> startup_32:
>- cld
>- cli
>+ /* check to see if KEEP_SEGMENTS flag is meaningful */
>+ cmpw $0x207, BP_version(%esi)
>+ jb 1f
>+
>+ /* test KEEP_SEGMENTS flag to see if the bootloader is asking
>+ * us to not reload segments */
>+ testb $(1<<6), BP_loadflags(%esi)
>+ jnz 2f
>+
>+1: cli
> movl $(__BOOT_DS),%eax
> movl %eax,%ds
> movl %eax,%es
That is, it added loads from %ds:offset(%esi) before the code
that sanitises %ds et al. Commenting out these loads and tests
made the kernel boot again.
Adding debugging code to head_32.S and decompress_kernel(),
I found that startup_32 actually is invoked with a good %ds
(== 0x18 == __BOOT_DS) and a flat 4GB data segment in the
corresponding GDT entry.
Since data accesses work after %ds is (re)loaded with __BOOT_DS,
it's clear that on this machine, the hidden registers behind %ds
are stale on entry to startup_32. After adding a patch to reload
%ds with itself (not __BOOT_DS) at startup_32 the kernel doesn't
crash and reboot any more on this machine.
The machine in question is a ca 1993 vintage Siemens 486 with
a Quadtel S3 / Phoenix BIOS from 1994, booting via grub-0.95-13
from Fedora Core 4.
Signed-off-by: Mikael Pettersson <mikpe@it.uu.se>
---
arch/x86/boot/compressed/head_32.S | 5 +++++
1 files changed, 5 insertions(+)
--- linux-2.6.24-rc1-git13/arch/x86/boot/compressed/head_32.S.~1~ 2007-11-04 16:34:33.000000000 +0100
+++ linux-2.6.24-rc1-git13/arch/x86/boot/compressed/head_32.S 2007-11-04 16:44:15.000000000 +0100
@@ -33,6 +33,11 @@
.globl startup_32
startup_32:
+ /* workaround for BIOSen or boot loaders that don't reload %ds
+ after changing the GDT (insane but unfortunately true) */
+ movl %ds,%eax
+ movl %eax,%ds
+
cld
/* test KEEP_SEGMENTS flag to see if the bootloader is asking
* us to not reload segments */
next reply other threads:[~2007-11-04 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 16:44 Mikael Pettersson [this message]
2007-11-04 18:29 ` H. Peter Anvin
2007-11-04 19:00 ` H. Peter Anvin
2007-11-04 19:38 Mikael Pettersson
2007-11-04 19:41 ` H. Peter Anvin
2007-11-04 21:58 Mikael Pettersson
2007-11-04 22:20 ` H. Peter Anvin
2007-11-04 23:05 ` Andi Kleen
2007-11-04 23:07 ` Jeremy Fitzhardinge
2007-11-04 23:12 ` H. Peter Anvin
2007-11-04 23:50 ` H. Peter Anvin
2007-11-05 0:15 ` Linus Torvalds
2007-11-05 0:23 ` Linus Torvalds
2007-11-04 23:51 ` H. Peter Anvin
2007-11-05 1:18 Mikael Pettersson
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=200711041644.lA4Gi4Ms013028@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®