crash - Ubuntu 16.10 overheating problem

i installed ubuntu 16.10 , since ubuntu reboots itself. output of: last | grep "oct 31" is:

aegefel  tty7         :0               mon oct 31 15:15    gone - no logout reboot   system boot  4.8.0-26-generic mon oct 31 15:14   still running aegefel  tty7         :0               mon oct 31 15:02 - down   (00:04) reboot   system boot  4.8.0-26-generic mon oct 31 15:02 - 15:06  (00:04) aegefel  tty7         :0               mon oct 31 14:33 - crash  (00:28) reboot   system boot  4.8.0-26-generic mon oct 31 14:33 - 15:06  (00:33) aegefel  tty7         :0               mon oct 31 14:12 - crash  (00:20) reboot   system boot  4.8.0-26-generic mon oct 31 14:12 - 15:06  (00:54) aegefel  tty7         :0               mon oct 31 13:08 - crash  (01:04) reboot   system boot  4.8.0-26-generic mon oct 31 13:08 - 15:06  (01:58)

which leads me believr it's caused crash

i don't know cause happened when tried see movie or when did backup

how should proceed?

edit 1

the command more /var/log/syslog* gives me:

nov  6 18:18:17 aegefel-akoya-e6424-md99850 gnome-terminal-[2674]: allocating size gtkbox 0x55558d2b47b0 without calling gtk_widget_get_preferred_width/height(). how code know size allocate? nov  6 18:18:17 aegefel-akoya-e6424-md99850 gnome-terminal-[2674]: allocating size gtkbox 0x55558d2b47b0 without calling gtk_widget_get_preferred_width/height(). how code know size allocate? nov  6 18:18:31 aegefel-akoya-e6424-md99850 gnome-terminal-[2674]: allocating size gtkbox 0x55558d2b4120 without calling gtk_widget_get_preferred_width/height(). how code know size allocate? nov  6 18:18:31 aegefel-akoya-e6424-md99850 gnome-terminal-[2674]: allocating size gtkbox 0x55558d2b4120 without calling gtk_widget_get_preferred_width/height(). how code know size allocate? nov  6 18:18:36 aegefel-akoya-e6424-md99850 systemd[1]: starting stop ureadahead data collection... nov  6 18:18:36 aegefel-akoya-e6424-md99850 systemd[1]: started stop ureadahead data collection.

then nothing happened during 1 minute, suppose pc rebooted.

the command ls -alt /var/crash gives me today:

total 21672 drwxrwsrwt  2 root     whoopsie     4096 nov  6 14:26 . -rwxrwxrwx  1 root     whoopsie        0 nov  6 14:26 .lock

edit 2

this append when cpu used @ 40% - 50% or more (my cpu intel core i5 6267u 2.9ghz)

edit 3

the command sensors gives me following:

coretemp-isa-0000 adapter: isa adapter physical id 0:  +37.0°c  (high = +100.0°c, crit = +100.0°c) core 0:         +34.0°c  (high = +100.0°c, crit = +100.0°c) core 1:         +36.0°c  (high = +100.0°c, crit = +100.0°c)  acpitz-virtual-0 adapter: virtual device temp1:        +38.0°c  (crit = +98.0°c)  pch_skylake-virtual-0 adapter: virtual device temp1:        +35.0°c

the high temperature equal critical. maybe laptop overheat , fan don't have time lower temperature. tried lower high temperature automatically lower critical (the critical must equal high)

edit 4

here have

and here crashes 20 november

edit 5

after test, think problem gpu overheating. in fact, laptop reboot when try watch movie, when tested free games on laptop or when used unreal engine 4. reason pc didn't reboot blender blender use, default, cpu (not gpu). have intel iris graphics 550 (skylake gt3e) idea ?

if concerned rebooting due kernel panics title of post suggests, can check file /etc/sysctl.conf directive similar kernel.panic = n n number indicates how many seconds delay before rebooting in of kernel panic. research indicates it's not supposed reboot default.

if instead, suspect more concerned determining root cause of these reboots (some hardware related failure opinion) you'll want review machine check events in order determine hardware malfunctioning. if don't have file /var/log/mcelog may need install the mcelog package enabling universe repository (if not enabled in sources) , issuing command sudo apt install mcelog moving forward these events logged /var/log/mcelog

for clarity here's excerpt man mcelog

x86  cpus  report  errors  detected  cpu machine check events        (mces).  these can data corruption detected in  cpu  caches,  in        main memory integrated memory controller, data transfer errors on        front side bus or cpu interconnect or other internal errors.   pos‐        sible  causes can cosmic radiation, instable power supplies, cooling        problems, broken hardware, or bad luck.         errors can corrected cpu  internal  error  correction        mechanisms. uncorrected errors cause machine check exceptions may        panic machine.

more information on mcelog file format can found here

linux systems don't typically reboot due kernel panic default may widh check file /etc/sysctl.conf mentioned previously.

sources:

http://www.techrepublic.com/blog/linux-and-open-source/auto-reboot-linux-after-a-kernel-panic/

http://packages.ubuntu.com

"mce: [hardware error]: machine check events logged" appears in syslog. should do?

http://mcelog.org/logfile.html

based on mcelog, cpu's 1 , 3 in system overheating. throttling down, cooling off , throttling (all design protect cpu overheating). root cause poorly applied thermal compound between cpu , heatsink, loose heatsink, blocked vents, or overly dusty or failing cooling equipment (fan?). (unlikely) possibility failure in thermal detection capabilities of cpu.

Search This Blog

Primitatvve