[clug] Diagnosing display freeezes

[Hal Ashburner]

Andrew said:
"If however it happens based upon certain X events..."
How do I work this out? What constitutes an X event? Keystroke? Change
active window? Mouse move? The first two are how I know it's frozen so
I guess they could be the cause as well as the symptom.



Thanks for the suggestons, still not winning yet:

 [hal at davis 11:40 ~] sudo smartctl --health /dev/sda
smartctl 6.2 2013-07-26 r3841
[x86_64-linux-3.10.0-123.13.2.el7.x86_64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED


[hal at davis 11:40 ~] ll /var/log/Xorg.0.log
-rw-r--r-- 1 root root 113K Jan 29 10:00 /var/log/Xorg.0.log

[hal at davis 11:40 ~] ls ~/.[xX]*
zsh: no matches found: /home/hal/.[xX]*



On 29 January 2015 at 10:52, Andrew Janke <a.janke at gmail.com> wrote:
>> The symptoms you describe remind me of a problem I used to see ages ago on an OpenSUSE
>> system.  From memory the problem turned out to be the size of the Xorg.0.log file in /var/log.
>>
>> For some unknown reason the Xorg server was doing a full read of that log file from time
>> to time and you'd see a long pause during that read.
>
> Good call!  While at it also be sure to nuke:
>
>     ~/.xsession-errors
>
> It can grow to preponderous proportions if left to its own devices and
> something is awry.
>
>
> a
> --
> linux mailing list
> linux at lists.samba.org
> https://lists.samba.org/mailman/listinfo/linux