From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id C5D6261A09 for ; Mon, 7 Sep 2020 13:38:01 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B43EFA785 for ; Mon, 7 Sep 2020 13:38:01 +0200 (CEST) Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 7E6BFA77B for ; Mon, 7 Sep 2020 13:38:00 +0200 (CEST) Date: Mon, 07 Sep 2020 11:29:19 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itg.uy; s=protonmail2; t=1599478166; bh=3DXqfnN3VwGZoaZ3gziqLotxg68vm+fkt58IlRa534c=; h=Date:To:From:Reply-To:Subject:In-Reply-To:References:From; b=Zxe0uxW5soDWM7iS9vuDgty+LscigU8xz/czK30/iVMW+f7f0YGCKKq47EEEaXb6I pUTL25DN7KuuXBVSxcHNfWOgGh1lfK4haYyA7fJEK1Tw+6j3qYIsHQeNoztJcvumX9 84OMCxS180wIJiDTv8X4Mlrj3d2QYkxmqnDX7X/xggqwaJyclGpqe2CQmAa3lVqLn4 5TCg5SsXan2RHLQyNoLLViAMQ0Ev/A//5Wzyd8ei2WHrDRmvviYSi7rES+poLvhDrw jrqzERtcCPehibt2tI/YDFkbCTXN1ZuEA1aKXLuzNVp21vgjYUqba1WsQaiPljwkLt wOGXG+kPdvxrg== To: Proxmox VE user list From: Chris Sutcliff Reply-To: Chris Sutcliff Message-ID: In-Reply-To: <0e58d1d5-384b-55d2-9042-ae8c1e2ade6c@qwer.tk> References: <0e58d1d5-384b-55d2-9042-ae8c1e2ade6c@qwer.tk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=10.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mailout.protonmail.ch X-SPAM-LEVEL: Spam detection results: 0 DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust RCVD_IN_MSPIKE_H2 -0.001 Average reputation (+2) SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [PVE-User] Server freezing randomly with Proxmox 6.2-4 on AMD Ryzen system X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Sep 2020 11:38:01 -0000 Hi, I'm using the 10G Lan variant of this board with a 3700x and haven't had an= y issues. There is a "beta" bios version available from ASRock which updates the AGES= A version to 1.0.0.6 (https://download.asrock.com/BIOS/Server/X470D4U(L3.37= )ROM.zip) which might be worth trying? I'm using the equivalent version on = my board. Kind Regards Chris Sutcliff Sutcliff Limited =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Friday, September 4, 2020 3:45 PM, Hermann Himmelbauer = wrote: > Dear Proxmox users, > > I'm trying to install a 3-node cluster (latest proxmox/ceph) and > experience random freezes. The node can either be completely frozen (no > blinking cursor on console, no ping) or can get somewhat blocked / slow e= tc. > > This happens most often on node 2 (approx. 3-4 times / day), node 3 > never got stuck within 14 days runtime, node 1 once. > > Unfortunately I did not find any way to trigger this behaviour, however, > I think that this happens most often if I stress the machine in some > way (performance test within a virtual machine) and then idling the machi= ne. > > When the machine freezes completely, there is no logfile. However, if it > is partially frozen, some info can be aquired via dmesg. (See attached > file). ("device=3D2b:00.0" is an intel 10GBit ethernet adapter (X550T). S= o > perhaps there is some driver issue regarding this ethernet adapter?) > > The system consists of the following components: > > - AMD Ryzen 3 3200G, 4x 3.60GHz, boxed (YD3200C5FHBOX) > > - ASRock Rack X470D4U2-2T (Mainboard) > > - Samsung SSD 970 EVO Plus 250GB, M.2 (MZ-V7S250BW) (builtin SSD for OS= ) > > - 2 * Kingston Server Premier DIMM 16GB, DDR4-2666, CL19-19-19, ECC (BO= M > Number: 9965745-002.A00G, Part Number: KSM26ED8/16ME) > > - be quiet! Pure Power 11 CM 400W ATX 2.4 (BN296) (Power supply) > > - 2 * Micron 5300 PRO - Read Intensive 960GB, SATA > (MTFDDAK960TDS-1AW1Z6) (SSD for Ceph) > > - LogiLink PC0075, 2x RJ-45, PCIe 2.0 x1 (second NIC with two ports) > > The system is Linux Debian 10.4 (Proxmox 6.2-4) with kernel 5.4.34-1-= pve > #1 SMP PVE 5.4.34-2 (Thu, 07 May 2020 10:02:02 +0200) x86_64 GNU/Linu= x. > > What I did so far (without success): > > - Disabled C6 as I read that this CPU-state can lead to unstable system= s > (via "python zenstates.py --c6-disable" -> still errors). > > - Updated my Bios to the latest version (3.30) > > - Checked that the CPU + RAM are compatible to the mainboard (they are > listed as compatible on the ASRock website) > > - Checked logs in IPMI (undervoltage, temperature etc., nothing is logg= ed) > > - Memory test (memtest86, no errors) > > Do you have any clue what could be the reason for these freezes? Shou= ld > I think of some hardware error? Or is this some known Linux bug that = can > be fixed? > > Best Regards, > Hermann > > -- > hermann@qwer.tk > PGP/GPG: 299893C7 (on keyservers) > > > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user