[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Build issues since XSA 240


  • To: "Jan Beulich" <JBeulich@xxxxxxxx>
  • From: Emmanuel Vadot <manu@xxxxxxxxxxxxxxxx>
  • Date: Tue, 17 Oct 2017 16:28:37 +0200
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 17 Oct 2017 14:28:54 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=NKnctR2tycbyS+UpoD7Cb+0nzX+QAl35TCGeXkZs0SA8Sc8B+ImlxJcr zmmKNAe9XyJbd50MRUPQYBEx06wdu+w7Fn9LMt+ox4IXIKR5s56jBVtsDsCbAy14 wuX4RB31aQ/OQVcOGWcoAOtjuw+RyxX4A1OMveutB+j1H59m4VY=
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

On Tue, 17 Oct 2017 06:57:45 -0600
"Jan Beulich" <JBeulich@xxxxxxxx> wrote:

> >>> On 17.10.17 at 14:44, <manu@xxxxxxxxxxxxxxxx> wrote:
> >  We are seeing some build issues since XSA 240 was released, since I
> > didn't know if it was related to our build job I've isolated everything
> > so anybody could recreate the test.
> >  We use Xen 4.8.2 and build it on debian 9 (9.1 to be exact) and since
> > XSA 240 we have xen crashing on some servers (mostly dev machine so
> > it's ok but still ...).
> >  As said to be sure that everyone can recreate the problem I've created
> > a script that ~do what our jenkins job is doing : 
> > https://gist.github.com/evadot/40f92fb5320121fd8ee3b6d0d9c256c1 
> >  I've set the bits for reproducible build since it makes it easier to
> > test on multiple machines.
> >  With this script runned on a debian 9.1 machine (either vm or
> > physical) from /root/ directly (I didn't found the variable that remove
> > build path for repro build if one exists) I get the build id
> > 0764c6f6d385feed46c4b18803dabc282a50ae8b and when starting this binary
> > on a Dell C6100 (Xeon L5640) I have this :
> > https://www.bidouilliste.com/xen/log_xen_4.8.2_xsa_231-xsa-245_gcc-0764c6f6d
> >  
> > 385feed46c4b18803dabc282a50ae8b.txt
> > 
> >  If I switch to clang (just added clang=y to make defconfig and make
> > build) I have this :
> > https://www.bidouilliste.com/xen/log_xen_4.8.2_xsa_231-xsa-245_clang-2261d6a
> >  
> > d42adef475fa638b87f7364df155919a9.txt
> >   There seems to be some memory corruption on this last one (where the
> > ram map is printed).
> > 
> >  But if I build it on my FreeBSD machine (12-CURRENT, clang 5.0.0) or a
> > FreeBSD 11.1 VM (clang 4.0.0) I can boot my dom0 and start VMs.
> 
> Wasn't it you who (under email address emmanuel.vadot@xxxxxxxxx)
> reported this same or a pretty similar problem to the discussion list
> already during the embargo, finding out later that this was due to
> flawed hardware on the build system of yours?
> 
> Jan

 Yes, since then I've run test on multiple VM and physical machines to
be sure that this wasn't our build system fault.

-- 
Emmanuel Vadot <manu@xxxxxxxxxxxxxxxx> <manu@xxxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.