Your message dated Wed, 09 Mar 2016 15:29:31 -0500
with message-id
<1457555371.1280128.544567618.2739c...@webmail.messagingengine.com>
and subject line Closing 736892 -- working as designed
has caused the Debian Bug report #736892,
regarding kernel: does not log when it skips an already up-do-date cpu
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.)
--
736892: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736892
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: amd64-microcode
Version: 2.20131007.1+really20130710.1
Severity: normal
Debian stock kernel linux-image-3.10-3-amd64 version 3.10.11-1
seems to be the last "production" kernel that works correctly.
(I didn't try the "rc" ones.) The next kernel after that,
linux-image-3.11-1-amd64 version 3.11.5-1 is the first stock
kernel to show the error. (I obtained these back-level kernel
packages from http://snapshot.debian.org.) The error persists
up to the latest kernel available in Debian testing at this
time.
My motherboard is a Gigabyte GA-78LMT-SP2, PCB revision 5.0,
BIOS version F3. My processor is an AMD FX-4300, which is
a quad-core chip. On newer kernels, only two out of the four
CPUs get their microcode upgraded. (It always seems to be
CPU0 and CPU2 that get upgraded, while CPU1 and CPU3 do not
get upgraded.) On older kernels, all four CPUs get their
microcode upgraded.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
--- End Message ---
--- Begin Message ---
Closing bug report -- working as designed
--
.''`. Stephen Powell <[email protected]>
: :' :
`. `'`
`-
--- End Message ---
