OK, I'm looking for possibilities to explain this.

Box locks up using X. Keyboard is totally dead, mouse does move but clicks have no effect. Only solution to date is power off. Feels like m$ windows :-(. Happens more in Slackware, particularly bad in Adobe Acrobat, so I stopped using it. Once/twice per day, once/twice per hour in Adobe Acrobat.
No other perceptable pattern to lockups, except they occur just as/after I've done something

I have a (2013) Samsung I3-3110, Panther Point chipset, 6G ram, only Intel HD4000 graphics, and 60G SSD partitioned
sda1 boot (Common to both systems)
sda2 swap (Common to both systems)
sda3 Slackware-14.0 /
sda4 extended partition holding
sda5 Fedora Electronic Spin /
sda6 home (Common to both systems)

Fedora kicked and squealed about this setup, and it was obligatory for the installer to fall over, but it's there now. It runs on the slackware-huge-3.2.29 kernel because I need to make an initrd (I think).

Things I have done
A few hours of memtest - no errors
regular disk checks - never fixes much, but complains about big discontiguous percentages.

Have you checked the logs for anything unusual at the time of the crash or other times. Logs are at '/var/log/syslog' and messages.

What is this about regular disk checks ? You mean SMART tests ? Just run a SMART long test and wait for the result, it plus the attributes will tell you if the disk is failing.

Thanks for the reply.

I ran a smart long test and it seemed happy enough. No fails in the errors. Should be - the disk is only a few months old.


The logs are showing no error. I had one of these lockups last evening, and the mouse was frozen as well. I may have been wrong about that earlier. The only thing is that it logs a remount of the discs after picking up a name from freedesktop. A classic way to get this is to start a mail in gmail, add an attachment, and while that's uploading, add another. Or use Adobe Reader.

I'm tempted to do an upgradepkg --reinstall on slackware, which presumes a disk error. Maybe I should upgrade the kernel off 3.2.29. I'm in a phase where I just want to USE things, and not mess with them. So my new poser phone arrived and I have to get stuck into that. My printer died or at least won't print on three boxes. I have to clean up the old phone to give it to someone. And the sun finally starts shining in Ireland, so my wife sees how much painting needs to get done :-/.

If there's nothing in the logs then it could be a hardware issue. If you can reinstall, do it and see if it still happens. I recommend running memtest86+ for at least one full cycle, the time it takes to run doesn't matter.

This article I wrote may help:
http://docs.slackware.com/howtos:har...re_diagnostics

Thanks H_TeXMeX_H:

I'll do the reinstall. I have what I really needed to know out of this thread - that there's nothing obvious I am missing. I have also uncommented smartd in the rc.d stuff so that will go. I'm thinking I must have set the disk check intervals too long initially, and Adobe Reader has screwed some stuff up.

Last night I "Upgraded" slackware-14.0/{a,ap,l,x,xap} with themselves. I missed xfce but I will do that after the next crash. Getting off kernel-3.2.29 for 3.8.8 as I write. Firefox got a downgrade but I fixed that with 20.0. I'll moan if probelms continue.

Epilogue:

From last post, it lasted an hour before locking up :-(. So did the rest of the backup, and updated firefox and kernel.

I then ran in Fedora working all day, and had no errors. It's definitely being thrown by the new gmail interface. A classic way of achieving a crash is to start an email, attach some big file and while it's uploading try to attach another.

Anyhow, as it's a slackware problem, I'll close this and take it up in the slackware forum if iot continues