#1 Le 05/02/2018, à 13:52
- 27yona
Plus de mémoire après un jour d'utilisation d'Ubuntu
Bonjour,
J'ai tout récemment installer Ubuntu. A première vue l'installation s'est bien déroulée.
Seulement, après un jour d'utilisation on me signale que je n'ai plus de mémoire: Le volume "racine du système de fichiers n'a plus que 0 octet d'espace disque disponible.
Dans l'analyseur d'utilisation des disques je vois que le dossier var prends beaucoup de place mais je sais pas à quoi cela fait réference.
Auriez vous une solution a mon problème?
merci à vous
Hors ligne
#2 Le 05/02/2018, à 14:05
- tcheupel
Re : Plus de mémoire après un jour d'utilisation d'Ubuntu
Bonjour,
J'ai tout récemment installer Ubuntu. A première vue l'installation s'est bien déroulée.Seulement, après un jour d'utilisation on me signale que je n'ai plus de mémoire: Le volume "racine du système de fichiers n'a plus que 0 octet d'espace disque disponible.
Dans l'analyseur d'utilisation des disques je vois que le dossier var prends beaucoup de place mais je sais pas à quoi cela fait réference.
Auriez vous une solution a mon problème?
merci à vous
Tu as fait le choix du partitionnement toi-même ? Le "/" donc la racine, doit être beaucoup trop petite, ou alors il n'y pas de partition /home ?
Tape df dans un terminal et poste la réponse.
- Portable Dell Inspiron 3581 : Debian 12 Gnome
SSD 1to - Ram 8go - Intel i3 - CG intégrée Intel HD 620
- Portable ASUS S406U : Debian 12 XFCE
SSD 240go - Ram 8go - Intel i5 - CG intégrée Intel HD 620
Hors ligne
#3 Le 05/02/2018, à 14:05
- moko138
Re : Plus de mémoire après un jour d'utilisation d'Ubuntu
Lance d'abord
sudo apt-get clean ; sudo apt-get autoremove
Ensuite montre le retour de
df -Th | grep -Ev "devpts|none|proc|tmpfs|udev"; echo ; df -Ti | grep -Ev "devpts|none|proc|tmpfs|udev"
/!\ Ne cherche surtout pas à retaper ces lignes ! Utilise
- un triple clic gauche sur une ligne pour la sélectionner tout entière et la copier,
- un clic milieu pour la coller.
%NOINDEX%
Un utilitaire précieux : ncdu
Photo, mini-tutoriel : À la découverte de dcraw
Hors ligne
#4 Le 05/02/2018, à 14:29
- LukePerp
Re : Plus de mémoire après un jour d'utilisation d'Ubuntu
Et aussi :
sudo fdisk -l
Desktop & Laptop - Ubuntu Mate dernière LTS - Intel i5 - 16 Go - Dual boot Windows offline
Hors ligne
#5 Le 05/02/2018, à 17:52
- ??
Re : Plus de mémoire après un jour d'utilisation d'Ubuntu
Dans l'analyseur d'utilisation des disques je vois que le dossier var prend beaucoup de place mais je sais pas à quoi cela fait référence.
Bonjour
tail -400 /var/log/syslog
et aussi les autres répertoires de /var qui sont volumineux
Dernière modification par ?? (Le 05/02/2018, à 17:55)
Utiliser REFIND au lieu du GRUB https://doc.ubuntu-fr.org/refind . Aidez à vous faire dépanner en suivant le guide et en utilisant les outils de diagnostic J'ai perdu ma gomme. Désolé pour les fautes d'orthographes non corrigées.
Hors ligne
#6 Le 05/02/2018, à 19:10
- 27yona
Re : Plus de mémoire après un jour d'utilisation d'Ubuntu
Et aussi :
sudo fdisk -l
abizmil@abizmil-X456UR:~$ sudo fdisk -l
Disque /dev/sda : 931,5 GiB, 1000204886016 octets, 1953525168 secteurs
Unités : sectors of 1 * 512 = 512 octets
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 19079CA2-3F2B-43F0-9128-492FC0C10760
Périphérique Start Fin Secteurs Size Type
/dev/sda1 2048 534527 532480 260M EFI System
/dev/sda2 534528 567295 32768 16M Microsoft reserved
/dev/sda3 567296 1889587199 1889019904 900,8G Microsoft basic data
/dev/sda4 1952501760 1953523711 1021952 499M Windows recovery environment
/dev/sda5 1889587200 1919586303 29999104 14,3G Linux filesystem
/dev/sda6 1919586304 1932505087 12918784 6,2G Partition d'échange Linux
/dev/sda7 1932505088 1952501759 19996672 9,5G Linux filesystem
Partition table entries are not in disk order.
Disque /dev/mapper/cryptswap1 : 6,2 GiB, 6613893120 octets, 12917760 secteurs
Unités : sectors of 1 * 512 = 512 octets
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Hors ligne
#7 Le 05/02/2018, à 19:12
- 27yona
Re : Plus de mémoire après un jour d'utilisation d'Ubuntu
Lance d'abord
sudo apt-get clean ; sudo apt-get autoremove
Ensuite montre le retour de
df -Th | grep -Ev "devpts|none|proc|tmpfs|udev"; echo ; df -Ti | grep -Ev "devpts|none|proc|tmpfs|udev"
/!\ Ne cherche surtout pas à retaper ces lignes ! Utilise
- un triple clic gauche sur une ligne pour la sélectionner tout entière et la copier,
- un clic milieu pour la coller.
abizmil@abizmil-X456UR:~$ sudo apt-get clean ; sudo apt-get autoremove
[sudo] Mot de passe de abizmil :
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 307 non mis à jour.
abizmil@abizmil-X456UR:~$ df -Th | grep -Ev "devpts|none|proc|tmpfs|udev"; echo ; df -Ti | grep -Ev "devpts|none|proc|tmpfs|udev"
Sys. de fichiers Type Taille Utilisé Dispo Uti% Monté sur
/dev/sda5 ext4 14G 14G 24M 100% /
/dev/sda7 ext4 9,3G 975M 7,9G 11% /home
/home/abizmil/.Private ecryptfs 9,3G 975M 7,9G 11% /home/abizmil
Sys. de fichiers Type Inœuds IUtil. ILibre IUti% Monté sur
/dev/sda5 ext4 938400 194355 744045 21% /
/dev/sda7 ext4 625856 20116 605740 4% /home
/home/abizmil/.Private ecryptfs 625856 20116 605740 4% /home/abizmil
Hors ligne
#8 Le 05/02/2018, à 19:14
- 27yona
Re : Plus de mémoire après un jour d'utilisation d'Ubuntu
27yona a écrit :Dans l'analyseur d'utilisation des disques je vois que le dossier var prend beaucoup de place mais je sais pas à quoi cela fait référence.
Bonjour
tail -400 /var/log/syslog
et aussi les autres répertoires de /var qui sont volumineux
abizmil@abizmil-X456UR:~$ tail -400 /var/log/syslog
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.000988] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.001252] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.001255] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.001257] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.001705] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002042] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002044] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002046] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002052] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002066] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002068] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002070] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002073] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002420] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002441] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002840] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002842] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002844] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002854] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002858] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002860] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.002862] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.011147] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.011152] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.011155] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.011156] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.011901] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.011910] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.011918] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.011920] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.011925] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.012273] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.012332] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.012337] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.012339] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.012341] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.020944] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.020949] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.020952] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.020953] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.021745] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.021749] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.021752] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.021754] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.021758] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.022106] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.022207] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.022212] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.022214] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.022215] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.031076] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.031081] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.031084] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.031086] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.032173] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.032189] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.032192] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.032193] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.032198] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.032524] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.032540] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.032544] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.032546] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.032547] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.033604] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.034016] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.034021] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.034023] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.034027] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.034375] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.034395] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.034745] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.034748] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.034749] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.034757] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.035105] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.035121] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.035126] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.035128] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.035129] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.035133] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.035479] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.035499] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.035503] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.035505] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.035506] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.041070] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.041075] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.041078] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.041080] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.041883] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042235] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042238] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042240] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042245] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042258] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042260] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042262] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042265] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042613] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042630] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042635] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042637] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042638] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.042642] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.043011] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.043012] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.043017] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.043020] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.043021] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.050963] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.050968] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.050971] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.050973] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.051720] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.051729] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.051731] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.051738] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.051743] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.052456] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.052457] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.052470] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.052471] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.052472] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.052482] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.052828] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.052845] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.052849] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.052850] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.052851] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.061411] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.061793] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.061797] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.061799] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062148] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062157] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062158] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062166] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062555] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062564] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062573] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062575] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062578] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062926] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062950] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062954] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062956] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.062957] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.071183] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.071190] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.071194] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.071196] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.071572] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.071922] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.071924] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.071925] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.071949] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.071957] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.071959] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.071960] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.072504] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.072510] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.072514] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.072517] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.081300] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.081307] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.081312] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.081315] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.082060] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.082423] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.082425] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.082430] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.082433] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.082435] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.083253] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.083259] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.083264] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.083267] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.083271] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.083626] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.083628] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.083642] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.083644] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.083649] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.083651] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.083653] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.083656] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.084004] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.084072] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.084078] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.084080] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.084082] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.091066] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.091074] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.091080] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.091083] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.091823] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.091838] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.091843] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.091847] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.091852] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.092201] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.092311] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.092320] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.092327] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.092332] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.101141] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.101162] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.101179] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.101190] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.101607] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.102360] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.102384] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.102394] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.102407] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.102764] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.102787] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.102801] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.102812] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.102821] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.102833] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.103190] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.103212] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.103226] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.103237] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.103247] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.103260] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.103617] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.103640] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.103653] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.103664] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.103673] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.103687] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104103] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104109] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104123] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104133] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104143] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104155] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104512] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104536] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104549] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104558] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104566] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104578] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104934] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.104966] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.105326] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.105347] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.105355] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.105367] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.105796] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.105814] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.106179] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.106199] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.106208] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.106219] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.106575] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.106647] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.107007] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.107027] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.107035] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.107048] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.107404] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.107428] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.107788] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.107807] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.107816] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.107829] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.108186] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.108209] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.108223] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.108233] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.108242] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.108255] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.108611] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.108638] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.108652] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.108661] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.108670] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.108682] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109039] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109044] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109066] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109077] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109086] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109098] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109455] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109478] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109492] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109503] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109514] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109527] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109951] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.109968] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.110338] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.110357] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.110366] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.110378] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.110759] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.110765] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.111126] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.111137] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.111160] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.111173] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.111528] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.111938] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.111963] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.111974] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.111983] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.112332] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.112348] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.112364] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.112377] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.112386] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.112394] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.121539] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.122307] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.122336] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.122347] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.122360] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.122718] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.122741] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.122758] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.122769] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.122780] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.122798] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.123155] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.123179] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.123191] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.123200] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.123209] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.123221] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.123577] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.123599] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.123612] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.123621] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.123630] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.123640] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.123996] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124001] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124022] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124031] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124038] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124048] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124404] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124425] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124437] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124446] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124454] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124465] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124821] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124828] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124850] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124860] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124868] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.124880] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.125236] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.125271] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.125284] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.125293] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.125302] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.131130] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.131144] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.131154] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.131160] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.131915] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.131939] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.131945] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.131951] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.131960] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.132314] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.132357] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.132367] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.132373] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.132378] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.141536] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.141996] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142013] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142034] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142315] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142332] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142349] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142364] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142373] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142389] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142406] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142764] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142787] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142800] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142811] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142819] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.142832] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.143189] pcieport 0000:00:1c.5: can't find device of ID00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.143211] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.143223] pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.143233] pcieport 0000:00:1c.5: device [8086:9d15] error status/mask=00000001/00002000
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.143242] pcieport 0000:00:1c.5: [ 0] Receiver Error (First)
Feb 5 18:06:12 abizmil-X456UR kernel: [ 683.143255] pcieport 0000:00:1c.5: AER: Corrected error received: id=00e5
Modération : merci d'utiliser les balises code (explications ici).
Dernière modification par cqfd93 (Le 05/02/2018, à 19:56)
Hors ligne
#9 Le 05/02/2018, à 19:35
- ??
Re : Plus de mémoire après un jour d'utilisation d'Ubuntu
On va tenter la correction indiquée là https://askubuntu.com/questions/748078/ … -bus-error
1) Ouvrir le fichier etc/default/grub avec un éditeur de text (gedit nano leafpad ....)
2) Modifier la ligne
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Pour qu'elle devienne
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi "
3) Sauvegarder, quitter l'éditeur et faire prendre en charge par la commande
sudo update-grub
4) Faire un peu de ménage
sudo rm -v /var/log/syslog*
5) Booter pour que ce message d'erreur disparaisse. En espérant qu'il n'y en a pas d'autres masqués par cette répétition.
Dernière modification par ?? (Le 05/02/2018, à 19:39)
Utiliser REFIND au lieu du GRUB https://doc.ubuntu-fr.org/refind . Aidez à vous faire dépanner en suivant le guide et en utilisant les outils de diagnostic J'ai perdu ma gomme. Désolé pour les fautes d'orthographes non corrigées.
Hors ligne
#10 Le 05/02/2018, à 20:18
- 27yona
Re : Plus de mémoire après un jour d'utilisation d'Ubuntu
Merci ça a l'air d'avoir fonctionné. J'ai désormais 66% pour /dev/sda5 au lieu de 100%.
Quel était le problème exactement?
Comment puis-je éviter que ce problème se renouvelle?
Hors ligne
#11 Le 06/02/2018, à 01:44
- ??
Re : Plus de mémoire après un jour d'utilisation d'Ubuntu
Tous les 5 millisecondes, le logiciel écrit une dizaine de lignes dans un fichier pour signaler un éventuel problème sur un périphérique.
device [8086:9d15] error status/mask=00000001/00002000
Au bout de la journée, cela fait un énorme volume qui est historisé pendant 10 jours.
En clair, Le logiciel n'est pas au point. https://bugs.launchpad.net/ubuntu/+sour … ug/1521173 Dans cette discussion, il propose un autre parametre plus évocateur. Mais le message d'erreur n'est pas exactement le même. Il est comme ce cas https://h30434.www3.hp.com/t5/Notebook- … -p/5933687
Dernière modification par ?? (Le 06/02/2018, à 02:06)
Utiliser REFIND au lieu du GRUB https://doc.ubuntu-fr.org/refind . Aidez à vous faire dépanner en suivant le guide et en utilisant les outils de diagnostic J'ai perdu ma gomme. Désolé pour les fautes d'orthographes non corrigées.
Hors ligne
#12 Le 06/02/2018, à 11:39
- LukePerp
Re : Plus de mémoire après un jour d'utilisation d'Ubuntu
Bravo ?? d'avoir identifié ce qui cloche. D'après toi, quel est le taux d'étendue chez les utilisateurs de ce bug ? Est-ce qu'il est très répandue ?
Dernière modification par LukePerp (Le 06/02/2018, à 11:42)
Desktop & Laptop - Ubuntu Mate dernière LTS - Intel i5 - 16 Go - Dual boot Windows offline
Hors ligne
#13 Le 08/02/2018, à 16:03
- ??
Re : Plus de mémoire après un jour d'utilisation d'Ubuntu
Bonjour
Je ne sais pas dire combien de personnes ont le problème
Cette recherche https://www.google.fr/search?as_q=&as_e … as_rights= donne 286 résultats
Cette recherche https://www.google.fr/search?as_q=&as_e … as_rights= donne 407 résultats
Cette recherche https://www.google.fr/search?as_q=&as_e … as_rights= donne 650 résultats
Cette recherche https://www.google.fr/search?as_q=&as_e … as_rights= donne 1550 résultats
Mais il y a des doublons.....
Officiellement 78 personnes se sont manifestées sur ce bug https://bugs.launchpad.net/ubuntu/+sour … ug/1521173 npour ubuntu, Mais il n'y a pas que ubuntu qui a le problème et là ils sont plus discrets https://bugzilla.redhat.com/show_bug.cgi?id=1293424
Dernière modification par ?? (Le 08/02/2018, à 16:09)
Utiliser REFIND au lieu du GRUB https://doc.ubuntu-fr.org/refind . Aidez à vous faire dépanner en suivant le guide et en utilisant les outils de diagnostic J'ai perdu ma gomme. Désolé pour les fautes d'orthographes non corrigées.
Hors ligne