Frequenti crash della GUI

[Overkill74]

Ciao a tutti,
ho un problema che mi fa impazzire. Mi capitano frequentemente (più volte al giorno) crash della GUI, con riavvio della stessa e conseguente chiusura di ogni programma aperto.
Ubuntu 22.04 aggiornatissimo con driver nvidia-510. Ma il comportamento era lo stesso sulle precedenti 21.04 e 21.10 con diverse versioni dei driver nvidia e anche rimuovendolo completamente.
Ho pensato al driver video perchè è l'unico che mi da errori nei vari log, anche se indagando sono problemi minori legati ai DRM.
Ho provato svariate versioni di kernel ma nessuna ha avuto alcun effetto ne' migliorativo ne' peggiorativo.
Con il 5.15.xx ognittanto ci sono dei sfarfallamenti del monitor del notebook (non sul monitor esterno), tipo perdita di sincronia dei vecchi VGA.
Non so come indagare, dmesg, klog, syslog e /var/log/errors non mi hanno mai fornito indicazioni utili.
La macchina è un notebook HP con i7-6700K e nvidia GTX960M, 16GB RAM e SSD 1T dei quali circa 100GB liberi.
Come posso indagare per capire quale componente crea il problema?

Grazie

P.S.
Nessuno di questi sintomi appare avviando il sistema in Windows Ergo escludo problemi HW

[andrea111]

Prima di tutto controlla se sei su X11 o Wayland come server grafico.
Posta

Codice: Seleziona tutto

echo $XDG_SESSION_TYPE

[caturen]

Fai un memtest della tua ram
https://linuxhint.com/run_memtest_ubuntu/

[Overkill74]

Prima di tutto controlla se sei su X11 o Wayland come server grafico.
Posta

Codice: Seleziona tutto

echo $XDG_SESSION_TYPE

$echo $XDG_SESSION_TYPE
wayland

A memoria ho provato anche con X11

[Overkill74]

A memoria ho provato anche con X11

Mi è appena capitato, stavolta x11.
Questa volta avevo aperto Chrome e navigavo su Amazon, mentre copiavo un file i 100GB circa da un HDD esterno.

Forse ho una traccia, dal file /var/log/messages

May 27 00:42:31 odino gnome-shell[18531]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x5582b59b8370] is on because it needs an allocation.
May 27 00:42:31 odino gnome-shell[18531]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5582b8dc9ad0] is on because it needs an allocation.
May 27 00:42:31 odino gnome-shell[18531]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5582b740ff60] is on because it needs an allocation.
May 27 00:42:31 odino gnome-shell[18531]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x5582b59b8370] is on because it needs an allocation.
May 27 00:42:31 odino gnome-shell[18531]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5582b8dc9ad0] is on because it needs an allocation.
May 27 00:42:31 odino gnome-shell[18531]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5582b740ff60] is on because it needs an allocation.
May 27 00:42:31 odino kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
May 27 00:42:31 odino kernel: i915 0000:00:02.0: [drm] Xorg[18049] context reset due to GPU hang
May 27 00:42:31 odino kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in Xorg [18049]
May 27 00:42:31 odino gnome-shell[18531]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x5582b59b8370] is on because it needs an allocation.
May 27 00:42:31 odino gnome-shell[18531]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5582b8dc9ad0] is on because it needs an allocation.
May 27 00:42:31 odino gnome-shell[18531]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5582b740ff60] is on because it needs an allocation.
May 27 00:42:31 odino gnome-shell[18531]: Can't update stage views actor <unnamed>[<MetaWindowGroup>:0x5582b59b8370] is on because it needs an allocation.
May 27 00:42:31 odino gnome-shell[18531]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x5582b8dc9ad0] is on because it needs an allocation.
May 27 00:42:31 odino gnome-shell[18531]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x5582b740ff60] is on because it needs an allocation.
May 27 00:42:48 odino kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
May 27 00:42:48 odino kernel: i915 0000:00:02.0: [drm] Xorg[18049] context reset due to GPU hang
May 27 00:42:48 odino kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in Xorg [18049]
May 27 00:44:52 odino kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
May 27 00:44:52 odino kernel: i915 0000:00:02.0: [drm] Xorg[18049] context reset due to GPU hang
May 27 00:44:52 odino kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in Xorg [18049]
May 27 00:45:07 odino ibus-daemon[18711]: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes.
May 27 00:45:07 odino anydesk_global_tray.desktop[18783]: anydesk: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
May 27 00:45:07 odino anydesk_global_tray.desktop[18783]: anydesk: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
May 27 00:45:07 odino gnome-shell[21343]: Running GNOME Shell (using mutter 42.0) as a X11 window and compositing manager
May 27 00:45:09 odino gnome-session[18492]: gnome-session-binary[18492]: WARNING: Could not get session class: No such device or address
May 27 00:45:09 odino io.snapcraft.Settings[19590]: Exiting on terminated.
May 27 00:45:09 odino evolution-calen[18618]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18)
May 27 00:45:09 odino indicator-messa[18773]: invalid uninstantiatable type '(null)' in cast to 'ActUser'
May 27 00:45:09 odino indicator-messa[18773]: instance of invalid non-instantiatable type '(null)'
May 27 00:45:09 odino indicator-messa[18773]: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
May 27 00:45:09 odino indicator-messa[18773]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
May 27 00:45:13 odino at-spi-bus-laun[21553]: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “RegisterClient”
May 27 00:45:13 odino indicator-keybo[21582]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
May 27 00:45:13 odino indicator-sound[21593]: volume-control-pulse.vala:741: unable to get pulse unix socket: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 was not provided by any .service files
May 27 00:45:13 odino indicator-sound[21593]: media-player-list-greeter.vala:55: Unable to get active entry: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.UnityGreeter was not provided by any .service files
May 27 00:45:13 odino tracker-miner-f[21629]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location.
May 27 00:45:13 odino tracker-miner-f[21629]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location.
May 27 00:45:13 odino tracker-miner-f[21629]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location.
May 27 00:45:13 odino tracker-miner-f[21629]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location.
May 27 00:45:13 odino tracker-miner-f[21629]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location.
May 27 00:45:13 odino tracker-miner-f[21629]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location.
May 27 00:45:13 odino tracker-miner-f[21629]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location.
May 27 00:45:13 odino tracker-miner-f[21629]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location.
May 27 00:45:13 odino tracker-miner-f[21629]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location.

[andrea111]

Con la nvidia è meglio stare su X11.
Hai la doppia grafica? di solito le CPU intel hanno l'integrata.
Posta

Codice: Seleziona tutto

sudo lshw -c video
sudo lshw -c cpu
cat /etc/X11/default-display-manager

Mi capitano frequentemente (più volte al giorno) crash della GUI, con riavvio della stessa

ovvero ti ritrovi al login?

Posta anche

Codice: Seleziona tutto

dmesg | grep -i drm

quello che hai postato indica problemi allo Xorg per la intel:

May 27 00:44:52 odino kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in Xorg [18049]

è un crash dello Xorg.
La nvidia per ora pare non c'entri.

[Overkill74]

Si doppia grafica, INTEL + NVIDIA

$sudo lshw -c video
*-display
description: 3D controller
product: GM107M [GeForce GTX 960M]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a2
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list rom
configuration: driver=nvidia latency=0
resources: irq:144 memory:93000000-93ffffff memory:80000000-8fffffff memory:90000000-91ffffff ioport:4000(size=128) memory:94080000-940fffff
*-display
description: VGA compatible controller
product: HD Graphics 530
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
logical name: /dev/fb0
version: 06
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
configuration: depth=32 driver=i915 latency=0 resolution=1920,1080
resources: irq:142 memory:92000000-92ffffff memory:a0000000-afffffff ioport:5000(size=64) memory:c0000-dffff


$sudo lshw -c cpu
*-cpu
description: CPU
product: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: 6.94.3
serial: To Be Filled By O.E.M.
slot: U3E1
size: 3275MHz
capacity: 4005MHz
width: 64 bits
clock: 100MHz
capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust sgx bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d cpufreq
configuration: cores=4 enabledcores=4 microcode=234 threads=8

$sudo dmesg | grep -i drm
[ 1.456518] ata2.00: supports DRM functions and may not be fully accessible
[ 1.460224] ata2.00: supports DRM functions and may not be fully accessible
[ 2.400117] systemd[1]: Starting Load Kernel Module drm...
[ 2.417721] systemd[1]: modprobe@drm.service: Deactivated successfully.
[ 2.417981] systemd[1]: Finished Load Kernel Module drm.
[ 3.254052] i915 0000:00:02.0: [drm] VT-d active for gfx access
[ 3.307319] i915 0000:00:02.0: [drm] Disabling framebuffer compression (FBC) to prevent screen flicker with VT-d enabled
[ 3.308170] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27)
[ 3.315834] i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
[ 3.356918] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[ 3.471573] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[ 3.561069] fbcon: i915drmfb (fb0) is primary device
[ 3.594075] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[ 4.155551] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 1
[ 1208.968091] i915 0000:00:02.0: [drm] [ENCODER:94:DDI A/PHY A] is disabled/in DSI mode with an ungated DDI clock, gate it
[ 1208.968097] i915 0000:00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
[ 1209.304344] ata2.00: supports DRM functions and may not be fully accessible
[ 1209.308826] ata2.00: supports DRM functions and may not be fully accessible
[ 1222.345116] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[ 1275.946281] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=4010 end=4011) time 429 us, min 1073, max 1079, scanline start 1068, end 1098
[ 1341.511265] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[ 1341.513504] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[ 2281.954381] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[ 8648.833944] i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[10060.256684] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[10085.407875] i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[10275.342016] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[10275.342029] i915 0000:00:02.0: [drm] Xorg[18049] context reset due to GPU hang
[10275.352222] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in Xorg [18049]
[10291.697785] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[10291.697794] i915 0000:00:02.0: [drm] Xorg[18049] context reset due to GPU hang
[10291.706283] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in Xorg [18049]
[10416.428188] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[10416.428197] i915 0000:00:02.0: [drm] Xorg[18049] context reset due to GPU hang
[10416.442327] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in Xorg [18049]
[10443.304441] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[10455.754957] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[10455.754968] i915 0000:00:02.0: [drm] Xorg[21406] context reset due to GPU hang
[10455.761919] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in Xorg [21406]
[10783.032549] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[10783.032561] i915 0000:00:02.0: [drm] Xorg[21406] context reset due to GPU hang
[10783.041232] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in Xorg [21406]
[10809.645868] i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[11396.771106] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[11396.771118] i915 0000:00:02.0: [drm] Xorg[21406] context reset due to GPU hang
[11396.784108] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in Xorg [21406]
[11408.859552] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[11507.062091] i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[11804.632911] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[11804.632921] i915 0000:00:02.0: [drm] Xorg[24380] context reset due to GPU hang
[11804.640865] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in Xorg [24380]
[12035.539813] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[12035.539824] i915 0000:00:02.0: [drm] Xorg[24380] context reset due to GPU hang
[12035.553585] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in Xorg [24380]

il DRM fa un po' di casino.

Comunque ho una traccia, sempre da /var/log/mssages

May 27 01:01:28 odino gnome-shell[24851]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
_loadFile@resource:///org/gnome/shell/ui/background.js:488:20
_load@resource:///org/gnome/shell/ui/background.js:518:14
_init@resource:///org/gnome/shell/ui/background.js:278:14
Background@resource:///org/gnome/shell/ui/background.js:234:4
getBackground@resource:///org/gnome/shell/ui/background.js:622:30
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:793:49
BackgroundManager@resource:///org/gnome/shell/ui/background.js:719:37
_createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:461:27
_updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:507:34
_monitorsChanged@resource:///org/gnome/shell/ui/layout.js:571:14
_init@resource:///org/gnome/shell/ui/layout.js:313:14
LayoutManager@resource:///org/gnome/shell/ui/layout.js:194:4
_initializeUI@resource:///org/gnome/shell/ui/main.js:210:21
start@resource:///org/gnome/shell/ui/main.js:175:5
@resource:///org/gnome/shell/ui/init.js:6:17

May 27 01:01:28 odino gnome-shell[24851]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:
_loadFile@resource:///org/gnome/shell/ui/background.js:488:20
_load@resource:///org/gnome/shell/ui/background.js:518:14
_init@resource:///org/gnome/shell/ui/background.js:278:14
Background@resource:///org/gnome/shell/ui/background.js:234:4
getBackground@resource:///org/gnome/shell/ui/background.js:622:30
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:793:49
BackgroundManager@resource:///org/gnome/shell/ui/background.js:719:37
_createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:461:27
_updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:507:34
_monitorsChanged@resource:///org/gnome/shell/ui/layout.js:571:14


E qui ne parlano https://bugs.launchpad.net/ubuntu/+sour ... ug/1965820

Potrebbe essere lo stesso fenomeno?

[andrea111]

Per ora smetto, ti dirò domani.

Per postare: copi quello che vuoi postare, premi l'icona col simbolo "</>" che vedi sopra la finestra in cui scrivi, appariranno due delimitatori (code)(/code), in mezzo ai due ci incolli quello che devi postare. Così lo svolgimento della discussione non occupa troppo spazio.

Intanto prova una cosa: dal pannello di controllo nvidia, imposta la nvidia come scheda grafica da usare (mi pare che sia "max performance".
Vedi se il problema persiste.

[Overkill74]

Per postare: copi quello che vuoi postare, premi l'icona col simbolo "</>" che vedi sopra la finestra in cui scrivi, appariranno due delimitatori (code)(/code), in mezzo ai due ci incolli quello che devi postare. Così lo svolgimento della discussione non occupa troppo spazio.

Ooops non lo sapevo, grazie per la "dritta"

Provo anche ad impostare la nvidia come principale, speriamo bene

[andrea111]

Se intendi questo del /log/messages

May 27 01:01:28 odino gnome-shell[24851]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:

si tratta di "warning" spuri, cose marginali.

Direi di concentrare l'attenzione sulla intel (drm= direct rendering manager).

Dimmi della nvidia impostata come grafica primaria predefinita (dal pannello di controllo nvidia o, al limite, da bios disabilitando la intel oppure facendolo dal grub)

[Janvitus]

Prova a usare il driver libero nouveau e vedi che succede.