x11 Mantém o console virtual de congelamento

Question

Eu tenho um problema no meu sistema Arch-Linux. Eu uso startx para iniciar minha GUI, e esse problema ocorre aleatoriamente durante todo o meu dia. Não há sinal de que algo esteja errado (até que eu mude para um Terminal / Console Virtual), e esse problema é persistente, independentemente do meu ambiente de área de trabalho.

Então, o problema é: Quando eu mudo para um VT do meu DE, a tela do meu VT parece congelada. Por "Congelado", quero dizer, ele mostra o texto que estava por último no VT antes dele (por falta de termo melhor) "Crashed". Tudo o que eu digito não é exibido, mas sei que todos os comandos que eu digito passam e são executados corretamente. Então, basicamente, o VT funciona bem e outras coisas, apenas essa tela fica congelada. Mesmo se eu mudar para um outro VT, ele exibe o mesmo texto "congelado".

Olhando para os logs ( journalctl -xe ) não mostra erros, nenhum aviso - nada de estranho em tudo. Isso não seria um problema se eu apenas iniciasse meu computador e usasse uma GUI, mas eu gasto muito tempo usando uma interface gráfica e o Terminal Virtual simultaneamente. Um padrão que eu notei é que ir em tela cheia em um aplicativo quase garante o VT para Congelar, mas novamente não há erros.

Então, a pergunta: Como faço para corrigir isso?

EDITAR:

Minha placa gráfica: Intel HD 5500 (Integrated Graphics)
Eu uso o pacote xf86-video-intel , para o DRI(2) Drivers
Usando light-dm ao invés de começar do VT não faz diferença, o erro ainda ocorreu em algum momento da minha sessão.

EDIT 2:

Agora, acho que isso pode ter sido causado por um GPU hang , mas não tenho 100% de certeza. Também notei que esse erro ocorre ao executar alguns programas ou jogos por meio de Wine .

EDIT 3:

Em exibição:

$ glxinfo | grep -i vendor

Saída:

server glx vendor string: SGI
client glx vendor string: Mesa Project and SGI
    Vendor: Intel Open Source Technology Center (0x8086)
OpenGL vendor string: Intel Open Source Technology Center

Meu driver de kernel é i915 :

$ lspci -nnk | grep -i vga -A3 | grep 'in use'
Kernel driver in use: i915

EDIT 4:

Saída de journctl -xe (do início do tempo relevante até o final do arquivo)

Apr 09 10:45:00 UNIX-ARCH-Ankush kernel: psmouse serio2: bad data from KBC - timeout
Apr 09 10:46:59 UNIX-ARCH-Ankush kernel: psmouse serio2: bad data from KBC - timeout
Apr 09 10:51:43 UNIX-ARCH-Ankush kernel: psmouse serio2: bad data from KBC - timeout
Apr 09 10:52:28 UNIX-ARCH-Ankush kernel: psmouse serio2: bad data from KBC - timeout
Apr 09 11:20:54 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: VBoxPciLinuxLinuxUnload
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: vboxdrv: Found 4 processor cores
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: vboxdrv: TSC mode is Invariant, tentative frequency 1995507786 Hz
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: vboxdrv: Successfully loaded version 5.0.16_OSE (interface 0x00240000)
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: VBoxNetAdp: Successfully started.
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: VBoxNetFlt: Successfully started.
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: VBoxPciLinuxInit
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: vboxpci: IOMMU not found (not registered)
Apr 09 11:22:40 UNIX-ARCH-Ankush kernel: capability: warning: 'VirtualBox' uses 32-bit capabilities (legacy support in use)
Apr 09 11:22:41 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:22:42 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:22:48 UNIX-ARCH-Ankush kernel: SUPR0GipMap: fGetGipCpu=0x3
Apr 09 11:22:49 UNIX-ARCH-Ankush kernel: vboxdrv: ffffffffa1008020 VMMR0.r0
Apr 09 11:22:50 UNIX-ARCH-Ankush kernel: vboxdrv: ffffffffa0258020 VBoxDDR0.r0
Apr 09 11:22:50 UNIX-ARCH-Ankush kernel: vboxdrv: ffffffffa002e020 VBoxDD2R0.r0
Apr 09 11:22:50 UNIX-ARCH-Ankush kernel: vboxdrv: ffffffffa0047020 VBoxEhciR0.r0
Apr 09 11:23:20 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:23:20 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:31:48 UNIX-ARCH-Ankush dbus[240]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Apr 09 11:31:48 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:31:48 UNIX-ARCH-Ankush dbus[240]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Apr 09 11:31:48 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:31:48 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:31:49 UNIX-ARCH-Ankush dbus[240]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Apr 09 11:31:49 UNIX-ARCH-Ankush dbus[240]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Apr 09 11:31:49 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:31:57 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:34:18 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:34:19 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:34:31 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:34:31 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).

Mesmo que Acima, mas não -xe ( journalctl )

Apr 09 11:20:54 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: VBoxPciLinuxLinuxUnload
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: vboxdrv: Found 4 processor cores
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: vboxdrv: TSC mode is Invariant, tentative frequency 1995507786 Hz
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: vboxdrv: Successfully loaded version 5.0.16_OSE (interface 0x00240000)
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: VBoxNetAdp: Successfully started.
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: VBoxNetFlt: Successfully started.
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: VBoxPciLinuxInit
Apr 09 11:22:35 UNIX-ARCH-Ankush kernel: vboxpci: IOMMU not found (not registered)
Apr 09 11:22:40 UNIX-ARCH-Ankush kernel: capability: warning: 'VirtualBox' uses 32-bit capabilities (legacy support in use)
Apr 09 11:22:41 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:22:42 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:22:48 UNIX-ARCH-Ankush kernel: SUPR0GipMap: fGetGipCpu=0x3
Apr 09 11:22:49 UNIX-ARCH-Ankush kernel: vboxdrv: ffffffffa1008020 VMMR0.r0
Apr 09 11:22:50 UNIX-ARCH-Ankush kernel: vboxdrv: ffffffffa0258020 VBoxDDR0.r0
Apr 09 11:22:50 UNIX-ARCH-Ankush kernel: vboxdrv: ffffffffa002e020 VBoxDD2R0.r0
Apr 09 11:22:50 UNIX-ARCH-Ankush kernel: vboxdrv: ffffffffa0047020 VBoxEhciR0.r0
Apr 09 11:23:20 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:23:20 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:31:48 UNIX-ARCH-Ankush dbus[240]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Apr 09 11:31:48 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:31:48 UNIX-ARCH-Ankush dbus[240]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Apr 09 11:31:48 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:31:48 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:31:49 UNIX-ARCH-Ankush dbus[240]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Apr 09 11:31:49 UNIX-ARCH-Ankush dbus[240]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Apr 09 11:31:49 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:31:57 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:34:18 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:34:19 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:34:31 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:34:31 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:39:47 UNIX-ARCH-Ankush dhcpcd[2126]: wlp7s0: carrier lost
Apr 09 11:39:47 UNIX-ARCH-Ankush dhcpcd[2126]: wlp7s0: deleting route to 192.168.1.0/24
Apr 09 11:39:47 UNIX-ARCH-Ankush dhcpcd[2126]: wlp7s0: deleting default route via 192.168.1.254
Apr 09 11:39:47 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:39:47 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:39:47 UNIX-ARCH-Ankush kernel: r8169 0000:08:00.0 enp8s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 09 11:55:25 UNIX-ARCH-Ankush kernel: psmouse serio2: bad data from KBC - timeout
Apr 09 11:57:07 UNIX-ARCH-Ankush dbus[240]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Apr 09 11:57:07 UNIX-ARCH-Ankush dbus[240]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Apr 09 11:57:46 UNIX-ARCH-Ankush dbus-daemon[585]: Activating service name='org.gnome.evince.Daemon'
Apr 09 11:57:46 UNIX-ARCH-Ankush dbus-daemon[585]: Successfully activated service 'org.gnome.evince.Daemon'
Apr 09 11:58:28 UNIX-ARCH-Ankush dbus[240]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Apr 09 11:58:28 UNIX-ARCH-Ankush dbus[240]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Apr 09 11:58:54 UNIX-ARCH-Ankush dbus[240]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Apr 09 11:58:54 UNIX-ARCH-Ankush dbus[240]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Apr 09 11:59:07 UNIX-ARCH-Ankush kernel: psmouse serio2: bad data from KBC - timeout
Apr 09 11:59:10 UNIX-ARCH-Ankush dbus[240]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Apr 09 11:59:10 UNIX-ARCH-Ankush dbus[240]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service not found.
Apr 09 12:03:05 UNIX-ARCH-Ankush dbus-daemon[585]: Activating service name='org.gnome.Terminal'
Apr 09 12:03:05 UNIX-ARCH-Ankush org.gnome.Terminal[585]: (gnome-terminal-server:7081): Gtk-WARNING **: Theme parsing error: gtk.css:700:22: 'text-decoration-line' is not a valid property name
Apr 09 12:03:05 UNIX-ARCH-Ankush dbus-daemon[585]: Successfully activated service 'org.gnome.Terminal'
Apr 09 12:07:41 UNIX-ARCH-Ankush dbus[240]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Apr 09 12:07:41 UNIX-ARCH-Ankush systemd[1]: Starting Hostname Service...
Apr 09 12:07:41 UNIX-ARCH-Ankush dbus[240]: [system] Successfully activated service 'org.freedesktop.hostname1'
Apr 09 12:07:41 UNIX-ARCH-Ankush systemd[1]: Started Hostname Service.
Apr 09 12:08:24 UNIX-ARCH-Ankush kernel: psmouse serio2: bad data from KBC - timeout
Apr 09 12:08:50 UNIX-ARCH-Ankush dbus-daemon[585]: Activating service name='org.gnome.gedit'
Apr 09 12:08:50 UNIX-ARCH-Ankush dbus-daemon[585]: Successfully activated service 'org.gnome.gedit'
Apr 09 12:08:50 UNIX-ARCH-Ankush org.gnome.gedit[585]: (gedit:7237): Gtk-WARNING **: Theme parsing error: gtk.css:700:22: 'text-decoration-line' is not a valid property name

    

Answer 1

Parece mesmo um problema de driver de vídeo.

Fontes
wiki.archlinux Intel_graphics
="https://wiki.archlinux.org/index.php/Xorg"> wiki.archlinux Xorg

X congelar / travar com o driver intel

Some issues with X crashing, GPU hanging, or problems with X freezing, can be fixed by disabling the GPU usage with the NoAccel option - add the following lines to your configuration file:

Option "NoAccel" "True"

Alternatively, try to disable the 3D acceleration only with the DRI option:

Option "DRI" "False"

If you experience crashes and have

Option "TearFree" "true"
Option "AccelMethod" "sna"

in your configuration file, in most cases these can be fixed by adding

i915.semaphores=1

to your boot parameters.

If you are using kernel 4.0.X or above on Baytrail architecture and frequently encounter complete system freezes (especially when watching video or using GFX intensivelly), you should try adding the following kernel option as a workaround, until this bug will be fixed permanently.

intel_idle.max_cstate=1

Se isso não resolver, tente solucionar o problema.

Solução de problemas com o driver de vídeo :
Para ver o driver atual que é usado:
lspci -nnk | grep -i vga -A3 | grep 'in use' (para informações completas remova o grep)

No meu caso: driver do kernel em uso: i915 .

Também é útil saber a saída:% glxinfo | grep -i vendor ( mesa-utils é necessário para glxinfo)

Todos os meus pacotes

Comando: pacman -Q | grep mesa

lib32-mesa 11.1.2-1
lib32-mesa-libgl 11.1.2-1

Comando: pacman -Q | grep video

videoproto 2.3.3-1
xf86-video-amdgpu 1.0.1-1
xf86-video-ark 0.7.5-7
xf86-video-ati 1:7.6.1-1
xf86-video-dummy 0.3.7-5
xf86-video-fbdev 0.4.4-5
xf86-video-glint 1.2.8-7
xf86-video-i128 1.3.6-7
xf86-video-intel 1:2.99.917+587+gc186d4d-1
xf86-video-mach64 6.9.5-2
xf86-video-neomagic 1.2.9-2
xf86-video-nouveau 1.0.12-1
xf86-video-nv 2.1.20-7
xf86-video-openchrome 0.3.3-6
xf86-video-r128 6.10.1-1
xf86-video-savage 2.3.8-2
xf86-video-siliconmotion 1.7.8-2
xf86-video-sis 0.10.8-2
xf86-video-tdfx 1.4.5-7
xf86-video-trident 1.3.7-2
xf86-video-vesa 2.3.4-2
xf86-video-vmware 13.1.0-3
xf86-video-voodoo 1.2.5-7

Intel_graphics

Install the xf86-video-intel package. It provides the DDX driver for 2D acceleration and it pulls in mesa as a dependency, providing the DRI driver for 3D acceleration.

To enable OpenGL support, also install mesa-libgl. If you are on x86_64 and need 32-bit support, also install lib32-mesa-libgl from the multilib repository.

Follow VA-API and VDPAU for hardware-accelerated video processing; on older GPUs, this is provided instead by the XvMC driver, which is included with the DDX driver.

For Vulkan support, install vulkan-intel on Ivy-Bridge or newer GPUs.

Para reinstalar o driver de vídeo baseado em intel:

sudo pacman -Syu
sudo pacman -S xf86-video-intel lib32-mesa lib32-mesa-libgl 

Lista completa de drivers:
$ pacman -Ss xf86-video

    

Answer 2

Eu tive o mesmo problema. E resolvi esse problema acidentalmente. A resposta é simples:

pacman -Syu