LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 07-20-2020, 02:38 PM   #1
varaonaid
Member
 
Registered: Mar 2007
Posts: 49

Rep: Reputation: 2
Question System locking up - canít figure it out, so discouraged


Hello,

Iíve been trying to get help for my 3-week-old OpenSUSE Tumbleweed install. I keep having issues with the system locking up and having to force a shutdown/reboot w/ the power button. I donít know whatís causing it. I thought it might be a KDE issue but Iíve installed other DEs as well and still have the problem.

Iíve tried to get the journalctl output for the timeframes when the lockup happens and I have to force the reboot. I just canít have this happening because itís a media server for us. Iíve included the journalctl output for a few different lockup events. Iím seeing a lot of problematic issues listed on journalctl but I donít know enough to be able to figure it out. If anyone could take a look and help, I would appreciate it so much. I donít know if itís an issue that happened with the initial install or something else. This problem has happened since I first installed (and before adding any extra DEs or other stuff). Iíve tried getting a tty session started but I have no control when this happens at all. Iíve also tried changing the compositor to no avail. Iíve really put in the work to look at journalctl & figure out how to see different outputs and save it. I hope thatís evident. Iíve not just posted with no effort behind it. This is days of working on it now.

Iím including several different journalctl outputs including boot, kernel, and the higher priority outputs (especially the latter seems to show things happening before the reboot). If you need anything more, please let me know and Iíll get it. I just donít know enough now to know what these errors mean or how to fix.

Journalctl Priority 1 (0 also included but had no output): https://pastebin.com/Le8E61pY
Journalctl Priority 2: https://pastebin.com/MSZmeubi
Journalctl Priority 3: https://pastebin.com/RZLaTyWr
Journalctl Priority 4: (if you need to see Priority 4, please let me know. It was too large for Pastebin but I could find another pastebin style option)
Journalctl Boot (-b): https://pastebin.com/uw2bT1j4
Journalctl Kernel (-k): https://pastebin.com/3eQb3Qsp

Thanks so much in advance! Hereís my hardware data:

Iím running the latest OpenSUSE Tumbleweed (and kept the packages up to date) using KDE. My hardware is:
Intel NUC 8i7BEH
Intel Core i7 8559u 4 core/8 thread processor
16gb RAM
Intel Iris 655 Graphics
m.2 NVMe SSD 512gb (this is a recent addition and where OpenSUSE is installed)
2.5Ē SATA SSD 256gb (this is what Iíve used for nearly two years and have had Mint installed on this SSD)
I also have various external HDDs - not that it would make a difference on this issue
8gb of the RAM is new. Intel specifically said that it didnít matter if the make/timings/speed, etc were the same on the memory that it should just match the RAM amount of the first stick for dual channel speeds. Having said that, I did match the RAM amount and speed of DDR4 2400.
Oddly, Mint hasnít shown any of these issues. I only say that because I would have thought that if it were a graphics/video cable or something hardware related, that both distros would be equally affected. The only things that are new that could be an issue are the recently added M.2 NVMe SSD and one of the 8GB RAM sticks. I also wondered if it might be an issue with KDE/Plasma itself. I donít want to run Mint, I want to run oST which is why Iím working to try to figure it all out.

If you need any more system info or specs or anything else, please let me know. Iím really discouraged by this that I canít seem to figure it out. Itís been a difficult time for other reasons, though, so Iím probably not as clear-headed as I might otherwise be. Any help would be amazing. Thanks so much.
 
Old 07-20-2020, 02:54 PM   #2
rtmistler
Moderator
 
Registered: Mar 2011
Location: USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu, Debian
Posts: 9,217
Blog Entries: 13

Rep: Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275
Any ability to load system consoles via CTRL-ATL-F2, F3, etc?

I've had lock-ups on other distributions, but I clearly did something bad via the DE and so I killed X and after that it reloaded the XServer and things worked again.
 
Old 07-20-2020, 03:58 PM   #3
varaonaid
Member
 
Registered: Mar 2007
Posts: 49

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by rtmistler View Post
Any ability to load system consoles via CTRL-ATL-F2, F3, etc?

I've had lock-ups on other distributions, but I clearly did something bad via the DE and so I killed X and after that it reloaded the XServer and things worked again.
Sorry, I tried to make this more clear but must not have. I cannot get any control of the system via CTRL-ATL-F2, F3, etc.

I did nothing (literally no changes at all) prior to this happening. Itís started within 24 hours of my clean install. I simply did a basic install - to be honest, I donít need to tinker with it (and donít really know enough to either!). This is why Iím so lost. Iíve really worked to try to figure out that issue with the journalctl output. Someone mentioned that I was crazy and a little daft for using Wayland - but I have no idea what it is, what it does, or how/why it got activated. Iíve done nothing for Wayland to be used and donít know how to undo using it either.

Thanks for your reply. I wish I could figure this out.
 
Old 07-20-2020, 06:17 PM   #4
jefro
Moderator
 
Registered: Mar 2008
Posts: 20,531

Rep: Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297
What leads you to believe you know what might be causing the issue? Any hard lockup may or may not leave some clues like one might find in /var.

24 hours doesn't seem a lot to prove it was good or not.

Guess you can try a different distro for a day or so even if it is on a usb flash drive.

Unless you tested the iso at the start we can't tell if the media was good.

Run memtest for a day or so might help.

Did this system ever work correctly on linux?

Does it have enough resources?

Put the command line program top up maybe to monitor if possible.

Last edited by jefro; 07-20-2020 at 06:18 PM.
 
Old 07-20-2020, 07:15 PM   #5
varaonaid
Member
 
Registered: Mar 2007
Posts: 49

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by jefro View Post
What leads you to believe you know what might be causing the issue? Any hard lockup may or may not leave some clues like one might find in /var.

24 hours doesn't seem a lot to prove it was good or not.

Guess you can try a different distro for a day or so even if it is on a usb flash drive.

Unless you tested the iso at the start we can't tell if the media was good.

Run memtest for a day or so might help.

Did this system ever work correctly on linux?

Does it have enough resources?

Put the command line program top up maybe to monitor if possible.
I have no idea whatsoever as to what is causing this issue - that’s my problem. Sorry if anything I said gave the impression that I do. Not knowing or being able to figure it out is what’s been so frustrating.

I’ve been using it for three weeks now (not 24 hours) and I’ve had it lock up, on average, once a day. The lockups started within 24 hours of my install (which was three weeks ago).

I don’t really want switch to another distro, if I don’t have to. I like OpenSUSE.

However, I did try three or four different distros via Live USB before installing OpenSUSE.

What’s the best way to test the iso to see if it is good? I may still have it and could test. Just the MD5 checksum?

I do have Mint installed on the same system but on a different SSD (my system support one M.2 NVMe and a standard 2.5” SATA SSD. The SATA SSD has been in use for nearly two years, the M.2 is new and is what I’ve installed OpenSUSE on. Unless there’s an issue that I can’t figure out with the M.2 SSD, it shouldn’t be an issue with my system.

I’ve run Top/htop and it doesn’t seem to be without resources. I added more RAM to be sure but it has 16gb RAM now, so that should be enough. It’s a 4 core/8 thread processor so I think has enough resources.

Please let me know if you need any more info. Thanks so much.

Last edited by varaonaid; 07-20-2020 at 07:17 PM.
 
Old 07-20-2020, 09:03 PM   #6
jefro
Moderator
 
Registered: Mar 2008
Posts: 20,531

Rep: Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297Reputation: 3297
One should always test a download. Usually it would be looking at the size and using a program to find a variable string. The two most common ways are MD5 and SHAL. Opensuse will provide the correct string to check.

You really can't compare a ssd to an M.2. Two different ways and many other things like bios/hardware compatibility issue.

Go go /var for some clues maybe.

Run memtest.

Maybe look at temperatures.
 
Old 07-20-2020, 10:09 PM   #7
rtmistler
Moderator
 
Registered: Mar 2011
Location: USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu, Debian
Posts: 9,217
Blog Entries: 13

Rep: Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275
Try another distro live boot. See if it works without crashing.

Perform some hardware checking. Seen lockups like this on systems with had MB or bad RAM.
 
Old 07-20-2020, 10:30 PM   #8
varaonaid
Member
 
Registered: Mar 2007
Posts: 49

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by rtmistler View Post
Try another distro live boot. See if it works without crashing.

Perform some hardware checking. Seen lockups like this on systems with had MB or bad RAM.
I have run three or four different live distros and didnít seem to encounter any of these lockups. Iím not really sure what this means.

I also ran the smart control tool on the M.2 SSD and came away with 0 errors. In addition, the temps were only between 30-38 deg C across multiple temp sensors, which seems well below what it needs to be.
 
Old 07-21-2020, 06:48 AM   #9
Mike_Walsh
Member
 
Registered: Jul 2017
Location: King's Lynn, UK
Distribution: Nowt but Puppies....
Posts: 514

Rep: Reputation: 280Reputation: 280Reputation: 280
Quote:
Originally Posted by varaonaid View Post
I have run three or four different live distros and didn’t seem to encounter any of these lockups. I’m not really sure what this means.
From the sound of things, your OpenSuse download was a " bad" one. It does happen, and can be affected by no end of things that are outside the average user's sphere of control.....because they occur at 'cloud-level', not at home.

As for the temps.....they're absolutely fine. The cooler any computer runs, the better. I used to have something of an anomaly; conventional "wisdom" always dictated that AMD processors ran hotter than Intel ones. My 16-yr old old Compaq tower, which died back in January, used a dual-core Athlon 64 X2, with a stock K8 air-cooler. No word of a lie, on winter mornings, even though this was in a centrally-heated house, I have seen that indicating a temperature in the high teens at boot - only 18į-19įC - for the first couple of minutes. Even after several hours, it would still only be running at high 20s/low 30s...

You've nowt to be concerned about.


Mike.

Last edited by Mike_Walsh; 07-21-2020 at 07:49 AM.
 
1 members found this post helpful.
Old 07-21-2020, 08:50 AM   #10
fatmac
Senior Member
 
Registered: Sep 2011
Location: Upper Hale, Surrey/Hants Border, UK
Posts: 4,018

Rep: Reputation: Disabled
Normally, a sudden lock up is caused by a power fail or faulty ram, but as you have run other distros without problems, it is down to your OpenSUSE distro, might be a faulty download, or maybe faulty software, also, has it been updated since first install(?)
 
1 members found this post helpful.
Old 07-21-2020, 09:27 AM   #11
rtmistler
Moderator
 
Registered: Mar 2011
Location: USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu, Debian
Posts: 9,217
Blog Entries: 13

Rep: Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275
I concur, something's wrong with that SUSE installation, or perhaps one of the drivers it uses really disagrees with your system.

Other distros run, so the hardware seems OK.

No where near an expert, but if the SUSE download turns out to be fine, then it may be a driver, and likely a video one which tend to be the most troublesome.

Can you share the specs on the system? Maybe you have a particular hardware configuration where one particular component does give various OS's trouble.
 
Old 07-21-2020, 09:29 AM   #12
rtmistler
Moderator
 
Registered: Mar 2011
Location: USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu, Debian
Posts: 9,217
Blog Entries: 13

Rep: Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275Reputation: 4275
Might be worth trying a different power supply, if this is a desktop (not laptop) system.

Also if it's old (or even new, but dirty/dusty), then clean it.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Is UUID in fstab and LILO discouraged? Soderlund Slackware 8 05-30-2014 08:40 PM
"Safely Remove Drive" highly discouraged -- disables device rknichols Linux - Hardware 17 05-26-2014 09:09 PM
LXer: Heartbleed postmortem-- OpenSSL's license discouraged scrutiny LXer Syndicated Linux News 0 05-02-2014 07:33 PM
Discouraged, But want to start new. Facing Severe Depression. mentalray01 Programming 11 05-31-2006 03:50 PM
first install; little discouraged e1000 Slackware 9 10-17-2003 08:24 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 06:28 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration