All of lore.kernel.org
 help / color / mirror / Atom feed
From: mfidelman@meetinghouse.net (Miles Fidelman)
To: kernelnewbies@lists.kernelnewbies.org
Subject: reboot.c and X86-64 architectures
Date: Tue, 03 Apr 2012 23:22:42 -0400	[thread overview]
Message-ID: <4F7BBE82.50701@meetinghouse.net> (raw)
In-Reply-To: <4F79E6BE.4030302@meetinghouse.net>


Hello Folks,

Perhaps someone here can help me understand the behavior of the kernel reboot code.

I've recently migrated from running a 32bit kernel to a 64bit one
(specifically Debian Lenny 32bit environment to 2.6.32-5-xen-amd64 on
top of xen-4.0-amd64 hypervisor build).

This is a somewhat older, and apparently quirky, hardware box.  I've
found that the only way to reboot it, short of power cycling, is jumping
through the bios - using the "reboot=bios" kernel option at boot time
works just fine for an X86_32 kernel.  But... this doesn't work with the
64bit kernel.

Pouring through both the documentation and the code for
arch/x86/kernel/reboot.c yields the very specific admonition (in comments
describing command-line kernel options), that reboot=bios (Reboot by jumping
through the BIOS) only applies to X86_32 - and the case statements in the
code seem to align with the comment.

None of the other available command line options seem to work with my
hardware, which leads to two questions:

1. What's the logic behind this?  Why not enable a bios reboot for 64bit
kernels?  Anybody know the history?

2. Anybody know a workaround, short of patching and compiling a custom
kernel? Are there other paths through the reboot code that can invoke a bios
reboot?  (Note: None of the available command line options seem to work on
this particular box/bios combination, and kexec-reboot is not available
for this combination of kernel and hypervisor).

Thank you very much,

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra

  reply	other threads:[~2012-04-04  3:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <S1753510Ab2DBRUx/20120402172053Z+301@vger.kernel.org>
2012-04-02 17:49 ` QUESTION: reboot.c and X86-64 architectures Miles Fidelman
2012-04-04  3:22   ` Miles Fidelman [this message]
2012-04-04 13:34     ` Jim Cromie
2012-04-04 13:48       ` Miles Fidelman
2012-04-05  5:54         ` Srivatsa S. Bhat
2012-04-05 12:58           ` Miles Fidelman
2012-04-05 13:28             ` Srivatsa S. Bhat

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=4F7BBE82.50701@meetinghouse.net \
    --to=mfidelman@meetinghouse.net \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.