All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Bernhard Walle <bwalle@suse.de>
Cc: kexec@lists.infradead.org, Jamey Sharp <jamey@thetovacompany.com>
Subject: Re: kexec --real-mode
Date: Wed, 23 Apr 2008 07:00:57 -0700	[thread overview]
Message-ID: <m163u8oeli.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <20080423103400.6e3d9d90@strauss.suse.de> (Bernhard Walle's message of "Wed, 23 Apr 2008 10:34:00 +0200")

Bernhard Walle <bwalle@suse.de> writes:

> * Jamey Sharp [2008-04-22 16:44]:
>>
>> On Tue, Apr 22, 2008 at 6:16 AM, Bernhard Walle <bwalle@suse.de> wrote:
>> > did anybody try the --real-mode option with current release? I tried
>> > it on two machines, and on one machine it just reboots, on the other
>> > machine it hangs.
>> 
>> I think you're experiencing a bug that I just proposed a patch for. :-)
>> You can confirm that: try adding the "--debug" option to your kexec
>> call. If that works correctly, then I think you'll find that the patch
>> in "[PATCH 2/9] Fix copy-paste bug: entry16 does not start at
>> entry16_debug" will solve your problem. That's archived here:
>> 
>> http://lists.infradead.org/pipermail/kexec/2008-April/001581.html
>
> No, I used --debug already.

If this used to work when booting older kernels on your hardware.
Jamey's patch 3/9 might help.

Otherwise if this is the first time you are trying it you may
simply have encountered the reason that --real-mode is not the default.
BIOS can get really strange after the kernel has been running.

When I had that the default I only had around a 50% success rate or
something like that.

You might try booting kexec_test and see where that puts you.

Eric

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2008-04-23 14:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 13:16 kexec --real-mode Bernhard Walle
2008-04-22 23:44 ` Jamey Sharp
2008-04-23  8:34   ` Bernhard Walle
2008-04-23 14:00     ` Eric W. Biederman [this message]
2008-04-28  8:22       ` Bernhard Walle
2008-04-28 17:55         ` Eric W. Biederman
2008-04-29 15:58           ` Bernhard Walle
2008-04-29 17:15             ` Eric W. Biederman
2008-04-30  8:38               ` Bernhard Walle
2008-04-30 19:35                 ` Eric W. Biederman
2008-04-30 21:08                   ` Jamey Sharp

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=m163u8oeli.fsf@frodo.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=bwalle@suse.de \
    --cc=jamey@thetovacompany.com \
    --cc=kexec@lists.infradead.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.