Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #52765 > unrolled thread

Bug#814301: initramfs-tools: module microcode not found in modules.dep

Back to article view | Back to linux.debian.kernel

Contents

  Bug#814301: initramfs-tools: module microcode not found in modules.dep Kevin Locke <kevin@kevinlocke.name> - 2016-02-10 06:30 +0100
    Processed: Re: Bug#814301: initramfs-tools: module microcode not  found in modules.dep owner@bugs.debian.org (Debian Bug Tracking System) - 2016-02-10 17:00 +0100
    Bug#814301: initramfs-tools: module microcode not found in modules.dep Ben Hutchings <ben@decadent.org.uk> - 2016-02-10 17:00 +0100

#52765 — Bug#814301: initramfs-tools: module microcode not found in modules.dep

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

[toc] | [next] | [standalone]

#52770 — Processed: Re: Bug#814301: initramfs-tools: module microcode not found in modules.dep

Processing control commands:

> reassign -1 intel-microcode
Bug #814301 [initramfs-tools] initramfs-tools: module microcode not found in modules.dep
Bug reassigned from package 'initramfs-tools' to 'intel-microcode'.
No longer marked as found in versions initramfs-tools/0.120.
Ignoring request to alter fixed versions of bug #814301 to the same values previously set

-- 
814301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814301
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#52772

[Multipart message — attachments visible in raw view] — view raw

Control: reassign -1 intel-microcode

On Tue, 2016-02-09 at 21:20 -0800, Kevin Locke wrote:
> 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.

It is a bug in intel-microcode, but only due to a change in Linux 4.4 -
the microcode driver can no longer be built as a module.

Ben.

-- 
Ben Hutchings
Beware of bugs in the above code;
I have only proved it correct, not tried it. - Donald Knuth

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web