From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: lists@ssl-mail.com
Cc: Juergen Gross <JGross@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Daniel Kiper <daniel.kiper@oracle.com>,
xen-devel@lists.xen.org
Subject: Re: Xen 4.7.0 boot PANIC on kernel 4.7.0-4 + UEFI ?
Date: Fri, 29 Jul 2016 11:42:05 -0400 [thread overview]
Message-ID: <20160729154205.GD20996@char.us.oracle.com> (raw)
In-Reply-To: <1469803017.3031782.680431321.4B531B9D@webmail.messagingengine.com>
On Fri, Jul 29, 2016 at 07:36:57AM -0700, lists@ssl-mail.com wrote:
> On Wed, Jul 27, 2016, at 09:34 AM, Andrew Cooper wrote:
> > This looks suspiciously like the issue which was fixed by c/s
> > d6b186c1e2d852a92c43f090d0d8fad4704d51ef "x86/xen: avoid m2p lookup when
> > setting early page table entries", but that fix is present in Linux 4.7.0
> >
> > Can you check to see whether the commit is included in your kernel?
> >
> > Failing that, can you find out exactly where the kernel crashed? You
> > need to manually decode ffffffff81f6374c with the debug symbols.
> >
> > ~Andrew
>
> Is an eventual fix to whatever is causing this crash likely in the kernel or Xen code?
>
> I've managed to try a couple of different kernels, older version, with no luck. Crash still happens.
>
> Getting my hands on an older Xen package is turning out to be a bit tougher. Still working on it.
>
> Not sure what specifically changed to break this , since this server clearly was running not that long ago.
did you apply the patch that Vitaly pointed out?
>
> I'd like to at least figure out what I can drop back to so I can get my server and guests back up and running.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-29 15:42 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 23:32 Xen 4.7.0 boot PANIC on kernel 4.7.0-4 + UEFI ? lists
2016-07-27 1:43 ` lists
2016-07-27 15:50 ` Andrew Cooper
2016-07-27 16:21 ` lists
2016-07-27 16:34 ` Andrew Cooper
2016-07-27 16:54 ` lists
2016-07-27 16:56 ` Andrew Cooper
2016-07-27 18:22 ` lists
2016-07-27 18:28 ` Andrew Cooper
2016-07-27 18:36 ` lists
2016-07-28 0:28 ` lists
2016-07-28 0:53 ` lists
2016-07-28 1:09 ` Konrad Rzeszutek Wilk
2016-07-28 17:20 ` lists
2016-07-28 18:21 ` Daniel Kiper
2016-07-28 18:25 ` lists
2016-07-28 19:05 ` Daniel Kiper
2016-07-28 19:06 ` lists
2016-07-29 14:36 ` lists
2016-07-29 15:42 ` Konrad Rzeszutek Wilk [this message]
2016-07-29 15:57 ` lists
2016-07-29 16:03 ` Konrad Rzeszutek Wilk
2016-07-29 16:12 ` lists
2016-08-01 20:11 ` lists
2016-08-01 22:27 ` [BUG] " lists
2016-08-02 6:57 ` Jan Beulich
2016-08-02 13:16 ` lists
2016-08-02 19:02 ` lists
2016-08-03 9:01 ` Jan Beulich
2016-08-03 13:33 ` lists
2016-08-03 13:57 ` Jan Beulich
2016-08-03 14:03 ` Andrew Cooper
2016-08-03 14:50 ` lists
2016-08-03 15:41 ` lists
2016-08-04 15:21 ` lists
2016-07-28 14:09 ` Vitaly Kuznetsov
2016-07-28 14:18 ` lists
2016-07-27 18:33 ` Juergen Gross
2016-08-02 6:36 ` Jan Beulich
2016-08-02 13:13 ` lists
2016-08-02 13:38 ` Jan Beulich
2016-08-02 13:54 ` lists
2016-08-02 14:13 ` Jan Beulich
2016-08-02 14:25 ` lists
2016-08-02 14:50 ` Jan Beulich
2016-08-02 15:04 ` lists
2016-08-02 15:55 ` Jan Beulich
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=20160729154205.GD20996@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JGross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=lists@ssl-mail.com \
--cc=xen-devel@lists.xen.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.