6

I'm running Ubuntu 20.04 (used to run Ubuntu 19.10) on some an HP laptop[RAM-4 GB, Intel Core i3-4005U CPU @ 1.70GHz x 4, 1TB HDD, AMD Hainan/Intel HD Graphics 440 (HSW GT2)]. I have turned off all the automatic shut-down or suspend option, but it's still shutting down suddenly without even giving a warning. If I'm leaving the laptop unused for just a few minutes then this is happening, it also occurred while working as well! So. I'm a little worried about it.

I have really no clue why it's like this, so it would be really helpful if someone helps me, I tried to contact few servers regarding this but not get any answer honestly.

Is there somewhere I can do to fix this?

QuicKil
  • 71
  • Could be overheating or faulty hardware. No way to tell without further investigation. – mikewhatever Apr 25 '20 at 13:04
  • I'm ready to give the information, can you please ask me how to know it? Because I have used Windows on it and it works really fine. No issues at all, so I was expecting the Linux to be smooth too! – QuicKil Apr 25 '20 at 13:15
  • Also, when I'm video streaming with it or leaving it after joining any Discord channel it's not actually shutting down! So, I'm really confused that what is the case. – QuicKil Apr 25 '20 at 13:18
  • I assume you meant i3-4005U CPU not y3-4005U. Is there any relevant information in /var/log/syslog or /var/log/kern.log? Use turbostat and run this command all the time, watch temperature: sudo ./turbostat --Summary --interval 15 --show Avg_MHz,Busy%,Bzy_MHz,IRQ,PkgTmp,PkgWatt,GFXWatt – Doug Smythies Apr 25 '20 at 15:16
  • [1/3] I checked the syslog and kern.log but didn't understand much. Today, there were two sudden shutdowns, on syslog I found May 1 18:48:41 Linuxbook kernel: [ 6214.544377] perf: interrupt took too long (2611 > 2500), lowering kernel.perf_event_max_sample_rate to 76500 May 1 18:49:23 Linuxbook rtkit-daemon[1224]: Supervising 5 threads of 3 processes of 1 users. my system was shutdown exactly at 18:49 on kern.log, I found May 1 18:48:41 Linuxbook kernel: [ 6214.544377] perf: interrupt took too long (2611 > 2500), lowering kernel.perf_event_max_sample_rate to 76500 – QuicKil May 01 '20 at 14:29
  • [2/3] and the second sudden shutdown occurred 19:17, on syslog May 1 19:15:28 Linuxbook dbus-daemon[1829]: [session uid=1000 pid=1829] Successfully activated service 'org.gnome.Logs' May 1 19:15:28 Linuxbook gnome-logs[3761]: g_file_info_get_attribute_boolean: assertion 'G_IS_FILE_INFO (info)' failed May 1 19:15:28 Linuxbook gnome-logs[3761]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed May 1 19:17:02 Linuxbook CRON[3779]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) – QuicKil May 01 '20 at 14:31
  • [3/3] on kern.log May 1 19:14:29 Linuxbook kernel: [ 543.816927] capability: warning:gvfsd-admin' uses 32-bit capabilities (legacy support in use)` – QuicKil May 01 '20 at 14:32
  • Since Windows seems to work fine on this machine, I'd probably rule out overheating. My next suspicion would be power states. It's possible Ubuntu is trying to use a power state that isn't playing well with your system. Try playing around with the power saving settings in the Bios? – Kelly Bang Jun 22 '20 at 20:37
  • You may first find out whether it is a battery problem or not. As Ubuntu 20.04 does not show low battery notification, it could be the problem. To ensure that, you may use a simple Python script named Battery Alert. This script can start as the laptop starts and maintains a log file indicating the discharging rate. It also sends you low battery notifications (also a sound notification) so that you never face the issue of the laptop shutting down due to low battery. 2. If it is not a battery problem, then it may be a hardware failure. In that
    • – Prasanta Dutta Sep 30 '21 at 11:15