linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Metzmacher <metze@samba.org>
To: "Steve French" <smfrench@gmail.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Björn JACKE" <bjacke@samba.org>
Cc: CIFS <linux-cifs@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] cifs fixes
Date: Sat, 13 Feb 2021 01:26:24 +0100	[thread overview]
Message-ID: <592ad76a-866e-f932-5a82-1af4a2ba4880@samba.org> (raw)
In-Reply-To: <CAH2r5mtj+-xGDy-YN0JwSJAsgvB+HpQFCBi-zdTNXTRBY_Mteg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1039 bytes --]

Am 12.02.21 um 21:39 schrieb Steve French:
> Metze/Bjorn,
> Linus is right - samba.org is down for me (I also verified with JRA).
> Any ETA on when it gets back up?
> 
> On Fri, Feb 12, 2021 at 2:05 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>>
>> On Fri, Feb 12, 2021 at 10:16 AM Steve French <smfrench@gmail.com> wrote:
>>>
>>>   git://git.samba.org/sfrench/cifs-2.6.git tags/5.11-rc7-smb3
>>
>> It looks like git.samba.org is feeling very sick and is not answering.
>> Not git, not ping (but maybe icmp ping is blocked).
>>
>> Please give it a kick, or provide some other hosting mirror?


It's online again.

The machine is running a 'AMD Ryzen Threadripper 2950X 16-Core Processor'
and is freezing without any trace every view days.

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',
with the ubuntu 20.04 5.8 kernel, we also tried 5.4 before), but nothing seems to help.

metze



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-02-13  0:27 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 [this message]
2021-02-13  1:02       ` Linus Torvalds
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=592ad76a-866e-f932-5a82-1af4a2ba4880@samba.org \
    --to=metze@samba.org \
    --cc=bjacke@samba.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smfrench@gmail.com \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).