O Ubuntu 16.04 e a placa gráfica Nvidia (nvs 310) congelam aleatoriamente ao abrir programas

0

Estou executando o Ubuntu 16.04 LTS, o gnome-shell com o tema adaptt gtk e várias extensões gnome (com ferramenta tweak).

Estou tendo problemas ao iniciar programas (pode estar relacionado ao redimensionamento de janelas?). O Ubuntu congela aleatoriamente quando eu inicio cromo, folga, spotify ou atom (programas que eu uso muito). Às vezes consigo mover o mouse depois que ele congela e posso entrar na CLI usando as teclas ctrl + alt + f, mas não consigo fazer o X funcionar novamente sem reiniciar o computador.

Estou suspeitando que isso esteja relacionado aos drivers de configurações X / placas gráficas. Minha placa gráfica é uma Nvidia (NVS 310) em execução em um computador de mesa HP Z420. Estou usando drivers proprietários da nvidia (atualmente 384.111): Drivers adicionais

Algumas capturas de tela do gnome-tweak-tool para que você possa ver quais temas e extensões eu executo: Aparência
Extensões

Aqui estão algumas informações de depuração do syslog na última vez que o ubuntu congelou: Apr 3 14:57:24 dbus[1151]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Apr 3 14:57:26 kernel: [10590.565125] NVRM: GPU at PCI:0000:05:00: GPU-cfb2498e-11d0-8fbb-a8a5-b843a1ea6bbb Apr 3 14:57:26 kernel: [10590.565129] NVRM: Xid (PCI:0000:05:00): 13, Graphics Exception on GPC 0: 3D-Z SYSMEM KIND Violation. Coordinates: (0x0, 0x0) Apr 3 14:57:26 kernel: [10590.565135] NVRM: Xid (PCI:0000:05:00): 13, Graphics Exception: ESR 0x500420=0x80004000 0x500434=0x0 0x500438=0x20000 0x50043c=0x310000 Apr 3 14:57:26 kernel: [10590.565164] NVRM: Xid (PCI:0000:05:00): 13, Graphics Exception: ChID 0003, Class 00009297, Offset 00001b0c, Data 1000f010 Apr 3 14:57:26 kernel: [10590.635461] NVRM: Xid (PCI:0000:05:00): 31, Ch 0000000f, engmask 00000101, intr 10000000 Apr 3 14:57:26 kernel: [10590.660408] code[22010]: segfault at 4 ip 00007ff80e8fb027 sp 00007ffe2972a058 error 6 in libnvidia-glcore.so.384.111[7ff80d648000+149e000] Apr 3 14:57:28 kernel: [10592.016774] NVRM: Xid (PCI:0000:05:00): 13, Graphics Exception on GPC 0: 3D-Z KIND Violation. Coordinates: (0xdc0, 0x258) Apr 3 14:57:28 kernel: [10592.016781] NVRM: Xid (PCI:0000:05:00): 13, Graphics Exception: ESR 0x500420=0x80000080 0x500434=0x2580dc0 0x500438=0x20000 0x50043c=0x100fe Apr 3 14:57:28 kernel: [10592.016808] NVRM: Xid (PCI:0000:05:00): 13, Graphics Exception: ChID 0003, Class 00009297, Offset 00001b0c, Data 1000f010 Apr 3 14:58:31 kernel: [10655.446415] NVRM: Xid (PCI:0000:05:00): 31, Ch 00000004, engmask 00000101, intr 10000000

Depure de um congelamento que eu consegui recuperar depois de esperar algum tempo e mudar de tty (desta vez eu estava começando a folga): Apr 4 20:18:12 dbus[1111]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Apr 4 20:18:13 slack.desktop[28951]: Creating Slack Application Apr 4 20:18:13 org.gnome.zeitgeist.Engine[19129]: ** (zeitgeist-datahub:19627): WARNING **: downloads-directory-provider.vala:120: Couldn't process /home/user/Downloads/__dummy__: Error when getting information for file '/home/user/Downloads/__dummy__': No such file or directory Apr 4 20:18:22 kernel: [102248.177810] NVRM: GPU at PCI:0000:05:00: GPU-cfb2498e-11d0-8fbb-a8a5-b843a1ea6bbb Apr 4 20:18:22 kernel: [102248.177816] NVRM: Xid (PCI:0000:05:00): 31, Ch 00000003, engmask 00000101, intr 10000000 Apr 4 20:18:22 kernel: [102248.207066] NVRM: Xid (PCI:0000:05:00): 13, Graphics Exception on GPC 0: 3D-C SYSMEM KIND Violation. Coordinates: (0x0, 0x0) Apr 4 20:18:22 kernel: [102248.207072] NVRM: Xid (PCI:0000:05:00): 13, Graphics Exception: ESR 0x500420=0x80008000 0x500434=0x0 0x500438=0x2a00 0x50043c=0x310011 Apr 4 20:18:22 kernel: [102248.207102] NVRM: Xid (PCI:0000:05:00): 13, Graphics Exception: ChID 0009, Class 00009297, Offset 00001978, Data 00000000 Apr 4 20:18:22 kernel: [102248.243530] slack[28993]: segfault at 4 ip 00007f9e63051027 sp 00007ffee9276a78 error 6 in libnvidia-glcore.so.384.111[7f9e61d9e000+149e000] Apr 4 20:18:23 kernel: [102249.256946] NVRM: Xid (PCI:0000:05:00): 13, Graphics Exception on GPC 0: 3D-Z SYSMEM KIND Violation. Coordinates: (0x0, 0x0) Apr 4 20:18:23 kernel: [102249.256952] NVRM: Xid (PCI:0000:05:00): 13, Graphics Exception: ESR 0x500420=0x80004000 0x500434=0x0 0x500438=0x20000 0x50043c=0x3100fe Apr 4 20:18:23 kernel: [102249.256977] NVRM: Xid (PCI:0000:05:00): 13, Graphics Exception: ChID 0003, Class 00009297, Offset 00001b0c, Data 1000f010 Apr 4 20:18:59 gnome-session[19267]: [19869:19869:0404/201859.783295:ERROR:gles2_cmd_decoder.cc(5385)] GLES2DecoderImpl::ResizeOffscreenFramebuffer failed because offscreen FBO was incomplete. Apr 4 20:18:59 gnome-session[19267]: [19869:19869:0404/201859.784908:ERROR:gles2_cmd_decoder.cc(3708)] ContextResult::kFatalFailure: Could not allocate offscreen buffer storage. Apr 4 20:18:59 gnome-session[19267]: Window manager warning: last_user_time (102259129) is greater than comparison timestamp (102251425). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Apr 4 20:18:59 gnome-session[19267]: Window manager warning: 0x1c00005 (Slack - TR) appears to be one of the offending windows with a timestamp of 102259129. Working around... Apr 4 20:19:00 kernel: [102285.817780] slack[29203]: segfault at 4 ip 00007f4ff2794027 sp 00007ffd63f15b88 error 6 in libnvidia-glcore.so.384.111[7f4ff14e1000+149e000] Apr 4 20:19:02 acpid: client 18872[0:0] has disconnected Apr 4 20:19:02 kernel: [102288.506058] slack[29218]: segfault at 4 ip 00007f005234c027 sp 00007ffd2f99a0b8 error 6 in libnvidia-glcore.so.384.111[7f0051099000+149e000] Apr 4 20:19:02 acpid: client connected from 18872[0:0] Apr 4 20:19:02 acpid: 1 client rule loaded Apr 4 20:19:20 acpid: client 18872[0:0] has disconnected Apr 4 20:19:21 systemd[1]: Started Getty on tty3. Apr 4 20:19:24 acpid: client connected from 18872[0:0] Apr 4 20:19:24 acpid: 1 client rule loaded

Isso vem acontecendo há um tempo e é muito chato, já que às vezes tenho que reiniciar meu computador várias vezes por dia porque ele não está respondendo. É muito aleatório, pode de repente funcionar por dias sem congelar.

A partir das informações fornecidas e do syslog, alguma sugestão sobre o que posso fazer para tentar corrigir isso?

Obrigado!

    
por mario 03.04.2018 / 15:49

0 respostas