ASRock Rack has created the first AM4 socket server boards, X470D4U, X470D4U2-2T

nx2l · November 29, 2019, 4:39pm

not sure what has happened but the OS and the IMPI are reporting that the MB temp is -28 degrees…

wtf

The ipmi reports the CPU temperature correctly but lm-sensors sees it as negative also.

jugs · November 29, 2019, 10:00pm

Hey guys, I can’t seem to find a place anywhere in the BIOS to change any system or DRAM voltages. Am I missing something?

FaunCB · November 29, 2019, 10:17pm

If I were to build a server, and I chose between a 1920x and a 1700x, would this board afford the same shit with a 1700x that I could get with a 1920 at base? Would I save any cash worth anything performance wise?

Mastakilla · November 30, 2019, 12:38am

Memory voltage controls:
afbeelding
This is on the X470D4U2-2T, but should be the same on yours… I also spend quite some time trying to find it

jugs · November 30, 2019, 12:41am

Oh my god thank you, I saw that but I didn’t know what MEM_VDDIO was.

MVP forum for helpful folks here.

nx2l · December 1, 2019, 3:33pm

Been seeing errors/warning like this the past week … anyone else seeing the same?

Nov 25 05:11:11 mainpve kernel: pcieport 0000:00:01.1: Signaling PME with IRQ 26
Nov 25 05:11:11 mainpve kernel: pcieport 0000:00:01.3: Signaling PME with IRQ 27
Nov 25 05:11:11 mainpve kernel: pcieport 0000:00:03.1: Signaling PME with IRQ 28
Nov 25 05:11:11 mainpve kernel: pcieport 0000:00:03.2: Signaling PME with IRQ 29
Nov 25 05:11:11 mainpve kernel: pcieport 0000:00:07.1: Signaling PME with IRQ 30
Nov 25 05:11:11 mainpve kernel: pcieport 0000:00:08.1: Signaling PME with IRQ 32
Nov 25 05:11:18 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 05:11:18 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 05:11:18 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 05:11:18 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 05:17:18 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 05:17:18 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 05:17:18 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 05:17:18 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 05:17:33 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 05:17:33 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 05:17:33 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 05:17:33 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 05:23:09 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 05:23:09 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 05:23:09 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 05:23:09 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 05:23:26 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 05:23:26 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 05:23:26 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 05:23:26 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 05:23:33 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 05:23:33 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 05:23:33 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 05:23:33 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 05:29:19 mainpve kernel: pcieport 0000:00:01.3: AER: Multiple Corrected error received: 0000:00:00.0
Nov 25 05:29:19 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 25 05:29:19 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00001040/00006000
Nov 25 05:29:19 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 05:29:19 mainpve kernel: pcieport 0000:00:01.3: [12] Timeout
Nov 25 05:30:54 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 05:30:54 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 05:30:54 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 05:30:54 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 05:35:54 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 05:35:54 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 05:35:54 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 05:35:54 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 05:40:28 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 05:40:28 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 05:40:28 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 05:40:28 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 05:42:09 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 05:42:09 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 05:42:09 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 05:42:09 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 05:47:31 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 05:47:31 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 05:47:31 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 05:47:31 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 05:57:44 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 05:57:44 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 05:57:44 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 05:57:44 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 05:59:38 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 05:59:38 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 05:59:38 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 05:59:38 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 06:00:31 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 06:00:31 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 06:00:31 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 06:00:31 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 06:05:11 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 06:05:11 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 06:05:11 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 06:05:11 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 17:43:00 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 17:43:00 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 17:43:00 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 17:43:00 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 19:16:35 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 19:16:35 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 19:16:35 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 19:16:35 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 20:59:55 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 20:59:55 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 20:59:55 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 20:59:55 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 21:19:19 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 21:19:19 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 21:19:19 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 21:19:19 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 21:19:30 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 21:19:30 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 21:19:30 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 21:19:30 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 21:20:18 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 21:20:18 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 21:20:18 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 21:20:18 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 21:42:07 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 21:42:07 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 21:42:07 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 21:42:07 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 21:49:19 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 21:49:19 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 21:49:19 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 21:49:19 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 21:49:23 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 21:49:23 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 21:49:23 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 21:49:23 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 22:06:01 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 22:06:01 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 22:06:01 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 22:06:01 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 22:06:28 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 22:06:28 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 22:06:28 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 22:06:28 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 22:09:24 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 22:09:24 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 22:09:24 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 22:09:24 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 25 22:34:24 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 25 22:34:24 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 25 22:34:24 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 25 22:34:24 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 26 00:16:19 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 26 00:16:19 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 26 00:16:19 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 26 00:16:19 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 26 00:27:18 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 26 00:27:18 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 26 00:27:18 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 26 00:27:18 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 26 01:22:33 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 26 01:22:33 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 26 01:22:33 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 26 01:22:33 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 26 04:05:43 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 26 04:05:43 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 26 04:05:43 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 26 04:05:43 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 26 11:34:42 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 26 11:34:42 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 26 11:34:42 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 26 11:34:42 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 26 12:45:35 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 26 12:45:35 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 26 12:45:35 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 26 12:45:35 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 26 20:21:05 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 26 20:21:05 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 26 20:21:05 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 26 20:21:05 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 26 21:31:30 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 26 21:31:30 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 26 21:31:30 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 26 21:31:30 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 26 21:32:39 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 26 21:32:39 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 26 21:32:39 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 26 21:32:39 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 26 22:37:10 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 26 22:37:10 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 26 22:37:10 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 26 22:37:10 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 26 23:59:05 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 26 23:59:05 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 26 23:59:05 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 26 23:59:05 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 27 00:28:18 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 27 00:28:18 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 27 00:28:18 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 27 00:28:18 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 27 08:30:04 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 27 08:30:04 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 27 08:30:04 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 27 08:30:04 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 27 09:18:43 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 27 09:18:43 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 27 09:18:43 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 27 09:18:43 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 27 16:36:55 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 27 16:36:55 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 27 16:36:55 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 27 16:36:55 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 27 17:34:36 mainpve kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Nov 27 17:34:36 mainpve kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 27 17:34:36 mainpve kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00001000/00006000
Nov 27 17:34:36 mainpve kernel: pcieport 0000:00:03.1: [12] Timeout
Nov 27 18:23:24 mainpve kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Nov 27 18:23:24 mainpve kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 27 18:23:24 mainpve kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00001000/00006000
Nov 27 18:23:24 mainpve kernel: pcieport 0000:00:03.1: [12] Timeout
Nov 27 18:54:08 mainpve kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Nov 27 18:54:08 mainpve kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 27 18:54:08 mainpve kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00001000/00006000
Nov 27 18:54:08 mainpve kernel: pcieport 0000:00:03.1: [12] Timeout
Nov 27 19:57:07 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 27 19:57:07 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 27 19:57:07 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 27 19:57:07 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 27 20:07:14 mainpve kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Nov 27 20:07:14 mainpve kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 27 20:07:14 mainpve kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00001000/00006000
Nov 27 20:07:14 mainpve kernel: pcieport 0000:00:03.1: [12] Timeout
Nov 27 20:09:52 mainpve kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Nov 27 20:09:52 mainpve kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 27 20:09:52 mainpve kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00001000/00006000
Nov 27 20:09:52 mainpve kernel: pcieport 0000:00:03.1: [12] Timeout
Nov 27 22:28:58 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 27 22:28:58 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 27 22:28:58 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 27 22:28:58 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 27 22:30:54 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 27 22:30:54 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 27 22:30:54 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 27 22:30:54 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 01:22:07 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 01:22:07 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 01:22:07 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 01:22:07 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 02:51:24 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 02:51:24 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 02:51:24 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 02:51:24 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 03:56:47 mainpve kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:00:00.0
Nov 28 03:56:47 mainpve kernel: pcieport 0000:00:03.1: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Nov 28 03:56:47 mainpve kernel: pcieport 0000:00:03.1: device [1022:1453] error status/mask=00001000/00006000
Nov 28 03:56:47 mainpve kernel: pcieport 0000:00:03.1: [12] Timeout
Nov 28 03:59:35 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 03:59:35 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 03:59:35 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 03:59:35 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 04:14:51 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 04:14:51 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 04:14:51 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 04:14:51 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 04:21:27 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 04:21:27 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 04:21:27 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 04:21:27 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 18:18:05 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 18:18:05 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 18:18:05 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 18:18:05 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 20:43:53 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 20:43:53 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 20:43:53 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 20:43:53 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 21:04:49 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 21:04:49 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 21:04:49 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 21:04:49 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 21:43:01 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 21:43:01 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 21:43:01 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 21:43:01 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 21:43:31 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 21:43:31 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 21:43:31 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 21:43:31 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 22:18:27 mainpve kernel: pcieport 0000:00:01.1: Signaling PME with IRQ 26
Nov 28 22:18:27 mainpve kernel: pcieport 0000:00:01.3: Signaling PME with IRQ 27
Nov 28 22:18:27 mainpve kernel: pcieport 0000:00:03.1: Signaling PME with IRQ 28
Nov 28 22:18:27 mainpve kernel: pcieport 0000:00:03.2: Signaling PME with IRQ 29
Nov 28 22:18:27 mainpve kernel: pcieport 0000:00:07.1: Signaling PME with IRQ 30
Nov 28 22:18:27 mainpve kernel: pcieport 0000:00:08.1: Signaling PME with IRQ 32
Nov 28 22:18:47 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 22:18:47 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 22:18:47 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 22:18:47 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 22:19:37 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 22:19:37 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 22:19:37 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 22:19:37 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 22:19:54 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 22:19:54 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 22:19:54 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 22:19:54 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 22:20:14 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 22:20:14 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 22:20:14 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 22:20:14 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 28 22:21:47 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 28 22:21:47 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 28 22:21:47 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 28 22:21:47 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 29 06:29:42 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 29 06:29:42 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 29 06:29:42 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 29 06:29:42 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 29 07:37:31 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 29 07:37:31 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 29 07:37:31 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 29 07:37:31 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 29 07:56:00 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 29 07:56:00 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 29 07:56:00 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 29 07:56:00 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 29 23:52:15 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 29 23:52:15 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 29 23:52:15 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 29 23:52:15 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 29 23:54:45 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 29 23:54:45 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 29 23:54:45 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 29 23:54:45 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 30 02:26:01 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 30 02:26:01 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 30 02:26:01 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 30 02:26:01 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 30 14:49:31 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 30 14:49:31 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 30 14:49:31 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 30 14:49:31 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 30 18:41:58 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 30 18:41:58 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 30 18:41:58 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 30 18:41:58 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Nov 30 22:32:09 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Nov 30 22:32:09 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Nov 30 22:32:09 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Nov 30 22:32:09 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP
Dec 01 06:49:58 mainpve kernel: pcieport 0000:00:01.3: AER: Corrected error received: 0000:00:00.0
Dec 01 06:49:58 mainpve kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Dec 01 06:49:58 mainpve kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00000040/00006000
Dec 01 06:49:58 mainpve kernel: pcieport 0000:00:01.3: [ 6] BadTLP

Pjhal · December 1, 2019, 6:07pm

Nope, at least i don’t think so…
I’ll gladly give you a read out or log from my board if it helps you. But i don’t know where this specific info is found, so you would need to explain it.

nx2l · December 1, 2019, 6:09pm

in linux… with journalctl command.

Pjhal · December 1, 2019, 6:16pm

Sorry, using Unraid, which is some custom Linux OS. But the command doesn’t seem to work, it is not recognized.

plebian · December 1, 2019, 6:34pm

I’m running proxmox 6 and not seeing these errors.

nx2l · December 1, 2019, 7:12pm

Whats what i am running also. thanks…

If I am reading it right… this is the device with the issue.

lspci | grep 0:01.3
00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge

@wendell

Found this; but its over a year old bug…

https://bugzilla.redhat.com/show_bug.cgi?id=1616364

Others in Nov2019 also need to be seeing the issue with fedora…

I wonder if thats what causing my motherboard to think the temperature is negative 28 degrees.

nx2l · December 1, 2019, 7:41pm

Just checked my other x470d4u motherboard.

Previous one has a 2700 (non X) and this one has a 3700x and running F31.

The atlantic device is the aquantia 10GbE nic. The other machine also an aquantic 10GbE nic.

Nov 27 19:57:02 evo860ryzen kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:2b:00.0
Nov 27 19:57:02 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Nov 27 19:57:02 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: device [1d6a:07b1] error status/mask=00000001/0000a000
Nov 27 19:57:02 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: [ 0] RxErr
–
Nov 27 20:15:06 evo860ryzen kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:2b:00.0
Nov 27 20:15:06 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Nov 27 20:15:06 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: device [1d6a:07b1] error status/mask=00000001/0000a000
Nov 27 20:15:06 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: [ 0] RxErr
–
Nov 27 20:27:51 evo860ryzen kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:2b:00.0
Nov 27 20:27:51 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Nov 27 20:27:51 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: device [1d6a:07b1] error status/mask=00000001/0000a000
Nov 27 20:27:51 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: [ 0] RxErr
–
Nov 28 00:34:38 evo860ryzen kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:2b:00.0
Nov 28 00:34:38 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Nov 28 00:34:38 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: device [1d6a:07b1] error status/mask=00000001/0000a000
Nov 28 00:34:38 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: [ 0] RxErr
–
Nov 28 06:23:08 evo860ryzen kernel: pcieport 0000:00:03.1: AER: Corrected error received: 0000:2b:00.0
Nov 28 06:23:08 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Nov 28 06:23:08 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: device [1d6a:07b1] error status/mask=00000001/0000a000
Nov 28 06:23:08 evo860ryzen kernel: atlantic 0000:2b:00.0: AER: [ 0] RxErr

lspci | grep 00:03.1
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

kura · December 3, 2019, 1:28am

Nope, error code “3b”, according to the manual stuff with memory initialization (memory is OK and working with a 3700X, also tried a CMOS reset and only using a single DIMM).

Edit : My 3950X is not dead on arrival, on an ASRock X570 Taichi (where the UEFI files are clearly labeled) I can install the UEFI with AGESA 1003 ABB (that or the newer ABBA is the version of the X470D4U’s beta L3.25) and there the motherboard always POSTs.

So either the X470 chipset in general needs AGESA 1004 B to operate the 3950X or it’s just another one of ASRock Rack’s UEFI-qualitiy uniquenesses …

I received my Ryzen 3950x today. System is booting with the 3.25 BIOS, so there doesn’t seem to be any general issue with the 3950x on the x470d4u board. I’m using 4 x 32gb Samsung UDIMM 2666 ECC memory sticks which run stable at 3200 MHz.

Huang_wei · December 3, 2019, 7:01am

how do you setup your memory to run at 3200MHz?

Dagarath · December 3, 2019, 8:32am

Binned 3200mhz ECC when?

Seriously this is really cool, kinda tiny but with the right CPU it would make my little Opteron Quad Socket look like trash.

Looks like ASRock might be seeing CPU crypto mining dollar signs, or who knows maybe it exists for some other weird reason.

mutation666 · December 3, 2019, 11:12am

2933 is coming soon you will probably be able to easily hit 3200 maybe even 3600 with those I think some people have hit 3200 on 2666

aBav.Normie-Pleb · December 3, 2019, 8:56pm

Been quite busy last couple of days.

I think these boards seem to dispise me…

This is my second X470D4U where something’s fishy, today I noticed that the one I had unsuccessfully tested the 3950X with corrupts its BMC image by itself when it is powered off for a few days

Checked the CMOS battery and the chip - I won’t fiddle around with this unit anymore, it’s going back to the retailer.

Only used the SilverStone SST-SX800-LTI PSU with it that seemed to be of good quality.

Happy to hear the X470D4U runs the 3950X! (I won’t plug mine back into a questionable motherboard until the availability has become better, which is…?)

Could you run a couple of long-duration load tests and check on the VRM temperatures (latest version of HWiNFO seems to recognizes the sensors on the X470D4U)?

kura · December 3, 2019, 10:14pm

how do you setup your memory to run at 3200MHz?

At first i tried to raise the memory frequency under

AMD CBS > UMC Common Options > DDR4 Common Options > DRAM Timing Configuration

but the system did not POST. Then found a new menu, which I have not noticed before “AMD Overclocking”. I don’t know if it is new in 3.25 or if has appeared when I put the 3950x in (had a 2400g CPU as placeholder before). But under

AMD Overclocking > DDR and Infinity Fabric Frequency/Timings > DDR Frequency and Timings > DRAM Timing Configuration

I found a menu which look just like the other DRAM Timing Configuration menu. Raising the memory frequency here did work. The system booted fine and it runs stable.

Binned 3200mhz ECC when?

The thing is Samsung did not bin those modules. They just produced those 32GB UDIMM ECC sticks in a low quantity as a test run. But those chips have a much higher quality then 2666 label on them suggests. Most 3200 MHz DIMMs on market even need more then 1.2V, but these run fine at that voltage. I bought mine back in august after seeing someone on this thread reaching 3200MHz on these. But at the moment they vanished from the market and are almost impossible to get.

If you want to google these modules the product name is M391A4G43MB1-CTD

cybrnook · December 4, 2019, 3:28am

Nice find, just put a mild 2666 overclock on my ECC ram as well. So far no issues.

plebian · December 5, 2019, 9:40pm

ASRock engineers, if you’re reading this:
PLEASE use TLS on your file hosting services. I can’t believe it’s 2019 and we’re downloading server BIOS & BMC images over insecure channels.