mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "René Rebe" <rene@exactcode.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [RFC] AMD Zen4 CPU bug? Spurious SMT Sibling Invalid Opcode Speculation
Date: Fri, 6 Oct 2023 11:21:13 +0200	[thread overview]
Message-ID: <797F7A00-541E-4333-B653-1120DF5C56B1@exactcode.com> (raw)
In-Reply-To: <20231004222511.GHZR3mR/oNFZuJGB9P@fat_crate.local>

Hi,

> On 5. Oct 2023, at 00:25, Borislav Petkov <bp@alien8.de> wrote:
> 
> On Wed, Oct 04, 2023 at 05:29:32PM +0200, René Rebe wrote:
>> during cross compiling our “Embedded” Linux Distribution T2 (https://t2sde.org) I observers some random illegal instruction build errors since we got ourselves a Ryzen 7950x on launch day a year ago:
> 
> Thanks for reporting. I'm looking into it.

Thank you Borislav, were you able to reproduce this on Zen 4 you have access to?

Thanks,
	René

--
ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
http://exactcode.com | http://exactscan.com | http://ocrkit.com


  reply	other threads:[~2023-10-06  9:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 15:29 René Rebe
2023-10-04 22:25 ` Borislav Petkov
2023-10-06  9:21   ` René Rebe [this message]
2023-10-06  9:32     ` Borislav Petkov
2023-10-10  8:39       ` Borislav Petkov
2023-10-10 21:18         ` René Rebe
2023-10-11  8:59           ` Borislav Petkov
2023-10-11  9:23 ` [tip: x86/urgent] x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs tip-bot2 for Borislav Petkov (AMD)
2023-10-11 21:28   ` Ingo Molnar
2023-10-12  7:40     ` Borislav Petkov
2023-10-12 18:12       ` [PATCH] x86/cpu: Fix the AMD Fam 17h, Fam 19h, Zen2 and Zen4 enumerations Ingo Molnar
2023-10-12 18:20 ` [tip: perf/core] x86/cpu: Fix the AMD Fam 17h, Fam 19h, Zen2 and Zen4 MSR enumerations tip-bot2 for Borislav Petkov

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=797F7A00-541E-4333-B653-1120DF5C56B1@exactcode.com \
    --to=rene@exactcode.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome