Bug 55324 - "loop.o: unresolved symbol" w/ 2.4.9-7.5
Summary: "loop.o: unresolved symbol" w/ 2.4.9-7.5
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.3
Hardware: s390
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact: David Sainty
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-10-29 18:43 UTC by David Sainty
Modified: 2007-04-18 16:37 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2001-11-05 11:35:21 UTC


Attachments (Terms of Use)

Description David Sainty 2001-10-29 18:43:10 UTC
Description of Problem:
w/ 2.4.9-7.5 kernel loaded w/ install image (RDR), I mount /dev/dasda1 (/)
and chroot - to install a new kernel.

rpm -ivh <new kernel rpm> works;  mkinitrd fails since loop.o is required.
loop.o cannot be insmod'ed because:

bash-2.05# /sbin/insmod /lib/modules/2.4.9-7.5/kernel/drivers/block/loop.o
/lib/modules/2.4.9-7.5/kernel/drivers/block/loop.o: unresolved symbol
generic_make_request_Rsmp_31f0df97
/lib/modules/2.4.9-7.5/kernel/drivers/block/loop.o: unresolved symbol
blk_queue_make_request_Rsmp_9e6e41d1

arjan's comments:

<arjan> saint: oh that's a s390 specific bug
<arjan> it needs a define in a header
...
<saint> arjan: is it already fixed?
<arjan> not 100% sure

Version-Release number of selected component (if applicable):
Installer env. from 7.2 RC2
kernel-2.4.9-7.5

How Reproducible:
Always

Steps to Reproduce:
1. see above.

Comment 1 Harald Hoyer 2001-11-05 11:34:40 UTC
retry with 2.9.7-9.1 or 2.9.7-13


Comment 2 Harald Hoyer 2001-11-05 11:35:14 UTC
oops, meant 2.4.9, of course :)


Comment 3 Karsten Hopp 2001-11-13 12:30:49 UTC
You need to do the insmod before you chroot ! The modules of the -BOOT kernel
are not copied into the chroot directories.
insmod loop.o works for me.


Comment 4 Harald Hoyer 2001-11-13 13:08:34 UTC
good point, karsten



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