linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Stefan Metzmacher <metze@samba.org>
Cc: "Steve French" <smfrench@gmail.com>,
	"Björn JACKE" <bjacke@samba.org>,
	CIFS <linux-cifs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] cifs fixes
Date: Fri, 12 Feb 2021 17:02:34 -0800	[thread overview]
Message-ID: <CAHk-=wh8n15NOcHkuxD=rXnMZCcsYD316JjRDdHUFwcFi8vq6g@mail.gmail.com> (raw)
In-Reply-To: <592ad76a-866e-f932-5a82-1af4a2ba4880@samba.org>

On Fri, Feb 12, 2021 at 4:26 PM Stefan Metzmacher <metze@samba.org> wrote:
>
> The machine is running a 'AMD Ryzen Threadripper 2950X 16-Core Processor'
> and is freezing without any trace every view days.

I don't think the first-gen Zen issues ever really got solved. There
were multiple ones, with random segfaults for the early ones (but
afaik those were fixed by an RMA process with AMD), but the "it
randomly locks up" ones never had a satisfactory resolution afaik.

There were lots of random workarounds, but judging by your email:

> We played with various boot parameters (currently we're using
> 'mem_encrypt=off rcu_nocbs=0-31 processor.max_cstate=1 idle=nomwait nomodeset consoleblank=0',

I suspect you've seen all the bugzilla threads on this issue (kernel
bugzilla 196683 is probably the main one, but it was discussed
elsewhere too).

I assume you've updated to latest BIOS and looked at various BIOS
power management settings too?

Zen 2 seems to have fixed things (knock wood - it's certainly working
for me), But many people obviously never saw any issues with Zen 1
either.

           Linus

  reply	other threads:[~2021-02-13  1:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 18:15 [GIT PULL] cifs fixes Steve French
2021-02-12 20:04 ` Linus Torvalds
2021-02-12 20:39   ` Steve French
2021-02-13  0:26     ` Stefan Metzmacher
2021-02-13  1:02       ` Linus Torvalds [this message]
2021-02-13  1:08         ` Stefan Metzmacher
2021-02-13  1:28           ` Linus Torvalds
2021-02-19 23:48             ` Stefan Metzmacher
2021-02-12 21:33   ` Steve French
2021-02-13 20:03 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2021-07-10 17:22 [GIT PULL] CIFS Fixes Steve French
2021-07-10 19:08 ` pr-tracker-bot
2021-03-10  2:49 [GIT PULL] cifs fixes Steve French
2021-03-10 18:13 ` pr-tracker-bot
2021-02-06 18:28 Steve French
2021-02-06 23:33 ` pr-tracker-bot
2020-05-17  2:45 [GIT PULL] CIFS Fixes Steve French
2020-05-17  4:45 ` pr-tracker-bot
2015-04-03  3:32 Steve French
2015-02-04 17:42 Steve French
2014-12-29 20:55 Steve French
2014-12-09 15:18 Steve French
     [not found] ` <CAH2r5muu_0byHxGJeKxmFinRSv4Aiduj=7U5ysyP-3MzK7e+HQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-10 23:40   ` Linus Torvalds
     [not found]     ` <CA+55aFzSTqAHhQSUjgQ+6wfD+q614SbEhQuBYhfUaQsmAmGrkQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-11  0:00       ` Steve French
2014-08-20 16:54 Steve French

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='CAHk-=wh8n15NOcHkuxD=rXnMZCcsYD316JjRDdHUFwcFi8vq6g@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=bjacke@samba.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=metze@samba.org \
    --cc=smfrench@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).