[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080319220431.GA11606@elte.hu>
Date: Wed, 19 Mar 2008 23:04:33 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Ian Campbell <ijc@...lion.org.uk>
Subject: Re: [PATCH 00 of 31] x86: unification and xen updates
* Jeremy Fitzhardinge <jeremy@...p.org> wrote:
>> config attached. randconfig generated, so it can have random
>> surprises enabled :)
>
> Thanks. What was the workload? Did it just happen, or were you doing
> something specific?
simple bootup triggered it.
> BTW, that other pud_populate config you sent fails to link for me:
>
> LD .tmp_vmlinux1
> arch/x86/kernel/built-in.o: In function `MP_processor_info':
> mpparse_32.c:(.cpuinit.text+0x32b2): undefined reference to `x86_cpu_to_apicid_early_ptr'
> mpparse_32.c:(.cpuinit.text+0x32c4): undefined reference to `x86_bios_cpu_apicid_early_ptr'
> mpparse_32.c:(.cpuinit.text+0x3363): undefined reference to `per_cpu__x86_cpu_to_apicid'
> mpparse_32.c:(.cpuinit.text+0x336e): undefined reference to `per_cpu__x86_bios_cpu_apicid'
> arch/x86/mach-generic/built-in.o: In function `cpu_present_to_apicid':
> summit.c:(.text+0xaf): undefined reference to `per_cpu__x86_bios_cpu_apicid'
> arch/x86/mach-generic/built-in.o: In function `cpu_present_to_apicid':
> bigsmp.c:(.text+0x47f): undefined reference to `per_cpu__x86_bios_cpu_apicid'
> arch/x86/mach-generic/built-in.o: In function `init_apic_ldr':
> bigsmp.c:(.text+0x6cc): undefined reference to `per_cpu__x86_bios_cpu_apicid'
> arch/x86/mach-generic/built-in.o: In function `cpu_present_to_apicid':
> es7000.c:(.text+0x774): undefined reference to `per_cpu__x86_bios_cpu_apicid'
> arch/x86/mach-generic/built-in.o:es7000.c:(.text+0x906): more undefined references to `per_cpu__x86_bios_cpu_apicid' follow
> make[2]: *** [.tmp_vmlinux1] Error 1
"git-remote update" should solve that for you.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists