[SOLVED] Sparky Linux (Debian Testing) Locks Up, FF Locks Up, Have to perform Hard Shutdowns
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Nothing really stands out in it except for the amount of hardware running in the machine. Troubleshooting 101, you always strip the machine back to the fewest number of components possible needed to boot then start adding back as you confirm stability. In addition to the hardware you do the same with software run as few as possible programs leaving out things like that virtualbox you have loading. Oh and if overclocking that 4770k drop back to stock settings until confirmed stress tested settings are found.
Nothing really stands out in it except for the amount of hardware running in the machine. Troubleshooting 101, you always strip the machine back to the fewest number of components possible needed to boot then start adding back as you confirm stability. In addition to the hardware you do the same with software run as few as possible programs leaving out things like that virtualbox you have loading. Oh and if overclocking that 4770k drop back to stock settings until confirmed stress tested settings are found.
Thanks for looking at the log.
I'll have to look into stopping VBox from loading.
Like HappyTux, I didn't see anything that really stood out except for this item...
Code:
[ 0.000000] WARNING: CPU: 0 PID: 0 at /build/linux-8fxPc5/linux-4.9.6/drivers/iommu/dmar.c:844 warn_invalid_dmar.part.8+0x71/0x80
[ 0.000000] Your BIOS is broken; DMAR reported at address 0!
BIOS vendor: American Megatrends Inc.; Ver: V1.2; Product Version: 1.0
I found an explanation for this here and here. However, this does not necessarily mean something is wrong with your system or that it's the reason why it's locking up. I mentioned this primarily as FYI.
In addition to HappyTux's advice, I would run a memory diagnostic using Memtest86+. Let it run a quite a number of passes, not just one and post back with the results. Also, see if Sparky has a S.M.A.R.T. monitoring program, such as GNOME Disks and see if there are any issues with your hard drive.
Could you give us more details concerning the issue? Did it start happening right after you installed Sparky or did the OS run fine for a while? Did this occur right after you installed or uninstalled a piece of software or hardware?
The os ran fine for a while after a fresh installation. The DE is KDE.
It started locking up a few months afterwards and the only programs I installed was Virtual Box, Sophos and Xiphos. I didn't install those programs all at once.
As I recall I installed Xiphos first and than a few weeks later I installed Sophos. Than Virtual Box a few months ago.
I can be in the middle of watching a video on You Tube and all of the sudden everything locks up.
I found S.M.A.R.T.: and I already have Memtest on a Live CD. I'll run it over the next 2 days to make sure the RAM isn't bad. http://smartlinux.sourceforge.net/
I'm not sure if this will help or not, but I was experiencing something similar when using Google Chrome on KDE (openSuSE), and since it happened mostly when minimizing/maximizing Chrome to a shortcut on the taskbar, I removed the shortcut and upgraded Chrome, and it stopped happening. Not sure exactly what was happening and what solved it, but that's how it got fixed.
Last edited by Hungry ghost; 06-22-2017 at 08:41 PM.
If you would, try running another distribution live on the system for a while and see if it locks up. It might help us determine better if this is a hardware or software issue. Please post the results from Memtest and S.M.A.R.T. when you're able. Thanks!
The system locked up the other day so I thought an upgrade would be a great idea.
Since the upgrade the system hasn't locked up.
All of the libraries/engines that are associated with Libre Office were broken pkg's after the upgrade. So...... I removed Libre Office in Synaptic and reinstalled the newer Libre Office.
Something else went wrong with the upgrade but I managed to find a fix for it.
During the upgrade the terminal kept returning:
Code:
Gtk-WARNING: Unable to locate theme engine in module_path "murrine"
Sent PM on this. Right now any part could be at fault. Hardware, software or firmware.
Saying it used to work is OK only if you re-create the original install and it then works correctly. Any change from that doesn't rule out hardware and software. It only proves that it could work.
As suggested, Memtest is safe and can run overnight.
I have some systems at work that overheat from faulty fans and lock up. You have to be at the system fast to be sure you see the fan not working in some cases.
Sent PM on this. Right now any part could be at fault. Hardware, software or firmware.
Saying it used to work is OK only if you re-create the original install and it then works correctly. Any change from that doesn't rule out hardware and software. It only proves that it could work.
As suggested, Memtest is safe and can run overnight.
I have some systems at work that overheat from faulty fans and lock up. You have to be at the system fast to be sure you see the fan not working in some cases.
Thank You Jefro:-
The RAM wasn't bad and the HDD checked out:-
APTUS (an update mgr wasn't working properly) And the dist-upgrade broke things (Libre Office) and wasn't successful.
***Performed a fresh installation of Open Suse (Gecko Linux) and all is well.***
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.