Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Panic kernel

Maamon

Bonsoir, j'ai une jolie panic kernel en ce moment :

AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0

si je fait

journalctl -r -p err
-- Logs begin at Sun 2019-10-20 23:37:06 CEST, end at Sun 2019-10-20 23:49:01 C>
oct. 20 23:48:36 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:48:36 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:48:36 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:48:36 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:47:37 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:47:33 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:47:33 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:47:33 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:44 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:44 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:44 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:43 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:13 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:46:13 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:46:13 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:46:13 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:46:13 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:46:13 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:46:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:11 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:11 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:11 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:11 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:44:50 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:44:50 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:44:50 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:44:50 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:44:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:44:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:44:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:44:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:39:45 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:39:45 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:39:45 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:39:45 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:39:03 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:39:01 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:38:59 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:38:59 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:38:59 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:38:59 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:38:59 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:38:58 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:38:58 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:38:58 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:38:58 Dsy kernel: AMD-Vi: Event logged [IO_PAGE_FAULT device=20:00.0>
oct. 20 23:38:57 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:38:57 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:38:57 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:38:57 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:38:57 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:38:56 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:13 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:11 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:11 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:11 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:46:11 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_>
oct. 20 23:45:09 Dsy kernel: r8169 0000:20:00.0: AMD-Vi: Event logged [IO_PAGE_

Ca fait peur :b
Je précise que je peux encore accéder au bureau sans problème.

Maamon

D'après ce que je comprends il s'agirait d'un problème de carte réseau...

xubu1957

Bonjour,

Montre :

lspci -k -nn | grep -A 3 -i net

Il est parfois conseillé de remplacer le pilote r8169 par un r8168.

Tente :

sudo apt-get install r8168-dkms

_ _ _

traduction a écritLe r8169 est chargé lorsque le r8168 est introuvable sur votre système. Cela vous donnera un réseau et une connexion Internet, mais avec le pilote r8169, votre carte RTL8168 sera très instable.

> unixblogger.com/how-to-get-your-realtek-rtl8111rtl8168-working-updated-guide

Maamon

Bonsoir, après la manip, j'ai une de mes 2 cartes réseau qui est passé sous le driver 8168, mais pas la seconde. Je vous envoie le résultat de la cmd demandée :

lspci -k -nn | grep -A 3 -i net
20:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller [10ec:8169] (rev 10)
	Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC [10ec:8169]
	Kernel driver in use: r8169
	Kernel modules: r8169
21:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
	Subsystem: Micro-Star International Co., Ltd. [MSI] RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1462:7a34]
	Kernel driver in use: r8168
	Kernel modules: r8168
23:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)

xubu1957

Bonsoir,

Tu peux montrer :

ip -c a

Maamon

ip -c a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp32s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 00:0a:cd:32:d1:45 brd ff:ff:ff:ff:ff:ff
3: enp33s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 4c:cc:6a:f4:3c:8b brd ff:ff:ff:ff:ff:ff
    inet 192.168.8.121/24 brd 192.168.8.255 scope global dynamic noprefixroute enp33s0
       valid_lft 85979sec preferred_lft 85979sec
    inet6 fe80::8acf:8c3b:f332:3441/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

xubu1957

Tente :

sudo ip link set enp32s0 down
sudo ip link set enp32s0 up
sudo dhclient enp32s0

Maamon

Xubu je ne vais pas m'embéter, ni toi d'ailleurs ^^, je vais simplement retirer physiquement la carté éseau qui pose problème.
elle pose aussi problème sur des distribs plus complexes que Ubuntu, donc ça va régler le problème.

Merci et désolé du dérangement 🙂

xubu1957

J'essaye d'aider, c'est pas un dérangement. 😉

Maamon

Et c'est tout à ton honneur 😉
Sur d'autres forums, ça fait longtemps qu'on m'aurait envoyer bouler avec tous mes bugs ^^

xubu1957

Moi je n'y connaissais rien, j'apprends sur le tas.

Notre base de données, accumulée au fil des années, est un trésor.