Bug 444417 - fscache module not included in with nfs root initrd
Summary: fscache module not included in with nfs root initrd
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: mkinitrd
Version: 5.2
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Brian Lane
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-28 10:39 UTC by Arnd Bergmann
Modified: 2013-03-20 13:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-20 13:36:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Arnd Bergmann 2008-04-28 10:39:25 UTC
Version-Release number of selected component (if applicable):

RHEL5u1 with kernel-debug-2.6.18-91.el5.ppc64.rpm prerelease kernel

How reproducible:

Follow the instructions for NFS root from
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/release-notes/RELEASE-NOTES-U1-ppc-en.html

The machine is a diskless IBM QS21 Cell/B.E. blade server.
  
Actual results:

Boot messages contain:
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 5 ports detected
Loading sunrpc.ko module
Loading nfs.ko module
nfs: Unknown symbol __fscache_relinquish_cookie
nfs: Unknown symbol __fscache_write_page
nfs: Unknown symbol __fscache_uncache_page
nfs: Unknown symbol __fscache_set_i_size
nfs: Unknown symbol nlmclnt_proc
nfs: Unknown symbol __fscache_acquire_cookie
nfs: Unknown symbol nfsacl_encode
nfs: Unknown symbol nfsacl_decode
nfs: Unknown symbol __fscache_read_or_alloc_pages
nfs: Unknown symbol lockd_down
nfs: Unknown symbol lockd_up_proto
nfs: Unknown symbol __fscache_read_or_alloc_page
nfs: Unknown symbol __fscache_unregister_netfs
nfs: Unknown symbol __fscache_register_netfs
insmod: error inserting '/lib/nfipr: Unknown symbol ata_sas_port_init
s.ko': -1 Unknowipr: Unknown symbol scsi_device_get
n symbol in moduipr: Unknown symbol scsi_block_requests

Expected results:

regular boot from NFS, as with RHEL5u1 kernel.

Additional info:

This was reported to me by a blade customer, "Howard D. Gray" 
<howard.gray>

The reported fix from him is

== begin quote ==
To get it all working I altered mkinitrd like this:

================== snip ==================
--- /sbin/mkinitrd.ORIG 2008-04-28 08:58:28.856918809 +0200
+++ /sbin/mkinitrd      2008-04-28 10:13:39.838703626 +0200
@@ -69,7 +69,7 @@ modulefile=/etc/modules.conf
 rc=0

 IMAGESIZE=8000
-PRESCSIMODS="sd_mod"
+PRESCSIMODS="sd_mod libata ipr"
 fstab="/etc/fstab"

 vg_list=""
@@ -272,6 +272,9 @@ findmodule() {
         modName="gfs2"
     elif [ "$modName" = "nfs" ]; then
         findmodule sunrpc
+       findmodule fscache
+       findmodule nfs_acl
+       findmodule lockd
         modName="nfs"
     elif [ "$modName" = "usb-storage" -o "$modName" = "ub" ]; then
         usbModName="$modName"
================== snip ==================

My script to build the initrd and combine with the kernel image looks
like this:

================== snip ==================
VERSION=2.6.18-91.el5

rm -f ~/initrd-$VERSION.img
mkinitrd --with tg3 --rootfs=nfs --net-dev=eth0 --with sungem_phy \
        --with  spidernet --with usb-storage --with dm-mod \
        --with dm-snapshot --with dm-zero --with dm-mirror \
        --with dm-crypt --with dm-multipath \
        ~/initrd-$VERSION.img $VERSION

rm -f ~/zImage.initrd-$VERSION
mkzimage ~/vmlinuz-$VERSION ~/config-$VERSION \
        ~/System.map-$VERSION ~/initrd-$VERSION.img \
        /usr/share/ppc64-utils/zImage.stub  ~/zImage.initrd-$VERSION

================== snip ==================
== end quote ==

Comment 1 David Cantrell 2013-03-20 13:36:17 UTC
While Red Hat welcomes bug reports on Red Hat products here in our public
bugzilla database, please keep in mind that bugzilla is not a support tool or
means of accessing support.  If you would like technical support please visit
our support portal at access.redhat.com or call us for information on
subscription offerings to suit your needs.


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