From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Julien Grall' <julien.grall@arm.com>, 'Jan Beulich' <JBeulich@suse.com>
Cc: "xen-devel (xen-devel@lists.xenproject.org)"
<xen-devel@lists.xenproject.org>
Subject: Re: debian stretch dom0 + xen 4.9 fails to boot
Date: Wed, 7 Jun 2017 08:05:18 +0000 [thread overview]
Message-ID: <05f3d79bf06440ff86d756b9f56541b4@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <a973c4bf-088c-f3a7-0292-49fd8cb81a3b@arm.com>
> -----Original Message-----
> From: Julien Grall [mailto:julien.grall@arm.com]
> Sent: 06 June 2017 18:41
> To: Paul Durrant <Paul.Durrant@citrix.com>; 'Jan Beulich'
> <JBeulich@suse.com>
> Cc: xen-devel (xen-devel@lists.xenproject.org) <xen-
> devel@lists.xenproject.org>
> Subject: Re: [Xen-devel] debian stretch dom0 + xen 4.9 fails to boot
>
> Hi Paul,
>
> On 06/06/17 16:51, Paul Durrant wrote:
> >> -----Original Message-----
> >> From: Jan Beulich [mailto:JBeulich@suse.com]
> >> Sent: 06 June 2017 16:11
> >> To: Paul Durrant <Paul.Durrant@citrix.com>
> >> Cc: xen-devel (xen-devel@lists.xenproject.org) <xen-
> >> devel@lists.xenproject.org>
> >> Subject: Re: [Xen-devel] debian stretch dom0 + xen 4.9 fails to boot
> >>
> >>>>> On 06.06.17 at 16:32, <Paul.Durrant@citrix.com> wrote:
> >>> I've been having fun setting up a new test rig...
> >>>
> >>> I have a skull canyon NUC and I put debian stretch (rc4) on it (so that's a
> >>> 4.9 kernel) and then tried building and installing the latest Xen staging-
> 4.9
> >>> code. The system failed to boot... basically it got stuck before even
> >>> managing to get sufficiently into Xen to spit out anything on the console.
> >>> Xen 4.8 OTOH booted just fine so I started bisecting and after 14
> iterations
> >>> I got down to the following commit is being the problem:
> >>>
> >>> commit c0655e492e6b33e26ec9cd33f59725d0db89cdd0
> >>> Author: Juergen Gross <jgross@suse.com>
> >>> Date: Fri Mar 24 14:18:54 2017 +0100
> >>>
> >>> x86: split boot trampoline into permanent and temporary part
> >>>
> >>> The hypervisor needs a trampoline in low memory for early boot and
> >>> later for bringing up cpus and during wakeup from suspend. Today this
> >>> trampoline is kept completely even if most of it isn't needed later.
> >>>
> >>> Split the trampoline into a permanent part and a temporary part
> needed
> >>> at early boot only. Introduce a new entry at the boundary.
> >>>
> >>> Reduce the stack for wakeup code in order for the permanent
> >>> trampoline to fit in a single page. 4k of stack seems excessive, about
> >>> 3k should be more than enough.
> >>>
> >>> Add an ASSERT() to the linker script to ensure the wakeup stack is
> >>> always at least 3k.
> >>>
> >>> Signed-off-by: Juergen Gross <jgross@suse.com>
> >>> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> >>>
> >>> To verify this I checked out master, reverted that commit, and tried
> again.
> >>> The NUC still booted fine.
> >>
> >> Well, interesting, but I don't think it is very realistic to expect any
> >> fix with just the information you supply. There must be something
> >> rather special about that system, and likely it would help if we
> >> knew what that is. E.g. an unusual E820 map. Worse would be if
> >> they used memory outside of properly marked E820 regions in a
> >> way colliding with what we do.
> >>
> >> Otherwise I'm afraid we need to hope for you to debug the issue.
> >>
> >
> > Yes, I was posting this more a heads-up for the moment, so that 4.9 does
> not go out with this regression.
>
> I would have appreciated to be CCed in this e-mail as this concern 4.9
> release... Please take the habit to CC the release manager for anything
> targeting a release.
>
Yes, sorry I should have cc-ed... I was in a bit of a rush and forgot.
Cheers,
Paul
> Cheers,
>
> --
> Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-06-07 8:05 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 14:32 debian stretch dom0 + xen 4.9 fails to boot Paul Durrant
2017-06-06 15:11 ` Jan Beulich
2017-06-06 15:51 ` Paul Durrant
2017-06-06 16:28 ` Paul Durrant
2017-06-06 17:00 ` Boris Ostrovsky
2017-06-07 8:07 ` Jan Beulich
2017-06-07 8:09 ` Paul Durrant
2017-06-07 8:19 ` Paul Durrant
2017-06-07 14:05 ` Boris Ostrovsky
2017-06-07 8:07 ` Paul Durrant
2017-06-07 8:27 ` Jan Beulich
[not found] ` <5937D4FF02000078001602F6@suse.com>
2017-06-07 9:03 ` Juergen Gross
2017-06-07 9:05 ` Paul Durrant
2017-06-07 9:09 ` Andrew Cooper
2017-06-07 10:36 ` Paul Durrant
2017-06-07 11:06 ` Paul Durrant
2017-06-07 11:57 ` Juergen Gross
2017-06-07 12:02 ` Paul Durrant
2017-06-07 12:13 ` Juergen Gross
2017-06-07 12:19 ` Jan Beulich
2017-06-07 12:26 ` Paul Durrant
2017-06-07 12:34 ` Jan Beulich
2017-06-07 11:50 ` Jan Beulich
2017-06-07 11:55 ` Paul Durrant
2017-06-07 12:00 ` Jan Beulich
2017-06-07 12:46 ` Paul Durrant
2017-06-07 12:55 ` Jan Beulich
2017-06-07 15:06 ` Paul Durrant
2017-06-07 15:33 ` Jan Beulich
2017-06-07 15:40 ` Paul Durrant
2017-06-07 15:52 ` Jan Beulich
2017-06-08 12:42 ` Paul Durrant
2017-06-08 12:46 ` Juergen Gross
2017-06-08 13:18 ` Jan Beulich
2017-06-08 13:24 ` Paul Durrant
2017-06-09 12:19 ` Paul Durrant
2017-06-09 13:05 ` Jan Beulich
2017-06-09 13:52 ` Boris Ostrovsky
2017-06-09 15:14 ` Paul Durrant
2017-06-09 15:41 ` Jan Beulich
2017-06-09 15:47 ` Paul Durrant
2017-06-09 15:58 ` Jan Beulich
2017-06-12 8:14 ` Paul Durrant
2017-06-12 10:40 ` Jan Beulich
2017-06-12 10:44 ` Paul Durrant
2017-06-12 10:53 ` Paul Durrant
2017-06-12 11:12 ` Jan Beulich
2017-06-12 12:05 ` Paul Durrant
2017-06-12 12:25 ` Paul Durrant
2017-06-12 13:54 ` Jan Beulich
2017-06-12 14:28 ` Paul Durrant
2017-06-12 14:43 ` Paul Durrant
2017-06-12 15:03 ` Paul Durrant
2017-06-12 15:07 ` Jan Beulich
2017-06-12 15:21 ` Paul Durrant
2017-06-06 17:40 ` Julien Grall
2017-06-07 8:05 ` Paul Durrant [this message]
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=05f3d79bf06440ff86d756b9f56541b4@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=JBeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).