Your message dated Thu, 01 May 2025 17:40:14 +0200 (CEST)
with message-id <20250501154014.60280be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1043355,
regarding linux: Select MICROCODE_LATE_LOADING
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 ow...@bugs.debian.org
immediately.)


-- 
1043355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 6.5~rc4-1~exp1
Severity: Normal


Dear Debian folks,


Currently, Debian’s Linux kernel does not allow late loading microcode updates. Although discouraged, there are environments where that is preferred to rebooting/kexec’ing the system. It’d be great, if you could enable this.

The option was introduced in Linux 5.19, and backported to Linux 5.15.99. Before the feature was working, but as the config defaults to no, it no longer does.

    $ grep LATE_L /boot/config-6.*
    /boot/config-6.4.0-1-amd64:# CONFIG_MICROCODE_LATE_LOADING is not set
    /boot/config-6.5.0-0-amd64:# CONFIG_MICROCODE_LATE_LOADING is not set

The reason is, that the commit adding the new option `CONFIG_MICROCODE_LATE_LOADING`, introduced in Linux with commit a77a94f86273 (x86/microcode: Default-disable late loading) [1] was backported to stable release v5.15.99 in commit 6d2b3a31 [2], and the Linux configuration was not updated.


Kind regards,

Paul


[1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a77a94f86273ce42a39cb479217dd8d68acfe0ff [2]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6d2b3a319144f3f5148d8a2b19549ea3bb118c2e
--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a (very) old kernel or the bug is old itself
without resolution. Maybe it was for a feature enablement which nobody
acted on. We are sorry we were not able to timely deal with this issue.
There are many open bugs for the src:linux package and thus we are
closing older bugs where it's unclear if they still occur in newer
versions and are still relevant to the reporter. For an overview see:
https://bugs.debian.org/src:linux .

If you can reproduce your issue with

- the current version in unstable/testing
- the latest kernel from backports

or, if it was a feature addition/wishlist and still consider it
relevant, then:

Please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Please try to provide as much fresh details including kernel logs where
relevant. In particular were an issue is coupled with specific hardware we
might ask you to do additional debugging on your side as the owner of the
hardware.

Regards,
Salvatore

--- End Message ---

Reply via email to