質問: 約7分ごとにゲームが途切れる linuxマシンでゲームをプレイするときはいつでも、約5秒間、7分ごとに途切れます。深刻な問題ではないようですが、それでも少し迷惑です。そのため、そのバグの原因を追跡し、それを修正する方法についてのアイデアもあります。私のacer aspire 5552gにubuntu 12.10がインストールされています。 amd 2.20 ghzプロセッサー amd独自の最新ドライバーを搭載したradeon hd 5650。 4 gbのram de:gnome 3 アップデート: スタッターが発生している間、cpu使用率のグラフを調べたところ、1つのコア(デュアルコア)が100%になり、これが発生している間、もう1つのコアはそのままでした。それはcpu障害の兆候である可能性がありますか、それとも単に悪いosインストールである可能性がありますか? 実際にはxorgの問題のようです。スタッターが発生すると、xorgが私のcpu容量の約60%を占めるようです。 これからトラブルシューティングする方法に関するアイデアはありますか?今ログファイルを確認すると、これは私が持っているログのリストです。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 そして、これはsyslogの末尾-fです。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) リストを正しく表示する方法がわかりません。しかし、syslogからわかるように、ワインに関する行だけがあり、問題はありません。だから私はおそらく他のいくつかのログを調べる必要がありますが、どのログですか?.30分実行した更新されたログ: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) 吃音が発生したときのタイムスタンプは11.21 11.31 11.36 11.41および11.46です。そのログによると、それらの時間には何も起こりませんでした。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) このログを見ると、もう一度エラーが表示されたくないようです。 編集:いくつかのスクリーンショットを、スタッターが発生した瞬間のトップモニタリングにリンクします。多分それは少し役立ちます。 ご覧のように、スタッターが発生すると、xorgは1つのコアから大量の処理能力を消費します。今回はわずか12.6%でしたが、厄介なものは最大37%かかり、数秒間実際のロックダウンを引き起こします。また、これはxorgがエラーを引き起こしているのではないかと思います。xorgのログを見ないでください。しかし、監視対象は非常に多いため、どちらを監視する必要がありますか。また、xorg.3.logを監視しようとしたときに、エラーのタイムスタンプが表示されなかったため、そこから何かを読み取るのは難しいかもしれません。
回答: amdグラフィックスドライバーをインストールしていない場合は、ダウンロードできます こちら それが機能しない場合は、xorgをアンインストールして再インストールしてみてくださいsudo apt-get remove --purge xserver-xorg その後sudo apt-get install xserver-xorg