mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lists@ssl-mail.com
To: linux-kernel@vger.kernel.org
Subject: [BUG] kernel 4.7 + Xen on UEFI boot crash.  patch ID'd & tested, just need to verify & get it into upstream
Date: Thu, 04 Aug 2016 09:01:55 -0700	[thread overview]
Message-ID: <1470326515.4029967.686078721.338EDF9E@webmail.messagingengine.com> (raw)

I'm running kernel 4.7/stable.

It's installed from Opensuse packages atm.

Using the current kernel causes a crash when booting Xen 4.7 on UEFI.  Referenced in this now ridiculously-long thread

	https://lists.xenproject.org/archives/html/xen-devel/2016-07/msg02758.html

In hunting down the problem, this specific code was asked about @ 'xen-devel' ML,

	@ https://lists.xenproject.org/archives/html/xen-devel/2016-07/msg02928.html

		While I see that you're running linux-4.7 could you please double-check
		that it has the following:

		commit 55f1ea15216a5a14c96738bd5284100a00ffa9dc
		Author: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>
		Date:   Tue May 31 11:23:43 2016 +0100

		    efi: Fix for_each_efi_memory_desc_in_map() for empty memmaps

A patch to the patch was proposed @ 'xen-devel' ML,

	https://lists.xen.org/archives/html/xen-devel/2016-08/msg00399.html

It seems to fix the problem.  Boot to Xen with kernel 4.7 no longer crashes.

But then THAT patched patch was questioned @ 'opensuse-kernel' ML

	https://lists.xenproject.org/archives/html/xen-devel/2016-08/msg00747.html

I'd just like to get to a correct fix & get it into upstream kernel, since that is what I'm told we need to wait for to get packages from the distro that have the patch & work.

Since it seems it IS a kernel problem, I was hoping someone here could help shortcircuit this back & forth between projects and get the fix into kernel code.

Thanks.

                 reply	other threads:[~2016-08-04 16:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1470326515.4029967.686078721.338EDF9E@webmail.messagingengine.com \
    --to=lists@ssl-mail.com \
    --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
all inboxes | Powered by JetHome®