Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 162801 - ia64 boot.img's vmlinuz corrupt
Summary: ia64 boot.img's vmlinuz corrupt
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2005-07-08 18:46 UTC by Prarit Bhargava
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-07-08 19:00:15 UTC

Attachments (Terms of Use)

Description Prarit Bhargava 2005-07-08 18:46:49 UTC
Description of problem: 
I noticed that the boot.img vmlinuz image did not unpack properly and was 
a different size than expected. 
The ia64 build process yields: 
Loading /lib/kbd/keymaps/i386/qwerty/ 
Loading /lib/kbd/keymaps/i386/qwerty/ 
Loading /lib/kbd/keymaps/i386/qwerty/ 
cannot find package kernel-BOOT in 
path /mnt/redhat/nightly/rawhide-20050708/ia64/Fedora/RPMS 
kernel-BOOT does not exist for ia64 -- using kernel package 
unpacking /mnt/redhat/nightly/rawhide-20050708/ia64/Fedora/RPMS/kernel-2.6.12-1.1422_FC5.ia64.rpm.ia64 
Wrote /tmp/makebootdisk.initrdimage.7107 (6720k compressed) 
cp: writing `/tmp/makebootdisk.tree.7107/vmlinuz': No space left on device 
(and continues on) 
Version-Release number of selected component (if applicable): 
How reproducible: 
Steps to Reproduce: 
1.  build installation 
Actual results: 
Build finishes, but kernel image is corrupt. 
Expected results: 
Build should fail? -- Jeremy, what do you think? 
Additional info: 
I'm going to pursue this for ia64.

Comment 1 Jeremy Katz 2005-07-08 19:00:15 UTC
Looks like the size of the boot.img just isn't big enough.  Bumped a bit.

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