Bug 81219 - unresolved symbols: irlmp_lap_tx_queue_full and cpu_possible
unresolved symbols: irlmp_lap_tx_queue_full and cpu_possible
Status: CLOSED RAWHIDE
Product: Red Hat Raw Hide
Classification: Retired
Component: kernel (Show other bugs)
1.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
:
Depends On:
Blocks: 79578
  Show dependency treegraph
 
Reported: 2003-01-06 15:53 EST by Sammy
Modified: 2007-04-18 12:49 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-02-11 01:19:29 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Sammy 2003-01-06 15:53:02 EST
I installed the 2.4.20-2.6 kernel which is giving the following errors: 
 
# depmod -ae 
depmod: *** Unresolved symbols in 
/lib/modules/2.4.20-2.6/kernel/arch/i386/oprofile/oprofile.o.gz 
depmod:         cpu_possible 
depmod: *** Unresolved symbols in /lib/modules/2.4.20-2.6/kernel/net/irda/irda.o.gz 
depmod:         irlmp_lap_tx_queue_full 
#
Comment 1 Mike McLean 2003-01-06 17:17:14 EST
Seeing those with kernel-2.4.20-2.7, plus the following:

depmod: *** Unresolved symbols in /lib/modules/2.4.20-2.7/kernel/net/tux/tux.o.gz
depmod: 	sys_wait4
Comment 2 Brian Brock 2003-01-07 19:17:18 EST
On `modprobe tux`, with 2.4.20-2.7smp, I get:

/lib/modules/2.4.20-2.7smp/kernel/net/tux/tux.o.gz: unresolved symbol sys_wait4
/lib/modules/2.4.20-2.7smp/kernel/net/tux/tux.o.gz: unresolved symbol
set_cpus_allowed
/lib/modules/2.4.20-2.7smp/kernel/net/tux/tux.o.gz: insmod
/lib/modules/2.4.20-2.7smp/kernel/net/tux/tux.o.gz failed
/lib/modules/2.4.20-2.7smp/kernel/net/tux/tux.o.gz: insmod tux failed


prevents tux from working, blocks testing of the tux (error in userland from
`service tux start` is limited to complaints about missing /proc entries).
Comment 3 Bill Nottingham 2003-02-11 01:19:29 EST
These should all be fixed now.

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