Description of problem: When the initrd is created during RHEL5.3 install, the aes_generic.ko file is loaded twice. This generates a harmless (but troubling) error message on boot: insmod: error inserting '/lib/aes_generic.ko': -1 File exists If you look at the init file in the initrd package, you see the cause of the problem: echo "Loading aes-x86_64.ko module" insmod /lib/aes-x86_64.ko echo "Loading aes_generic.ko module" insmod /lib/aes_generic.ko <-- 1st load request echo "Loading aes_generic.ko module" insmod /lib/aes_generic.ko <-- 2nd load request echo "Loading crypto_api.ko module" insmod /lib/crypto_api.ko Version-Release number of selected component (if applicable): RHEL5.3 20081006.0 build How reproducible: Every time the system boots. Steps to Reproduce: 1. Install RHEL5.3, checking the disk encryption checkbox 2. Boot system 3. Error appears Actual results: Error appears on screen, then boot continues normally. Expected results: No errors. Additional info:
Anaconda doesn't do anything special with mkinitrd. In fact, it doesn't even directly call mkinitrd.
In the 32-bit arch, the insmod and echo lines for the /lib/padlock.ko module are duplicated but the aes_generic.ko line only appears once.
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: This release note is for 5.3. When using an encrypted device, you may see the following error message on boot: insmod: error inserting '/lib/aes_generic.ko': -1 File exists This message is harmless and can be ignored.
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,6 +1,5 @@ -This release note is for 5.3. +When using an encrypted device, the following error message may be reported during bootup: -When using an encrypted device, you may see the following error message on boot: insmod: error inserting '/lib/aes_generic.ko': -1 File exists -This message is harmless and can be ignored.+This message can safely be ignored.
Moving to RHEL 5.5 so it doesn't get mistakenly closed by the bot
Denise, isn't this one a duplicate of bug #472227 ? At least they are quite close.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.