similar to: Link to kernelcap documentation?

Hey everyone, I''ve searched through all of the previous posts and tried everything mentioned but I am still getting these messages. Is there anything else I can do? My host machine is running CentOS 5 w/ Xen 3.3.1. My Xen VM is also running CentOS 5. I''ve tried doing: # echo ''hwcap 0 nosegneg'' > /etc/ld.so.conf.d/libc6-xen.conf && ldconfig

Hi, dovecot-2.0-rc3 dovecot-2-0-pigeonhole-4cb55beaca07 when I run 'doveadm config', it prints such error, any help? thanks :) *** glibc detected *** /home/mail/bin/doveconf: munmap_chunk(): invalid pointer: 0x001115fc *** ======= Backtrace: ========= /lib/i686/nosegneg/libc.so.6(cfree+0x188)[0x36e758] /home/mail/lib/dovecot/libdovecot.so.0[0x7db41a]

Hi, Found this in logfiles: Jul 25 14:12:38 dovecot: pop3(cen at so.red): Error: UIDL: File name lookup failed: Message was expunged Jul 25 14:12:38 dovecot: pop3(cen at so.red): Disconnected: POP3 UIDLs couldn't be listed top=187/356348, retr=0/0, del=0/1207, size=789346199 Jul 25 14:12:38 dovecot: pop3(cen at so.red): Panic: file ioloop.c: line 39 (io_add_file): assertion failed: (fd

The attached re-enables the pygrub build and fixes the build with older e2fsprogs (tested on RHEL4 with e2fsprogs-1.35 and rawhide with e2fsprogs-1.38) Signed-off-by: Jeremy Katz <katzj@redhat.com> Jeremy _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol defined by the hypervisor is different from VCLOCK_PVCLOCK. Implement the required support by adding hvclock_page VVAR. Signed-off-by: Vitaly Kuznetsov <vkuznets at redhat.com> --- arch/x86/entry/vdso/vclock_gettime.c | 36 +++++++++++++++++++++++++++++++++++ arch/x86/entry/vdso/vdso-layout.lds.S | 3 ++-

Hi, I'm trying to install xen+Debian Etch on a Geode LX system. Xen boots fine, but although the package "libc6-xen" is installed I have a large number of such errors: 4gb seg fixup, process syslogd (pid 1878), cs:ip 73:b7f24610 All processes triggers it, and from what I've found on the web it's a sign that libc6-xen is not recognized. Indeed:

Now that 'smp_read_barrier_depends()' has gone the way of the Norwegian Blue, drop the inclusion of <asm/barrier.h> in 'asm-generic/rwonce.h'. This requires fixups to some architecture vdso headers which were previously relying on 'asm/barrier.h' coming in via 'linux/compiler.h'. Signed-off-by: Will Deacon <will at kernel.org> ---

Dear all, Despite of moving /lib/tls to /lib/tls.disabled I get this warning: *************************************************************** *************************************************************** ** WARNING: Currently emulating unsupported memory accesses ** ** in /lib/tls glibc libraries. The emulation is ** ** slow. To ensure full performance you should ** ** install a

On Fri, Jul 10, 2020 at 9:52 AM Will Deacon <will at kernel.org> wrote: > > Now that 'smp_read_barrier_depends()' has gone the way of the Norwegian > Blue, drop the inclusion of <asm/barrier.h> in 'asm-generic/rwonce.h'. > > This requires fixups to some architecture vdso headers which were > previously relying on 'asm/barrier.h' coming in via

Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol defined by the hypervisor is different from VCLOCK_PVCLOCK. Implement the required support re-using pvclock_page VVAR as VCLOCK_PVCLOCK is mutually exclusive with VCLOCK_HVCLOCK at run time. Signed-off-by: Vitaly Kuznetsov <vkuznets at redhat.com> --- arch/x86/entry/vdso/vclock_gettime.c | 48

On Fri, Sep 14, 2018 at 2:52 PM Thomas Gleixner <tglx at linutronix.de> wrote: > > Matt attempted to add CLOCK_TAI support to the VDSO clock_gettime() > implementation, which extended the clockid switch case and added yet > another slightly different copy of the same code. > > Especially the extended switch case is problematic as the compiler tends to > generate a jump

On Mon, 2007-03-05 at 13:06 +0100, Ingo Molnar wrote: > Subject: [patch] paravirt: VDSO page is essential > From: Ingo Molnar <mingo@elte.hu> > > commit 3bbf54725467d604698721384d858b5983b87e8f disables the VDSO for > CONFIG_PARAVIRT kernels. This #ifdeffery was a bad change: the VDSO is > an essential component of Linux, and this change forces all of them to > use

On Mon, 2007-03-05 at 13:06 +0100, Ingo Molnar wrote: > Subject: [patch] paravirt: VDSO page is essential > From: Ingo Molnar <mingo@elte.hu> > > commit 3bbf54725467d604698721384d858b5983b87e8f disables the VDSO for > CONFIG_PARAVIRT kernels. This #ifdeffery was a bad change: the VDSO is > an essential component of Linux, and this change forces all of them to > use

Hi, I upgraded to 4.1.7 from 4.1.4 last night; no other changes. Now, every minute I am getting errors from cron as it tries to execute a cron job (I'm not actually sure if the job fails or succeeds): Jun 4 00:28:01 server crond[1080]: PAM adding faulty module: /lib64/security/pam_winbind.so Jun 4 00:28:01 server crond[1082]: PAM unable to dlopen(/lib64/security/pam_winbind.so):

On Fri, 14 Sep 2018, Arnd Bergmann wrote: > On Fri, Sep 14, 2018 at 2:52 PM Thomas Gleixner <tglx at linutronix.de> wrote: > A couple of architectures (s390, ia64, riscv, powerpc, arm64) > implement the vdso as assembler code at the moment, so they > won't be as easy to consolidate (other than outright replacing all > the code). > > The other five: >

> On Oct 3, 2018, at 2:22 AM, Vitaly Kuznetsov <vkuznets at redhat.com> wrote: > > Andy Lutomirski <luto at kernel.org> writes: > >> Hi Vitaly, Paolo, Radim, etc., >> >>> On Fri, Sep 14, 2018 at 5:52 AM Thomas Gleixner <tglx at linutronix.de> wrote: >>> >>> Matt attempted to add CLOCK_TAI support to the VDSO clock_gettime()

On Wed, Feb 8, 2017 at 9:07 AM, Vitaly Kuznetsov <vkuznets at redhat.com> wrote: > Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol > defined by the hypervisor is different from VCLOCK_PVCLOCK. Implement the > required support re-using pvclock_page VVAR as VCLOCK_PVCLOCK is mutually > exclusive with VCLOCK_HVCLOCK at run time. > > Signed-off-by:

On Wed, Feb 8, 2017 at 9:07 AM, Vitaly Kuznetsov <vkuznets at redhat.com> wrote: > Hyper-V TSC page clocksource is suitable for vDSO, however, the protocol > defined by the hypervisor is different from VCLOCK_PVCLOCK. Implement the > required support re-using pvclock_page VVAR as VCLOCK_PVCLOCK is mutually > exclusive with VCLOCK_HVCLOCK at run time. > > Signed-off-by:

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