public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Disconnect <lkml@sigkill.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: [2.4][2.5][Trivial Patch] Bug in i386/kernel/process.c?
Date: 03 Jul 2003 12:26:15 -0400	[thread overview]
Message-ID: <1057249575.2372.18.camel@slappy> (raw)

I was poking into how to force a warm boot (found it easily enough) and
started reading process.c, where the details live.

We have:
static int reboot_mode;
int reboot_thru_bios;
                                                                                
static int __init reboot_setup(char *str)
{
...set reboot_mode/reboot_thru_bios according to reboot=...
}
__setup("reboot=", reboot_setup);

Farther down:
        /* Write 0x1234 to absolute memory location 0x472.  The BIOS
reads
           this on booting to tell it to "Bypass memory test (also warm
           boot)".  This seems like a fairly standard thing that gets
set by
           REBOOT.COM programs, and the previous reset routine did this
           too. */
                                                                                
        *((unsigned short *)0x472) = reboot_mode;
                                                                                (similar code farther down in !reboot_thru_bios)

....but reboot_mode doesn't seem to be initialized if you don't set it
via reboot=...? (Same for reboot_thru_bios)

A simple patch to use the defaults (according to the code comments) is
below; if this is right please push accordingly:

Its against 2.4 but should apply to 2.5 as well.
--- build-dis5-final/arch/i386/kernel/process.c.orig    2003-07-03 12:15:36.000000000 -0400
+++ build-dis5-final/arch/i386/kernel/process.c 2003-07-03 12:16:46.000000000 -0400
@@ -152,8 +152,8 @@
 __setup("idle=", idle_setup);
  
 static long no_idt[2];
-static int reboot_mode;
-int reboot_thru_bios;
+static int reboot_mode = 0x1234;
+int reboot_thru_bios = 1;
  
 #ifdef CONFIG_SMP
 int reboot_smp = 0;

-- 
Disconnect <lkml@sigkill.net>


             reply	other threads:[~2003-07-03 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03 16:26 Disconnect [this message]
2003-07-04 16:40 ` [2.4][2.5][Trivial Patch] Bug in i386/kernel/process.c? Disconnect

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=1057249575.2372.18.camel@slappy \
    --to=lkml@sigkill.net \
    --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