linux-kernel - Re: microcode should perform update after suspend to disk

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 04 Jan 2012 09:53:58 +0100
From:	Sven Köhler <sven.koehler@...il.com>
To:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
CC:	linux-kernel@...r.kernel.org, Borislav Petkov <bp@...64.org>,
	Linux PM mailing list <linux-pm@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: microcode should perform update after suspend to disk

Am 04.01.2012 07:07, schrieb Srivatsa S. Bhat:
> Which kernel version are you using?

I was using 3.1.4 or something. However, I updated to 3.1.7 lately.
Sorry, I should have mentioned that.

> I tried doing suspend-to-ram and suspend-to-disk on latest kernel (3.2-rc7+)
> and I saw exactly the same messages getting emitted from the microcode
> module in both cases. Not sure what is going wrong in your case...

I'm absolutely puzzled, cause I just tried to reproduce it again, and
microcode was updated successfully during resume from suspend to disk. I
apologize for the noise.


Regards,
  Sven
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/