public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Hirte <johannes.hirte@datenkhaos.de>
To: Borislav Petkov <bp@alien8.de>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
	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: Fri, 6 Oct 2017 20:49:33 +0200	[thread overview]
Message-ID: <20171006184933.GA7676@probook> (raw)
In-Reply-To: <20170930155055.7v7xroo23u5gu57q@pd.tnic>

On 2017 Sep 30, Borislav Petkov wrote:
> On Sat, Sep 30, 2017 at 02:47:11PM +0200, Markus Trippelsdorf wrote:
> > Changing the TLB code so late might not be a good idea...
> 
> The new lazy code is too risky to keep as we don't know what else will
> break. The conservative and thus safe thing to do is to revert to the
> old behavior for old machines.
>

I see the same behaviour on Carizzo. Is Excavator an old machine too?

--
Regards,
  Johannes

  parent reply	other threads:[~2017-10-06 18:57 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
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 [this message]
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=20171006184933.GA7676@probook \
    --to=johannes.hirte@datenkhaos.de \
    --cc=bp@alien8.de \
    --cc=kilobyte@angband.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=markus@trippelsdorf.de \
    --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