Displaying 20 results from an estimated 1000 matches similar to: "[vhost:vhost 20/20] ERROR: "page_poisoning_enabled" [drivers/virtio/virtio_balloon.ko] undefined!"
2018 Feb 07
2
[vhost:vhost 20/20] ERROR: "page_poisoning_enabled" [drivers/virtio/virtio_balloon.ko] undefined!
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:
2018 Feb 07
2
[vhost:vhost 20/20] ERROR: "page_poisoning_enabled" [drivers/virtio/virtio_balloon.ko] undefined!
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:
2018 Feb 07
0
[vhost:vhost 20/20] ERROR: "page_poisoning_enabled" [drivers/virtio/virtio_balloon.ko] undefined!
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: ia64-allmodconfig (attached as .config)
> compiler: ia64-linux-gcc (GCC) 7.2.0
>
2018 Feb 07
0
[vhost:vhost 20/20] ERROR: "page_poisoning_enabled" [drivers/virtio/virtio_balloon.ko] undefined!
On Wednesday, February 7, 2018 10:52 AM, Michael S. Tsirkin wrote:
> 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:
2018 Feb 07
2
[PATCH v27 3/4] mm/page_poison: expose page_poisoning_enabled to kernel modules
On Wed, Feb 07, 2018 at 02:54:30PM +0800, Wei Wang wrote:
> In some usages, e.g. virtio-balloon, a kernel module needs to know if
> page poisoning is in use. This patch exposes the page_poisoning_enabled
> function to kernel modules.
>
> Signed-off-by: Wei Wang <wei.w.wang at intel.com>
> Cc: Andrew Morton <akpm at linux-foundation.org>
> Cc: Michal Hocko
2018 Feb 07
2
[PATCH v27 3/4] mm/page_poison: expose page_poisoning_enabled to kernel modules
On Wed, Feb 07, 2018 at 02:54:30PM +0800, Wei Wang wrote:
> In some usages, e.g. virtio-balloon, a kernel module needs to know if
> page poisoning is in use. This patch exposes the page_poisoning_enabled
> function to kernel modules.
>
> Signed-off-by: Wei Wang <wei.w.wang at intel.com>
> Cc: Andrew Morton <akpm at linux-foundation.org>
> Cc: Michal Hocko
2020 Apr 29
1
[PATCH] vhost: fix default for vhost_iotlb
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"
2008 Feb 16
2
zaptel: modpost section mismatch ?
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
2019 Aug 14
3
trouble building dahdi on kernel 5.2.7
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.
2020 Apr 15
2
linux-next: Tree for Apr 15 (vdpa)
On 4/14/20 10:22 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200414:
>
on x86_64:
ERROR: modpost: "vringh_set_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined!
ERROR: modpost: "vringh_init_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined!
ERROR: modpost: "vringh_iov_push_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined!
ERROR:
2020 Apr 15
2
linux-next: Tree for Apr 15 (vdpa)
On 4/14/20 10:22 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200414:
>
on x86_64:
ERROR: modpost: "vringh_set_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined!
ERROR: modpost: "vringh_init_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined!
ERROR: modpost: "vringh_iov_push_iotlb" [drivers/vdpa/vdpa_sim/vdpa_sim.ko] undefined!
ERROR:
2007 Apr 18
3
Section mismatch in parainstructions
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
2007 Apr 18
3
Section mismatch in parainstructions
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
2009 Jun 24
3
dahdi-linux-2.2.0 compile problem
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?
2011 Jul 06
5
Error of building dom0 kernel
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)
2012 Jul 13
3
BCM4313 on CentOS 6.3
Hi all,
I'm a complete newbie in Linux and am trying to get my Broadcom BCM4313
working in my Lenovo S10-3t netbook (CentOS 6.3 installed from LiveCD).
I followed the steps in the wiki, which lead me to ELRepo: wl-kmod. I
followed the instructions there until Step 2:
$ mkdir -p ~/rpmbuild/{BUILD,RPMS,SPECS,SOURCES,SRPMS}
$ echo -e "%_topdir $(echo $HOME)/rpmbuild\n%dist .el$(lsb_release
2009 Sep 20
1
DAHDI installation warning
Hey list,
I'm getting the following warning when installing
dahdi-linux-complete-2.2.0.2+2.2.0 :
make[2]: Entering directory `/usr/src/kernels/2.6.18-128.1.6.el5-i686'
Building modules, stage 2.
MODPOST
WARNING: could not find /usr/src/dahdi-linux-complete-2.2.0.2
+2.2.0/linux/drivers/dahdi/vpmadt032_loader/.vpmadt032_x86_32.o.cmd
for /usr/src/dahdi-linux-complete-2.2.0.2
2011 Jul 03
1
[PATCH] Modpost section mismatch fix
[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
2011 Jul 03
1
[PATCH] Modpost section mismatch fix
[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
2011 Jul 03
1
[PATCH] Modpost section mismatch fix
[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