gelegentliche Abstürze des Gnome-Desktops, [2175]: cr_parser_new_from_buf: Assertion 'a_buf && a_len' fehlgeschlagen, 20.04.3 LTS

Question

Ich betreibe einen Digital Storm-Server mit einer Nvidia GeForce RTX 3080 und der Desktop stürzt gelegentlich ab oder friert ein. Wir haben alle passenden Updates und Upgrades für 20.04.3 LTS, GNOME Shell 3.36.9 mit 5.11.0-34-generic-Kernel ausgeführt.

In den Protokollen wird Folgendes angezeigt:

Sep 28 13:45:43  gnome-shell[2175]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Sep 28 13:45:43  gnome-shell[2175]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Sep 28 13:45:43  gnome-shell[2175]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Sep 28 13:45:43  gnome-shell[2175]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Sep 28 13:45:43  gnome-shell[2175]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Sep 28 13:45:43  gnome-shell[2175]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Sep 28 13:45:43  gnome-shell[2175]: g_dbus_connection_emit_signal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Sep 28 13:45:43  gnome-shell[2175]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Sep 28 13:45:43  gnome-shell[2175]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Sep 28 13:46:53  /usr/lib/gdm3/gdm-x-session[2047]: (II) event20 - RH USB Gaming Mouse: SYN_DROPPED event - some input events have been lost.
Sep 28 13:46:53  rtkit-daemon[1231]: Supervising 5 threads of 3 processes of 2 users.
Sep 28 13:46:53  rtkit-daemon[1231]: Successfully made thread 18807 of process 1957 owned by '1001' RT at priority 5.
Sep 28 13:46:53  rtkit-daemon[1231]: Supervising 6 threads of 3 processes of 2 users.
Sep 28 13:47:00  dbus-daemon[1000]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.81' (uid=1001 pid=2175 comm="/usr/bin/gnome-shell " label="unconfined")
Sep 28 13:47:00  systemd[1]: Starting Fingerprint Authentication Daemon...
Sep 28 13:47:00  dbus-daemon[1000]: [system] Successfully activated service 'net.reactivated.Fprint'
Sep 28 13:47:00  systemd[1]: Started Fingerprint Authentication Daemon.
Sep 28 13:47:08  gnome-shell[2175]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Sep 28 13:47:08  gnome-shell[2175]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Sep 28 13:47:08  NetworkManager[1003]: <info>  [1632851228.7464] agent-manager: agent[de0546a1ee00c48c,:1.81/org.gnome.Shell.NetworkAgent/1001]: agent registered
Sep 28 13:47:08  dbus-daemon[1962]: [session uid=1001 pid=1962] Activating service name='org.freedesktop.FileManager1' requested by ':1.37' (uid=1001 pid=2175 comm="/usr/bin/gnome-shell " label="unconfined")
Sep 28 13:47:08  gnome-shell[2175]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Sep 28 13:47:08  gnome-shell[2175]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Sep 28 13:47:08  dbus-daemon[1962]: [session uid=1001 pid=1962] Activating service name='org.gnome.Nautilus' requested by ':1.37' (uid=1001 pid=2175 comm="/usr/bin/gnome-shell " label="unconfined")
Sep 28 13:47:08  gnome-shell[2175]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Sep 28 13:47:08  gnome-shell[2175]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Sep 28 13:47:08  dbus-daemon[1962]: [session uid=1001 pid=1962] Successfully activated service 'org.gnome.Nautilus'
Sep 28 13:47:08  org.gnome.Nautilus[18843]: Failed to register: Unable to acquire bus name 'org.gnome.Nautilus'
Sep 28 13:47:08  dbus-daemon[1962]: [session uid=1001 pid=1962] Successfully activated service 'org.freedesktop.FileManager1'
Sep 28 13:47:09  gnome-shell[2175]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Sep 28 13:47:09  gnome-shell[2175]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Sep 28 13:47:09  gnome-shell[2175]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Sep 28 13:47:09  gnome-shell[2175]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Sep 28 13:47:09  gnome-shell[2175]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Sep 28 13:47:09  gnome-shell[2175]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Sep 28 13:47:09  gnome-shell[2175]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Sep 28 13:47:09  gnome-shell[2175]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Sep 28 13:47:09  gnome-shell[2175]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Sep 28 13:47:09  gnome-shell[2175]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Sep 28 13:47:09  gnome-shell[2175]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).

Wahrscheinlich nicht damit verbunden. Ich sehe auch:

fwupd[19086]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a)

Das klingtähnlich mit denselben Fehlern, aber es ist 21.04. Und wir haben vor Kurzem den Ruhezustand deaktiviert, oder zumindest glauben wir das.

sudo systemctl status sleep.target suspend.target hibernate.target hybrid-sleep.target

● sleep.target
     Loaded: masked (Reason: Unit sleep.target is masked.)
     Active: inactive (dead)

● suspend.target - Suspend
     Loaded: loaded (/lib/systemd/system/suspend.target; static; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:systemd.special(7)

● hibernate.target
     Loaded: masked (Reason: Unit hibernate.target is masked.)
     Active: inactive (dead)

● hybrid-sleep.target
     Loaded: masked (Reason: Unit hybrid-sleep.target is masked.)
     Active: inactive (dead)

Answer 1

Es stellt sich heraus, dass diese Meldungen ein wenig irreführend sind. Obwohl es immer noch ein Problem mit GDM geben könnte, besteht das eigentliche Problem darin, dass mindestens eines der Speichermodule defekt ist und das das Einfrieren verursacht hat. Was das Ganze noch ärgerlicher machte, war, dass wir Memtest86 nicht zum Laufen bringen konnten, da auf diesem System ein funktionierender Speicherchip erforderlich ist, um überhaupt von einem USB/DVD zu booten!