昨天我添加了一个新的 1TB SATA SSD（Seagate 120）
我从昨天开始的日志中看到一个错误反复发生。在 Google 上搜索这个错误时，人们通常会说“使用内核设置来抑制它”，但我无法确认在我的情况下是否完全一样。
Mar 22 07:50:24 komp kernel: [ 2451.204660] pcieport 0000:00:1d.6: AER: Corrected error received: 0000:03:00.0
Mar 22 07:50:24 komp kernel: [ 2451.204872] alx 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Mar 22 07:50:24 komp kernel: [ 2451.204880] alx 0000:03:00.0: AER: device [1969:e0a1] error status/mask=00000080/00002000
Mar 22 07:50:24 komp kernel: [ 2451.204886] alx 0000:03:00.0: AER: [ 7] BadDLLP
Mar 22 07:50:24 komp kernel: [ 2451.205132] pcieport 0000:00:1d.6: AER: Corrected error received: 0000:03:00.0
Mar 22 07:50:24 komp kernel: [ 2451.205583] pcieport 0000:00:1d.6: AER: Corrected error received: 0000:03:00.0
Mar 22 07:50:29 komp kernel: [ 2456.213360] pcieport 0000:00:1d.6: AER: Corrected error received: 0000:03:00.0
Mar 22 07:50:29 komp kernel: [ 2456.213440] alx 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Mar 22 07:50:29 komp kernel: [ 2456.213448] alx 0000:03:00.0: AER: device [1969:e0a1] error status/mask=00000001/00002000
Mar 22 07:50:29 komp kernel: [ 2456.213454] alx 0000:03:00.0: AER: [ 0] RxErr
Mar 22 07:50:29 komp kernel: [ 2456.214389] pcieport 0000:00:1d.6: AER: Corrected error received: 0000:03:00.0
Mar 22 07:50:29 komp kernel: [ 2456.214477] alx 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Mar 22 07:50:29 komp kernel: [ 2456.214485] alx 0000:03:00.0: AER: device [1969:e0a1] error status/mask=00000080/00002000
Mar 22 07:50:29 komp kernel: [ 2456.214490] alx 0000:03:00.0: AER: [ 7] BadDLLP
Mar 22 07:50:32 komp kernel: [ 2459.213381] pcieport 0000:00:1d.6: AER: Corrected error received: 0000:03:00.0
Mar 22 07:50:32 komp kernel: [ 2459.213442] alx 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Mar 22 07:50:32 komp kernel: [ 2459.213449] alx 0000:03:00.0: AER: device [1969:e0a1] error status/mask=00000040/00002000
Mar 22 07:50:32 komp kernel: [ 2459.213454] alx 0000:03:00.0: AER: [ 6] BadTLP
Mar 22 07:50:32 komp kernel: [ 2459.213763] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: 0000:03:00.0
Mar 22 07:50:32 komp kernel: [ 2459.214132] alx 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Mar 22 07:50:32 komp kernel: [ 2459.214136] alx 0000:03:00.0: AER: device [1969:e0a1] error status/mask=00000080/00002000
Mar 22 07:50:32 komp kernel: [ 2459.214140] alx 0000:03:00.0: AER: [ 7] BadDLLP
Mar 22 07:50:32 komp kernel: [ 2459.214410] pcieport 0000:00:1d.6: AER: Corrected error received: 0000:03:00.0
Mar 22 07:50:32 komp kernel: [ 2459.214830] pcieport 0000:00:1d.6: AER: Corrected error received: 0000:03:00.0
Mar 22 07:50:32 komp kernel: [ 2459.214938] alx 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Mar 22 07:50:32 komp kernel: [ 2459.214942] alx 0000:03:00.0: AER: device [1969:e0a1] error status/mask=00000080/00002000
Mar 22 07:50:32 komp kernel: [ 2459.214945] alx 0000:03:00.0: AER: [ 7] BadDLLP
Mar 22 07:50:32 komp kernel: [ 2459.215697] pcieport 0000:00:1d.6: AER: Corrected error received: 0000:03:00.0
Mar 22 07:50:32 komp kernel: [ 2459.215814] alx 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Mar 22 07:50:32 komp kernel: [ 2459.215821] alx 0000:03:00.0: AER: device [1969:e0a1] error status/mask=00000080/00002000
Mar 22 07:50:32 komp kernel: [ 2459.215825] alx 0000:03:00.0: AER: [ 7] BadDLLP
Mar 22 07:50:32 komp kernel: [ 2459.217799] pcieport 0000:00:1d.6: AER: Corrected error received: 0000:03:00.0
Mar 22 07:50:32 komp kernel: [ 2459.217930] alx 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Mar 22 07:50:32 komp kernel: [ 2459.217939] alx 0000:03:00.0: AER: device [1969:e0a1] error status/mask=00000080/00002000
Mar 22 07:50:32 komp kernel: [ 2459.217946] alx 0000:03:00.0: AER: [ 7] BadDLLP
Mar 22 07:50:33 komp kernel: [ 2460.209405] pcieport 0000:00:1d.6: AER: Corrected error received: 0000:03:00.0
Mar 22 07:50:33 komp kernel: [ 2460.209472] alx 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Mar 22 07:50:33 komp kernel: [ 2460.209480] alx 0000:03:00.0: AER: device [1969:e0a1] error status/mask=00000081/00002000
Mar 22 07:50:33 komp kernel: [ 2460.209485] alx 0000:03:00.0: AER: [ 0] RxErr
Mar 22 07:50:33 komp kernel: [ 2460.209489] alx 0000:03:00.0: AER: [ 7] BadDLLP
Mar 22 07:50:34 komp kernel: [ 2461.204259] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: 0000:03:00.0
Mar 22 07:50:34 komp kernel: [ 2461.204404] alx 0000:03:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Mar 22 07:50:34 komp kernel: [ 2461.204412] alx 0000:03:00.0: AER: device [1969:e0a1] error status/mask=00000040/00002000
Mar 22 07:50:34 komp kernel: [ 2461.204417] alx 0000:03:00.0: AER: [ 6] BadTLP
从 lspci 来看，它似乎来自千兆以太网控制器。
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Device 3e9b
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:14.3 Network controller: Intel Corporation Wireless-AC 9560 [Jefferson Peak] (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Device a353 (rev 10)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 (rev f0)
00:1d.6 PCI bridge: Intel Corporation Device a336 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a30d (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
01:00.0 VGA compatible controller: NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5003 (rev 01)
03:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10)
自从我安装了新的 1TB 硬盘后，错误就开始出现了，但甚至在我对其进行格式化之前 - 几个小时后才对硬盘进行了分区和格式化。
我不知道这些错误是什么意思。驱动器似乎工作正常，除了日志中显示的错误之外，我没有发现任何其他错误。
这是什么意思？我希望有类似 BIOS 设置的东西来解决冲突……但希望不大。在过去 15 年左右的时间里，我真的没有在 PC 硬件或 BIOS 上花太多功夫。
该计算机是 MSI GP63 Leopard 8RE，运行 KDE Neon 5.18
johan@komp:~$ uname -a
Linux komp 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
编辑：
1. 根据下面的评论，错误是由 alx 驱动程序发现的。但是 alx 和新驱动器可以共享总线，因此不能 100% 确定。2
. 错误是在我安装新驱动器后启动时开始的。但可能存在我不知道的潜在问题，例如在安装新驱动器之前已安装但未重新启动的驱动程序或内核。我不经常重新启动。3. 我刚刚使用有线网络端口进行了测试，我不经常使用它。当有数据通过网络时，错误率会大幅上升。使用新驱动器时，错误率保持绝对恒定 - 这看起来像是预定的轮询。4. 看起来错误在我睡眠（挂起）时消失，但在下次重新启动时再次开始。这可能隐藏了错误很长时间，因为我可能从未在正确的时刻查看日志。
以上所有情况都让人怀疑这是否真的是新的驱动器或仅仅是巧合。