On Tue, Oct 30, 2012 at 09:14:48PM -0200, Henrique de Moraes Holschuh wrote: > References: bugs #690285 and #690286 > > The versions of both intel-microcode and amd64-microcode currently in Wheezy > can trigger a nasty bug in initramfs-tools that renders the system > unbootable. The packages in unstable work around this issue. > > The bug will only happen when $TMPDIR (usually /tmp) is mounted noexec at > the time "update-initramfs" is run. While this is quite unusual, it did hit > one user (bug #689301). > > In addition to the changes fixing that issue, the intel-microcode package > also contains a new upstream release. Intel issued a microcode hotfix for > all current i5/i7/Xeon processors in 2012-10-01. Due to the very unusual > nature of this microcode update (it is labeled "20120606-v2" by Intel, a > strong hint that it is fixing mishaps in the microcode release currently in > Wheezy), and the inclusion of microcode updates even to very high-end Xeon > E7 processors, it is likely fixing something very relevant. > > The packages have been 20 days in unstable already, without any issues > reported. > > Please consider unblocking intel-microcode (#690286) and amd64-microcode > (#690285).
Really pretty please file an unblock bug for each package next time, thanks.
--- amd64-microcode-1.20120910/debian/initramfs.init-premount 2012-09-14
15:27:31.000000000 +0000
+++ amd64-microcode-1.20120910/debian/initramfs.init-premount 2012-10-09
11:17:36.000000000 +0000
@@ -9,7 +9,7 @@
# dependencies: firmware loader, microcode kernel support (built-in/module)
-PREREQ="udev"
+PREREQ=""
prereqs()
{
If the main problem was in the name of the script, why is this still needed?
Same for intel-microcode.
Kind regards
Philipp Kern
signature.asc
Description: Digital signature
