Your message dated Sat, 23 Apr 2016 15:50:52 +0000
with message-id <[email protected]>
and subject line Bug#814301: fixed in intel-microcode 3.20151106.2
has caused the Debian Bug report #814301,
regarding intel-microcode: module microcode not found in modules.dep
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
814301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814301
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.120
Severity: minor

Dear Maintainer,

When the intel-microcode package is installed and the running kernel
configured with CONFIG_MICROCODE=y, the following message is printed at
boot:

Loading, please wait...
modprobe: module microcode not found in modules.dep

It is likely invisible to most users, but appears immediately before the
cryptsetup prompt if the root filesystem is encrypted.

The cause appears to be that intel-microcode calls `force_load
microcode` from its hook script[1] which unconditionally adds its
arguments to /conf/modules in the initramfs, which results in the above
error when the module is not present.

Although this could be considered a bug in intel-microcode, the other
uses of force_load that I could find do not appear to protect against
this case, so it seems appropriate to fix it there.  But do reassign if
you disagree.

Thanks,
Kevin

1.  
https://anonscm.debian.org/cgit/users/hmh/intel-microcode.git/tree/debian/initramfs.hook?h=debian/3.20151106.1_deb8u1#n123


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.1+kevinoid1+ (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages initramfs-tools depends on:
ii  busybox      1:1.22.0-18
ii  cpio         2.11+dfsg-4.1
ii  klibc-utils  2.0.4-7
ii  kmod         22-1
ii  udev         228-6

Versions of packages initramfs-tools recommends:
ii  busybox  1:1.22.0-18

Versions of packages initramfs-tools suggests:
ii  bash-completion  1:2.1-4.2

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: intel-microcode
Source-Version: 3.20151106.2

We believe that the bug you reported is fixed in the latest version of
intel-microcode, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Henrique de Moraes Holschuh <[email protected]> (supplier of updated 
intel-microcode package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 17 Apr 2016 12:38:12 -0300
Source: intel-microcode
Binary: intel-microcode
Architecture: source amd64
Version: 3.20151106.2
Distribution: unstable
Urgency: medium
Maintainer: Henrique de Moraes Holschuh <[email protected]>
Changed-By: Henrique de Moraes Holschuh <[email protected]>
Description:
 intel-microcode - Processor microcode firmware for Intel CPUs
Closes: 814301
Changes:
 intel-microcode (3.20151106.2) unstable; urgency=medium
 .
   * Makefile: make the build less verbose.
   * debian/changelog: fix error in past entry.
     Correct the version of the microcode that caused bug #776431,
     in the entry for version 3.20150121.1.
   * initramfs: don't force_load microcode.ko when missing.
     Detect a missing microcode.ko and don't attempt to force_load() it,
     otherwise we get spurious warnings at boot.  In verbose mode, log the
     fact that the microcode driver is modular.   For Linux 4.4 and later,
     skip the entire module loading logic, since the microcode driver cannot
     be modular for those kernels (closes: #814301).
   * initramfs: update copyright notice
   * initramfs: use iucode_tool -l for verbose mode
   * README.Debian: enhance and add recovery instructions.
     Rewrite large parts of the README.Debian document, and add recovery
     instructions (use of the "dis_ucode_ldr" kernel parameter).
Checksums-Sha1:
 f5e606a56ecf5eff13f0708af0508e0f4537b3b3 1774 intel-microcode_3.20151106.2.dsc
 ce258fd61ae8f42356f577fc52b9e53c5abd7920 937940 
intel-microcode_3.20151106.2.tar.xz
 38a07e2d31752904c48f2e99b8c58958a30eaa97 474500 
intel-microcode_3.20151106.2_amd64.deb
Checksums-Sha256:
 679006ea58510443c624c3f6994ad3ab187c5af560eb7c0effe5e6662ca6f314 1774 
intel-microcode_3.20151106.2.dsc
 3a4fd21c4a9ec183716b0f8032177c485d15ac67a4f6a224299bdb02b4611854 937940 
intel-microcode_3.20151106.2.tar.xz
 355dd67446a185c477fce76f6138bba1597eb0a908d38317471f756319c7ba84 474500 
intel-microcode_3.20151106.2_amd64.deb
Files:
 d11749e8a5acdb27c738c9eccdcccfff 1774 non-free/admin standard 
intel-microcode_3.20151106.2.dsc
 af2377e435fc8f467251f94a9591ec3f 937940 non-free/admin standard 
intel-microcode_3.20151106.2.tar.xz
 3a2b0ff83f99161e12c428f4bec19d72 474500 non-free/admin standard 
intel-microcode_3.20151106.2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJXE8xHAAoJEP4Rv6aLFY6YLLkP/2MancC6QuxbDksztbTcSADI
SaBFgmDfB6lHIV5kcblk8FXEc+4oe8aD7qs7u1YEbsoZsBKOcv8g9J+HlPnX4U5P
GZvONmpLchIYirlFbj5/DjI4cjlAqxsctaCfCS2gi6TrGrnMC0dk6Cud2ud6y3qy
g0KgW7Yyu9XrFiMMHu4yM5UhDRzGbvVPDPO4nEP29RAu5VLL5vQ+hcnzPuufQ0rS
gbZAwP77SLV0JBUmczzM4rdev6uRIHrhEbi5mjpJ0euSPeeGwB8QvShXZtCQo0Ti
WzvT4IF9QSwha/OlwCdWriQNfWbH986zbWloHKPvpUu9hiBQdOJcBZh/IpcOOaFK
YW1W6XVV5rSYyMB0UkXXzXS3TmJm2AUvZbFoa2lspWJfiyI6fmV2vv0y+mopJ+PL
BL8My64YG8lN0c2oJnwoxS9jyG6UfdPqM+Ib4SshE++rNQoVegB08fOdySENIolI
ote+3dujC4R/QpHrJJIJv8zVCxTf5CBGlgdNBTR/UIbn+bunAdk6gRw13QVVfgzg
mCM5MWygA9LpDuHfDofa+RG7DF89dLGT3bKwmRqupUc1eRmLvXFjr8bYRWQjVYKB
DTuf7oaCECvBiUaRbbUOo+Hs2v7+1idg0Ul/Jd3OeK8qN5CHYyAzuT4tg4WhTfdL
P/5OEuGs+pLGzeRIAWBk
=mXo0
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to