From: Borislav Petkov <bp@alien8.de>
To: Christoph Fritz <chf.fritz@googlemail.com>
Cc: Daniel J Blueman <daniel@quora.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: lockup when C1E and high-resolution timers enabled
Date: Sun, 14 Jun 2015 18:47:45 +0200 [thread overview]
Message-ID: <20150614164745.GA14892@pd.tnic> (raw)
In-Reply-To: <1434256796.1699.5.camel@googlemail.com>
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.
--
next prev parent reply other threads:[~2015-06-14 16:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 3:13 lockup when C1E and high-resolution timers enabled Daniel J Blueman
2015-06-14 4:39 ` Christoph Fritz
2015-06-14 7:54 ` Daniel J Blueman
2015-06-14 14:49 ` Christoph Fritz
2015-06-14 15:24 ` Daniel J Blueman
2015-06-14 23:38 ` Christoph Fritz
2015-06-14 16:47 ` Borislav Petkov [this message]
2015-06-14 23:05 ` Christoph Fritz
2015-06-15 7:54 ` Borislav Petkov
2015-06-15 8:01 ` Christoph Fritz
2015-06-15 8:10 ` Borislav Petkov
2015-07-13 7:32 ` Christoph Fritz
-- strict thread matches above, loose matches on Subject: below --
2015-06-13 19:53 Christoph Fritz
2015-06-13 20:19 ` Heinz Diehl
2015-06-13 20:58 ` Christoph Fritz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150614164745.GA14892@pd.tnic \
--to=bp@alien8.de \
--cc=chf.fritz@googlemail.com \
--cc=daniel@quora.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.