Bug 162763 - i586 kernel modules show wrong arch in vermagic
Summary: i586 kernel modules show wrong arch in vermagic
Status: CLOSED DUPLICATE of bug 165603
Alias: None
Product: Fedora
Classification: Fedora
Component: cman-kernel   
(Show other bugs)
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Chris Feist
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-07-08 13:36 UTC by Chris Evich
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-29 21:03:47 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Chris Evich 2005-07-08 13:36:43 UTC
Description of problem:
Have a somewhat FC4 box that I'm trying to setup as a gnbd server.  All the
cluster stuff installed fine and without error (after manually finding and
resolving upgrade dependencies).  When trying to load any of the cluster modules
I get a "Invalid module format" error.  Looking in messages it indicates the
vermagic is wrong for the module.  Further investigation shows:

# QF='%{name}-%{version}-%{release}.%{arch}\n'
# rpm -q --qf "$QF" cman-kernel
# modinfo -F vermagic cman
2.6.11-1.1369_FC4 686 REGPARM 4KSTACKS gcc-4.0
# rpm -q --qf "$QF" dlm-kernel
# modinfo -F vermagic dlm
2.6.11-1.1369_FC4 686 REGPARM 4KSTACKS gcc-4.0
# rpm -q --qf "$QF" gnbd-kernel
# modinfo -F vermagic gnbd
2.6.11-1.1369_FC4 686 REGPARM 4KSTACKS gcc-4.0
# uname -vrpimo
2.6.11-1.1369_FC4 #1 Thu Jun 2 22:53:35 EDT 2005 i586 i586 i386 GNU/Linux
# rpm -q --qf "$QF" gcc
# rpm -q --qf "$QF" glibc glibc-kernheaders

As you can see, the i586 packages are installed but the actual modules are
tagged i686, perhaps there was a mistake building from the SRPM?

Comment 1 Chris Evich 2005-07-19 11:52:21 UTC
Found the same to be true for the GFS modules as well.  Also checked the later
2.6.12-1398 kernel, it has the same problem.

Comment 2 Chris Feist 2005-07-19 19:44:23 UTC
The problem is caused by looking for kernel devel information in
/lib/modules/`uname -r`/build we need to be looking for that information in
/usr/src/kernels/`unamr -r`-i586.  I'll work on getting this fixed.

Comment 3 Chris Feist 2006-09-29 21:03:47 UTC

*** This bug has been marked as a duplicate of 165603 ***

Note You need to log in before you can comment on or make changes to this bug.