Jeux bégayant toutes les 7 minutes environ
Chaque fois que je joue à un jeu sur ma machine Linux, il bégaie toutes les 7 minutes environ pendant environ 5 secondes. Cela ne semble pas être un problème grave, mais c'est quand même un peu ennuyeux. Donc, toutes les idées sur la façon même de rechercher la cause de ce bogue, puis d'essayer de le résoudre également.
J'ai Ubuntu 12.10 installé sur mon Acer aspire 5552g qui a:
- Processeur AMD 2,20 GHz
- Radeon HD 5650 avec les derniers pilotes propriétaires AMD.
- 4 Go de RAM
- DE: Gnome 3
Mises à jour:
J'ai jeté un œil au tableau d'utilisation du processeur pendant que le bégaiement s'est produit et il a montré qu'un cœur (double cœur) est monté à 100% pendant que cela se produisait et que l'autre est resté tel qu'il était. Cela pourrait-il être le signe d'une défaillance du processeur ou pourrait-il simplement s'agir d'une mauvaise installation du système d'exploitation?
Il semble que ce soit un problème de Xorg. Lorsque le bégaiement se produit, Xorg semble occuper environ 60% de ma capacité CPU.
Une idée sur la façon de dépanner à partir d'ici?
Vérification des fichiers journaux maintenant et voici la liste des journaux que j'ai:
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
Et voici la queue -F de 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)
Je ne sais pas comment faire apparaître la liste correctement .. Mais comme je peux le voir dans syslog, il n'y a que des lignes sur le vin et pas mon problème. J'ai donc probablement besoin de regarder dans d'autres journaux, mais lesquels.
Journal mis à jour que j'ai exécuté pendant une demi-heure:
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)
Les horodatages lorsque le bégaiement s'est produit sont 11,21 11,31 11,36 11,41 et 11,46 Selon ce journal, rien ne s'est passé à ces moments-là.
Journaux 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)
En voyant ce journal, il semble qu'une fois de plus l'erreur ne veut pas apparaître.
Modifier: relier certaines captures d'écran avec une surveillance supérieure au moment où le bégaiement se produit. Peut-être que ça aide un peu. 
Comme on peut le voir, lorsque le bégaiement se produit, Xorg prend beaucoup de puissance de traitement d'un cœur. Cette fois, il n'était que de 12,6%, mais les plus méchants prennent jusqu'à 37%, ce qui provoque un véritable verrouillage pendant quelques secondes. Je me demande aussi si c'est Xorg qui fait l'erreur, ne devrais-je pas regarder les journaux Xorg? Mais lequel devrais-je surveiller car il y en a tellement. De plus, lorsque j'ai essayé de surveiller Xorg.3.log, il n'a montré aucun horodatage pour ses erreurs, donc il pourrait être difficile de lire des choses à partir de là, je suppose.
Si vous n'avez pas installé vos pilotes graphiques AMD, vous pouvez les télécharger ici
Si cela ne fonctionne pas, essayez de désinstaller et de réinstaller xorg à l'aide de
Sudo apt-get remove --purge xserver-xorg
ensuite
Sudo apt-get install xserver-xorg
Il peut s'agir simplement d'une erreur de jeu (ou d'un bug). Essayez de réinstaller le jeu ou réinstallez Ubuntu. Cela pourrait aider à obtenir plus RAM et une version 64 bits d'Ubuntu. De plus, les ordinateurs portables sont toujours plus lents que les PC # s.