#26 Le 17/09/2021, à 08:18
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Je vais tenter d'autres démarrages
- avec
pci=noaer
dans les options du noyau de GRUB
et
params ASPM de la carte ETH désactivés:
cat /etc/modprobe.d/r8169.conf
options r8169 aspm=0et un 5ème en retirant les params suivants de GRUB:
acpi_osi=! acpi_osi='Windows 2015' drm.debug=0xe avec ou sans
pci=noaeravec ou sans
params ASPM de la carte ETH désactivés
Clevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#27 Le 17/09/2021, à 08:23
- xubu1957
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Bonjour,
Le vpn, ce n'est pas protonvpn, comme dans ce fil ?
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
En ligne
#28 Le 17/09/2021, à 09:19
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Bonjour,
Le vpn, ce n'est pas protonvpn, comme dans ce fil ?
Non, pas du tout, j'suis chez Mullvad
Mais, comme déjà dit plus, le VPN n'est pas lié du tout
Sans VPN, sur Xubuntu Live USB (SSD), c'est la même chose.
Je pense pas qu'il faille se concentrer UNIQUEMENT & PRIORITAIREMENT sur la carte ETH Realtek.
Il me semble que ce n'est pas là que le problème se situe.
Vu que le problème se pose aussi pour la carte audio nVidia, en plus de la carte réseau Realtek.
Je commence à réellement songer à:
- soit un problème matériel
- soit à un problème avec le noyau & sa config
https://askubuntu.com/questions/1104219 … nomsi-mean
noaer [PCIE] If the PCIEAER kernel config parameter is enabled, this kernel boot option can be used to disable the use of PCIE advanced error reporting
je vais aller faire un p'tit tour dans
/var/log/kern.logvoir ce que ça y cause 
Clevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#29 Le 17/09/2021, à 10:13
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Ok 4ème reboot:
-- paramètres de boot
-> GRUB:
acpi_osi=! acpi_osi='Windows 2015' blacklist=nouveau elevator=deadline drm.debug=0xe quiet splash noresum-> r8169
cat /etc/modprobe.d/r8169.conf
options r8169 aspm=0-> câble ETH branché
Conséquences:
- CPU & FAN: calmes
- dmesg: pas de messages d'erreurs DPC / AER / pcieport
- lspci -v (je poste uniquement ce qui est intéressant)
00:1d.6 PCI bridge: Intel Corporation Device a336 (rev f0) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 125
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
I/O behind bridge: 00003000-00003fff
Memory behind bridge: 7f300000-7f3fffff
Prefetchable memory behind bridge: 00000000a2100000-00000000a21fffff
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: CLEVO/KAPOK Computer Device 95e1
Capabilities: [a0] Power Management version 3
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Access Control Services
Capabilities: [150] Precision Time Measurement
Capabilities: [220] #19
Capabilities: [250] Downstream Port Containment
Kernel driver in use: pcieport
Kernel modules: shpchp
01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
Subsystem: CLEVO/KAPOK Computer RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
Flags: fast devsel, IRQ 18
I/O ports at 0000
Memory at <ignored> (64-bit, non-prefetchable)
Memory at <ignored> (64-bit, prefetchable)
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
Capabilities: [d0] Vital Product Data
Kernel modules: r8169Donc
Shpchp -> pcieport = semble OK
audio nvidia = NOK erreur "!!! Unknown header type 7f"
- NM= option "Se connecter" pour ETH présente au début du boot puis disparaît (il me semble)
En tout cas là je la vois plus!
Clevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#30 Le 17/09/2021, à 12:14
- xubu1957
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Que propose :
ubuntu-drivers devices?
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
En ligne
#31 Le 17/09/2021, à 12:37
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Que propose :
ubuntu-drivers devices?
voilà
ubuntu-drivers devices
WARNING:root:_pkg_get_support nvidia-driver-390: package has invalid Support Legacyheader, cannot determine support level
== /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0 ==
modalias : pci:v000010DEd00001C20sv00001558sd000095E1bc03sc00i00
vendor : NVIDIA Corporation
model : GP106M [GeForce GTX 1060 Mobile]
driver : nvidia-driver-418-server - distro non-free
driver : nvidia-driver-450-server - distro non-free
driver : nvidia-driver-415 - third-party non-free
driver : nvidia-driver-460 - distro non-free
driver : nvidia-driver-470-server - distro non-free
driver : nvidia-driver-390 - distro non-free
driver : nvidia-driver-460-server - distro non-free
driver : nvidia-driver-470 - distro non-free recommended
driver : nvidia-driver-410 - third-party non-free
driver : xserver-xorg-video-nouveau - distro free builtin
== /sys/devices/pci0000:00/0000:00:1f.3 ==
modalias : pci:v00008086d0000A348sv00001558sd000095E1bc04sc03i00
vendor : Intel Corporation
driver : oem-audio-hda-daily-dkms - third-party free
== /sys/devices/pci0000:00/0000:00:1d.5/0000:03:00.0 ==
modalias : pci:v00008086d00002526sv00001A56sd00001550bc02sc80i00
vendor : Intel Corporation
manual_install: True
driver : backport-iwlwifi-dkms - distro freeClevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#32 Le 17/09/2021, à 12:42
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
le fichier
/var/log/kern.logqui débute en date du dimanche 12/09/21 pèse pas long de 7 Go à lui tout seul
à partir du 15/09/21 peu après 20h30, il est rempli de milliers de lignes d'erreurs telles que celles affichées par dmesg:
[ 168.664136] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.664143] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.664149] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.664155] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.664162] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.664168] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.664175] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.664181] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.664209] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.664216] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.664222] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.664229] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.664235] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
etc etc etc
[ 168.666397] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
[ 168.666399] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
...
[ 168.667231] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
[ 168.667237] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.667243] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.667250] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.667256] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.667265] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
[ 168.667266] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
[ 168.667266] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
[ 168.667270] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
[ 168.667278] pcieport 0000:00:1d.6: can't find device of ID00ee
[ 168.667278] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
[ 168.667285] pcieport 0000:00:1d.6: can't find device of ID00ee
[ 168.667286] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
[ 168.667293] pcieport 0000:00:1d.6: can't find device of ID00ee
[ 168.667294] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
[ 168.667301] pcieport 0000:00:1d.6: can't find device of ID00ee
[ 168.667302] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
[ 168.667309] pcieport 0000:00:1d.6: can't find device of ID00ee
[ 168.667309] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
[ 168.667317] pcieport 0000:00:1d.6: can't find device of ID00ee
[ 168.667318] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
...
[ 168.822875] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.822910] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
[ 168.822916] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
[ 168.822927] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
[ 168.822942] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000041/00002000
[ 168.822944] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
[ 168.822945] pcieport 0000:00:1d.6: [ 6] Bad TLP
[ 168.822954] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
[ 168.822961] pcieport 0000:00:1d.6: can't find device of ID00ee
[ 168.822962] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
[ 168.822970] pcieport 0000:00:1d.6: can't find device of ID00ee
[ 168.822971] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
[ 168.822980] pcieport 0000:00:1d.6: can't find device of ID00ee
[ 168.823000] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00eececi expliquant cela
Clevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#33 Le 17/09/2021, à 12:43
- xubu1957
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Montre :
dpkg -l | grep nvidia_ _ _
Vu :
pcieport 0000:00:1d.6: [ 6] Bad TLP Tu avais mis en place tlp ?
_ _ _
(edit=messages regroupés)
_ _ _
Ce bug non corrigé > bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 AER: Corrected error received: id=00e0
Dernière modification par xubu1957 (Le 17/09/2021, à 15:03)
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
En ligne
#34 Le 17/09/2021, à 13:16
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Montre :
dpkg -l | grep nvidia
voilà xubu1957
dpkg -l | grep nvidia
ii libnvidia-cfg1-460:amd64 460.91.03-0ubuntu0.18.04.1 amd64 NVIDIA binary OpenGL/GLX configuration library
ii libnvidia-common-460 460.91.03-0ubuntu0.18.04.1 all Shared files used by the NVIDIA libraries
ii libnvidia-compute-460:amd64 460.91.03-0ubuntu0.18.04.1 amd64 NVIDIA libcompute package
ii libnvidia-compute-460:i386 460.91.03-0ubuntu0.18.04.1 i386 NVIDIA libcompute package
ii libnvidia-decode-460:amd64 460.91.03-0ubuntu0.18.04.1 amd64 NVIDIA Video Decoding runtime libraries
ii libnvidia-decode-460:i386 460.91.03-0ubuntu0.18.04.1 i386 NVIDIA Video Decoding runtime libraries
ii libnvidia-encode-460:amd64 460.91.03-0ubuntu0.18.04.1 amd64 NVENC Video Encoding runtime library
ii libnvidia-encode-460:i386 460.91.03-0ubuntu0.18.04.1 i386 NVENC Video Encoding runtime library
ii libnvidia-extra-460:amd64 460.91.03-0ubuntu0.18.04.1 amd64 Extra libraries for the NVIDIA driver
ii libnvidia-fbc1-460:amd64 460.91.03-0ubuntu0.18.04.1 amd64 NVIDIA OpenGL-based Framebuffer Capture runtime library
ii libnvidia-fbc1-460:i386 460.91.03-0ubuntu0.18.04.1 i386 NVIDIA OpenGL-based Framebuffer Capture runtime library
ii libnvidia-gl-460:amd64 460.91.03-0ubuntu0.18.04.1 amd64 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii libnvidia-gl-460:i386 460.91.03-0ubuntu0.18.04.1 i386 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii libnvidia-ifr1-460:amd64 460.91.03-0ubuntu0.18.04.1 amd64 NVIDIA OpenGL-based Inband Frame Readback runtime library
ii libnvidia-ifr1-460:i386 460.91.03-0ubuntu0.18.04.1 i386 NVIDIA OpenGL-based Inband Frame Readback runtime library
ii nvidia-compute-utils-460 460.91.03-0ubuntu0.18.04.1 amd64 NVIDIA compute utilities
ii nvidia-dkms-460 460.91.03-0ubuntu0.18.04.1 amd64 NVIDIA DKMS package
ii nvidia-driver-440 450.119.03-0ubuntu0.18.04.1 amd64 Transitional package for nvidia-driver-450
ii nvidia-driver-450 460.91.03-0ubuntu0.18.04.1 amd64 Transitional package for nvidia-driver-460
ii nvidia-driver-460 460.91.03-0ubuntu0.18.04.1 amd64 NVIDIA driver metapackage
ii nvidia-kernel-common-460 460.91.03-0ubuntu0.18.04.1 amd64 Shared files used with the kernel module
ii nvidia-kernel-source-460 460.91.03-0ubuntu0.18.04.1 amd64 NVIDIA kernel source package
ii nvidia-opencl-dev:amd64 9.1.85-3ubuntu1 amd64 NVIDIA OpenCL development files
ii nvidia-prime 0.8.16~0.18.04.1 all Tools to enable NVIDIA's Prime
ii nvidia-settings 470.57.01-0ubuntu0.18.04.1 amd64 Tool for configuring the NVIDIA graphics driver
ii nvidia-utils-460 460.91.03-0ubuntu0.18.04.1 amd64 NVIDIA driver support binaries
ii xserver-xorg-video-nvidia-460 460.91.03-0ubuntu0.18.04.1 amd64 NVIDIA binary Xorg driverou j'ai TLP et TLPUI
mais là, dans le message d'erreur retourné par le kernel que tu cites, TLP c'est tout autre chose; ça concerne le PCI Express
C'est pour Transaction Layer Packet
The Transaction Layer uses TLPs to communicate request and completion data with other PCI Express devices.
Clevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#35 Le 17/09/2021, à 13:26
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
re,
Je dépose quelques extraits significatifs du fichier
/var/log/kern.logep 15 16:39:59 vrettou-P95xER kernel: [ 2.526908] pcieport 0000:00:1d.0: AER enabled with IRQ 123
Sep 15 16:39:59 vrettou-P95xER kernel: [ 2.526941] pcieport 0000:00:1d.5: AER enabled with IRQ 124
Sep 15 16:39:59 vrettou-P95xER kernel: [ 2.526974] pcieport 0000:00:1d.6: AER enabled with IRQ 125
Sep 15 16:39:59 vrettou-P95xER kernel: [ 2.527009] pcieport 0000:00:1d.7: AER enabled with IRQ 126
Sep 15 16:39:59 vrettou-P95xER kernel: [ 2.527024] pcieport 0000:00:01.0: Signaling PME with IRQ 122
Sep 15 16:39:59 vrettou-P95xER kernel: [ 2.527045] pcieport 0000:00:1d.0: Signaling PME with IRQ 123
Sep 15 16:39:59 vrettou-P95xER kernel: [ 2.527059] pcieport 0000:00:1d.5: Signaling PME with IRQ 124
Sep 15 16:39:59 vrettou-P95xER kernel: [ 2.527073] pcieport 0000:00:1d.6: Signaling PME with IRQ 125
Sep 15 16:39:59 vrettou-P95xER kernel: [ 2.527088] pcieport 0000:00:1d.7: Signaling PME with IRQ 126
Sep 15 16:39:59 vrettou-P95xER kernel: [ 2.527115] dpc 0000:00:1d.0:pcie010: DPC error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Sep 15 16:39:59 vrettou-P95xER kernel: [ 2.527131] dpc 0000:00:1d.5:pcie010: DPC error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Sep 15 16:39:59 vrettou-P95xER kernel: [ 2.527147] dpc 0000:00:1d.6:pcie010: DPC error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Sep 15 16:39:59 vrettou-P95xER kernel: [ 2.527166] dpc 0000:00:1d.7:pcie010: DPC error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Sep 15 20:34:00 vrettou-P95xER kernel: [ 2.528394] pcieport 0000:00:1d.0: AER enabled with IRQ 123
Sep 15 20:34:00 vrettou-P95xER kernel: [ 2.528428] pcieport 0000:00:1d.5: AER enabled with IRQ 124
Sep 15 20:34:00 vrettou-P95xER kernel: [ 2.528461] pcieport 0000:00:1d.6: AER enabled with IRQ 125
Sep 15 20:34:00 vrettou-P95xER kernel: [ 2.528494] pcieport 0000:00:1d.7: AER enabled with IRQ 126
Sep 15 20:34:00 vrettou-P95xER kernel: [ 2.528509] pcieport 0000:00:01.0: Signaling PME with IRQ 122
Sep 15 20:34:00 vrettou-P95xER kernel: [ 2.528529] pcieport 0000:00:1d.0: Signaling PME with IRQ 123
Sep 15 20:34:00 vrettou-P95xER kernel: [ 2.528543] pcieport 0000:00:1d.5: Signaling PME with IRQ 124
Sep 15 20:34:00 vrettou-P95xER kernel: [ 2.528557] pcieport 0000:00:1d.6: Signaling PME with IRQ 125
Sep 15 20:34:00 vrettou-P95xER kernel: [ 2.528576] pcieport 0000:00:1d.7: Signaling PME with IRQ 126
Sep 15 20:34:00 vrettou-P95xER kernel: [ 2.528602] dpc 0000:00:1d.0:pcie010: DPC error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Sep 15 20:34:00 vrettou-P95xER kernel: [ 2.528619] dpc 0000:00:1d.5:pcie010: DPC error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Sep 15 20:34:00 vrettou-P95xER kernel: [ 2.528636] dpc 0000:00:1d.6:pcie010: DPC error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Sep 15 20:34:00 vrettou-P95xER kernel: [ 2.528654] dpc 0000:00:1d.7:pcie010: DPC error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.575510] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.575515] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.575518] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.865586] [drm:intel_backlight_device_get_brightness [i915]] get backlight PWM = 60000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.895515] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.895540] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.895545] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD buf size -1
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932311] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932317] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932331] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932335] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932337] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932447] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932450] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932460] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932463] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932465] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932496] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932499] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932508] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932510] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932512] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932606] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932610] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932620] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932622] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932624] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932838] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932842] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932850] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932852] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932854] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932913] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932915] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932924] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932926] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.932928] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933071] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933074] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933083] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933085] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933087] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933316] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933320] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933329] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933331] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933333] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933375] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933377] pcieport 0000:00:1d.6: AER: Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933385] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933387] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933389] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933495] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933498] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933507] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933509] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.933511] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934075] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934079] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934088] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934090] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934092] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934643] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934648] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934657] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934660] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934663] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934720] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934731] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934733] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934742] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934744] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934746] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934758] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934760] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934769] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934771] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934773] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934778] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.934784] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935027] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935030] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935039] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935041] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935043] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935055] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935058] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935064] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935156] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935159] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935168] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935170] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935172] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.935562] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.936107] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.936363] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.936558] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.937774] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.939786] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.939899] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.940699] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.941130] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.941244] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.942640] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.942674] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.942837] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.943781] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.944137] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.944173] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.944202] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.944481] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947267] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947297] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947502] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947518] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947522] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947524] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947531] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947537] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947541] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947548] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947550] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947562] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947569] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947571] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947573] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947578] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947585] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947586] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947592] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947593] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947600] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947601] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947607] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947608] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947615] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947616] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947625] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947635] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947637] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947638] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947644] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947650] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947651] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947658] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947659] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947665] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947667] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947672] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947674] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947680] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947681] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947687] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947688] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947695] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947696] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947702] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947703] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947710] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947711] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947717] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947718] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947724] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947725] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.947733] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.948705] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.948710] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.948725] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.948729] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.948731] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.948775] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.948786] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.948808] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.948811] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.948813] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.949061] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.949065] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.949074] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.949077] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.949079] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950237] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950246] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950252] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950261] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950264] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950266] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950272] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950278] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950412] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950416] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950425] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950427] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000001/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950429] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950874] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.950878] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953396] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953404] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953414] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953423] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953433] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953443] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953452] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953463] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953471] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953479] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953504] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953529] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953541] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.953544] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.993259] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.993271] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.993275] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=000000c1/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.993279] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.993283] pcieport 0000:00:1d.6: [ 6] Bad TLP
Sep 15 20:34:03 vrettou-P95xER kernel: [ 48.993286] pcieport 0000:00:1d.6: [ 7] Bad DLLP
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.006542] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.006552] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.006559] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.006567] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.006575] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.006583] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.006590] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.007303] r8169 0000:04:00.0 enp4s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.007793] pcieport 0000:00:1d.6: can't find device of ID00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.007795] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.007806] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.007810] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000041/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.007812] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.007813] pcieport 0000:00:1d.6: [ 6] Bad TLP
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.036207] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.036217] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.036224] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.036233] dpc 0000:00:1d.6:pcie010: DPC containment event, status:0x1f00 source:0x0000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.036239] pcieport 0000:00:1d.6: AER: Multiple Corrected error received: id=00ee
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.036252] pcieport 0000:00:1d.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ee(Receiver ID)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.036256] pcieport 0000:00:1d.6: device [8086:a336] error status/mask=00000081/00002000
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.036258] pcieport 0000:00:1d.6: [ 0] Receiver Error (First)
Sep 15 20:34:03 vrettou-P95xER kernel: [ 49.036260] pcieport 0000:00:1d.6: [ 7] Bad DLLP à partir de là, c'est quasi comme ça tout le long...
Clevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#36 Le 17/09/2021, à 13:32
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Ce bug non corrigé > bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 AER: Corrected error received: id=00e0
je suis en train de lire ça
mais même avec
pci=noaerdans les options de boot, ça ne fonctionne pas.
le truc que j'y gagne, c'est qu'au moins ça ne tape dans le CPU et le FAN
Clevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#37 Le 17/09/2021, à 13:33
- xubu1957
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Je n'ai pas le niveau des aidants intervenants sur le fil de Nico
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
En ligne
#38 Le 17/09/2021, à 14:20
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
ok xubu1957,
je vais regarder ça
petite mise à jour
J'ai éteint le PC, tout déconnecté (USB, ETH, lecteur cartes, etc), débranché le PC de l'alim secteur, démonté le cache du dessous, retiré la batterie, les barrettes mémoires, et effectué un reset électrique.
là, remonté le tout, booté l'ordi
- sans le paramètres
pci=noaer
dans GRUB
- avec désactivé de la gestion de l'alimentation de la carte ETH
options r8169 aspm=0Au boot
- pas d'affollement du CPU ni du FAN
- pas de bourrage de dmesg avec messages d'erreurs DPC / AER / pcieport etc
Ça a l'air bon me dis-je!
Je plugue le câble ETH dans le port, et j'active la connexion via NM: ça marche! Je l'utilise actuellement.
Par contre en moins de 5-6 minutes, j'ai quand eu 2 décos.
Du coup, je me suis connecté à mon VPN, pas de soucis là non plus!
Clevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#39 Le 17/09/2021, à 14:31
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
du coup, ça donne ça:
ifconfig -a
enp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::3532:e134:33c3:4e9d prefixlen 64 scopeid 0x20<link>
inet6 2001:861:48c0:1cf0:e79c:bbea:5934:9aa9 prefixlen 64 scopeid 0x0<global>
ether 80:fa:5b:58:05:b5 txqueuelen 1000 (Ethernet)
RX packets 29109 bytes 23681255 (23.6 MB)
RX errors 0 dropped 7 overruns 0 frame 0
TX packets 21353 bytes 3335978 (3.3 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Boucle locale)
RX packets 1552 bytes 164801 (164.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1552 bytes 164801 (164.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.5.0.4 netmask 255.255.0.0 destination 10.5.0.4
inet6 fe80::a8cd:9753:e5d:be52 prefixlen 64 scopeid 0x20<link>
inet6 fdda:d0d0:cafe:443::1002 prefixlen 64 scopeid 0x0<global>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC)
RX packets 11407 bytes 9478309 (9.4 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8167 bytes 722063 (722.0 KB)
TX errors 0 dropped 213 overruns 0 carrier 0 collisions 0
wlp3s0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 94:b8:6d:f3:6f:0b txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0par contre lspci -v me retourne toujours l'erreur sur la carte audio nVidia
01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intelsur la carte ETH Realtek 8169, ça a l'air plus complet les infos, que ce que j'avais plus haut lors de mon précédent boot:
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
Subsystem: CLEVO/KAPOK Computer RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
Flags: bus master, fast devsel, latency 0, IRQ 18
I/O ports at 3000 [size=256]
Memory at 7f300000 (64-bit, non-prefetchable) [size=4K]
Memory at a2100000 (64-bit, prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
Capabilities: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
Capabilities: [170] Latency Tolerance Reporting
Kernel driver in use: r8169
Kernel modules: r8169j'vais voir si ça tient, et j'vais aussi tester un boot
- sans
pci=noaer- avec activation de la gestion de l'alimentation de la carte ETH
options r8169 aspm=0je vais aussi tester de télécharger un assez gros fichier, pour voir si ça encaisse le coup
je vous tiens au courant
Clevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#40 Le 17/09/2021, à 15:00
- ylag
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Bonjour,
Sous toute réserve, je ne crois pas que l'option aspm=0 soit un paramètre valable pour le module r8169 ?
La commande modinfo -F parm r8169 devrait afficher les paramètres disponibles pour le module r8169.
J'ai ceci chez-moi sur une 18.04 :
yvan@yvan-maison:~$ modinfo -F parm r8169
use_dac:Enable PCI DAC. Unsafe on 32 bit PCI slot. (int)
debug:Debug verbosity level (0=none, ..., 16=all) (int)
yvan@yvan-maison:~$Je crois que s'il est nécessaire de l'utiliser, le paramètre aspm=0 devrait être passé dans les options du noyau de GRUB ?
A+
Hors ligne
#41 Le 17/09/2021, à 15:10
- xubu1957
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
@ylag
Salut !
Je trouve > unix.stackexchange.com/questions/665530/what-r8169-cant-disable-aspm-means-and-how-should-i-fix-it, qui parle d'options du BIOS.
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
En ligne
#42 Le 17/09/2021, à 15:16
- ylag
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
@xubu1957 :
Bonjour!
Concernant ce genre de messages dans les retours de dmesg : « kernel: r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control », j'ai toujours eu quelque chose de semblable sur ma 18.04, apparemment sans conséquences :
yvan@yvan-maison:~$ dmesg | grep -i ASPM
[ 0.164708] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.164764] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[ 0.169014] pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
[ 0.169454] pci 0000:04:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
[ 0.989040] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 6.389870] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 9184.602279] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 9184.863408] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
yvan@yvan-maison:~$ ...les quatre dernières entrées seraient consécutives à des sorties de mise en veille.
A+
Dernière modification par ylag (Le 17/09/2021, à 15:19)
Hors ligne
#43 Le 17/09/2021, à 15:26
- xubu1957
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
(au #22) > bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772 r8169 ethernet card don't work after returning from suspension
La mise en veille peut être dangereuse.
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
En ligne
#44 Le 17/09/2021, à 15:39
- ylag
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
@xubu1957 :
Bonjour,
« La mise en veille peut être dangereuse. »
Pour info, sur ma 18.04, il me faut systématiquement faire une manip du genre de :
sudo modprobe -r r8169 ; sleep 2 ; sudo modprobe r8169...ou encore :
sudo ip link set enp4s0 down ; sleep 2 ; sudo ip link set enp4s0 up...pour réactiver mon interface éthernet (enp4s0 chez-moi) à chaque sortie de veille.
Sans en être certain, je crois que c'est la résolution DNS qui coince en sortie de veille, puisque j'arrive à «pinger» une adresse IP mais pas un nom de domaine...?
J'ai tenté de créer un service systemd pour le faire automatiquement lors des sorties de veille, mais bien que le service se lance correctement, la connexion n'est pas rétablie sauf si je relance manuellement ce service dans le terminal après la réactivation de ma session ; je suspecte que ce service ne soit lancé trop tôt dans le processus de sortie de veille. Mais là, je ne sais pas comment «débugger» le problème.
C'est ch..., mais c'est tout ce que j'ai pu trouver pour ravoir ma connexion lors des sorties de veille.
Sauf ce problème, la mise en veille fonctionne parfaitement pour moi, je l'utilise 4 à 5 fois par jour...
Note que je n'ai pas ce problème sur une 20.04 ni sur une Debian stable avec le même matos.
A+
Dernière modification par ylag (Le 31/10/2021, à 22:51)
Hors ligne
#45 Le 17/09/2021, à 15:53
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Bonjour,
Sous toute réserve, je ne crois pas que l'option aspm=0 soit un paramètre valable pour le module r8169 ?
La commande modinfo -F parm r8169 devrait afficher les paramètres disponibles pour le module r8169.
J'ai ceci chez-moi sur une 18.04 :yvan@yvan-maison:~$ modinfo -F parm r8169 use_dac:Enable PCI DAC. Unsafe on 32 bit PCI slot. (int) debug:Debug verbosity level (0=none, ..., 16=all) (int) yvan@yvan-maison:~$Je crois que s'il est nécessaire de l'utiliser, le paramètre aspm=0 devrait être passé dans les options du noyau de GRUB ?
A+
ok, ça me donne le même résultat que toi, mais franchement je ne sais pas ce qui est exploitable et utilisable dans le retour de cette commande - ni même ce que celasignifie
désolé
@ylag
Salut !
Je trouve > unix.stackexchange.com/questions/665530/what-r8169-cant-disable-aspm-means-and-how-should-i-fix-it, qui parle d'options du BIOS.
désolé, mais il n'y a rien que je puisse changer dans le SETUP de BIOS/UEFI FW, il est vraiment épuré
@xubu1957 :
Bonjour!
Concernant ce genre de messages dans les retours de dmesg : « kernel: r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control », j'ai toujours eu quelque chose de semblable sur ma 18.04, apparemment sans conséquences :
yvan@yvan-maison:~$ dmesg | grep -i ASPM [ 0.164708] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [ 0.164764] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM [ 0.169014] pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' [ 0.169454] pci 0000:04:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' [ 0.989040] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control [ 6.389870] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control [ 9184.602279] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control [ 9184.863408] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control yvan@yvan-maison:~$...les quatre dernières entrées seraient consécutives à des sorties de mise en veille.
A+
la commande ne me retourne rien car la sortie concernée dans le /var/log/kern.log remonte à trop loin dans le temps (2 jours) et en plus comme j'ai désactivé (je pense) la gestion de l'alimentation de la carte ETH Realtek...
(au #22) > bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772 r8169 ethernet card don't work after returning from suspension
La mise en veille peut être dangereuse.
je n'utilise pas la mise en veille, pas du tout.
********************************************************************************************
bon sinon, j'ai balancé 3 téléchargements
2 via JDownloader (JD), 1 avec QBitTorrent (QBT)
- 1er down via JD, fichier de 2 Go, FAN réglé à 50%: pas de déco, CPU monte en T°C maxi 72°C
- 2ème down via JD, fichier de 13 Go, FAN réglé à 100%: pas de déco, CPU monte en T°C, maxi 62°C
- 3ème down via QBT, fichier de 9 Go, FAN réglé à 70%: pas de déco, CPU monte en T°C, maxi 60
°C
Et, sinon, aucune déco depuis tout à l'heure (je l'aurai vu NM est paramétré Sans connexion auto si réseau disponible - obligé de me connecter manuellement)
Clevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#46 Le 17/09/2021, à 16:41
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Ok
j'ai rebooté l'ordi
- pas d'option désactivant l'Advanced Error Reporting au kernel dans GRUB
pci=noaer- pas de désactivation de la gestion de l'alim de la carte ETH RTL8111/8168
cat /etc/modprobe.d/r8169.conf
#options r8169 aspm=0- câble ETH plugué au boot
Résultat
- CPU et FAN calmes
- aucune erreur AER/DPC/pcieport etc dans dmesg
- connexion ETH RTL 8111/8168 OK via NM (VPN OK aussi)
- carte ETH Ok dans lspci
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
Subsystem: CLEVO/KAPOK Computer RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
Flags: bus master, fast devsel, latency 0, IRQ 18
I/O ports at 3000 [size=256]
Memory at 7f300000 (64-bit, non-prefetchable) [size=4K]
Memory at a2100000 (64-bit, prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
Capabilities: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
Capabilities: [170] Latency Tolerance Reporting
Kernel driver in use: r8169
Kernel modules: r8169- toujours l'erreur pour la carte audio nVidia (HDMI??)
01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intelça a l'air de fonctionner!!! 
Clevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#47 Le 17/09/2021, à 16:44
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
EUH!
...
- toujours l'erreur pour la carte audio nVidia (HDMI??)01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intelça a l'air de fonctionner!!!
Enfin, j'veux dire, presque!
Clevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#48 Le 17/09/2021, à 17:19
- xubu1957
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Que donne :
dmesg | grep r8169?
commande reprise dans > Ethernet connection does not come up after suspend
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
En ligne
#49 Le 17/09/2021, à 17:31
- phiphiloo
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Que donne :
dmesg | grep r8169?
commande reprise dans > Ethernet connection does not come up after suspend
OK
dmesg | grep r8169
[ 3.399446] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 3.412013] r8169 0000:04:00.0 eth0: RTL8168g/8111g at 0x (ptrval), 80:fa:5b:58:05:b5, XID 0c000800 IRQ 130
[ 3.412016] r8169 0000:04:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 3.419329] r8169 0000:04:00.0 enp4s0: renamed from eth0
[ 30.313716] r8169 0000:04:00.0 enp4s0: link down
[ 30.313754] r8169 0000:04:00.0 enp4s0: link down
[ 33.511753] r8169 0000:04:00.0 enp4s0: link upQuestion: comment faire pour vider le fichier
/var/log/kern.logcar il est trop gros là
15011851 -rw-r----- 1 syslog adm 5,6G sept. 17 17:30 kern.logAh, tiens! il a été un peu dégrossi
Clevo P950ER - i7-8750H CPU @ 2,20/4,1 Ghz - 64 Go DDR4 RAM Corsair Vengeance - Cannon Lake PCH / HM470 Chipset - UHD Graphics 630 (CoffeeLake-H GT2) / GeForce GTX 1060 Mobile (GP106M) - Realtek RTL8111/8168/8411 / Wi-Fi 6 AX210 / AX210 Bluetooth - Crucial P1 NVMe/PCIe SSD 1 To / Samsung SSD 870 SATA 4 To - Realtek ALC1220 / HDA Intel PCH / HDA nVidia - Xubuntu 22.04 / Kernel 5.15.0-69-generic
Hors ligne
#50 Le 17/09/2021, à 17:36
- xubu1957
Re : [Résolu] Carte ETH KO / Wifi OK / Autres problèmes: liées ou pas?
Tu as essayé un autre câble RJ45 ?
Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci. Membre de Linux-Azur
En ligne