similar to: WARNING: modpost: Found 10 section mismatch(es).

Building zaptel-1.4 from today's svn against kernel 2.6.25-git2: ............ Building modules, stage 2. MODPOST 13 modules WARNING: modpost: Found 1 section mismatch(es). ........ The other warnings were about "BIT" redefined, which I assume are benign. Should I worry? If so, what do I do? sean

[Sorry if duplicate, one earlier was corrupt] Hi, I got section mismatches reported by modpost in latest build. It got reported for xen_register_pirq and xen_unplug_emulated_devices functions. xen_register_pirq makes reference to acpi_sci_override_gsi in init.data section; marking xen_register_pirq with __init is not feasible since calls are made to it from

[Sorry if duplicate, one earlier was corrupt] Hi, I got section mismatches reported by modpost in latest build. It got reported for xen_register_pirq and xen_unplug_emulated_devices functions. xen_register_pirq makes reference to acpi_sci_override_gsi in init.data section; marking xen_register_pirq with __init is not feasible since calls are made to it from

[Sorry if duplicate, one earlier was corrupt] Hi, I got section mismatches reported by modpost in latest build. It got reported for xen_register_pirq and xen_unplug_emulated_devices functions. xen_register_pirq makes reference to acpi_sci_override_gsi in init.data section; marking xen_register_pirq with __init is not feasible since calls are made to it from

Hi, I recently compiled a Xen-4.0.1 and pv-ops Dom0 2.6.32.27 kernel from JF''s tree.Where my hypervisor could not boot and unfortunately the system is rebooting so frequently that I am not able to note down the error messages on a paper and pencil.So now I am planning to go for a non pv-ops Dom0.I am not clear as what should be the approach? I have been Googling it every now and then and

Following is one grub entry menuentry "Ubuntu, Linux 2.6.32.27" { insmod ntfs set root=''(hd0,2)'' search --no-floppy --fs-uuid --set 96f65c80f65c6313 loopback loop0 /ubuntu/disks/root.disk set root=(loop0) linux /boot/vmlinuz-2.6.32.27 root=/dev/sda2 loop=/ubuntu/disks/root.disk ro quiet splash initrd

Is it OK for section .parainstructions to reference exit.text? I'm seeing: WARNING: drivers/net/hamradio/scc.o - Section mismatch: reference to .exit.text: from .parainstructions after '' (at offset 0x0) WARNING: drivers/net/hamradio/scc.o - Section mismatch: reference to .exit.text: from .parainstructions after '' (at offset 0x8) If that's OK, we need a small patch to

Is it OK for section .parainstructions to reference exit.text? I'm seeing: WARNING: drivers/net/hamradio/scc.o - Section mismatch: reference to .exit.text: from .parainstructions after '' (at offset 0x0) WARNING: drivers/net/hamradio/scc.o - Section mismatch: reference to .exit.text: from .parainstructions after '' (at offset 0x8) If that's OK, we need a small patch to

On Tue, 14 Nov 2006 23:56:22 +0100 Adrian Bunk <bunk@stusta.de> wrote: > Since people were recently complaining about too many warnings: > Here is a list of the warnings I'm getting in MODPOST and later. > > Since the warnings by far exceed the 100kB limit of linux-kernel (sic), > I had to attach them compressed. > > With the exception of the

On Tue, 14 Nov 2006 23:56:22 +0100 Adrian Bunk <bunk@stusta.de> wrote: > Since people were recently complaining about too many warnings: > Here is a list of the warnings I'm getting in MODPOST and later. > > Since the warnings by far exceed the 100kB limit of linux-kernel (sic), > I had to attach them compressed. > > With the exception of the

I compiled the pvops kernel like this : [root@localhost xen-4.0.0]# ls buildconfigs config Config.mk.orig dist extras install.sh Makefile README tools xen build-linux-2.6-pvops_x86_32 Config.mk COPYING docs file linux-2.6-pvops.git messages stubdom unmodified_drivers [root@localhost build-linux-2.6-pvops_x86_32]# make -j2 bzImage

I compiled the pvops kernel like this : [root@localhost xen-4.0.0]# ls buildconfigs config Config.mk.orig dist extras install.sh Makefile README tools xen build-linux-2.6-pvops_x86_32 Config.mk COPYING docs file linux-2.6-pvops.git messages stubdom unmodified_drivers [root@localhost build-linux-2.6-pvops_x86_32]# make -j2 bzImage

Hi, i try the kernel from [1] and get: WARNING: vmlinux.o (__xen_guest): unexpected non-allocatable section. Did you forget to use "ax"/"aw" in a .S file? Note that for example <linux/init.h> contains section definitions for use in .S files. WARNING: modpost: Found 2 section mismatch(es). To see full details build your kernel with: ''make

Hi, I decided to test new Xen pv-ops Dom0 kernel. I have a 64 bit VT machine there in it Vmware work station installed Ubuntu 10.04 64 bit and then apt-get install libcurl4-openssl-dev xserver-xorg-dev mercurial gitk build-essential libncurses5-dev uuid-dev gawk gettext texinfo bcc libncurses5-dev dpkg-dev debhelper iasl texinfo bridge-utils bison flex apt-get build-dep xen-3.3 cd /usr/src

Hi, Ubuntu 10.04 x64 installing xen4.0 testing when compiling kernel 2.6.32.16 from jeremy git i get this error: WARNING: modpost: Found 7 section mismatch(es). To see full details build your kernel with: ''make CONFIG_DEBUG_SECTION_MISMATCH=y'' GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD

I tried debugging it and the issue seems to be in the implementation of MachineInstrIterator.h and the way it interacts with GraphWriter.h functions. I found this by replacing the ( template <> struct GraphTraits<MCDFGraph<MachineFunction*> >) with a similar MCDFGraph based template of CFG similar to the one in MachineFunction.h (similarly replacing the DOTGraphTraits with the

Hi, I am trying to generate the DFG of machine functions. Initially, I added a pass to generate the DFG of LLVM IR functions. This was based on the mail thread - http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-September/025582.html. This pass worked fine and I was able to generate DFG of LLVM IR functions. Later, I ported the DFG pass code for machine functions. I ported the InstIterator.h

Hi all, I follow instructions(http://wiki.xensource.com/xenwiki/XenParavirtOps) to build XEN and dom0 kernel. Building XEN has no problem, but there is an error which I cannot solve to build dom0 kernel. The brief instructions for building dom0 are get linux-2.6-xen code from git and make ARCH=x86_64 menuconfig, finally generate kernel.deb. (I did every step exactly as the web page says)

Hi all,   I install Xen on a fresh Ubuntu 9.04 from source. During the code runing it shows usually "Warning: not literal format or no paramaters". By "make" linux kernel after 1 hours code running it ends with: (The installation steps is shown below)   --------------------------------------------------------------------------- WARNING: modpost: Found 1 section mismatch(es). To

Hi Gert, Thanks for your reply. But we can't upgrade to 7.2 version also we don't have plan to upgrade in near future. Can I fix these vulnerabilities in the current version? Regards Abhishek On Tue, Mar 8, 2016 at 6:42 PM, Gert Doering <gert at greenie.muc.de> wrote: > Hi, > > On Tue, Mar 08, 2016 at 06:14:01PM +0530, abhi dhiman wrote: > > Actually I am working