severity 760765 grave thanks On Sun, 07 Sep 2014, A Mennucc wrote: > Package: intel-microcode > Version: 2.20140624.1 > Severity: critical > Justification: breaks the whole system
Urk. > I have installed a small wheezy system, and then promptly > upgraded it to jessie. This system has rootfs crypted > with cryptsetup (altogh I am not sure this is relevant). This is likely an important point, as the early initramfs is known to work in the general case (I use it everywhere, for example). And I know for a fact a lot of users are using it safely with 3.14 (or at least were using it safely until a week ago), so I will lower the severity to grave for the moment. > When I try to boot using 3.14-2-amd64 , the scripts in initrd > complain that it cannot find the rootfs. Ok. > I tried to investigate the problem, and found this startling > fact. Usually initrd.img is a CPIO archive, compressed > with GZIP. Instead, initrd.img-3.14-2-amd64 is a CPIO file > but not compressed, and it seems to contain only this file This is normal. It is called an hybrid initramfs, with an early initramfs prepended to the regular initramfs. It is supported by every kernel in different ways: The kernel will load cpio *segments* it finds. Each segment can be in any of the formats it supports. It will just overlay one on the top of the other. > $ cpio -t < /boot/initrd.img-3.14-2-amd64 > kernel > kernel/x86 > kernel/x86/microcode > kernel/x86/microcode/GenuineIntel.bin > > (even if initrd.img-3.14-2-amd64 is itself quite large, roughly 14MB). There are no userspace tools to process initramfs archives. We have stuff that handles cpio just fine, but nothing that can really read a fully-featured initramfs the same way the kernel does. You can strip off the first initramfs (the one with the microcode), and you should have the regular compressed initramfs. > After some fiddling, I noted that if I delete the file > /usr/share/initramfs-tools/hooks/intel_microcode > and regenerate initrd.img-3.14-2-amd64 > then it is fine. Unfortunately I cannot understand > why it is broken. Just edit /etc/default/intel-microcode to work around the problem. > You may find the broken initrd in > http://mennucc1.debian.net/tmp/initrd.img-3.14-2-amd64 Ah, thanks. will inspect. > Versions of packages intel-microcode depends on: > ii iucode-tool 1.0.3-1 This could be relevant, as it has a workaround that creates a filename with NULs at the end (which the kernel, Debian cpio and pax will ignore, but still maybe some other tool is at play). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
