all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Chris Sutcliff <chris@itg.uy>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Server freezing randomly with Proxmox 6.2-4 on AMD Ryzen system
Date: Mon, 07 Sep 2020 11:29:19 +0000	[thread overview]
Message-ID: <DDapw2kXnog3TMSjt0QdBsbgMGq-79wAnyqHfqvoCGU_cX-vmZpsTeDXCTMcKU4UqriDNXIdk_lD3krEp69qO0LO1nZNNZLS9OEZH1Aw7TE=@itg.uy> (raw)
In-Reply-To: <0e58d1d5-384b-55d2-9042-ae8c1e2ade6c@qwer.tk>

Hi,

I'm using the 10G Lan variant of this board with a 3700x and haven't had any issues.

There is a "beta" bios version available from ASRock which updates the AGESA 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

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, September 4, 2020 3:45 PM, Hermann Himmelbauer <hermann@qwer.tk> 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 etc.
>
> 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 machine.
>
> 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=2b:00.0" is an intel 10GBit ethernet adapter (X550T). So
> 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 (BOM
>     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/Linux.
>
>     What I did so far (without success):
>
> -   Disabled C6 as I read that this CPU-state can lead to unstable systems
>     (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 logged)
>
> -   Memory test (memtest86, no errors)
>
>     Do you have any clue what could be the reason for these freezes? Should
>     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





  parent reply	other threads:[~2020-09-07 11:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0e58d1d5-384b-55d2-9042-ae8c1e2ade6c@qwer.tk>
2020-09-07 11:21 ` Wolfgang Link
2020-09-07 18:44   ` Hermann Himmelbauer
2020-09-08  4:25     ` Wolfgang Link
2020-09-07 11:29 ` Chris Sutcliff [this message]
2020-11-16 17:21 ` Hermann Himmelbauer

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='DDapw2kXnog3TMSjt0QdBsbgMGq-79wAnyqHfqvoCGU_cX-vmZpsTeDXCTMcKU4UqriDNXIdk_lD3krEp69qO0LO1nZNNZLS9OEZH1Aw7TE=@itg.uy' \
    --to=chris@itg.uy \
    --cc=pve-user@lists.proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal