lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 01 Jan 2012 17:37:13 +0100
From:	Sven Köhler <>
Subject: microcode should perform update after suspend to disk


at startup I load the microcode module and it correctly loads the
microcode from /lib/firmware/intel-ucode/. In dmesg, I can see that the
microcode has been updated from 0xc to 0xd.
After suspend to ram, dmesg shows new messages from the microcode
module, telling me that the microcode is still at revision 0xd. Hence,
no update is performed.
However, after suspend to disk, dmesg shows no new messages from the
microcode module. After rmmod microcode; modprobe microcode dmesg tells
me that the microcode had to be updated from 0xc to 0xd.

Somethings wrong here. My interpretation of the messages in dmesg is,
that microcode is trying to update the microcode after suspend to ram
but not after suspend to disk. It should try in both cases. Note that I
don't unload the microcode module.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists