Bug 125381 - 2.6.6-1.422 fails to install properly
Summary: 2.6.6-1.422 fails to install properly
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-06-05 17:01 UTC by Kaj J. Niemi
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-06-05 17:08:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kaj J. Niemi 2004-06-05 17:01:13 UTC
Description of problem:
The %postinstall scriptlet fails while attempting to create a new
initrd image.

Version-Release number of selected component (if applicable):
kernel-2.6.6-1.422
mkinitrd-3.5.23-1
module-init-tools-3.0-0.pre10.1


How reproducible:
Always

Steps to Reproduce:
1. rpm -ivh kernel-2.6.6-1.422.i686.rpm
2. 
3.
  
Actual results:
# rpm -ivh kernel-2.6.6-1.422.i686.rpm
Preparing...               
########################################### [100%]
   1:kernel                
########################################### [100%]
memlock: Cannot allocate memory
Couldn't lock into memory, exiting.
mkinitrd failed


Expected results:
Should install normally.

Additional info:
2.6.6-1.414 (and earlier ones) worked fine

Comment 1 Kaj J. Niemi 2004-06-05 17:02:24 UTC
Executing the same commands manually results in the same thing.

# [ -x /sbin/new-kernel-pkg ] && /sbin/new-kernel-pkg --mkinitrd
--depmod --install 2.6.6-1.422
memlock: Cannot allocate memory
Couldn't lock into memory, exiting.
mkinitrd failed
#


Comment 2 Arjan van de Ven 2004-06-05 17:03:34 UTC
this is actually a bug in 414 that you are running;
ulimit -l unlimited before the rpm -i will fix it


Comment 3 Kaj J. Niemi 2004-06-05 17:08:36 UTC
Yup, that one does it. Thanks. Closing as WORKSFORME.


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