All of lore.kernel.org
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Borislav Petkov <bp@alien8.de>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	x86@kernel.org, linux-edac@vger.kernel.org,
	Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: 4.15-rc6 PTI regression: L1 TLB mismatch MCE on Athlon64
Date: Wed, 3 Jan 2018 09:07:00 +0200 (EET)	[thread overview]
Message-ID: <alpine.LRH.2.21.1801030906200.3307@math.ut.ee> (raw)
In-Reply-To: <20180102212706.5gtevvg4rr7rfy5o@pd.tnic>

> > These MCE-s do not happen on 4.14 and 4.15.0-rc4-00041-gace52288edf0. 
> > They do happen on each boot into 4.15-rc6. Will try to bisect.
> 
> Please do. And try -rc5 too.

4.15-rc5 is OK. Will try CONFIG_X86_PTDUMP on the next kernel.
 
> And then Linus' pti merges:
> 
> 52c90f2d32bfa7d6eccd66a56c44ace1f78fbadd
> 5aa90a84589282b87666f92b6c3c917c8080a9bf
> caf9a82657b313106aae8f4a35936c116a152299
> 64a48099b3b31568ac45716b7fafcb74a0c2fcfe


-- 
Meelis Roos (mroos@linux.ee)

      parent reply	other threads:[~2018-01-03  7:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02 20:49 4.15-rc6 PTI regression: L1 TLB mismatch MCE on Athlon64 Meelis Roos
2018-01-02 21:27 ` Borislav Petkov
2018-01-02 23:07   ` Thomas Gleixner
2018-01-03  9:16     ` Meelis Roos
2018-01-03 12:42       ` Borislav Petkov
2018-01-03 13:17         ` Thomas Gleixner
2018-01-03 13:17           ` Thomas Gleixner
2018-01-03 14:01           ` Meelis Roos
2018-01-03 14:01             ` mroos
2018-01-03 16:22           ` [tip:x86/pti] x86/pti: Make sure the user/kernel PTEs match tip-bot for Thomas Gleixner
2018-02-09 23:30             ` Dave Hansen
2018-02-13 15:59               ` Thomas Gleixner
2018-01-03  7:07   ` Meelis Roos [this message]

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=alpine.LRH.2.21.1801030906200.3307@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.lendacky@amd.com \
    --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 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.