System becomes unresponsive after a couple of months of use

asked 2015-03-31 15:32:39 -0600

alfC gravatar image

updated 2015-04-14 02:38:10 -0600

This is the second time it happens, after a fresh installation the system works well for few months and then it starts become unresponsive. Basically the interactivity becomes delayed. The system seems to run smoothly, video and audio run but click, key presses and mouse drags are unresponsive for around 2 second. This happens randomly, several times per minute. (The mouse pointer doesn't freeze.)

Last time this happened in Fedora 20, few month after installation I changed my SSD drive (the only part of the hardware that is suspicious and that I change in practice). Now, it happens again with Fedora 21 and a different SSD drive.

Examples, 1) one drags a file in Files (the icon stays frozen) along the way 2) One is typing an email or in gedit, one presses keys and only after a few seconds all the characters appear 3) Alt-TAB seems to be the worst, sometimes it works, sometimes the window banner doesn't appear for a while. 4) Changing focus with the mouse can take 2 or 3 seconds. 5) Window dragging get frozen for couple of seconds.

The system is not particularly slow, it is just that interactivity is unresponsive.

Hardware: Dell Inspiron 17R Intel® Core™ i7-3612QM CPU @ 2.10GHz × 8 | 64-bit | Intel® Ivybridge Mobile | 7.7 GiB

EDIT 1:

top doesn't report high utilization of CPU. Rebooting doesn't help. Filesystems are not full:

Filesystem     1K-blocks      Used Available Use% Mounted on
devtmpfs         4006508         0   4006508   0% /dev
tmpfs            4016456        92   4016364   1% /dev/shm
tmpfs            4016456       988   4015468   1% /run
tmpfs            4016456         0   4016456   0% /sys/fs/cgroup
/dev/sdb1       61409300  15853836  42413016  28% /
tmpfs            4016456       612   4015844   1% /tmp
/dev/sda2      222807676 146173644  65293028  70% /home
tmpfs             803292        24    803268   1% /run/user/1000

EDIT 2:

I did the Dell hardware test and no problem was found.

EDIT 3: This is the typical output of sar -q 1 1000 (nothing strange)

12:34:37 AM   runq-sz  plist-sz   ldavg-1   ldavg-5  ldavg-15   blocked
12:34:38 AM         0       607      1.77      1.64      1.48         0
12:34:39 AM         1       607      1.77      1.64      1.48         0
12:34:40 AM         1       607      1.77      1.64      1.48         0
12:34:41 AM         0       607      1.71      1.63      1.48         0
12:34:42 AM         0       607      1.71      1.63      1.48         0
12:34:43 AM         1       606      1.71      1.63      1.48         0
12:34:44 AM         1       606      1.71      1.63      1.48         0
12:34:45 AM         1       606      1.71      1.63      1.48         0
12:34:46 AM         1       606      1.73      1.64      1.48         0
12:34:47 AM         1       606      1.73      1.64      1.48         0
12:34:48 AM         1       606      1.73      1.64      1.48         0
12:34:49 AM         3       606      1.73      1.64      1.48         0
12:34:50 AM         2       606      1.73      1.64      1 ...
(more)
edit retag flag offensive close merge delete

Comments

Similar question here: https://ask.fedoraproject.org/en/ques... . One user points to the presence of a Logitech Wireless mouse which I do have. I will stop using these mice (I have many Logitech Anywhere MX mice in different locators, all sharing the same usb connector, which is very handy).

alfC gravatar imagealfC ( 2015-03-31 17:27:52 -0600 )edit

It's not likely, but you may be running short of disk space and not realize it. Run the command df and let us know if any of your partitions are getting full.

sideburns gravatar imagesideburns ( 2015-03-31 18:45:03 -0600 )edit

@sideburns, I added the disk space info to the question.

alfC gravatar imagealfC ( 2015-03-31 19:06:54 -0600 )edit
1

Thanx! That eliminates the possibility of not enough disk space.

sideburns gravatar imagesideburns ( 2015-03-31 19:26:49 -0600 )edit
1

These sorts of symptoms can appear from a wide range of causes. Have you taken a general look at your systemd journal to see if you can find any faulting applications or other noteworthy issues? I'd start there, and if you really can't turn up anything of note, I might suggest that you make use of a general hardware diagnostics platform (such as a utility built into your BIOS or UEFI motherboard firmware, or maybe the Ultimate Boot CD, etc.) to rule out hardware issues. A faulty CPU or RAM module could cause this, for example. If no software problems are evident, I'd suspect hardware.

bitwiseoperator gravatar imagebitwiseoperator ( 2015-04-01 14:50:07 -0600 )edit