From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Adam Borowski <kilobyte@angband.pl>,
linux-kernel@vger.kernel.org, Andy Lutomirski <luto@kernel.org>,
x86-ml <x86@kernel.org>
Subject: Re: random insta-reboots on AMD Phenom II
Date: Sat, 30 Sep 2017 14:47:11 +0200 [thread overview]
Message-ID: <20170930124711.GB238@x4> (raw)
In-Reply-To: <20170930115302.ezvch7pdx7ws2k5h@pd.tnic>
On 2017.09.30 at 13:53 +0200, Borislav Petkov wrote:
> On Sat, Sep 30, 2017 at 01:29:03PM +0200, Adam Borowski wrote:
> > On Sat, Sep 30, 2017 at 01:11:37PM +0200, Borislav Petkov wrote:
> > > On Sat, Sep 30, 2017 at 04:05:16AM +0200, Adam Borowski wrote:
> > > > Any hints how to debug this?
> > >
> > > Do
> > > rdmsr -a 0xc0010015
> > > as root and paste it here.
> >
> > 1000010
> > 1000010
> > 1000010
> > 1000010
> > 1000010
> > 1000010
> >
> > on both 4.13.4 and 4.14-rc2+.
>
> Boot into -rc2+ and do as root:
>
> # wrmsr -a 0xc0010015 0x1000018
>
> If the issue gets fixed then Mr. Luto better revert the new lazy TLB
> flushing fun'n'games for 4.14 before it is too late and that kernel
> releases b0rked.
The issue does get fixed by setting TlbCacheDis to 1. I have been
running it for the last few weeks without any problems.
Performance is not affected at all. So it might by easier to just set
the bit for older AMD processors as a boot quirk.
Changing the TLB code so late might not be a good idea...
--
Markus
next prev parent reply other threads:[~2017-09-30 12:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 2:05 random insta-reboots on AMD Phenom II Adam Borowski
2017-09-30 11:11 ` Borislav Petkov
2017-09-30 11:29 ` Adam Borowski
2017-09-30 11:53 ` Borislav Petkov
2017-09-30 12:47 ` Markus Trippelsdorf [this message]
2017-09-30 14:20 ` Brian Gerst
2017-09-30 15:21 ` Markus Trippelsdorf
2017-09-30 15:50 ` Borislav Petkov
2017-09-30 16:04 ` Andy Lutomirski
2017-10-06 18:49 ` Johannes Hirte
2017-10-06 18:53 ` Borislav Petkov
2017-10-06 19:02 ` Johannes Hirte
2017-10-06 19:24 ` Borislav Petkov
2017-09-30 15:11 ` Andy Lutomirski
2017-09-30 15:48 ` Borislav Petkov
2017-10-01 13:07 ` Adam Borowski
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=20170930124711.GB238@x4 \
--to=markus@trippelsdorf.de \
--cc=bp@alien8.de \
--cc=kilobyte@angband.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@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