From: David F Barrera <dfbp@us.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Li Ge <lge@us.ibm.com>, xen-devel <xen-devel@lists.xensource.com>
Subject: RE: Xen Daily Builds
Date: Fri, 27 May 2005 10:38:21 -0500 [thread overview]
Message-ID: <1117208301.5415.21.camel@localhost.localdomain> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D372001730416A686@scsmsx402.amr.corp.intel.com>
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@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] On Behalf Of Li Ge
> Sent: Thursday, May 26, 2005 12:51 PM
> To: Keir Fraser
> Cc: dfbp@us.ibm.com; xen-devel; xen-devel-bounces@lists.xensource.com
> 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@cl.cam.ac.uk>Keir
> Fraser <Keir.Fraser@cl.cam.ac.uk>
>
>
> Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
>
> 05/26/2005 12:03 PM
>
>
> To
>
> Li
> Ge/Austin/IBM@IBMUS
>
> cc
>
> xen-devel <xen-
> devel@lists.xensource.com>, dfbp@us.ltcfwd.linux.ibm.com, xen-devel-bounces@lists.xensource.com
>
> 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@lists.xensource.com
> 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
next prev parent reply other threads:[~2005-05-27 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 20:33 Xen Daily Builds Nakajima, Jun
2005-05-27 15:38 ` David F Barrera [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-27 16:03 Nakajima, Jun
2005-05-26 15:12 David F Barrera
2005-05-26 16:51 ` Li Ge
2005-05-26 17:03 ` Keir Fraser
2005-05-26 18:10 ` Li Ge
2005-05-26 19:51 ` Li Ge
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=1117208301.5415.21.camel@localhost.localdomain \
--to=dfbp@us.ibm.com \
--cc=jun.nakajima@intel.com \
--cc=lge@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.