similar to: GFS-kernel module - Version Magic Error

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19

Hi all, I have some problem with xm save/restore in Xen-4.0.0 & linux-2.6.31.13, First, the /etc/init.d/xendomains seems do not work properly because of bash version. So I modified it as follow: root@r02k08027 # diff -up /etc/init.d/xendomains /etc/init.d/xendomains_31 --- /etc/init.d/xendomains 2010-04-08 00:12:04.000000000 +0800 +++ /etc/init.d/xendomains_31 2010-04-19

Followed the "instructions" on voip-info.org regardinging fedora FC2, making Zaptel seems to work fine, however when I modprobe I get this. It looks like a version mismatch somehow. Ideas? If this ooc, sorry first post here :-) modprobe tor2 WARNING: Error inserting zaptel (/lib/modules/2.6.5-1.358smp/misc/zaptel.ko): Invalid module format WARNING: Error inserting zaptel

Hi all, I am creating a CentOS 5.1 Paravirtualized guest On Xen 3.2.1 / Fedora 8 Dom0. I built DomU kernel from the Xen Linux 2.6.18.8 source. I also created an initrd image (I face some problems there as I had to manually copy some modules line xennet, ahci and libata). Anyway, I dounloaded the CentOS5.1 image from http://jailtime.org/ and copied it to a new partition. When I create the

Hi I think I hit the cifs bug described at http://wiki.centos.org/TipsAndTricks/WindowsShares and http://bugs.centos.org/view.php?id=1776 As CentOS Wiki said, CentOS 5.0 do have a bug fixed cifs.ko, so I thought it should be in CentOSPlus repository ... so I upgrade my kernel and using 2.6.18-8.1.10.el5.centos.plus. After I use this kernel release, I check the cifs.ko and see the following: $

Hi All, I seem to have exactly the same problem which was described in this thread a while ago. I have gone through every piece of information I was able to find on mailing list archives but all I found was people reporting similar problems and not a solution to it. As in the original discussion if I use smbclient it works fine but if I use mount.cifs it does not work at all. To make smbclient

Hi list, I install dahdi-linux successfully with the module of oslec for the echo, but when I specify it in the system.conf the echo canceller oslec it shows me errors: DAHDI_ATTACH_ECHOCAN failed on channel 4: Invalid argument (22) I see that the echo cancellers is supported: mg2, kb1, sec2, and sec because oslec is not supported?, but he has support to compile it with dahdi_linux! best

[root@asterisk zaptel]# modprobe ztdummy WARNING: Error inserting zaptel (/lib/modules/2.6.5-1.315/misc/zaptel.ko): Invalid module format WARNING: Error inserting zaptel (/lib/modules/2.6.5-1.315/misc/zaptel.ko): Invalid module format FATAL: Error inserting ztdummy (/lib/modules/2.6.5-1.315/misc/ztdummy.ko): Invalid module format FATAL: Error running install command for ztdummy [root@asterisk

Hi, I am new to LLVM and clang and I would like to seek some professional help. :) I have been trying to compile some C code on a linux x86 computer for a Sparc machine. I used: clang -ccc-host-triple sparc-unknown-linux -ccc-clang-archs sparc -pthreads -lm -emit-llvm test.c -c -o -test.bc The following error messages are produced: /usr/include/pthread.h:665:6: error: 'regparm' is

On Fri, Sep 16, 2011 at 4:40 PM, Christine Cheng <clcheng at stanford.edu> wrote: > Hi, > > I am new to LLVM and clang and I would like to seek some professional help. > :) > > I have been trying to compile some C code on a linux x86 computer for a > Sparc machine. > > I used: > >  clang -ccc-host-triple sparc-unknown-linux -ccc-clang-archs sparc -pthreads

I'm using ocfs2 and all modules from Suse (SLES9), no self compilations. Here are the details: * 32-bit machine (writing to ocfs2 partition/LUN and where the corruption was reported): Kernel: 2.6.5-7.257-bigsmp #1 SMP i686 i386 GNU/Linux OCFS2 rpms: ocfs2console-1.2.1-4.2 ocfs2-tools-1.2.1-4.2 o2cb_ctl -V: o2cb_ctl version 1.2.1 /etc/init.d/o2cb status: Module "configfs":

Hi, is the areca 1100 Raid Controller supported by CentOS 5? Or is there a kmod rpm available? Thanks Juergen

Hi *, I'm running into a problem configuring bonding on an HP DL 360 G4p, running 4.3 + tg3 driver version 3.43f. I'm connecting eth0 and eth1 to a Cisco 2948 (CatOS 8.1(3)) and receiving flapping notices. The ethernet address is that of the primary interface. I have tried several different modes, including balance-rr (0), active-backup (1), and balance-alb (6). All have the

--- ../multipath-tools-0.2.8.1/klibc/klibc/arch/i386/MCONFIG 2004-07-20 10:51:42.000000000 +0200 +++ klibc/klibc/arch/i386/MCONFIG 2004-07-27 17:10:12.000000000 +0200 @@ -13,7 +13,7 @@ # them to be cdecl # REGPARM = -mregparm=3 -DREGPARM -gcc_major := $(shell $(CC) -v 2>&1 | awk '/gcc version/{print int($$3)}') +gcc_major := $(shell unset LANG;$(CC) -v 2>&1 | awk

I have installed OCFS2 on two nodes SuSE 10. Seems all works superb and nice from the first sight. But, /dev/sda ocfs2 rac1 is not sharing through net (port 7777) with rac0. On both nodes I have 500Mb /dev/sda disks that are mounted (and are ocfs2). But they did not share the content with each other (files and folders in it). So when I am creating the file in one node I am expecting to

[Added Chris Wright, Rusty and Virt list because they were involved with this issue before] On Thu, 3 Jan 2008, Ingo Molnar wrote: > > * Steven Rostedt <rostedt@goodmis.org> wrote: > > > +# function tracing might turn this off: > > +config REGPARM > > + bool > > + depends on !MCOUNT > > + default y > > are you sure -pg really needs this? Nope!

[Added Chris Wright, Rusty and Virt list because they were involved with this issue before] On Thu, 3 Jan 2008, Ingo Molnar wrote: > > * Steven Rostedt <rostedt@goodmis.org> wrote: > > > +# function tracing might turn this off: > > +config REGPARM > > + bool > > + depends on !MCOUNT > > + default y > > are you sure -pg really needs this? Nope!

If you have used * to support a pri as pri_net (as opposed to pri_cpe), either to talk to another * system or a PBX of some sort, I would be very interested in hearing about your experiences. Imparticular, I would like to know that it works before I invest in the extra hardware. TIA Bruce Komito High Sierra Networks, Inc. www.servers-r-us.com (775) 284-5800 ext 115

Macros to use VMI calls from assembly and C languages are introduced. The macros are quite complex, but the end result is rather impressive. The result is that when compiling a VMI kernel, the native code is emitted inline, with no function call overhead, and some wiggle room for register allocation. The hypervisor compatibility code is emitted out of line into a separate section, and patched

Macros to use VMI calls from assembly and C languages are introduced. The macros are quite complex, but the end result is rather impressive. The result is that when compiling a VMI kernel, the native code is emitted inline, with no function call overhead, and some wiggle room for register allocation. The hypervisor compatibility code is emitted out of line into a separate section, and patched