Jogos gaguejando a cada 7 minutos

Question

Sempre que jogo um jogo na minha máquina Linux, ele gagueja a cada 7 minutos aproximadamente durante 5 segundos. Parece que não é um problema sério, mas ainda é um pouco chato. Então, qualquer idéia de como rastrear a causa desse bug e talvez tentar consertá-lo também.

Eu tenho o Ubuntu 12.10 instalado no meu Acer aspire 5552g que tem:

• Processador AMD 2.20 GHz
• Radeon HD 5650 com os mais recentes drivers proprietários da AMD.
• 4 GB de RAM
• DE: Gnomo 3

Atualizações:

1. Eu dei uma olhada no gráfico de uso da CPU enquanto a gagueira ocorria e mostrava que um núcleo (dual core) subia para 100% enquanto isso acontecia e o outro permanecia como estava. Pode ser um sinal de falha na CPU ou pode ser apenas uma instalação ruim do SO?

2. Parece ser um problema do Xorg na verdade. Quando a gagueira ocorre, o Xorg parece ocupar cerca de 60% da minha capacidade de CPU.

Alguma ideia sobre como solucionar problemas daqui em diante?

Verificando os arquivos de log agora e esta é a lista dos registros que eu tenho:

kaspar@kaspar-pc:/var/log$ ls
alternatives.log    btmp.1          jockey.log.2.gz     syslog.3.gz
alternatives.log.1  ConsoleKit      kern.log            syslog.4.gz
apport.log          cups            kern.log.1          syslog.5.gz
apport.log.1        dist-upgrade    kern.log.2.gz       syslog.6.gz
apport.log.2.gz     dmesg           kern.log.3.gz       syslog.7.gz
apport.log.3.gz     dmesg.0         kern.log.4.gz       udev
apport.log.4.gz     dmesg.1.gz      lastlog             ufw.log
apport.log.5.gz     dmesg.2.gz      lightdm             unattended-upgrades
apport.log.6.gz     dmesg.3.gz      mail.err            upstart
apport.log.7.gz     dmesg.4.gz      mail.log            wtmp
apt                 dpkg.log        news                wtmp.1
auth.log            dpkg.log.1      pm-powersave.log    Xorg.0.log
auth.log.1          faillog         pm-powersave.log.1  Xorg.0.log.old
auth.log.2.gz       fontconfig.log  pm-suspend.log      Xorg.1.log
auth.log.3.gz       fsck            pm-suspend.log.1    Xorg.1.log.old
auth.log.4.gz       gdm             samba               Xorg.2.log
boot                hp              speech-dispatcher   Xorg.2.log.old
boot.log            installer       syslog              Xorg.3.log
bootstrap.log       jockey.log      syslog.1            Xorg.failsafe.log
btmp                jockey.log.1    syslog.2.gz         Xorg.failsafe.log.old

E esta é a cauda -F do syslog:

kaspar@kaspar-pc:~$ tail -F /var/log/syslog
Feb 23 00:39:41 kaspar-pc kernel: [18312.601860] ptrace of pid 5563 was attempted by: wineserver (pid 4058)
Feb 23 00:39:41 kaspar-pc kernel: [18312.601915] ptrace of pid 8585 was attempted by: wineserver (pid 4058)
Feb 23 00:39:41 kaspar-pc kernel: [18312.608335] ptrace of pid 4064 was attempted by: wineserver (pid 4058)
Feb 23 00:39:41 kaspar-pc kernel: [18312.608402] ptrace of pid 4068 was attempted by: wineserver (pid 4058)
Feb 23 00:39:41 kaspar-pc kernel: [18312.608454] ptrace of pid 4076 was attempted by: wineserver (pid 4058)
Feb 23 00:40:44 kaspar-pc kernel: [18376.177046] yama_ptrace_access_check: 4 callbacks suppressed
Feb 23 00:40:44 kaspar-pc kernel: [18376.177051] ptrace of pid 4064 was attempted by: wineserver (pid 4058)
Feb 23 00:40:44 kaspar-pc kernel: [18376.177103] ptrace of pid 4068 was attempted by: wineserver (pid 4058)
Feb 23 00:40:44 kaspar-pc kernel: [18376.177154] ptrace of pid 4076 was attempted by: wineserver (pid 4058)
Feb 23 00:40:44 kaspar-pc kernel: [18376.177204] ptrace of pid 4085 was attempted by: wineserver (pid 4058)

Eu não tenho idéia de como fazer a lista aparecer corretamente .. Mas como eu posso ver a partir de syslog há apenas linhas sobre o vinho lá e não o meu problema. Então eu provavelmente preciso procurar em outros logs, mas quais.

Log atualizado que eu corri por meia hora:

kaspar@kaspar-pc:~$ tail -F /var/log/syslog
Feb 23 11:10:12 kaspar-pc kernel: [26160.563462] ptrace of pid 18061 was attempted by: wineserver (pid 18055)
Feb 23 11:10:12 kaspar-pc kernel: [26160.563502] ptrace of pid 18065 was attempted by: wineserver (pid 18055)
Feb 23 11:10:12 kaspar-pc kernel: [26160.563537] ptrace of pid 18074 was attempted by: wineserver (pid 18055)
Feb 23 11:10:12 kaspar-pc kernel: [26160.563572] ptrace of pid 18082 was attempted by: wineserver (pid 18055)
Feb 23 11:10:12 kaspar-pc kernel: [26160.568618] ptrace of pid 18061 was attempted by: wineserver (pid 18055)
Feb 23 11:10:12 kaspar-pc kernel: [26160.568661] ptrace of pid 18065 was attempted by: wineserver (pid 18055)
Feb 23 11:10:12 kaspar-pc kernel: [26160.568697] ptrace of pid 18074 was attempted by: wineserver (pid 18055)
Feb 23 11:10:12 kaspar-pc kernel: [26160.568733] ptrace of pid 18082 was attempted by: wineserver (pid 18055)
Feb 23 11:10:12 kaspar-pc kernel: [26161.074357] ptrace of pid 18061 was attempted by: wineserver (pid 18055)
Feb 23 11:10:12 kaspar-pc kernel: [26161.074413] ptrace of pid 18065 was attempted by: wineserver (pid 18055)
Feb 23 11:14:03 kaspar-pc kernel: [26391.217175] yama_ptrace_access_check: 23 callbacks suppressed
Feb 23 11:14:03 kaspar-pc kernel: [26391.217181] ptrace of pid 18061 was attempted by: wineserver (pid 18055)
Feb 23 11:14:03 kaspar-pc kernel: [26391.217218] ptrace of pid 18065 was attempted by: wineserver (pid 18055)
Feb 23 11:14:03 kaspar-pc kernel: [26391.217254] ptrace of pid 18074 was attempted by: wineserver (pid 18055)
Feb 23 11:14:03 kaspar-pc kernel: [26391.217292] ptrace of pid 18082 was attempted by: wineserver (pid 18055)
Feb 23 11:14:03 kaspar-pc kernel: [26391.217500] ptrace of pid 18109 was attempted by: wineserver (pid 18055)
Feb 23 11:14:03 kaspar-pc kernel: [26391.217536] ptrace of pid 18124 was attempted by: wineserver (pid 18055)
Feb 23 11:14:03 kaspar-pc kernel: [26391.217571] ptrace of pid 18429 was attempted by: wineserver (pid 18055)
Feb 23 11:14:04 kaspar-pc kernel: [26392.427695] ptrace of pid 18061 was attempted by: wineserver (pid 18055)
Feb 23 11:14:04 kaspar-pc kernel: [26392.427737] ptrace of pid 18065 was attempted by: wineserver (pid 18055)
Feb 23 11:14:04 kaspar-pc kernel: [26392.427775] ptrace of pid 18074 was attempted by: wineserver (pid 18055)
Feb 23 11:14:58 kaspar-pc cracklib: no dictionary update necessary.
tail: '/var/log/syslog' has become inaccessible: No such file or directory
tail: cannot watch '/var/log/syslog': Permission denied
tail: cannot watch '/var/log/syslog': Permission denied
tail: '/var/log/syslog' has appeared;  following end of new file
Feb 23 11:16:13 kaspar-pc anacron[12106]: Job 'cron.daily' terminated
Feb 23 11:16:13 kaspar-pc anacron[12106]: Normal exit (1 job run)
Feb 23 11:17:02 kaspar-pc CRON[18745]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 23 11:48:12 kaspar-pc kernel: [28437.994551] yama_ptrace_access_check: 5 callbacks suppressed
Feb 23 11:48:12 kaspar-pc kernel: [28437.994556] ptrace of pid 18061 was attempted by: wineserver (pid 18055)
Feb 23 11:48:12 kaspar-pc kernel: [28437.994594] ptrace of pid 18065 was attempted by: wineserver (pid 18055)
Feb 23 11:48:12 kaspar-pc kernel: [28437.994631] ptrace of pid 18074 was attempted by: wineserver (pid 18055)
Feb 23 11:48:12 kaspar-pc kernel: [28437.994667] ptrace of pid 18082 was attempted by: wineserver (pid 18055)
Feb 23 11:48:12 kaspar-pc kernel: [28437.994702] ptrace of pid 18109 was attempted by: wineserver (pid 18055)
Feb 23 11:48:12 kaspar-pc kernel: [28437.994738] ptrace of pid 18124 was attempted by: wineserver (pid 18055)
Feb 23 11:48:12 kaspar-pc kernel: [28437.994773] ptrace of pid 18429 was attempted by: wineserver (pid 18055)
Feb 23 11:48:12 kaspar-pc kernel: [28437.999638] ptrace of pid 18061 was attempted by: wineserver (pid 18055)
Feb 23 11:48:12 kaspar-pc kernel: [28437.999678] ptrace of pid 18065 was attempted by: wineserver (pid 18055)
Feb 23 11:48:12 kaspar-pc kernel: [28437.999714] ptrace of pid 18074 was attempted by: wineserver (pid 18055)
Feb 23 11:48:38 kaspar-pc kernel: [28463.842282] yama_ptrace_access_check: 4 callbacks suppressed
Feb 23 11:48:38 kaspar-pc kernel: [28463.842288] ptrace of pid 18061 was attempted by: wineserver (pid 18055)
Feb 23 11:48:38 kaspar-pc kernel: [28463.842339] ptrace of pid 18065 was attempted by: wineserver (pid 18055)
Feb 23 11:48:38 kaspar-pc kernel: [28463.842390] ptrace of pid 18074 was attempted by: wineserver (pid 18055)
Feb 23 11:48:38 kaspar-pc kernel: [28463.842441] ptrace of pid 18082 was attempted by: wineserver (pid 18055)

Os carimbos de data e hora em que ocorreu a gagueira são 11,21 11,31 11,36 11,41 e 11,46 De acordo com esse log, nada aconteceu nesses momentos.

Registros de kern.log

    kaspar@kaspar-pc:~$ tail -F /var/log/kern.log
    Feb 24 18:13:38 kaspar-pc kernel: [33595.438757] ptrace of pid 22763 was attempted by: wineserver (pid 22757)
    Feb 24 18:13:38 kaspar-pc kernel: [33595.438797] ptrace of pid 22767 was attempted by: wineserver (pid 22757)
    Feb 24 18:13:38 kaspar-pc kernel: [33595.438833] ptrace of pid 22775 was attempted by: wineserver (pid 22757)
    Feb 24 18:13:38 kaspar-pc kernel: [33595.438868] ptrace of pid 22784 was attempted by: wineserver (pid 22757)
    Feb 24 18:13:38 kaspar-pc kernel: [33595.440681] ptrace of pid 22763 was attempted by: wineserver (pid 22757)
    Feb 24 18:13:38 kaspar-pc kernel: [33595.440716] ptrace of pid 22767 was attempted by: wineserver (pid 22757)
    Feb 24 18:13:38 kaspar-pc kernel: [33595.440751] ptrace of pid 22775 was attempted by: wineserver (pid 22757)
    Feb 24 18:13:38 kaspar-pc kernel: [33595.440785] ptrace of pid 22784 was attempted by: wineserver (pid 22757)
    Feb 24 18:13:39 kaspar-pc kernel: [33596.007100] ptrace of pid 22763 was attempted by: wineserver (pid 22757)
    Feb 24 18:13:39 kaspar-pc kernel: [33596.007139] ptrace of pid 22767 was attempted by: wineserver (pid 22757)
    Feb 24 18:18:36 kaspar-pc kernel: [33893.269211] yama_ptrace_access_check: 23 callbacks suppressed
    Feb 24 18:18:36 kaspar-pc kernel: [33893.269216] ptrace of pid 22763 was attempted by: wineserver (pid 22757)
    Feb 24 18:18:36 kaspar-pc kernel: [33893.269257] ptrace of pid 22767 was attempted by: wineserver (pid 22757)
    Feb 24 18:18:36 kaspar-pc kernel: [33893.269296] ptrace of pid 22775 was attempted by: wineserver (pid 22757)
    Feb 24 18:18:36 kaspar-pc kernel: [33893.269335] ptrace of pid 22784 was attempted by: wineserver (pid 22757)
    Feb 24 18:18:36 kaspar-pc kernel: [33893.269374] ptrace of pid 22816 was attempted by: wineserver (pid 22757)
    Feb 24 18:18:36 kaspar-pc kernel: [33893.269413] ptrace of pid 22831 was attempted by: wineserver (pid 22757)
    Feb 24 18:18:36 kaspar-pc kernel: [33893.269452] ptrace of pid 23091 was attempted by: wineserver (pid 22757)
    Feb 24 18:18:37 kaspar-pc kernel: [33894.217138] ptrace of pid 22763 was attempted by: wineserver (pid 22757)
    Feb 24 18:18:37 kaspar-pc kernel: [33894.217192] ptrace of pid 22767 was attempted by: wineserver (pid 22757)
    Feb 24 18:18:37 kaspar-pc kernel: [33894.217243] ptrace of pid 22775 was attempted by: wineserver (pid 22757)
    Feb 24 18:57:59 kaspar-pc kernel: [36252.769962] yama_ptrace_access_check: 5 callbacks suppressed
    Feb 24 18:57:59 kaspar-pc kernel: [36252.769968] ptrace of pid 22763 was attempted by: wineserver (pid 22757)
    Feb 24 18:57:59 kaspar-pc kernel: [36252.770047] ptrace of pid 22767 was attempted by: wineserver (pid 22757)
    Feb 24 18:57:59 kaspar-pc kernel: [36252.770107] ptrace of pid 22775 was attempted by: wineserver (pid 22757)
    Feb 24 18:57:59 kaspar-pc kernel: [36252.770159] ptrace of pid 22784 was attempted by: wineserver (pid 22757)
    Feb 24 18:57:59 kaspar-pc kernel: [36252.770209] ptrace of pid 22816 was attempted by: wineserver (pid 22757)
    Feb 24 18:57:59 kaspar-pc kernel: [36252.770259] ptrace of pid 22831 was attempted by: wineserver (pid 22757)
    Feb 24 18:57:59 kaspar-pc kernel: [36252.770310] ptrace of pid 23091 was attempted by: wineserver (pid 22757)
    Feb 24 18:57:59 kaspar-pc kernel: [36252.778003] ptrace of pid 22763 was attempted by: wineserver (pid 22757)
    Feb 24 18:57:59 kaspar-pc kernel: [36252.778045] ptrace of pid 22767 was attempted by: wineserver (pid 22757)
    Feb 24 18:57:59 kaspar-pc kernel: [36252.778093] ptrace of pid 22775 was attempted by: wineserver (pid 22757)

Ver este log parece que mais uma vez o erro não quer aparecer.
Editar: Vinculando algumas capturas de tela com monitoramento superior no momento em que a gagueira ocorre. Talvez isso ajude um pouco.

Como pode ser visto, quando a gagueira ocorre, o Xorg está consumindo muito poder de processamento de um núcleo. Desta vez, foi apenas 12,6%, mas os mais desagradáveis ocupam até 37%, o que causa um bloqueio real por alguns segundos. Também gostaria de saber se este é o Xorg fazendo o erro, não deveria olhar para os logs do Xorg? Mas qual deles eu deveria estar monitorando, pois há muitos deles. Além disso, quando tentei monitorar o Xorg.3.log, ele não exibiu nenhum registro de data e hora para seus erros, então pode ser difícil ler coisas de lá, eu acho.

    

Answer 1

Se você não tiver os seus Drivers de gráficos AMD instalados, você pode baixá-los aqui

Se isso não funcionar, tente desinstalar e reinstalar o xorg usando

sudo apt-get remove --purge xserver-xorg

então

sudo apt-get install xserver-xorg

    

Answer 2

Pode ser apenas um erro do jogo (ou bug). Tente reinstalar o jogo ou reinstale o Ubuntu. Pode ajudar a obter mais RAM e uma versão de 64 bits do Ubuntu. Além disso, os laptops são sempre mais lentos que os PCs.