From: Miles Fidelman <mfidelman@meetinghouse.net>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, peter.chubb@nicta.com.au,
michael.d.labriola@gmail.com, mjg@redhat.com
Subject: reboot via bios on X86_64?
Date: Mon, 09 Apr 2012 11:39:32 -0400 [thread overview]
Message-ID: <4F8302B4.8040901@meetinghouse.net> (raw)
[cc'd to maintainers of reboot.c]
Re. the 2.6.32.5 kernel (currently used in Debian stable), and this
seems to apply to
later ones as well:
The reboot code in arch/x86/kernel/reboot.c provides for rebooting
through the bios
by either a kernel option of "reboot=bios" or as automatically invoked
by quite
a few of the quirks case statements.
But... reboot=bios is enabled only when configured for 32-bit mode -
which just bit me
when I moved from a 32bit kernel to a 64bit one on an old P4 box, which
hangs on
reboot for all reboot options except reboot=bios when running in 32 bit
mode.
Which leads to two questions:
1. What's the logic behind this? Why not enable a bios reboot for 64bit
kernels? Is there any reason why the machine_real_restart code wouldn't
work just as well in 64bit mode? 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: someone suggested trying a kexec-reboot, but that's also
not supported on my configuration (running over a Xen hypervisor).]
Thank you very much,
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
next reply other threads:[~2012-04-09 15:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 15:39 Miles Fidelman [this message]
2012-04-09 15:51 ` reboot via bios on X86_64? Matthew Garrett
2012-04-09 17:26 ` Miles Fidelman
2012-04-09 17:32 ` Matthew Garrett
2012-04-09 17:57 ` Miles Fidelman
2012-04-09 17:59 ` H. Peter Anvin
2012-04-09 18:06 ` Miles Fidelman
2012-04-09 18:07 ` Matthew Garrett
2012-04-10 14:03 ` Miles Fidelman
2012-04-10 14:22 ` Matthew Garrett
2012-04-10 17:26 ` Miles Fidelman
2012-04-10 17:44 ` Matthew Garrett
2012-04-10 18:09 ` Miles Fidelman
2012-04-09 17:53 ` H. Peter Anvin
2012-04-09 18:07 ` Miles Fidelman
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=4F8302B4.8040901@meetinghouse.net \
--to=mfidelman@meetinghouse.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.d.labriola@gmail.com \
--cc=mingo@redhat.com \
--cc=mjg@redhat.com \
--cc=peter.chubb@nicta.com.au \
--cc=tglx@linutronix.de \
--cc=x86@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