Bug 27006 - kernel-2.2.17-14 unresolved module symbols
kernel-2.2.17-14 unresolved module symbols
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
6.2
sparc64 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-10 22:39 EST by Charles R. Anderson
Modified: 2008-08-01 12:22 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-30 11:38:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Charles R. Anderson 2001-02-10 22:39:17 EST
I just upgraded my Red Hat 6.2 (zoot) sparc64 system to kernel-2.2.17-14,
and two modules have unresolved symbols:

#/sbin/depmod -a
depmod: *** Unresolved symbols in /lib/modules/2.2.17-14/misc/ffb.o
depmod: *** Unresolved symbols in /lib/modules/2.2.17-14/net/cipcb.o
Comment 1 Bill Nottingham 2001-02-13 19:15:33 EST
depmod -ae output is a little more helpful.
Comment 2 Charles R. Anderson 2001-02-13 19:20:37 EST
Ok, here it is:

#/sbin/depmod -ae
depmod: *** Unresolved symbols in /lib/modules/2.2.17-14/misc/ffb.o
depmod:         pte_wrprotect
depmod:         agp_enable
depmod:         io_remap_page_range
depmod: *** Unresolved symbols in /lib/modules/2.2.17-14/net/cipcb.o
depmod:         L_Blowfish_Decrypt
depmod:         L_Blowfish_Encrypt
Comment 3 Michael K. Johnson 2001-02-13 20:18:22 EST
Those modules are new in that kernel and should simply not have
been turned on.  You can ignore those errors for now; they will
go away in the next errata kernel we release.
Comment 4 Bugzilla owner 2004-09-30 11:38:54 EDT
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

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