search

mfrw / compcache

Automatically exported from code.google.com/p/compcache
0 stars 0 forks source link

compcache modules not usable on fedora with 2.6.31.9-174.fc12.i686 kernel. "Invalid module format" #51

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. compile compache-0.6 on fedora kernel 2.6.31.9-174.fc12.i686
2. execute load_modules.sh
3.

What version of the product are you using? On what operating system?
compache 0.6 on fedora 12 kernel 2.6.31.9-174.fc12.i686

Please provide any additional information below.

Compile on 2.6.31.6-166.fc12.i686 kernel worked fine.

Error displayed:

[root@i4000 compcache-0.6]# ./load_modules.sh 
Loading modules ...
insmod: error inserting './xvmalloc.ko': -1 Invalid module format
insmod: error inserting './ramzswap.ko': -1 Invalid module format
Done!

Original issue reported on code.google.com by rvpitt...@gmail.com on 11 Jan 2010 at 10:19

GoogleCodeExporter commented 9 years ago 
Tried with the same kernel version but everything works as expected on my side.
Try cleaning up old binaries and rebuild:

make clean
make

Original comment by nitingupta910@gmail.com on 11 Jan 2010 at 11:35

GoogleCodeExporter commented 9 years ago 
I did a make clean...even did a fresh tar -zxvf ....the only additional thing 
I've
notice is a warning at compile time but I'm not sure if the warning was always 
there
or not.

Compile time warning for both modules was:

WARNING: "preempt_schedule" [/workarea/compcache-0.6/ramzswap.ko] undefined!

Original comment by rvpitt...@gmail.com on 11 Jan 2010 at 12:54

GoogleCodeExporter commented 9 years ago 
> WARNING: "preempt_schedule" [/workarea/compcache-0.6/ramzswap.ko] undefined!

This warning makes sure that module will fail to load.
Can you please confirm if you have same version for following 3 packages:
 - kernel
 - kernel-devel
 - kernel-headers

If all these packages have same version and you still get this error, please 
provide:
 - full compiler output
 - kernel log
 - uname -a

Original comment by nitingupta910@gmail.com on 11 Jan 2010 at 2:03

GoogleCodeExporter commented 9 years ago 
The attached error.txt shows the kernel packages are in sync, the output of the
compile and the results of uname -a.  I'm unsure what kernel log you want so if 
you
can clarify for me I'll be happy to provide.  As mentioned before,  If I go 
back to
the previous kernel (166) it compiles/works fine.  I am using the "default" 
kernel
and have not compiled my own.

Original comment by rvpitt...@gmail.com on 12 Jan 2010 at 10:40

Attachments:

GoogleCodeExporter commented 9 years ago 
Can you try compiling compcache version attached?
If this fails to compile, please provide verbose compiler output from:

make V=1

this error.txt was sufficient. No kernel logs are required.

Original comment by nitingupta910@gmail.com on 12 Jan 2010 at 1:59

Attachments:

GoogleCodeExporter commented 9 years ago 
Your new version creates the ramzswap.ko and I don't see the warning in the 
compile
however the xvmalloc.ko is not being created.  I went into the allocator subdir 
and
did make there and got the same error as before.  The verbose make you 
requested is
attached.

Original comment by rvpitt...@gmail.com on 12 Jan 2010 at 2:17

Attachments:

GoogleCodeExporter commented 9 years ago 
Ah, I forgot to tell you that this new version does not create separate xvmalloc
module. It just creates single ramzswap module. Try loading and using this
ramzswap.ko module.

Original comment by nitingupta910@gmail.com on 12 Jan 2010 at 2:29

GoogleCodeExporter commented 9 years ago 
Loading failed with the same error.

[root@i4000 compcache-0.6.1]# ./load_modules.sh
Loading modules ...
insmod: error inserting './ramzswap.ko': -1 Invalid module format
Done!

This is from the make verbose previously attached.

Original comment by rvpitt...@gmail.com on 12 Jan 2010 at 3:06

GoogleCodeExporter commented 9 years ago 
I'm confused. Some googling reveals some other instances of similar problem:
http://fedoraforum.org/forum/showthread.php?t=32348&page=2
(see comment #16 and #19)
In this case, simply reinstalling fedora worked.

So, in your case, maybe, there is some dependency which does not match running
kernel. Can you try compiling after upgrading everything to make sure that all
packages are in sync? (yum upgrade -y)

I suspect some sort of dependency problem on your side since I don't get any 
problem
on my Fedora 12 (x86 and x86_64) machines.

Original comment by nitingupta910@gmail.com on 13 Jan 2010 at 1:28

GoogleCodeExporter commented 9 years ago 
I did a "yum upgrade -y" and it says I'm current as I've been installing 
available
updates....I could try uninstalling the 174 kernel and reinstalling 
maybe....not sure
what dependency would only affect the 174 kernel and not affect the 166 
one....I went
back to the 166 kernel and did the whole compile sequence there and it compiled 
and
loaded fine.  I suppose I can always just stick with the 166 kernel and see if 
the
next version works ok.

Original comment by rvpitt...@gmail.com on 13 Jan 2010 at 2:07

GoogleCodeExporter commented 9 years ago 
Following your advise I uninstalled the 174 kernel, kernel-devel and 
kernel-headers.
  I then reinstalled them and tried to compile compache again and it worked fine.   I
can only assume something was corrupted during the automated update process to 
the
new kernel.  Previously I had uninstalled the kernel but not the devel and 
headers. 
This issue can be closed and my thanks for helping me figure out the cause.

Original comment by rvpitt...@gmail.com on 13 Jan 2010 at 6:42

GoogleCodeExporter commented 9 years ago

Original comment by nitingupta910@gmail.com on 14 Jan 2010 at 1:53

GoogleCodeExporter commented 9 years ago 
does comp-cache works for kernel version 3.0 onward.
please reply
thanks arpan

Original comment by arpan.de...@gmail.com on 8 Feb 2012 at 1:29

GoogleCodeExporter commented 9 years ago 
Yes, it does work for kernel versions >= 3.0. In fact zram version included 
with these newer kernels is more recent than what's available for download (or 
what's in the repository).  I will try to sync the two versions after some more 
pending changes are accepted in the mainline.

Original comment by nitingupta910@gmail.com on 8 Feb 2012 at 1:46