From mboxrd@z Thu Jan 1 00:00:00 1970 From: "John L. Poole" Subject: Re: Xen 4.12.0-rc Hangs Around masked ExtINT on CPU# Date: Mon, 27 May 2019 15:35:21 -0700 Message-ID: References: <9288a3b8-8c59-c80f-68f3-14aaca9272d4@gmail.com> <5C99DD160200007800221D00@prv1-mh.provo.novell.com> <25b66cdf-94ad-6af1-de5f-e0f5369ae000@gmail.com> <5C9B30D002000078002220F5@prv1-mh.provo.novell.com> <1fccf915-9d0b-52ac-4d6d-df16194dabb0@gmail.com> <5C9B86FA0200007800222232@prv1-mh.provo.novell.com> <20190429120238.b4kjlmkpk5l2t6yb@Air-de-Roger> <20190429152734.qy34zz56e43pawvf@Air-de-Roger> <20190527161832.arry25rh4chyxkio@Air-de-Roger> Reply-To: jlpoole56@gmail.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1139027853598050043==" Return-path: In-Reply-To: <20190527161832.arry25rh4chyxkio@Air-de-Roger> Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" To: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= Cc: Jan Beulich , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============1139027853598050043== Content-Type: multipart/alternative; boundary="------------93230702A7A3F237FA18D691" Content-Language: en-US This is a multi-part message in MIME format. --------------93230702A7A3F237FA18D691 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 5/27/2019 9:18 AM, Roger Pau Monné wrote: > On Mon, Apr 29, 2019 at 05:27:34PM +0200, Roger Pau Monné wrote: >> IMO it would be better if you can build directly from the upstream git >> repository [0], that way you could use git-bisect(1) in order to figure >> out which commit broke your system. For example: >> >> # git clone git://xenbits.xen.org/xen.git >> # cd xen >> # git checkout RELEASE-4.7.0 >> # make xen -j8 >> >> That should give you a set of Xen binaries in the xen/ directory, IIRC >> you are booting from EFI so you likely need xen/xen.efi. >> >> If that works, then you can test RELEASE-4.8.0 and if that fails to >> boot you should have a range of commits that you can bisect in order >> to find the culprit. > FWIW, I've been unable to find a box with the same CPU model (C2750) > that you are using. I've found a couple of old Atom boxes using > different CPUs but they all seem to boot fine using latest > xen-unstable. I've looked on eBay for that CPU but everything > containing it is server-grade and >200$ which I'm sadly not going to > pay. > > Unless you are able to bisect the tree and give us the bad commit > that's causing your issues I'm afraid at least myself I won't be able > to progress this any further, sorry. > > Roger. I attempted to work backwards and ran into a nightmare with Gentoo.   I kept getting compiler errors which I suspect was a result of having a newer version of GCC and other things.  It's not an easy thing to travel back in time in Gentoo because everything keeps getting upgraded.  I just cannot make the time now to unravel this as I have some demands on my time and will be engaged for the next four to six weeks. How much would it cost for you to obtain the machine you need? I may consider paying for it. I bought this Atom server just to economically run Xen so the machine has marginal value to me if I cannot run Xen on it. John --------------93230702A7A3F237FA18D691 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit


On 5/27/2019 9:18 AM, Roger Pau Monné wrote:
On Mon, Apr 29, 2019 at 05:27:34PM +0200, Roger Pau Monné wrote:

IMO it would be better if you can build directly from the upstream git
repository [0], that way you could use git-bisect(1) in order to figure
out which commit broke your system. For example:

# git clone git://xenbits.xen.org/xen.git
# cd xen
# git checkout RELEASE-4.7.0
# make xen -j8

That should give you a set of Xen binaries in the xen/ directory, IIRC
you are booting from EFI so you likely need xen/xen.efi.

If that works, then you can test RELEASE-4.8.0 and if that fails to
boot you should have a range of commits that you can bisect in order
to find the culprit.

FWIW, I've been unable to find a box with the same CPU model (C2750)
that you are using. I've found a couple of old Atom boxes using
different CPUs but they all seem to boot fine using latest
xen-unstable. I've looked on eBay for that CPU but everything
containing it is server-grade and >200$ which I'm sadly not going to
pay.

Unless you are able to bisect the tree and give us the bad commit
that's causing your issues I'm afraid at least myself I won't be able
to progress this any further, sorry.

Roger.
I attempted to work backwards and ran into a nightmare with Gentoo.   I kept
getting compiler errors which I suspect was a result of having a newer version
of GCC and other things.  It's not an easy thing to travel
back in time in Gentoo because everything keeps getting upgraded.  I just
cannot make the time now to unravel this as I have some demands on my time
and will be engaged for the next four to six weeks.

How much would it cost for you to obtain the machine you need? I may
consider paying for it. I bought this Atom server just to economically run
Xen so the machine has marginal value to me if I cannot run Xen on it.

John


--------------93230702A7A3F237FA18D691-- --===============1139027853598050043== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cHM6Ly9saXN0 cy54ZW5wcm9qZWN0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3hlbi1kZXZlbA== --===============1139027853598050043==--