Slackware 15 on Chromebox freezing occasionally and running out of memory
by garymaxwell from LinuxQuestions.org on (#6ETZD)
Hello...
I recently installed Slackware 15 on a converted Chromebox with updated firmware to coreboot (UEFI).
It's been 14 years since I looked at Slackware and it is at once timely yet timeless--a classic. I installed and found the installation the same after all these years!
Sadly, there are two big issues that I do not have an immediate answer for.
First, The desktop will freeze. I can move the mouse and the caps lock works but nothing on the desktop will work or function correctly. I have to do a hard reset. And even the hard reset would reboot the machine but fail to start X. It complained about not being able to find the server and to check server logs.
Secondly, I installed a Memory Usage widget on the desktop and the next time it froze, I noticed that memory usage consumed the whole 128GB of my hard drive! Needless to say, I had to reset again.
The reset usually fixes this but is there something I can do to fix this? Sounds like a memory leak of some sort to me.
Other distributions--notably, Arch and Debian--do not have these issues on the same machine.
Thanks for your help.
I recently installed Slackware 15 on a converted Chromebox with updated firmware to coreboot (UEFI).
It's been 14 years since I looked at Slackware and it is at once timely yet timeless--a classic. I installed and found the installation the same after all these years!
Sadly, there are two big issues that I do not have an immediate answer for.
First, The desktop will freeze. I can move the mouse and the caps lock works but nothing on the desktop will work or function correctly. I have to do a hard reset. And even the hard reset would reboot the machine but fail to start X. It complained about not being able to find the server and to check server logs.
Secondly, I installed a Memory Usage widget on the desktop and the next time it froze, I noticed that memory usage consumed the whole 128GB of my hard drive! Needless to say, I had to reset again.
The reset usually fixes this but is there something I can do to fix this? Sounds like a memory leak of some sort to me.
Other distributions--notably, Arch and Debian--do not have these issues on the same machine.
Thanks for your help.