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:	Sun, 14 Jun 2015 18:47:45 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Christoph Fritz <chf.fritz@...glemail.com>
Cc:	Daniel J Blueman <daniel@...ra.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: lockup when C1E and high-resolution timers enabled

On Sun, Jun 14, 2015 at 06:39:56AM +0200, Christoph Fritz wrote:
> Don't you mean family 15h for 'AMD FX(tm)-8350' ?
> 
> already using latest microcode:
> 
> [    0.514490] microcode: CPU0: patch_level=0x06000822
> [    0.514497] microcode: CPU1: patch_level=0x06000822
> [    0.514508] microcode: CPU2: patch_level=0x06000822
> [    0.514519] microcode: CPU3: patch_level=0x06000822
> [    0.514529] microcode: CPU4: patch_level=0x06000822
> [    0.514540] microcode: CPU5: patch_level=0x06000822
> [    0.514550] microcode: CPU6: patch_level=0x06000822
> [    0.514561] microcode: CPU7: patch_level=0x06000822

This is not the latest microcode.

This is the latest:

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 21
model           : 2
model name      : AMD FX(tm)-8350 Eight-Core Processor
stepping        : 0
microcode       : 0x6000832
		  ^^^^^^^^^

in your first email, you did have the latest:

$ cat /proc/cpuinfo
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 21
model           : 2
model name      : AMD FX(tm)-8350 Eight-Core Processor
stepping        : 0
microcode       : 0x6000832

so what changed?

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ