linux-kernel - Re: 2.6.19-rc5-mm1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20061108120547.78048229.akpm@osdl.org>
Date:	Wed, 8 Nov 2006 12:05:47 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Reuben Farrelly <reuben-linuxkernel@...b.net>
Cc:	linux-kernel@...r.kernel.org, davej@...hat.com,
	Roman Zippel <zippel@...ux-m68k.org>
Subject: Re: 2.6.19-rc5-mm1

On Wed, 08 Nov 2006 22:11:26 +1100
Reuben Farrelly <reuben-linuxkernel@...b.net> wrote:

> 
> 
> On 8/11/2006 8:54 PM, Andrew Morton wrote:
> > Temporarily at
> > 
> > http://userweb.kernel.org/~akpm/2.6.19-rc5-mm1/
> > 
> > will turn up at
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc5/2.6.19-rc5-mm1/
> > 
> > 
> > when kernel.org mirroring catches up.
> > 
> > 
> > 
> > - Merged the Kernel-based Virtual Machine patches.  See kvm.sf.net for 
> > userspace tools, instructions, etc.
> > 
> > It needs a recent binutils to build.
> > 
> > - The hrtimer+dynticks code still doesn't work right for machines which halt 
> > their TSC in low-power states.
> 
> I think this might be a davej thing:
> 
>    CC      init/version.o
>    LD      init/built-in.o
>    LD      .tmp_vmlinux1
> arch/x86_64/kernel/built-in.o: In function `acpi_cpufreq_cpu_exit':
> /usr/src/linux/linux-mm/arch/x86_64/kernel/cpufreq/../../../i386/kernel/cpu/cpufreq/acpi-cpufreq.c:762:
> undefined reference to `cpufreq_frequency_table_put_attr'
> arch/x86_64/kernel/built-in.o: In function `acpi_cpufreq_target':
> /usr/src/linux/linux-mm/arch/x86_64/kernel/cpufreq/../../../i386/kernel/cpu/cpufreq/acpi-cpufreq.c:406:
> undefined reference to `cpufreq_frequency_table_target'
> arch/x86_64/kernel/built-in.o: In function `acpi_cpufreq_verify':
> /usr/src/linux/linux-mm/arch/x86_64/kernel/cpufreq/../../../i386/kernel/cpu/cpufreq/acpi-cpufreq.c:491:
> undefined reference to `cpufreq_frequency_table_verify'
> arch/x86_64/kernel/built-in.o: In function `acpi_cpufreq_cpu_init':
> /usr/src/linux/linux-mm/arch/x86_64/kernel/cpufreq/../../../i386/kernel/cpu/cpufreq/acpi-cpufreq.c:698:
> undefined reference to `cpufreq_frequency_table_cpuinfo'
> /usr/src/linux/linux-mm/arch/x86_64/kernel/cpufreq/../../../i386/kernel/cpu/cpufreq/acpi-cpufreq.c:734:
> undefined reference to `cpufreq_frequency_table_get_attr'
> arch/x86_64/kernel/built-in.o: In function `trampoline_end':
> (.data+0x40c0): undefined reference to `cpufreq_freq_attr_scaling_available_freqs'
> drivers/built-in.o: In function `ondemand_powersave_bias_init':
> /usr/src/linux/linux-mm/drivers/cpufreq/cpufreq_ondemand.c:164: undefined
> reference to `cpufreq_frequency_get_table'
> drivers/built-in.o: In function `powersave_bias_target':
> /usr/src/linux/linux-mm/drivers/cpufreq/cpufreq_ondemand.c:126: undefined
> reference to `cpufreq_frequency_table_target'
> /usr/src/linux/linux-mm/drivers/cpufreq/cpufreq_ondemand.c:134: undefined
> reference to `cpufreq_frequency_table_target'
> /usr/src/linux/linux-mm/drivers/cpufreq/cpufreq_ondemand.c:138: undefined
> reference to `cpufreq_frequency_table_target'
> make: *** [.tmp_vmlinux1] Error 1
> [root@...nado linux-mm]#
> 
> .config looks like this:

It's pretty useless sending a mangled config.  In future, please send the
whole thing.  

The problem is that you have 

> CONFIG_CPU_FREQ_TABLE=m
> CONFIG_X86_ACPI_CPUFREQ=y

but acpi-cpufreq needs the stuff in freq_table.c.

This happens again and again and again and again.  I wish people would just
stop using `select'.  It.  Doesn't.  Work.

Either we fix select or we stop using the damn thing.

-
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/