[SOLVED] Mint 18.2 and 18.3 64bit cinnamon lockups

Thane · 01-08-2018, 09:42 AM

Having major screen lockup problems. Had these lockups on Mint 18.2 cinnamon 64 bit and had no success in solving the issue. The motherboard then bricked (unrelated I am sure). I replaced the motherboard, cpu and memory in the computer. So they are all new, although the lockups are still happening with the new mobo, cpu and memory as well. New mobo is a Gigabyte Z270P-D3 and there is 16GB of ram to play with. I flashed the new motherboard’s intel mobo bios to the latest version the other day, after reading in another forum posting, that Intel bios updates would solve the problem. I have also checked all of my sda drives using Spinrite. Still getting frequent lockups.

I had previously read in a forum posting somewhere that the problem could have been due (whether right or wrong) in part to having the option of no login required on installation, I changed this so that I needed to log in to the OS on each startup. No change. Reinstalled 18.2 the other day and no change in the lockups I’m afraid, so yesterday I installed the 18.3 64bit cinnamon version using the “Something Else” partitioning option. New /home partition formatted and then needed files copied over from backup. The only additional programs I have installed on the system came through Synaptic, with the one exception of Google Chrome installed from google. Firefox is my main browser however and Thunderbird is my email program. Cat6 wired connection, only computer on the system. All available Mint updates have been installed.

When the system locks up, I do still have mouse control. Mouse clicks and (seemingly all) keyboard input are non-existent however. One other odd thing I have noticed for some time now, is that sometimes clicking on the open programs in the bottom bar will indeed bring them to the forefront, but they will be almost invisibly shadow-like on screen. Context buttons on those screens will be responsive to clicks though if I can see them. Also occasionally just moving the cursor over top of these bottom bar icons has the effect of bringing up that program, as if in a "preview" mode until the cursor is no longer over the icon. This was the case with the old hardware as well.

I did see one poster on a forum requesting

Code:

inxi

output from a user with problems. So I have included my output here in case it helps:

Code:

 ~ $ inxi
CPU~Dual core Intel Core i3-7100 (-HT-MCP-) speed/max~799/3900 MHz Kernel~4.10.0-42-generic x86_64 Up~45 min Mem~1026.2/15933.8MB HDD~8501.7GB(31.3% used) Procs~223 Client~Shell inxi~2.2.35

Firefox is usually running, when the lockups occur and also sometimes thunderbird and/or my todo list on libreoffice writer. Usually there has been nothing else running. On my 18.2 installation I was using oracle java 8, but I am still running the installed java version on the new installation of 18.3 so far.

hydrurga · 01-08-2018, 04:38 PM

Two things. First, can you upgrade the kernel to the latest version supported by Mint (currently 4.13.0-21) through the Update Manager and see if the problem persists.

Secondly, can you run Driver Manager from the Mint menu and tell us what it reports. What graphics card do you have? The output from inxi -G might be handy.

"Lockups" have been known to occur because of the system being slowed down appreciably by scripts on web pages. Have you ever experienced the problem when Firefox wasn't running?

Thane · 01-08-2018, 05:09 PM

Thanks for your reply. Kernel now updated to 4.13.0-21 as requested.

Code:

inxi -G

returns

Code:

~ $ inxi -G
Graphics:  Card: Intel Device 5912
           Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1920x1200@59.95hz
           GLX Renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
           GLX Version: 3.0 Mesa 17.2.4

And I've included a screenshot of the hardware drivers page. I will keep an eye on the situation, if the output included here doesn't point to anything else to try and will definitely report back on the state of the lockups. Many thanks. By the way I am using the mobo video and not a separate video card.

cbertram68 · 01-08-2018, 06:18 PM

Here is an article that does not address your problem directly, but could be a part of it, and hydurga is correct you need a newer kernel.

https://www.pcworld.com/article/3173...ernel-410.html

if you don't know how to update your kernel, post that here, and we can give you instructions.

Thane · 01-12-2018, 07:53 AM

Happy to say that after almost four days, your suggestions seem to have done the trick. The newly installed 4.13.0-21 kernel has also itself been updated to 4.13.0-26 at Update Manager's request. Also from the Linux Mint Blog page I have made sure all of the Meltdown and Spectre precautions have been satisfied. Yesterday there was also a new Intel Microcode update suggested by and installed through Update Manager. I have been trying to load up the Desktop with active programs and so far all seems well. Will mark this thread as solved and only report back again if the problem behaviour reoccurs. Many thanks friends.

hydrurga · 01-12-2018, 08:10 AM

Quote:

Originally Posted by Thane

Happy to say that after almost four days, your suggestions seem to have done the trick. The newly installed 4.13.0-21 kernel has also itself been updated to 4.13.0-26 at Update Manager's request. Also from the Linux Mint Blog page I have made sure all of the Meltdown and Spectre precautions have been satisfied. Yesterday there was also a new Intel Microcode update suggested by and installed through Update Manager. I have been trying to load up the Desktop with active programs and so far all seems well. Will mark this thread as solved and only report back again if the problem behaviour reoccurs. Many thanks friends.

Many thanks for letting us know, Thane. Will keep my fingers crossed.

Thane · 01-29-2018, 10:00 PM

Unfortunately the screen lockups are back with a vengeance and worse. Everything seemed to be working perfectly for two weeks, but now over the last few days, the screen lockup problem has returned and gotten even worse. The first instance was the usual "mouse will move but won't respond to clicks" behaviour as before. Then there was the interchangeable "moves but no click response" interspersed with "mouse completely unresponsive" behaviours. Every update suggested by Update Manager), including Firefox, Thunderbird, Google Chrome, and the others have been applied over the last two weeks.
Tonight I booted computer, came back 5 minutes later, logged in and mouse was completely frozen immediately, without even opening any programs. Not to lay the blame at Intel's feet, but I understand Intel was sure they had a microcode fix for the latest problems and put it out as an update, only to just recently realize the fix wasn't a fix at all and then they've recanted and advised rolling back to earlier microcode versions (as I've been led to believe). I don't know if this is the true case, but in the last number of days since my system seemed to have been fixed, Update Manager set to automatic updates, has suggested various microcode and other kernel updates. I have installed each and every one. So I'm not sure if some of the updates (from Intel/Mint?) are a part of the problem, or if there is now something new going on.

cbertram68 · 01-29-2018, 10:33 PM

I have not seen that behavior, but I have to admit my machines are on the latest release of the kernel. I am not suggesting this to you because there can be glitches in software when you are on the leading edge.

One other thing I am checking is that I have the MicroCode installed on my machines, I just did it on the machine I am typing this message on, so I will let it run for a bit and see if I have any issues.

One other thing I have seen issues with is suspend and hibernate. I usually turn these off even on my Windows machines, just had too many quirky issues when those are enabled, especially Hibernate.

I will report back if I notice anything, and you should try changing your power settings to at least not hibernate.

Thane · 01-30-2018, 08:07 AM

Thanks cbertram68. I always set all screensaver and power management settings to Never as well. My intel-microcode version is

Code:

3.20180108.0+really20170707ubuntu16.04.1

My system info is included as a .png file.

hydrurga · 01-30-2018, 09:39 AM

Can you think back to determine the exact date (perhaps after a reboot) that things started going wrong?

Also, paste the output from the last few lines (since perhaps a couple of days before the problem started) of the following file so that we can see what has been installed, and therefore may have caused the problem:

/var/log/apt/history.log

cbertram68 · 01-30-2018, 09:51 AM

I have only been running mine since last night, but I have the same version of the Microcode as well.

Let's see what you get from the log file hydrurga requested.

So far on my machine no issues.

Thane · 01-30-2018, 01:09 PM

Thanks hydrurga. I think the lockups started again around the 26th or 27th. Here is the /var/log/apt/history.log file excerpt beginning on the 25th:

Code:

Start-Date: 2018-01-25  19:14:56
Commandline: /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 79691809 -o Synaptic::closeZvt=true --set-selections-file /tmp/tmptxuump3_
Requested-By: x (1000)
Upgrade: libfwup0:amd64 (0.5-2ubuntu5, 0.5-2ubuntu7), fwupdate:amd64 (0.5-2ubuntu5, 0.5-2ubuntu7)
End-Date: 2018-01-25  19:15:02

Start-Date: 2018-01-26  09:13:14
Commandline: /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 77594653 -o Synaptic::closeZvt=true --set-selections-file /tmp/tmpo8l9zqxk
Requested-By: x (1000)
Install: linux-image-extra-4.13.0-32-generic:amd64 (4.13.0-32.35~16.04.1), linux-headers-4.13.0-32-generic:amd64 (4.13.0-32.35~16.04.1), linux-headers-4.13.0-32:amd64 (4.13.0-32.35~16.04.1), linux-image-4.13.0-32-generic:amd64 (4.13.0-32.35~16.04.1)
End-Date: 2018-01-26  09:14:35

Start-Date: 2018-01-29  13:56:37
Commandline: /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 75497540 -o Synaptic::closeZvt=true --set-selections-file /tmp/tmpls207xrk
Requested-By: x (1000)
Upgrade: libmpx0:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libgcc-5-dev:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), lib32stdc++6:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), cpp-5:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libitm1:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libcilkrts5:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libasan2:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libquadmath0:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), thunderbird-gnome-support:amd64 (1:52.5.0+build1-0ubuntu0.16.04.1, 1:52.6.0+build1-0ubuntu0.16.04.1), gcc-5-base:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), gcc-5-base:i386 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libstdc++-5-dev:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libtsan0:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libubsan0:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), g++-5:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libgfortran3:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), thunderbird-locale-en-us:amd64 (1:52.5.0+build1-0ubuntu0.16.04.1, 1:52.6.0+build1-0ubuntu0.16.04.1), gcc-5:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), liblsan0:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libgomp1:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), thunderbird:amd64 (1:52.5.0+build1-0ubuntu0.16.04.1, 1:52.6.0+build1-0ubuntu0.16.04.1), libatomic1:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libcc1-0:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libstdc++6:amd64 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libstdc++6:i386 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), thunderbird-locale-en:amd64 (1:52.5.0+build1-0ubuntu0.16.04.1, 1:52.6.0+build1-0ubuntu0.16.04.1)
End-Date: 2018-01-29  13:57:16

Thane · 01-30-2018, 01:11 PM

Code:

Start-Date: 2018-01-25  09:41:35
Commandline: /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 77594653 -o Synaptic::closeZvt=true --set-selections-file /tmp/tmpo_6ua571
Requested-By: x (1000)
Upgrade: firefox-locale-en:amd64 (57.0.4+linuxmint1+sylvia, 58.0+linuxmint2+sylvia), firefox:amd64 (57.0.4+linuxmint1+sylvia, 58.0+linuxmint2+sylvia)
End-Date: 2018-01-25  09:41:48

Start-Date: 2018-01-25  16:40:34
Commandline: /usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 79691809 -o Synaptic::closeZvt=true --set-selections-file /tmp/tmpg1shtk5i
Requested-By: x (1000)
Upgrade: libtasn1-6:amd64 (4.7-3ubuntu0.16.04.2, 4.7-3ubuntu0.16.04.3), libtasn1-6:i386 (4.7-3ubuntu0.16.04.2, 4.7-3ubuntu0.16.04.3)
End-Date: 2018-01-25  16:40:39

hydrurga · 01-30-2018, 01:44 PM

Thanks. That kernel update on the 26th looks the most likely culprit, if any.

Reboot your machine and, on the boot-up Grub menu, select Advanced Options (or similar) and choose to boot from the 4.13.0-31 kernel, if you have it installed. See if there is any difference with your system.

Note that any reboots after that will return the kernel to the 4.13.0-32 kernel unless you re-select Advanced Options.

Thane · 01-30-2018, 02:25 PM

I'm afraid the grub menu doesn't show up on reboots. I have tried holding down the shift key after Post and also rapidly tapping the shift key. Neither seems to have any effect.