Red Hat Bugzilla – Bug 816040
panic at initramfs unpacking failure on EFI Mac boot
Last modified: 2013-03-14 14:44:51 EDT
Description of problem:
Initramfs unpacking failed: broken padding
Version-Release number of selected component (if applicable):
kernel 3.3.2-8.fc17.x86_64 on Fedora-Mac-EFI-test.iso located at
Steps to Reproduce:
1. gdisk to nuke GPT and MBR off a USB stick.
2. dd if=ISO of=/dev/USB
no other options
3. Boot with option/alt key to bring up Mac's startup disk menu.
4. Choose blue Fedora logo icon labeled EFI Boot.
5. At GRUB menu wait for timeout.
glorious successful boot.
Screenshot is from MacBook Pro 4,2 (2008).
A MacBook Pro 8,2 (2011) seems to panic also. Screen appears as in this bug, except is freezes about 1/2 way down, and I can't blindly get to a console to reboot as I normally can from livecd-iso-disk based USB sticks.
Created attachment 580071 [details]
photo of panic
I said screenshot, I meant photo. Madness.
Correction: MacBook Pro 4,1 (2008), not 4,2.
Addition 1: When this ISO is burned to a disk, and I CSM boot from it by selecting the "Windows" option, the panic does not occur.
Created attachment 580087 [details]
photo of panic 2a
Removed 'rhgb quiet' to get more text, and I consistently get a different panic cause than when I don't edit params. This is as early as I can get it. Next shot will contain the panic.
Created attachment 580088 [details]
photo of panic 2b
This is the shot about 1/3 of a second after 2a. Contains panic message. But not the initramfs problem found in the original report.
I suspect this is the same thing in both cases, it's just that the initramfs warning has scrolled too far. I suspect that we're managing to put the initramfs in a memory region that something really doesn't like. Let me take a look at the grub code.
Created attachment 580184 [details]
Can you take the USB stick, mount partition 2 on it, copy this grub.efi to EFI/BOOT/BOOTX64.efi and then unmount it and try booting the *non*-Fedora logo image. Grub should print some debug messages about allocating pages - can you either grab a picture of that or transcribe it, and let me know?
Created attachment 580230 [details]
photo of test grub 1
photo of boot results, 580184 test grub, on MBP 4,1
Created attachment 580236 [details]
photo of test grub 2
photo of boot results, 580184 test grub, on MBP 8,2
How much RAM does each of these machines have?
MBP4,1 = 4G
MBP8,2 = 8G
Hm. Haven't been able to reproduce on an MBP 8,2 here.
Perhaps differences in firmware? This model has had an inordinate number of firmware updates from Apple, possibly a record. I've done at least 4. I see I have the current "EFI Boot ROM" version of MBP81.0047.B27. But I am one behind the SMC Version at 1.69f3 instead of 1.70f5. Conversely, the MBP 4,1 has original EFI firmware, a newer one was never issued, there was one SMC update.
I was confused. The SMC 1.70f5 is for the 8,3.
The most recent EFI firmware update for this model was Feb 23. I don't know of a linux command to get this information, but on Mac OS it's:
system_profiler | grep ROM
Boot ROM Version: MBP81.0047.B27
ROM Revision: 113-C0170L-573
system_profiler is part of Darwin, and it's also on the ~620MB Recovery HD partition that will fit on a USB boot stick, and boot a Mac.
Have the same symptoms, but not on a Mac.
ASUS Sabertooth X79 MB
32 Gig RAM
120 Gig SSD
WD 2T Green HD
PNY Quadro 600 graphics adapter (Nvidia-based)
Fedora 16 64bit live CD
Tried also 64bit DVD, FC 17 64bit, etc.
Here the story:
Copied Fedora 16 64-bit live CD onto USB stick using both UNetboot and dd command. In both cases the USB stick would eventually boot (after a long delay).
Installed Fedora on the SSD as follows (all ext4 formatted):
/dev/sda1 - /boot
/dev/sda2 - created following LVs:
/dev/sdb1 - created following LV:
/dev/mapper/vol2-swap as swap drive
Repeatedly tried to boot, but the boot process stops at kernel panic following either init not found or initramfs unpacking failure.
I did different installs, both nogpt and gpt:
/dev/sda1 as BOOTmbr (?) 1 MB
/dev/sda2 as /boot
/dev/sda3 as VG for LVs as listed above.
I can't get the system to boot from disk. Also checked the BIOS settings, and changed them from legacy to UEFI (both didn't help). Furthermore I checked grub.cfg and it points to the kernel files. I also tried to add insmod lvm directly into the grub.cfg, as I haven't seen it in there - didn't help.
The MB has the latest firmware. For comparison, Linux Mint 12 LMDE installs and boots.
Any suggestions are welcome. Hope my report relates to the bug reported.
Is this still an issue in Fedora 18 with the 3.8.2 kernel?
Not an issue with any of the Fedora 18 kernels, including 3.8.2.