This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] Problems with tip (Remus?)

To: Brendan Cully <brendan@xxxxxxxxx>
Subject: RE: [Xen-devel] Problems with tip (Remus?)
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Mon, 9 Nov 2009 14:17:39 -0800 (PST)
Cc: "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 09 Nov 2009 14:18:49 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20091109221112.GB2822@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Backed out to c/s 20404 and everything is fine again,
so either Remus or libxenlight or one of the e820 c/s.

> -----Original Message-----
> From: Brendan Cully [mailto:brendan@xxxxxxxxx]
> Sent: Monday, November 09, 2009 3:11 PM
> To: Dan Magenheimer
> Cc: Xen-Devel (E-mail)
> Subject: Re: [Xen-devel] Problems with tip (Remus?)
> On Monday, 09 November 2009 at 14:02, Dan Magenheimer wrote:
> > Just updated to latest tip (20419), including rebuilding 
> tools (but not dom0,
> > not sure if there is a new dependency there) and I'm 
> getting an infinite
> > loop of error messages when xend is trying to launch, along 
> the lines
> > of "Xend died due to signal 6!" and "Xend died due to signal 11!".
> >  
> > Everything was fine earlier today on a c/s >20400.  I'll 
> try backing out
> > the remus changes that just went in, but thought I would 
> give warning
> > and see if others run into the problem.
> I'll attempt to reproduce. Right now I'm being stopped by a different
> error:
> gcc -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls 
> -m32 -march=i686 -g -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wno-unused-value 
> -Wdeclaration-after-statement  -nostdinc -fno-builtin 
> -fno-common -iwithprefix include -Werror -Wno-pointer-arith 
> -pipe -I/home/brendan/remus/xen-unstable.32/xen/include  
> -I/home/brendan/remus/xen-unstable.32/xen/include/asm-x86/mach
> -generic 
> -I/home/brendan/remus/xen-unstable.32/xen/include/asm-x86/mach
> -default -msoft-float -fno-stack-protector -g -D__XEN__ 
> -DVERBOSE -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER -MMD 
> -MF .unlzma.o.d -c unlzma.c -o unlzma.o
> cc1: warnings being treated as errors
> unlzma.c:534: warning: C99 inline functions are not 
> supported; using GNU89
> unlzma.c:534: warning: to disable this warning use 
> -fgnu89-inline or the gnu_inline function attribute
> make[4]: *** [unlzma.o] Error 1
> make[4]: Leaving directory 
> `/home/brendan/remus/xen-unstable.32/xen/common'
> which I would guess is due to 20401:c4630f8f69cc interacting badly
> with my Ubuntu 8.04 build environment.

Xen-devel mailing list