Problema di DNS, ma solo con funzionamento a batteria…? 
Comunque ho provato e già con il primo comando non è successo niente… internet inchiodato e così resta…
A me suona molto strana la cosa. Se è solo in una condizione, batteria, deve essere collegato alla gestione energetica.
Hai ragione, infatti non capisco. Con l’alimentazione da rete può capitare, ma ci può stare, anche per colpa del router o del fornitore. Insomma quelle interruzioni saltuarie che però non creano problemi.
Invece a batteria, non importa con quale router (di casa o in giro) o un hotspot con lo smartphone è un disastro. Il wifi sembra ok, di per sé. Ma dopo un tot di secondi o minuti (anche la tempistica appare random) internet non va più (ma il wifi resta connesso) e l’unico modo è spegnere e riaccendere il wifi. A quel punto si ricollega e si rinaviga… fino al successivo blocco.
Prova a vedere i log del kernel se trovi qualcosa di interessante…sto studiando ma on trovo particolari soluzioni…
Eccomi, allora beccato poco fa, alle 12:3x, dove “x” non lo so perché il minuto esatto non l’ho colto, ma di sicuro è successo dalle 12:30 alle 12:39, in questo range. Il log mi dice:
[root@hp-15sfq5017nl master]# dmesg -T | grep -i "Nov 27 12:3"
[lun nov 27 12:38:57 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[lun nov 27 12:38:57 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[lun nov 27 12:38:57 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[lun nov 27 12:38:57 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[lun nov 27 12:38:57 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[lun nov 27 12:38:57 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[lun nov 27 12:38:57 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[lun nov 27 12:38:57 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[lun nov 27 12:38:58 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[lun nov 27 12:38:58 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[lun nov 27 12:38:58 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[lun nov 27 12:38:58 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[lun nov 27 12:38:58 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[lun nov 27 12:38:58 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[lun nov 27 12:38:58 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[lun nov 27 12:38:59 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[lun nov 27 12:38:59 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[lun nov 27 12:38:59 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[lun nov 27 12:38:59 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[lun nov 27 12:38:59 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[lun nov 27 12:38:59 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[lun nov 27 12:38:59 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[lun nov 27 12:38:59 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[lun nov 27 12:38:59 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[lun nov 27 12:38:59 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[lun nov 27 12:38:59 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[lun nov 27 12:38:59 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[lun nov 27 12:39:07 2023] pcieport 0000:00:1c.0: AER: Uncorrected (Non-Fatal) error received: 0000:01:00.0
[lun nov 27 12:39:07 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
[lun nov 27 12:39:07 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00004000/00400000
[lun nov 27 12:39:07 2023] rtw_8822ce 0000:01:00.0: [14] CmpltTO (First)
[lun nov 27 12:39:07 2023] rtw_8822ce 0000:01:00.0: AER: can't recover (no error_detected callback)
[lun nov 27 12:39:07 2023] pcieport 0000:00:1c.0: AER: device recovery failed
[lun nov 27 12:39:07 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:07 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:07 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:09 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:09 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:09 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:11 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:11 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:13 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:15 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:15 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:15 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:15 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:17 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:17 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:17 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:19 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:19 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:21 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:23 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:25 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:27 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:29 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:31 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:33 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:35 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:37 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:39 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:41 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:43 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:45 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:47 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:49 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:49 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:49 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:51 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:51 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:51 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:53 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps state
[lun nov 27 12:39:53 2023] rtw_8822ce 0000:01:00.0: failed to send h2c command
[lun nov 27 12:39:53 2023] rtw_8822ce 0000:01:00.0: firmware failed to leave lps stateOttimo! Si tratta di un bug noto e qualche soluzione l’hanno già suggerita.
Vedi questi ad esempio:
https://bugzilla.kernel.org/show_bug.cgi?id=215496
e qua:
Io procederei in questo modo:
- verifica se ci sono aggiornamenti del bios da poter fare, se si aggiornalo e poi vedi se il problema persiste.
- se il problema persiste o non riesci ad aggiornare il bios o non ci sono aggiornamenti si può provare a disabilitare la gestione energetica di NetworkManager.
Potresti farlo semplicemente così:
$ sudo dd of=/etc/NetworkManager/conf.d/30-powersave.conf << EOF
[connection]
# Values are 0 (use default), 1 (ignore/don't touch), 2 (disable) or 3 (enable).
wifi.powersave = 2
EOF
$ sudo systemctl restart NetworkManagerO in alternativa riavvia completamente il pc e vedi se il problema viene risolto.
Se tutto funziona meglio si potrebbe provare con un’altra soluzione, a detta di alcuni migliore, agendo direttamente sui parametri del firmware della tua scheda di rete.
Ciao! Allora, non mi pare ci siano aggiornamenti del bios al momento. Così ho provato la soluzione gestione energetica NetworkManager e per sicurezza ho proprio riavviato il notebook. Niente da fare.
Ironia della sorte, prima di effettuare la procedura per circa 15 minuti non ci sono stati problemi. poi ho riavviato (con le modifiche, verificando anche la presenza del file conf sopra definito) e dopo 2 minuti il problema è subito apparso.
Quello che ho notato, ma non so se è un caso, è che quando uso il terminale con ssh (lo uso spesso per collegarmi a pc remoti) la cosa sembra verificarsi più di frequente. Ma, ripeto, non so se è un caso e magari solo la mia impressione… (ma in ogni caso succede anche senza neanche aprirlo il terminale…)
Preciso che il file /etc/NetworkManager/conf.d/30-powersave.conf non esisteva.
Puoi, con questa modifica, ricontrollare i log del kernel?
Ecco qua. In questo “frangente” non andava, ho sbloccato con il solito attiva/disattiva il wifi, e quasi subito dopo bloccato di nuovo:
[root@hp-15sfq5017nl master]# dmesg -T | grep -i "Nov 28 16:2"
[mar nov 28 16:21:23 2023] wlo1: deauthenticating from 84:16:f9:ae:ba:80 by local choice (Reason: 3=DEAUTH_LEAVING)
[mar nov 28 16:21:28 2023] wlo1: authenticate with 84:16:f9:ae:ba:80
[mar nov 28 16:21:28 2023] wlo1: 80 MHz not supported, disabling VHT
[mar nov 28 16:21:28 2023] wlo1: send auth to 84:16:f9:ae:ba:80 (try 1/3)
[mar nov 28 16:21:28 2023] wlo1: authenticated
[mar nov 28 16:21:28 2023] wlo1: associate with 84:16:f9:ae:ba:80 (try 1/3)
[mar nov 28 16:21:28 2023] wlo1: RX AssocResp from 84:16:f9:ae:ba:80 (capab=0x31 status=0 aid=17)
[mar nov 28 16:21:28 2023] wlo1: associated
[mar nov 28 16:21:41 2023] pcieport 0000:00:1c.0: AER: Uncorrected (Non-Fatal) error received: 0000:01:00.0
[mar nov 28 16:21:41 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
[mar nov 28 16:21:41 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00004000/00400000
[mar nov 28 16:21:41 2023] rtw_8822ce 0000:01:00.0: [14] CmpltTO (First)
[mar nov 28 16:21:41 2023] rtw_8822ce 0000:01:00.0: AER: can't recover (no error_detected callback)
[mar nov 28 16:21:41 2023] pcieport 0000:00:1c.0: AER: device recovery failed
[mar nov 28 16:22:19 2023] wlo1: deauthenticating from 84:16:f9:ae:ba:80 by local choice (Reason: 3=DEAUTH_LEAVING)
[mar nov 28 16:22:42 2023] wlo1: authenticate with 84:16:f9:ae:ba:80
[mar nov 28 16:22:42 2023] wlo1: 80 MHz not supported, disabling VHT
[mar nov 28 16:22:42 2023] wlo1: send auth to 84:16:f9:ae:ba:80 (try 1/3)
[mar nov 28 16:22:42 2023] wlo1: authenticated
[mar nov 28 16:22:42 2023] wlo1: associate with 84:16:f9:ae:ba:80 (try 1/3)
[mar nov 28 16:22:42 2023] wlo1: RX AssocResp from 84:16:f9:ae:ba:80 (capab=0x31 status=0 aid=17)
[mar nov 28 16:22:42 2023] wlo1: associated
[mar nov 28 16:22:55 2023] pcieport 0000:00:1c.0: AER: Uncorrected (Non-Fatal) error received: 0000:01:00.0
[mar nov 28 16:22:55 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
[mar nov 28 16:22:55 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00004000/00400000
[mar nov 28 16:22:55 2023] rtw_8822ce 0000:01:00.0: [14] CmpltTO (First)
[mar nov 28 16:22:55 2023] rtw_8822ce 0000:01:00.0: AER: can't recover (no error_detected callback)
[mar nov 28 16:22:55 2023] pcieport 0000:00:1c.0: AER: device recovery failed
[mar nov 28 16:22:55 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[mar nov 28 16:22:55 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[mar nov 28 16:22:55 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=0000a001/0000e000
[mar nov 28 16:22:55 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[mar nov 28 16:23:01 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[mar nov 28 16:23:01 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[mar nov 28 16:23:01 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[mar nov 28 16:23:01 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[mar nov 28 16:23:05 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[mar nov 28 16:23:05 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[mar nov 28 16:23:05 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[mar nov 28 16:23:05 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[mar nov 28 16:23:07 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[mar nov 28 16:23:07 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[mar nov 28 16:23:07 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/0000e000
[mar nov 28 16:23:07 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)Toglimi questa curiosità:
$ lsmod | grep rtw Ecco qua:
[root@hp-15sfq5017nl master]# lsmod | grep rtw
rtw88_8822ce 12288 0
rtw88_8822c 487424 1 rtw88_8822ce
rtw88_pci 40960 1 rtw88_8822ce
rtw88_core 249856 2 rtw88_pci,rtw88_8822c
mac80211 1572864 2 rtw88_pci,rtw88_core
cfg80211 1331200 2 rtw88_core,mac80211
Il problema è sempre sul risparmio energetico. Si potrebbe provare a passare i parametri necessari per disabilitarlo sul kernel.
$ sudo dd of=/etc/modprobe.d/rtl8822ce.conf << EOF
options rtw88_pci disable_msi=y disable_aspm=y
options rtw88_core disable_lps_deep=y
EOFRiavvia completamente la macchina e vedi come si comporta.
Da una prima prova sembra ok! Ho anche aggiornato il sistema, prima non riuscivo a farlo.
Magari lo provo un po’ di volte nei prossimi giorni, prima di cantare vittoria. Ma intanto grazie!
Ottimo facci sapere!
Eccomi! Allora stamattina ho avuto un po’ più tempo e ho usato il notebook in batteria per quasi 2 ore arrivando dal 100% al 35% di carica e ho fatto di tutto, anche l’ssh.
Sembra tutto ok, mitico MarioS!!! 
PS: fra un po’ passerò a fc39… chissà come andrà 
Tutto dipende se hanno sistemato i driver con le nuove versioni ma dubito. Poi facile dovrai seguire questa discussione per risolvere il problema!
Ahia… oggi ci risiamo… ti invio direttamente il log…
[root@hp-15sfq5017nl master]# dmesg -T | grep -i "Nov 30 15:0"
[gio nov 30 15:01:18 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[gio nov 30 15:01:18 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[gio nov 30 15:01:18 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00000001/00000000
[gio nov 30 15:01:18 2023] rtw_8822ce 0000:01:00.0: [ 0] RxErr (First)
[gio nov 30 15:05:14 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[gio nov 30 15:05:14 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[gio nov 30 15:05:14 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=0000a000/00000000
[gio nov 30 15:05:14 2023] rtw_8822ce 0000:01:00.0: [13] NonFatalErr
[gio nov 30 15:05:14 2023] rtw_8822ce 0000:01:00.0: [15] HeaderOF
[gio nov 30 15:05:14 2023] pcieport 0000:00:1c.0: AER: Uncorrected (Non-Fatal) error received: 0000:01:00.0
[gio nov 30 15:05:14 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
[gio nov 30 15:05:14 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00014000/00000000
[gio nov 30 15:05:14 2023] rtw_8822ce 0000:01:00.0: [14] CmpltTO (First)
[gio nov 30 15:05:14 2023] rtw_8822ce 0000:01:00.0: [16] UnxCmplt
[gio nov 30 15:05:14 2023] rtw_8822ce 0000:01:00.0: AER: TLP Header: 00000000 00000000 00000000 00000000
[gio nov 30 15:05:14 2023] rtw_8822ce 0000:01:00.0: AER: can't recover (no error_detected callback)
[gio nov 30 15:05:14 2023] pcieport 0000:00:1c.0: AER: device recovery failed
[gio nov 30 15:06:05 2023] wlo1: deauthenticating from 16:76:27:d4:14:94 by local choice (Reason: 3=DEAUTH_LEAVING)
[gio nov 30 15:06:11 2023] wlo1: authenticate with 16:76:27:d4:14:94
[gio nov 30 15:06:11 2023] wlo1: 80 MHz not supported, disabling VHT
[gio nov 30 15:06:11 2023] wlo1: send auth to 16:76:27:d4:14:94 (try 1/3)
[gio nov 30 15:06:11 2023] wlo1: authenticated
[gio nov 30 15:06:11 2023] wlo1: associate with 16:76:27:d4:14:94 (try 1/3)
[gio nov 30 15:06:11 2023] wlo1: RX AssocResp from 16:76:27:d4:14:94 (capab=0x411 status=0 aid=1)
[gio nov 30 15:06:11 2023] wlo1: associated
[gio nov 30 15:08:08 2023] pcieport 0000:00:1c.0: AER: Multiple Corrected error received: 0000:01:00.0
[gio nov 30 15:08:08 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Transaction Layer, (Receiver ID)
[gio nov 30 15:08:08 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=0000a000/00000000
[gio nov 30 15:08:08 2023] rtw_8822ce 0000:01:00.0: [13] NonFatalErr
[gio nov 30 15:08:08 2023] rtw_8822ce 0000:01:00.0: [15] HeaderOF
[gio nov 30 15:08:08 2023] pcieport 0000:00:1c.0: AER: Uncorrected (Non-Fatal) error received: 0000:01:00.0
[gio nov 30 15:08:08 2023] rtw_8822ce 0000:01:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
[gio nov 30 15:08:08 2023] rtw_8822ce 0000:01:00.0: device [10ec:c822] error status/mask=00014000/00000000
[gio nov 30 15:08:08 2023] rtw_8822ce 0000:01:00.0: [14] CmpltTO (First)
[gio nov 30 15:08:08 2023] rtw_8822ce 0000:01:00.0: [16] UnxCmplt
[gio nov 30 15:08:08 2023] rtw_8822ce 0000:01:00.0: AER: TLP Header: 00000000 00000000 00000000 00000000
[gio nov 30 15:08:08 2023] rtw_8822ce 0000:01:00.0: AER: can't recover (no error_detected callback)
[gio nov 30 15:08:08 2023] pcieport 0000:00:1c.0: AER: device recovery failed
L’unica differenza rispetto a ieri è che ieri avevo provato con il router di casa (e il problema prima di ieri c’era anche così) mentre ora essendo in giro per lavoro sto usando l’hotspot dello smartphone…
E’ sempre un problema sulla gestione del bus PCI. Prova a vedere nell’ordine:
-
Bios se c’è una opzione per disabilitare ASPM
-
O il comando sopra non piglia entrambe le opzioni, quindi prova così:
$ sudo dd of=/etc/modprobe.d/rtl8822ce.conf << EOF
options rtw88_pci disable_msi=y
options rtw88_pci disable_aspm=y
options rtw88_core disable_lps_deep=y
EOF- se ancora da problemi ripristina il file di sopra con il primo comando che ti avevo fornito, questo. Quindi proviamo a disabilitare la gestione energetica del kernel:
$ sudo vim /etc/default/grubModifichi la voce GRUB_CMDLINE_LINUX aggiungendo in fondo pcie_aspm=off
Esempio, da così:
GRUB_CMDLINE_LINUX="bla bla bla"a così:
GRUB_CMDLINE_LINUX="bla bla bla pcie_aspm=off"Salva ed esci e ricrei il menu di grub:
$ sudo grub2-mkconfig -o /boot/grub2/grub.cfgRiavvia la macchina e vedi se permane il problema.
Eccomi, allora sul bios non c’è alcun ASPM. La modifica a rtl8822ce.conf non ha sortito effetto e quindi ho rimesso com’era, come da tua istruzione.
Così ho fatto il discorso del grub.
Niente ne non usciamo… però ora il log fornisce solo:
[root@hp-15sfq5017nl master]# dmesg -T | grep -i "Dic 1 13:0"
[ven dic 1 13:00:09 2023] wlo1: deauthenticating from 16:76:27:d4:14:94 by local choice (Reason: 3=DEAUTH_LEAVING)
[ven dic 1 13:00:31 2023] wlo1: authenticate with 16:76:27:d4:14:94
[ven dic 1 13:00:31 2023] wlo1: 80 MHz not supported, disabling VHT
[ven dic 1 13:00:31 2023] wlo1: send auth to 16:76:27:d4:14:94 (try 1/3)
[ven dic 1 13:00:31 2023] wlo1: authenticated
[ven dic 1 13:00:31 2023] wlo1: associate with 16:76:27:d4:14:94 (try 1/3)
[ven dic 1 13:00:31 2023] wlo1: RX AssocResp from 16:76:27:d4:14:94 (capab=0x411 status=0 aid=1)
[ven dic 1 13:00:31 2023] wlo1: associated
Ho notato che non appena cerco di usare l’ssh… puff! Non solo, ma anche quando navigo semplicemente… ma con l’ssh sembra più “sistematico”, ma magari è solo un’impressione.
Per scriverti questo post sto riconnettendo n volte!
Update dopo 10 minuti: si è stabilizzato per un po’, poi ho aperto il terminale e provato ssh e… puff di nuovo. Per dire…
Prova l’ultima soluzione fornendo l’opzione al kernel e vediamo!