similar to: zaptel: modpost section mismatch ?

[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

What does this message means WARNING: modpost: Found 10 section mismatch(es). To see full details build your kernel with: ''make CONFIG_DEBUG_SECTION_MISMATCH=y'' GEN .version I got when did make deb-pkg -- Regards Abhi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

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

dahdi built fine on 5.1.20, but on 5.2.7: ............. CC [M] /home/asterisk/rpmbuild/BUILD/linux-dade6ac/drivers/dahdi/vpmadt032_loader/dahdi_vpmadt032_loader.o SHIPPED /home/asterisk/rpmbuild/BUILD/linux-dade6ac/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_64.o LD [M] /home/asterisk/rpmbuild/BUILD/linux-dade6ac/drivers/dahdi/dahdi_vpmadt032_loader.o Building modules, stage 2.

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

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: 96bcd04462b99e2c80e09f6537770a0ca6b288d0 commit: 96bcd04462b99e2c80e09f6537770a0ca6b288d0 [20/20] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT config: ia64-allmodconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 7.2.0 reproduce: wget

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: 96bcd04462b99e2c80e09f6537770a0ca6b288d0 commit: 96bcd04462b99e2c80e09f6537770a0ca6b288d0 [20/20] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT config: ia64-allmodconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 7.2.0 reproduce: wget

On Wed, Feb 07, 2018 at 10:25:35AM +0800, Wei Wang wrote: > On 02/07/2018 09:26 AM, kbuild test robot wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost > > head: 96bcd04462b99e2c80e09f6537770a0ca6b288d0 > > commit: 96bcd04462b99e2c80e09f6537770a0ca6b288d0 [20/20] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT > > config:

On Wed, Feb 07, 2018 at 10:25:35AM +0800, Wei Wang wrote: > On 02/07/2018 09:26 AM, kbuild test robot wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost > > head: 96bcd04462b99e2c80e09f6537770a0ca6b288d0 > > commit: 96bcd04462b99e2c80e09f6537770a0ca6b288d0 [20/20] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT > > config:

During randconfig build testing, I ran into a configuration that has CONFIG_VHOST=m, CONFIG_VHOST_IOTLB=m and CONFIG_VHOST_RING=y, which makes the iotlb implementation left out from vhost_ring, and in turn leads to a link failure of the vdpa_sim module: ERROR: modpost: "vringh_set_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined! ERROR: modpost: "vringh_init_iotlb"

Hello I did the following commands and resulted in a segmentation fault. [root@localhost ~]# mkfs.btrfs /dev/sda6 WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using fs created label (null) on /dev/sda6 nodesize 4096 leafsize 4096 sectorsize 4096 size 46.93GB Btrfs Btrfs v0.19 [root@localhost ~]# mount /dev/sda6 /mnt/btra [root@localhost ~]#

LD [M] /root/wanpipe/patches/kdrivers/wanec/wanec.o Building modules, stage 2. MODPOST *** Warning: "register_wanec_iface" [/root/wanpipe/patches/kdrivers/wanec/wanec.ko] undefined! *** Warning: "unregister_wanec_iface" [/root/wanpipe/patches/kdrivers/wanec/wanec.ko] undefined! CC /root/wanpipe/patches/kdrivers/wanec/wanec.mod.o LD [M]

The Asterisk Development Team has announced the releases of: DAHDI-Linux 2.6.1 DAHDI-Linux 2.5.1 DAHDI-Tools 2.6.1 DAHDI-Tools 2.5.1 DAHDI-Linux-Complete 2.6.1+2.6.1 DAHDI-Linux-Complete 2.5.1+2.5.1 These releases are available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools

The Asterisk Development Team has announced the releases of: DAHDI-Linux 2.6.1 DAHDI-Linux 2.5.1 DAHDI-Tools 2.6.1 DAHDI-Tools 2.5.1 DAHDI-Linux-Complete 2.6.1+2.6.1 DAHDI-Linux-Complete 2.5.1+2.5.1 These releases are available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools

I have an i686 cpu and when compiling from source I get this error: touch /usr/src/dahdi-linux-2.2.0/drivers/dahdi/xpp/init_fxo_modes.verified Building modules, stage 2. MODPOST WARNING: could not find /usr/src/dahdi-linux-2.2.0/drivers/dahdi/vpmadt032_loader/.vpmadt032_x86_32. o.cmd for /usr/src/dahdi-linux-2.2.0/drivers/dahdi/vpmadt032_loader/vpmadt032_x86_32.o Anyone else seeing this?

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)