Freeze and reboot

fshsweden · Post by **fshsweden** » Tue Oct 24, 2017 5:19 am

Hello,

I am an experienced "user" of LInux, but never had do deal with any lower level issues, until now.

My desktop machine regularly freezes and after about 30 seconds it automatically reboots.

At first, I suspected a heating problem, but circumstances (and some naive temperature monitoring) makes me think thats not the case.

Then I suspected "Synergy", a keyboard/mouse sharing software that lets me control my linux box as well as a separate IMac.

The machine can freeze/reboot even when I am not at the desk.

I know I should look in /var/logs for "unusual" messages, but I haven't really got a clue what to look for? There is so munch there and I don't know what is normal and what is not.

What should I do/look for?

Thanks

------ edit ----

Code: Select all

inxi -Fxz
System:    Host: monster-mint Kernel: 4.8.0-36-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.3) Distro: Linux Mint 18.1 Serena
Machine:   System: ASUS product: All Series
           Mobo: ASUSTeK model: H87I-PLUS v: Rev X.0x Bios: American Megatrends v: 0702 date: 08/30/2013
CPU:       Quad core Intel Core i7-4770K (-HT-MCP-) cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 27999
           clock speeds: max: 4300 MHz 1: 1600 MHz 2: 2777 MHz 3: 1620 MHz 4: 1649 MHz 5: 1599 MHz
           6: 2732 MHz 7: 2033 MHz 8: 1600 MHz
Graphics:  Card: NVIDIA GK110 [GeForce GTX 780] bus-ID: 01:00.0
           Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
           Resolution: 2560x1440@59.95hz, 1920x1080@60.00hz
           GLX Renderer: GeForce GTX 780/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 378.13 Direct Rendering: Yes
Audio:     Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 NVIDIA GK110 HDMI Audio driver: snd_hda_intel bus-ID: 01:00.1
           Sound: Advanced Linux Sound Architecture v: k4.8.0-36-generic
Network:   Card: Intel Ethernet Connection I217-V driver: e1000e v: 3.2.6-k port: f040 bus-ID: 00:19.0
           IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 3256.7GB (13.8% used) ID-1: /dev/sda model: Samsung_SSD_840 size: 256.1GB
           ID-2: /dev/sdb model: WDC_WD20EZRX size: 2000.4GB
           ID-3: USB /dev/sdc model: MK1059GSM size: 1000.2GB
Partition: ID-1: / size: 111G used: 96G (91%) fs: ext4 dev: /dev/sdb5
           ID-2: swap-1 size: 17.11GB used: 0.00GB (0%) fs: swap dev: /dev/sdb6
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 39.0C mobo: 113.0C gpu: 0.0:38C
           Fan Speeds (in rpm): cpu: 0 fan-1: 1739 fan-2: 1228 fan-5: 0
Info:      Processes: 284 Uptime: 26 min Memory: 1803.0/15985.0MB Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35

catweazel · Post by **catweazel** » Tue Oct 24, 2017 5:31 am

It will assist people who can help you to know more about your machine. Please start a terminal and post the output of this command:

Code: Select all

inxi -Fxz

Enclose the results in code tags, which you can select from the mini toolbar above the textbox where you type your reply. Note that F in -Fxz is an upper case F.

As for logs, looking in /var/log/syslog around the time that the freeze occurs is a good start.

coffee412 · Post by **coffee412** » Tue Oct 24, 2017 5:31 am

Have you tested your hardware?
- Hard drive smart tests.
- Memory tests.

Note the time that the computer locked up and rebooted and go the the kern.log and see if there is anything weird looking around that time. If you see some warnings or errors then post them and it will give a better idea what to be looking for.

fshsweden · Post by **fshsweden** » Tue Oct 24, 2017 5:45 am

Here is a part from syslog from around the time of the last freeze and reboot (just before 11.06 local time i think)

Sorry but I have no clue what to look for.

Which is the *first* message in the syslog that indicates a restart btw?

syslog:

Code: Select all

Oct 24 09:45:01 monster-mint CRON[26332]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Oct 24 09:55:01 monster-mint CRON[27744]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Oct 24 10:05:01 monster-mint CRON[29170]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Oct 24 10:09:01 monster-mint CRON[29727]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
Oct 24 10:15:01 monster-mint CRON[31047]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Oct 24 10:17:01 monster-mint CRON[31295]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Oct 24 10:25:01 monster-mint CRON[32340]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Oct 24 10:35:01 monster-mint CRON[1171]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Oct 24 10:39:01 monster-mint CRON[1774]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
Oct 24 10:45:01 monster-mint CRON[2719]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Oct 24 10:55:01 monster-mint CRON[4197]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)

Oct 24 11:06:18 monster-mint systemd[1]: Mounted Huge Pages File System.
Oct 24 11:06:18 monster-mint systemd[1]: Mounted POSIX Message Queue File System.
Oct 24 11:06:18 monster-mint systemd[1]: Mounted Debug File System.
Oct 24 11:06:18 monster-mint systemd[1]: Started Create list of required static device nodes for the current kernel.
Oct 24 11:06:18 monster-mint systemd[1]: Starting Create Static Device Nodes in /dev...
Oct 24 11:06:18 monster-mint systemd[1]: Started LVM2 metadata daemon.
Oct 24 11:06:18 monster-mint systemd-modules-load[433]: Inserted module 'lp'
Oct 24 11:06:18 monster-mint systemd-modules-load[433]: Inserted module 'ppdev'
Oct 24 11:06:18 monster-mint rsyslogd-2039: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ]
Oct 24 11:06:18 monster-mint systemd-modules-load[433]: Inserted module 'parport_pc'
Oct 24 11:06:18 monster-mint systemd[1]: Mounted RPC Pipe File System.
Oct 24 11:06:18 monster-mint systemd-modules-load[433]: Inserted module 'coretemp'
Oct 24 11:06:18 monster-mint systemd-modules-load[433]: Inserted module 'nct6775'
Oct 24 11:06:18 monster-mint kernel: [    0.000000] microcode: microcode updated early to revision 0x22, date = 2017-01-27
Oct 24 11:06:18 monster-mint rsyslogd-2007: action 'action 10' suspended, next retry is Tue Oct 24 11:06:48 2017 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Oct 24 11:06:18 monster-mint kernel: [    0.000000] Linux version 4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu
 SMP Sun Feb 5 09:39:57 UTC 2017 (Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11)
Oct 24 11:06:18 monster-mint kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2ca2ab2f-caa0-409b-a723-4a142e1a570d ro quiet splash vt.handoff
=7
Oct 24 11:06:18 monster-mint systemd-modules-load[433]: Inserted module 'cuse'
Oct 24 11:06:18 monster-mint kernel: [    0.000000] KERNEL supported cpus:

kern.log

Code: Select all

Oct 23 13:03:08 monster-mint NetworkManager[1247]: <info>  [1508756588.5951] device (docker0): Activation: successful, device activated.
Oct 23 13:03:09 monster-mint kernel: [   54.423190] aufs au_opts_verify:1597:dockerd[2845]: dirperm1 breaks the protection by the permission bits on the lower branch
Oct 23 13:03:11 monster-mint kernel: [   56.611669] nvidia-modeset: Allocated GPU:0 (GPU-663f4db7-4c91-b351-ecc4-f261ef33ee97) @ PCI:0000:01:00.0
Oct 23 13:03:11 monster-mint kernel: [   56.779403] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 3
Oct 23 13:05:00 monster-mint kernel: [  166.196293] snd_hda_codec_hdmi hdaudioC1D0: HDMI: invalid ELD data byte 1
Oct 23 13:35:51 monster-mint kernel: [ 2016.531674] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
Oct 24 05:44:10 monster-mint kernel: [60121.862867] perf: interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
Oct 24 11:06:18 monster-mint kernel: [    0.000000] microcode: microcode updated early to revision 0x22, date = 2017-01-27
Oct 24 11:06:18 monster-mint kernel: [    0.000000] Linux version 4.8.0-36-generic (buildd@lgw01-18) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #36~16.04.1-Ubuntu
 SMP Sun Feb 5 09:39:57 UTC 2017 (Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11)
Oct 24 11:06:18 monster-mint kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=2ca2ab2f-caa0-409b-a723-4a142e1a570d ro quiet splash vt.handoff
=7
Oct 24 11:06:18 monster-mint kernel: [    0.000000] KERNEL supported cpus:
Oct 24 11:06:18 monster-mint kernel: [    0.000000]   Intel GenuineIntel
Oct 24 11:06:18 monster-mint kernel: [    0.000000]   AMD AuthenticAMD
Oct 24 11:06:18 monster-mint kernel: [    0.000000]   Centaur CentaurHauls
Oct 24 11:06:18 monster-mint kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Oct 24 11:06:18 monster-mint kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Oct 24 11:06:18 monster-mint kernel: [    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Oct 24 11:06:18 monster-mint kernel: [    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Oct 24 11:06:18 monster-mint kernel: [    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Oct 24 11:06:18 monster-mint kernel: [    0.000000] x86/fpu: Using 'eager' FPU context switches.
Oct 24 11:06:18 monster-mint kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 24 11:06:18 monster-mint kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Oct 24 11:06:18 monster-mint kernel: [    0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved

coffee412 · Post by **coffee412** » Tue Oct 24, 2017 6:15 am

Looks to be a hard lockup when the cron jobs are running. Doing a bit of DD points to a possible problem with swapping of your memory to drive swap file. This is where I would start with the issue.

How much memory do you have in this system? Also what is the size of your swap partition?

Can you post the output of this command:

Code: Select all

cat /proc/sys/vm/swappiness

On my system I have a swappiness of 60.

We can try and change the swappiness of the system temporarily until the next boot and see if it makes a difference. I would experiment a bit and see if the problem gets better or worse.

Here is a good resource for changing the swappyness of your system:

https://help.ubuntu.com/community/SwapF ... ange_it.3F

Let me know...

fshsweden · Post by **fshsweden** » Tue Oct 24, 2017 6:32 am

I have 16GB RAM, this is what free says

Code: Select all

monster-mint[~] >free
              total        used        free      shared  buff/cache   available
Mem:       16368672     2691552    11347060      103628     2330060    13116892
Swap:      16711676           0    16711676

Code: Select all

monster-mint[~] >cat /proc/sys/vm/swappiness
60

Usually I run RubyMine (an Ruby IDE by Jetbrains), and one or two rails servers, and a bunch of Chrome webpages.

Haven't thought of checking the swap so far, will monitor it going forward.

fshsweden · Post by **fshsweden** » Tue Oct 24, 2017 6:37 am

I was wondering about this line:

Code: Select all

inxi -Fxz
...
Sensors:   System Temperatures: cpu: 38.0C mobo: 113.0C gpu: 0.0:43C
           Fan Speeds (in rpm): cpu: 0 fan-1: 1744 fan-2: 1218 fan-5: 0

Motherboard 113 degrees Celsius? Can't be right??

catweazel · Post by **catweazel** » Tue Oct 24, 2017 6:41 am

It could be right. If the crashing is more random than predictable then it could be that the motherboard is on its way out.

fshsweden · Post by **fshsweden** » Tue Oct 24, 2017 6:51 am

It could also be a bad sensor. Cpu and Gpu temps are changing, but the mobo is fixed at 113C.

And the machine is only 3-4 years old, would be disappointing if it gave up already?

Pjotr · Post by **Pjotr** » Tue Oct 24, 2017 7:25 am

You might try a BIOS upgrade. Check the support section of your motherboard manufacturer.

Also a kernel upgrade is worth a try. Install the latest kernel of the 4.10 series (it should show up as a level 4 update anyway).

fshsweden · Post by **fshsweden** » Thu Nov 02, 2017 3:42 am

This problem is still bugging me. Worked fine for almost a week, then now I have 3-4 crashes in a couple of days.

I donit really want to replace parts just on a guess, isnt there any way I can identify the problem? Let's say its a faulty harddrive or a buggy graphics driver. Or can it be Cinnamon? Where are the logs that give the evidence?

I upgraded kernel to 4.11, but immediately got a message thet Cinnamon crashed, so I stepped back to 4.8.

Any help is appreciated.

coffee412 · Post by **coffee412** » Thu Nov 02, 2017 5:12 am

Have you tried:

1. Take the memory down to just one stick (if you have more than one in it) and run it to see if the problem is still there. Then switch the sticks out and see if it still happens.

2. Reduce the speed of the processor in the bios to see if that makes a difference.

FreedomTruth · Post by **FreedomTruth** » Thu Nov 02, 2017 1:11 pm

coffee412 wrote:Have you tested your hardware?
- Hard drive smart tests.
- Memory tests.

Just to rule things out, if nothing else. memtest should be on your grub menu when you reboot. I like the gui gsmartcontrol for vieweing/running smart tests.

fshsweden · Post by **fshsweden** » Thu Nov 02, 2017 6:25 pm

OK Now I have run memtest86+ for about 2 hours, the Extended self-test on the SSD and the Short self-test on the HD.
They all completed without errors.

After that I checked BIOS, and changed from "Performance"-profile, to "Normal". There are just too many options in the BIOS and the machine is fast enough. Don't know if this will make a difference but we'll see.

So no obvious hardware errors at least. What would you suggest I do next?
Thx

PS. And I continue with the 4.8 kernel. I dont have time to play with the 4.11 since Cinnemon crashes immediately on that one. DS

FreedomTruth · Post by **FreedomTruth** » Fri Nov 03, 2017 10:08 am

How long does it typically run before freeze/reboot?

What I'd try next (still thinking possibly hardware related. Sorry, I'm not past that yet), reboot, enter BIOS setup. In the "Advanced Mode" page, go to the "Monitor" tab. If any of the voltages are very far out (+/- 10% or more) the issue could be your power supply. In any case, maybe leave it at this screen (overnight?) and see if it ever does its reboot thing. That could at least help rule out a hardware issue.

If it's software related, maybe try a 4.10 kernel? Or even 4.4.

fshsweden · Post by **fshsweden** » Wed Nov 15, 2017 6:54 am

Thought I add some info. After changing BIOS profile from "performance" to "normal", I haven't experienced any problem for more than 10 days now.

So... I guess I'm happy I don't have any crashes, but unhappy that I couldn't really diagnose the problem properly.

Thanks for all help anyway!

Linux Mint Forums

Freeze and reboot

Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot

Re: Freeze and reboot