WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Xen Daily Builds

On Thu, 2005-05-26 at 13:33 -0700, Nakajima, Jun wrote:
> I think the problem on x86-64 has the same cause.

Unfortunately, the x86_64 build is broken, so I cannot test it.

> gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -
> iwithprefix include
 -Wall -Werror -Wno-pointer-arith -pipe -I/tmp/xen-unstable/xen/include -I/tmp/x
en-unstable/xen/include/asm-x86/mach-generic -I/tmp/xen-unstable/xen/include/asm
-x86/mach-default -O3 -fomit-frame-pointer -msoft-float -m64 -mno-red-zone -fpic
 -fno-reorder-blocks -fno-asynchronous-unwind-tables -DNDEBUG -c cpu/common.c -o
 cpu/common.o
cc1: warnings being treated as errors
cpu/common.c: In function ‘early_cpu_detect’:
cpu/common.c:209: warning: pointer targets in passing argument 2 of ‘cpuid’ diff
er in signedness
cpu/common.c:209: warning: pointer targets in passing argument 3 of ‘cpuid’ diff
er in signedness
cpu/common.c:209: warning: pointer targets in passing argument 4 of ‘cpuid’ diff
er in signedness
cpu/common.c:209: warning: pointer targets in passing argument 5 of ‘cpuid’ diff
er in signedness
cpu/common.c: In function ‘generic_identify’:
cpu/common.c:241: warning: pointer targets in passing argument 2 of ‘cpuid’ diff
er in signedness
cpu/common.c:241: warning: pointer targets in passing argument 3 of ‘cpuid’ diff
er in signedness
cpu/common.c:241: warning: pointer targets in passing argument 4 of ‘cpuid’ diff
er in signedness
cpu/common.c:241: warning: pointer targets in passing argument 5 of ‘cpuid’ diff
er in signedness
cpu/common.c:250: warning: pointer targets in passing argument 3 of ‘cpuid’ diff
er in signedness
make[3]: *** [cpu/common.o] Error 1
make[3]: Leaving directory `/tmp/xen-unstable/xen/arch/x86'
make[2]: *** [/tmp/xen-unstable/xen/xen] Error 2
make[2]: Leaving directory `/tmp/xen-unstable/xen'
make[1]: *** [xen] Error 2
make[1]: Leaving directory `/tmp/xen-unstable'
make: *** [world] Error 2

> Jun
> ---
> Intel Open Source Technology Center 
> 
>  
> 
> 
> ______________________________________________________________________
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Li Ge
> Sent: Thursday, May 26, 2005 12:51 PM
> To: Keir Fraser
> Cc: dfbp@xxxxxxxxxx; xen-devel; xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Xen Daily Builds
> 
> 
> 
> You are right. I just tested it with the latest repository source and
> the problem is gone. I can boot domain0 and create domainU without a
> problem. 
> 
> Thanks,
> Li
> Inactive hide details for Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>Keir
> Fraser <Keir.Fraser@xxxxxxxxxxxx>
> 
> 
>                                 Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> 
>                                 
>                                 05/26/2005 12:03 PM
>                                 
> 
>                To
> 
> Li
> Ge/Austin/IBM@IBMUS
> 
>                cc
> 
> xen-devel <xen-
> devel@xxxxxxxxxxxxxxxxxxx>, dfbp@xxxxxxxxxxxxxxxxxxxxxxx, 
> xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> 
>           Subject
> 
> Re: [Xen-devel]
> Xen Daily Builds
> 
> 
> 
> 
> 
> > In today's build (2005/05/26) on HS20 x86 SMP, I got a CPU FATAL
> TRAP 
> > 13 error when booting xen.
> 
> I think this is a bug that I already fixed in the repository. Should
> be 
> in tonight's snapshot tarballs.
> 
>  -- Keir
> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel