kernel August 2008

kernel@lists.fedoraproject.org

28 participants
21 discussions

warning :section mismatch while compiling fedora 2.6.21-1.3194.fc7 kernel
by nayan kumar 13 Aug '08

13 Aug '08

Hi All while compiling linux kernel downloaded from kernel.org i am getting warning as given below WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .text between 'is386' (at offset 0xc1001171) and 'check_x87' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'rest_init' (at offset 0xc10013e6) and 'try_name' WARNING: vmlinux - Section mismatch: reference to .init.data: from .text between 'probe_bigsmp' (at offset 0xc1002012) and 'init_apic_ldr' WARNING: vmlinux - Section mismatch: reference to .init.text:find_unisys_acpi_oem_table from .text between 'acpi_madt_oem_check' (at offset 0xc1002220) and 'enable_apic_mode' WARNING: vmlinux - Section mismatch: reference to .init.text:parse_unisys_oem from .text between 'acpi_madt_oem_check' (at offset 0xc100226d) and 'enable_apic_mode' WARNING: vmlinux - Section mismatch: reference to .init.text:setup_unisys from .text between 'acpi_madt_oem_check' (at offset 0xc1002274) and 'enable_apic_mode' WARNING: vmlinux - Section mismatch: reference to .init.text:parse_unisys_oem from .text between 'mps_oem_check' (at offset 0xc100220d) and 'acpi_madt_oem_check' WARNING: vmlinux - Section mismatch: reference to .init.text:es7000_sw_apic from .text between 'enable_apic_mode' (at offset 0xc1002284) and 'check_apicid_present' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc100a8a9) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'init_gdt' (at offset 0xc100a8bf) and 'cpu_init' WARNING: vmlinux - Section mismatch: reference to .init.text:sysenter_setup from .text between 'identify_cpu' (at offset 0xc100ad9b) and 'detect_ht' WARNING: vmlinux - Section mismatch: reference to .init.text:mtrr_bp_init from .text between 'identify_cpu' (at offset 0xc100ada5) and 'detect_ht' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc11f990a) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.data:initkmem_list3 from .text between 'set_up_list3s' (at offset 0xc106d7e1) and 's_start' WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem from .text between 'vgacon_startup' (at offset 0xc10f3987) and 'vgacon_scrolldelta' WARNING: vmlinux - Section mismatch: reference to .init.data:logo_linux_clut224 from .text between 'fb_find_logo' (at offset 0xc10fc5a8) and 'backlight_class_release' WARNING: vmlinux - Section mismatch: reference to .init.text: from .text between 'iret_exc' (at offset 0xc11f9f7e) and '_etext' The same warnings are also being reported when I compile my external module using the above built kernel. Is there any suggestions on how to solve this problem...? thanks in advance.. regards _________________________________________________________________ Searching for the best deals on travel? Visit MSN Travel. http://msn.coxandkings.co.in/cnk/cnk.do

1 0

Lawmaker Wants Schools To Phase Out Fluff
by Chrzan Kiepert 11 Aug '08

11 Aug '08

Hej,

1 0

kernel-vanilla builds for 2.6.27-rc1
by Josh Boyer 09 Aug '08

09 Aug '08

http://jwboyer.fedorapeople.org/pub/ Let the kernel installs begin. Hopefully I didn't fsck something up horridly. If I did, then I'll fix it for -rc2. josh

2 5

:o)
by Trafford Kibbey 09 Aug '08

09 Aug '08

Hoi,

1 0

:o)
by Aldredge Rodibaugh 07 Aug '08

07 Aug '08

Salve,

1 0

When will we stop shipping WLAN improvements ahead of upstream in released Fedora version?
by Thorsten Leemhuis 06 Aug '08

06 Aug '08

Hi all John (CCed), I really appreciate your work in the wireless area and would like to use the opportunity to say "thanks for all you work", as support for WLAN hardware in the Linux kernel improved a lot in the upstream kernel and Fedora thx to your (and other linux wireless developers) work over the last two years. But we now for at least the second time in the past few weeks had/have a more-than-minor wireless breakage in a Fedora kernel for a released distro (bug #453390 now; http://lwn.net/Articles/286558/ is discussing the one some weeks ago; I think there was one more breakage not that long ago, but I can't remember). I and many users (see for example #453390) got hit by those problems. That's why I was wondering: what are we at Fedora doing to prevent similar problems in the future? Three things spring to my mind and I just propose then here for discussion; maybe something good comes out of it in the end: - a karama of "+3" in bodhi seems not enough for a auto-move from testing to stable (or even worse: straight to stable if enough people tested the kernel and gave their +1 after the update got filed in bodhi but *before* it actually hit fedora-testing) if there are no other pressing issues (like security fixes). The kernel is a to complex beast; more then 3 people should be needed to give a +1. And a bit of time needs to pass to give enough people the opportunity to install, test and report problems with new kernels. For the latest kernel it seems to me that "to less time" really was the problem, otherwise the problem from #453390 would have been noticed earlier - should we separate security updates and other kernel fixes in a better way to make sure those "other fixes" get proper testing before they get send out to the users? - John, having all those pending and not-yet-upstream-merged improvements for wireless hardware in the Fedora kernel was something good in the past when WLAN support in the kernel was quite bad/incomplete. But the main and most important bits for proper wireless hardware support seem to be in the upstream kernel now; sure, there will always be improvements in the queue, but that's the same in most other linux subsystems with drivers as well. So I'm wondering: isn't it time now to finally stop shipping all those wireless-next bits (currently quite some big patches; see: -rw-rw-r-- 1 thl thl 2484 14. Mär 17:06 linux-2.6-ms-wireless-receiver.patch -rw-rw-r-- 1 thl thl 39874 4. Jul 22:21 linux-2.6-wireless-fixups.patch -rw-rw-r-- 1 thl thl 2656652 4. Jul 22:21 linux-2.6-wireless-pending.patch -rw-rw-r-- 1 thl thl 4165718 4. Jul 22:21 linux-2.6-wireless.patch ) in released Fedora Version (e.g. 8 and 9 currently) when we start shipping 2.6.26? Just my 2 cent. Cu knurd

9 14

Re: kernel-2.6.27-0.215.rc1.git4.fc10.i686 oops and no X :(
by Kyle McMartin 05 Aug '08

05 Aug '08

On Tue, Aug 05, 2008 at 12:37:32PM -0700, Antonio Olivares wrote: > Dear fellow testers, > > New kernel oops again and no X when starting it > > kernel-2.6.27-0.215.rc1.git4.fc10.i686 > > Here's oops > > http://www.kerneloops.org/submitresult.php?number=48331 > nasty... did this just start recently? Any thoughts, Dave? r, Kyle

2 2

[PATCH] kernel.spec: adding --with firmware & --without vdso_install build options
by Steve Dickson 05 Aug '08

05 Aug '08

Now that devel kernels rpms require the kernel-firmware rpm, it makes sense to me that one should be able to build both of them at the same time. So this patch adds the "--with firmware" build option which will allow kernel-firmware rpms to built with kernel rpms. This patch also adds the "--without vdso_install" build option which stop the VDSO binaries from being installed. This cuts down the overall build time especially when you build over NFS like I do.. Signed-Off-By: Steve Dickson <steved(a)redhat.com> diff -up SPECS/kernel.spec.orig SPECS/kernel.spec --- SPECS/kernel.spec.orig 2008-07-29 09:07:48.000000000 -0400 +++ SPECS/kernel.spec 2008-07-29 11:44:39.000000000 -0400 @@ -75,11 +75,13 @@ Summary: The Linux kernel # kernel-headers %define with_headers %{?_without_headers: 0} %{?!_without_headers: 1} # kernel-firmware -%define with_firmware %{?_without_firmware: 0} %{?!_without_firmware: 1} +%define with_firmware %{?_with_firmware: 1} %{?!_with_firmware: 0} # kernel-debuginfo %define with_debuginfo %{?_without_debuginfo: 0} %{?!_without_debuginfo: 1} # kernel-bootwrapper (for creating zImages from kernel + initrd) %define with_bootwrapper %{?_without_bootwrapper: 0} %{?!_without_bootwrapper: 1} +# Want to build a the vsdo directories installed +%define with_vdso_install %{?_without_vdso_install: 0} %{?!_without_vdso_install: 1} # don't build the kernel-doc package %define with_doc 0 @@ -188,8 +190,10 @@ Summary: The Linux kernel %define all_x86 i386 i586 i686 +%if %{with_vdso_install} # These arches install vdso/ directories. %define vdso_arches %{all_x86} x86_64 ppc ppc64 +%endif # Overrides for generic default options @@ -217,7 +221,6 @@ Summary: The Linux kernel # only package docs noarch %ifnarch noarch %define with_doc 0 -%define with_firmware 0 %endif # no need to build headers again for these arches, @@ -231,6 +234,7 @@ Summary: The Linux kernel %define with_up 0 %define with_headers 0 %define all_arch_configs kernel-%{version}-*.config +%define with_firmware 1 %endif # bootwrapper is only on ppc

4 8

[PATCH] be less annoying on boot
by Bill Nottingham 05 Aug '08

05 Aug '08

As long as we're printing mostly useless messages on every boot regardless of debug level, make them 5% more amusing. Signed-off-by: Bill Nottingham <notting(a)redhat.com>

6 6

Re: rpms/kernel/devel kernel.spec,1.847,1.848
by Kyle McMartin 05 Aug '08

05 Aug '08

On Tue, Aug 05, 2008 at 05:48:04AM +0000, Dave Jones wrote: > + cp -a acpi config keys linux math-emu media mtd net pcmcia rdma rxrpc scsi sound video drm asm-generic $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/include > + if [ -f asm ]; then > + cp -a `readlink asm` $RPM_BUILD_ROOT/lib/modules/$KernelVer/build/include > fi > This looks like it will DTRT thing in both cases. Cool.

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel August 2008