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] Latest bk can NOT compile on x86_64

To: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>, "Li, Xin B" <xin.b.li@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Latest bk can NOT compile on x86_64
From: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Date: Mon, 30 May 2005 23:15:12 -0700
Delivery-date: Tue, 31 May 2005 06:14:34 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVlbTlnxzVIlcVvRLKIshNiy2RwYAALp+aAAALZMWA=
Thread-topic: [Xen-devel] Latest bk can NOT compile on x86_64
Nakajima, Jun wrote:
> Actually xen itself is broken (again) too on x86-64. It dies like the
> below. I think the breakage happened very recently (today, yesterday,
> or the day before yesterday).

Did a quick debugging. It's failing at phys_pkg_id (it's NULL) in
detect_ht because genacpi is not set yet when this is called. Putting
"apic=default" makes it boot. I think it should be initialized as
"default".

void __init detect_ht(struct cpuinfo_x86 *c) {
...
        phys_proc_id[cpu] = phys_pkg_id((ebx >> 24) & 0xFF, index_msb);

Jun
---
Intel Open Source Technology Center

> ---
>  Xen version 3.0-devel (jnakajim@xxxxxxxxxxxx) (gcc version 3.4.2
> 20041017 (Red
> Hat 3.4.2-6.fc3)) Mon May 30 21:26:28 PDT 2005
>  Latest ChangeSet: 2005/05/30 20:19:59 1.1577
> 429bd7dfnKHSDeYeOeCr4yRO7YCrFQ
> 
> (XEN) Physical RAM map:
> (XEN)  0000000000000000 - 000000000009fc00 (usable)
> (XEN)  000000000009fc00 - 00000000000a0000 (reserved)
> (XEN)  00000000000e6000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 000000003f630000 (usable)
> (XEN)  000000003f630000 - 000000003f640000 (ACPI data)
> (XEN)  000000003f640000 - 000000003f6f0000 (ACPI NVS)
> (XEN)  000000003f6f0000 - 000000003f800000 (reserved)
> (XEN)  00000000cff00000 - 00000000f0000000 (reserved)
> (XEN)  00000000fed13000 - 00000000fed1a000 (reserved)
> (XEN)  00000000fed1c000 - 00000000fed90000 (reserved)
> (XEN) System RAM: 1013MB (1038140kB)
> (XEN) Xen heap: 14MB (14828kB)
> (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
> (XEN) CPU: L2 cache: 2048K
> (XEN) Unknown interrupt
> 
> Li, Xin B wrote:
>> When doing "make linux-2.6-xen0-build", it failed with:
>> 
>> make[3]: `arch/xen/x86_64/kernel/asm-offsets.s' is up to date.
>>   CHK     include/linux/compile.h
>>   CHK     usr/initramfs_list
>>   GEN     .version
>>   CHK     include/linux/compile.h
>>   UPD     include/linux/compile.h
>>   CC      init/version.o
>>   LD      init/built-in.o
>>   LD      .tmp_vmlinux1
>> arch/xen/x86_64/kernel/built-in.o(.text+0x291): In function
>> `xen_idle':
>>> undefined reference to `set_timeout_timer'
>> make[2]: *** [.tmp_vmlinux1] Error 1
>> make[2]: Leaving directory
>> `/home/xin/bk/xeno-unstable.bk/linux-2.6.11-xen0'
>> make[1]: *** [build] Error 2
>> make[1]: Leaving directory `/home/xin/bk/xeno-unstable.bk'
>> make: *** [linux-2.6-xen0-build] Error 2
>> 
>> -Xin
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
> 
> 
> 
> Jun
> ---
> Intel Open Source Technology Center
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel




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