Mint keeps Shutting Down randomly

Questions about hardware, drivers and peripherals
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Post Reply
dev2
Level 1
Level 1
Posts: 6
Joined: Sun Mar 17, 2024 3:04 pm

Mint keeps Shutting Down randomly

Post by dev2 »

System Informaton

Code: Select all

System:
  Kernel: 6.5.0-25-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33
    wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: LENOVO product: 82FG v: IdeaPad 5 15ITL05 serial: <superuser required>
    Chassis: type: 10 v: IdeaPad 5 15ITL05 serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0Q55722 WIN serial: <superuser required> UEFI: LENOVO
    v: FHCN70WW date: 11/17/2022
Battery:
  ID-1: BAT0 charge: 47.8 Wh (100.0%) condition: 47.8/57.0 Wh (83.8%) volts: 12.9 min: 11.5
    model: SMP L19M3PF6 type: Li-poly serial: <filter> status: Full cycles: 742
CPU:
  Info: quad core model: 11th Gen Intel Core i5-1135G7 bits: 64 type: MT MCP smt: enabled
    arch: Tiger Lake rev: 1 cache: L1: 320 KiB L2: 5 MiB L3: 8 MiB
  Speed (MHz): avg: 2005 high: 3100 min/max: 400/4200 cores: 1: 1187 2: 3100 3: 400 4: 2728
    5: 400 6: 3100 7: 2219 8: 2909 bogomips: 38707
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: Lenovo driver: i915 v: kernel ports:
    active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2, HDMI-A-3 bus-ID: 0000:00:02.0
    chip-ID: 8086:9a49 class-ID: 0300
  Device-2: NVIDIA TU117M [GeForce MX450] vendor: Lenovo driver: nvidia v: 535.161.07
    bus-ID: 0000:01:00.0 chip-ID: 10de:1f97 class-ID: 0302
  Device-3: Syntek Integrated Camera type: USB driver: uvcvideo bus-ID: 3-5:4 chip-ID: 174f:2459
    class-ID: fe01 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting,nvidia
    unloaded: fbdev,nouveau,vesa gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 98 s-size: 499x280mm (19.6x11.0") s-diag: 572mm (22.5")
  Monitor-1: eDP-1 model: AU Optronics res: 1920x1080 hz: 60 dpi: 142
    size: 344x194mm (13.5x7.6") diag: 395mm (15.5") modes: 1920x1080
  OpenGL: renderer: Mesa Intel Xe Graphics (TGL GT2) v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.2
    direct render: Yes
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio vendor: Lenovo driver: sof-audio-pci-intel-tgl
    bus-ID: 0000:00:1f.3 chip-ID: 8086:a0c8 class-ID: 0401
  Sound Server-1: ALSA v: k6.5.0-25-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi v: kernel bus-ID: 0000:00:14.3 chip-ID: 8086:a0f0
    class-ID: 0280
  IF: wlp0s20f3 state: down mac: <filter>
  Device-2: TP-Link USB 10/100 LAN type: USB driver: cdc_ether bus-ID: 3-4:3 chip-ID: 2357:0602
    class-ID: 0a00 serial: <filter>
  IF: enx3460f9b43efd state: unknown speed: 100 Mbps duplex: half mac: <filter>
  IF-ID-1: br-68624fe46d3d state: down mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 3-10:6 chip-ID: 8087:0026
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
    sub-v: 20ce hci-v: 5.2 rev: 20ce
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd v: 0.6 port: N/A
    bus-ID: 0000:00:0e.0 chip-ID: 8086:9a0b rev: class-ID: 0104
Drives:
  Local Storage: total: 476.94 GiB used: 553.59 GiB (116.1%)
  ID-1: /dev/nvme0n1 vendor: Micron model: MTFDHBA512QFD size: 476.94 GiB speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: 0011P6LN temp: 34.9 C scheme: GPT
Partition:
  ID-1: / size: 467.89 GiB used: 276.79 GiB (59.2%) fs: ext4 dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 2-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-4: 3-1:2 info: Manufacturer hub ports: 4 rev: 2.0 speed: 12 Mb/s power: 100mA
    chip-ID: 0a05:7211 class-ID: 0900
  Device-1: 3-1.1:7 info: USB OPTICAL MOUSE type: Mouse driver: hid-generic,usbhid interfaces: 1
    rev: 1.1 speed: 1.5 Mb/s power: 100mA chip-ID: 0000:3825 class-ID: 0301
  Device-2: 3-1.3:8 info: Dell KB216 Wired Keyboard type: Keyboard,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 100mA
    chip-ID: 413c:2113 class-ID: 0300
  Device-3: 3-4:3 info: TP-Link USB 10/100 LAN type: Ethernet Network,CDC-Data driver: cdc_ether
    interfaces: 2 rev: 2.1 speed: 480 Mb/s power: 100mA chip-ID: 2357:0602 class-ID: 0a00
    serial: <filter>
  Device-4: 3-5:4 info: Syntek Integrated Camera type: Video driver: uvcvideo interfaces: 3
    rev: 2.0 speed: 480 Mb/s power: 500mA chip-ID: 174f:2459 class-ID: fe01 serial: <filter>
  Device-5: 3-7:5 info: Elan Micro ELAN:Fingerprint type: <vendor specific> driver: N/A
    interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 04f3:0c58 class-ID: 0000
  Device-6: 3-10:6 info: Intel AX201 Bluetooth type: Bluetooth driver: btusb interfaces: 2
    rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 8087:0026 class-ID: e001
  Hub-5: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 56.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: apt: 2636
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https: //brave-browser-apt-release.s3.brave.com/ stable main
  Active apt repos in: /etc/apt/sources.list.d/docker.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/docker.gpg] https: //download.docker.com/linux/ubuntu jammy stable
  Active apt repos in: /etc/apt/sources.list.d/hashicorp.list
    1: deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https: //apt.releases.hashicorp.com jammy main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https: //mirrors.cicku.me/linuxmint/packages virginia main upstream import backport
    2: deb https: //ubuntu-archive.mirror.net.in jammy main restricted universe multiverse
    3: deb https: //ubuntu-archive.mirror.net.in jammy-updates main restricted universe multiverse
    4: deb https: //ubuntu-archive.mirror.net.in jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/papirus-papirus-jammy.list
    1: deb [signed-by=/etc/apt/keyrings/papirus-papirus-jammy.gpg] https: //ppa.launchpadcontent.net/papirus/papirus/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/vscode.list
    1: deb [arch=amd64,arm64,armhf] http: //packages.microsoft.com/repos/code stable main
  Active apt repos in: /etc/apt/sources.list.d/vscodium.list
    1: deb [ signed-by=/usr/share/keyrings/vscodium-archive-keyring.gpg ] https: //download.vscodium.com/debs vscodium main
Info:
  Processes: 325 Uptime: 19m wakeups: 1 Memory: 15.4 GiB used: 4.69 GiB (30.5%) Init: systemd
  v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Cinnamon v: 6.0.4 inxi: 3.3.13

Linux Mint Keeps shutting down randomly even though system memory usage is relatively low and there is memory available. The system is also not overheating as even on a fresh boot and opening just VS Code and a few Firefox tabs, Mint will restart. the restart also doesn't show up on last -x

last -x output

Code: Select all

❯ last -x
anon     tty7         :0               Mon Mar 18 00:22    gone - no logout
runlevel (to lvl 5)   6.5.0-25-generic Mon Mar 18 00:21   still running
reboot   system boot  6.5.0-25-generic Mon Mar 18 00:21   still running
anon     tty7         :0               Sun Mar 17 18:58 - crash  (05:22)
runlevel (to lvl 5)   6.5.0-25-generic Sun Mar 17 18:58 - 00:21  (05:23)
reboot   system boot  6.5.0-25-generic Sun Mar 17 18:58   still running
shutdown system down  6.5.0-25-generic Sun Mar 17 15:24 - 18:58  (03:34)
anon     tty7         :0               Sun Mar 17 15:19 - 15:24  (00:05)
runlevel (to lvl 5)   6.5.0-25-generic Sun Mar 17 15:18 - 15:24  (00:05)
reboot   system boot  6.5.0-25-generic Sun Mar 17 15:18 - 15:24  (00:05)
shutdown system down  6.5.0-25-generic Sun Mar 17 15:18 - 15:18  (00:00)
anon     tty7         :0               Sun Mar 17 15:16 - 15:18  (00:01)
runlevel (to lvl 5)   6.5.0-25-generic Sun Mar 17 15:16 - 15:18  (00:01)
reboot   system boot  6.5.0-25-generic Sun Mar 17 15:16 - 15:18  (00:01)
anon     tty7         :0               Sun Mar 17 11:52 - crash  (03:24)
runlevel (to lvl 5)   6.5.0-25-generic Sun Mar 17 11:51 - 15:16  (03:25)
reboot   system boot  6.5.0-25-generic Sun Mar 17 11:51 - 15:18  (03:27)
shutdown system down  6.5.0-25-generic Sun Mar 17 11:50 - 11:51  (00:00)
anon     tty7         :0               Sun Mar 17 11:48 - 11:50  (00:02)
runlevel (to lvl 5)   6.5.0-25-generic Sun Mar 17 11:48 - 11:50  (00:02)
reboot   system boot  6.5.0-25-generic Sun Mar 17 11:47 - 11:50  (00:03)
shutdown system down  6.5.0-25-generic Sun Mar 17 11:47 - 11:47  (00:00)
anon     tty7         :0               Sun Mar 17 11:45 - 11:47  (00:01)
runlevel (to lvl 5)   6.5.0-25-generic Sun Mar 17 11:45 - 11:47  (00:01)
reboot   system boot  6.5.0-25-generic Sun Mar 17 11:45 - 11:47  (00:01)
runlevel (to lvl 5)   6.5.0-25-generic Sun Mar 17 11:39 - 11:45  (00:05)
anon     tty7         :0               Sun Mar 17 11:39 - crash  (00:06)
reboot   system boot  6.5.0-25-generic Sun Mar 17 11:38 - 11:47  (00:08)
shutdown system down  6.5.0-25-generic Sun Mar 17 11:38 - 11:38  (00:00)
anon     tty7         :0               Sun Mar 17 11:36 - 11:37  (00:01)
runlevel (to lvl 5)   6.5.0-25-generic Sun Mar 17 11:36 - 11:38  (00:01)
reboot   system boot  6.5.0-25-generic Sun Mar 17 11:36 - 11:38  (00:01)
anon     tty7         :0               Sun Mar 17 11:35 - crash  (00:00)
reboot   system boot  6.5.0-25-generic Sun Mar 17 11:35 - 11:38  (00:02)
runlevel (to lvl 5)   6.5.0-25-generic Sun Mar 17 10:58 - 11:36  (00:37)
anon     tty7         :0               Sun Mar 17 10:57 - crash  (00:37)
shutdown system down  6.5.0-25-generic Fri Mar 15 01:50 - 08:54  (07:03)
there was a shutdown at around 00:18 but that doesn't show up here
User avatar
xenopeek
Level 25
Level 25
Posts: 29615
Joined: Wed Jul 06, 2011 3:58 am

Re: Mint keeps Shutting Down randomly

Post by xenopeek »

With shut down do you mean the computer powers off completely?

I have a Sleep key on keyboard that I accidentally pressed a couple of times before figuring it out, but that looks the PC going off at first. Pressing a key couple of times will after a short wait wake it up again. Just mentioning it to make sure it's not something like that.

When next it happens I would try journalctl -b -1 -e in a maximized terminal (so you don't have to scroll as much) to open the system log at the end of the previous boot. Does the time line up when it happened? If so see if you can spot something in the last 15 seconds of the log or so that could hold a clue what happened. You may also try journalctl -b -1 -p warning -e to show the same but only show warning and error messages.

You can also try if journalctl --list-boots will show something other than your last -x. If it does show the boots that ended in a random shut down. You can use the IDX number with the earlier journalctl command to show the log messages for that boot (-b -1 is the previous boot, -b -2 the boot before that and so on).
Image
dev2
Level 1
Level 1
Posts: 6
Joined: Sun Mar 17, 2024 3:04 pm

Re: Mint keeps Shutting Down randomly

Post by dev2 »

With shut down, do you mean the computer powers off completely?
Yes, the Laptop just powers down.

I have a Sleep key on the keyboard that I accidentally pressed a couple of times before figuring it out, but that looks the PC going off at first. Pressing a key a couple of times will after a short wait wake it up again. Just mentioning it to make sure it's not something like that.
As far as I can remember, there isn't anything like this present on my IdeaPad 5 and I have turned off "flip to turn on" in the bios settings.

When the shut-down happens again, will run the commands as mentioned.
Will post an update when it happens again.
dev2
Level 1
Level 1
Posts: 6
Joined: Sun Mar 17, 2024 3:04 pm

Re: Mint keeps Shutting Down randomly

Post by dev2 »

Ok, since last time the shutdown has happened 3 times.

The first one didn't show last -x, there were also no logs as I ran, journalctl -b -1 -e and there was no activity from the time of the shutdown. After the first shutdown I restarted the system and it shutdown again after like 10 minutes, this time when I ran journalctl -b -1 -e I got,

Code: Select all

Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6332] device (docker0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6334] device (docker0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6335] device (docker0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6341] manager: (br-68624fe46d3d): new Bridge device (/org/freedesktop/NetworkManager/Devices/6)
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6345] device (docker0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6387] device (docker0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6389] device (docker0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6395] device (docker0): Activation: successful, device activated.
Mar 20 00:54:54 dev avahi-daemon[797]: Joining mDNS multicast group on interface br-68624fe46d3d.IPv4 with address 172.19.0.1.
Mar 20 00:54:54 dev avahi-daemon[797]: New relevant interface br-68624fe46d3d.IPv4 for mDNS.
Mar 20 00:54:54 dev avahi-daemon[797]: Registering new address record for 172.19.0.1 on br-68624fe46d3d.IPv4.
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6595] device (br-68624fe46d3d): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6599] device (br-68624fe46d3d): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external>
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6606] device (br-68624fe46d3d): Activation: starting connection 'br-68624fe46d3d' (4fc50c24-4076-4aee-b18f-bccb9acdbb1f)
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6608] device (br-68624fe46d3d): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6610] device (br-68624fe46d3d): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6612] device (br-68624fe46d3d): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6618] device (br-68624fe46d3d): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6650] device (br-68624fe46d3d): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6652] device (br-68624fe46d3d): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Mar 20 00:54:54 dev NetworkManager[925]: <info>  [1710876294.6657] device (br-68624fe46d3d): Activation: successful, device activated.
Mar 20 00:54:54 dev dockerd[3439]: time="2024-03-20T00:54:54.925210600+05:30" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be>
Mar 20 00:54:55 dev dockerd[3439]: time="2024-03-20T00:54:55.003960087+05:30" level=info msg="Loading containers: done."
and running journalctl -b -1 -p warning -e, I got

Code: Select all

Mar 20 00:54:36 dev kernel:  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Mar 20 00:54:36 dev kernel: RIP: 0033:0x78140c51e88d
Mar 20 00:54:36 dev kernel: Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48>
Mar 20 00:54:36 dev kernel: RSP: 002b:00007ffcf0855a78 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Mar 20 00:54:36 dev kernel: RAX: ffffffffffffffda RBX: 00005e5aebf3be80 RCX: 000078140c51e88d
Mar 20 00:54:36 dev kernel: RDX: 0000000000000000 RSI: 00005e5aebb39cd2 RDI: 0000000000000003
Mar 20 00:54:36 dev kernel: RBP: 0000000000040000 R08: 0000000000000000 R09: 0000000000000002
Mar 20 00:54:36 dev kernel: R10: 0000000000000003 R11: 0000000000000246 R12: 00005e5aebb39cd2
Mar 20 00:54:36 dev kernel: R13: 00005e5aebf43460 R14: 00005e5aebf3b460 R15: 00005e5aebf3c320
Mar 20 00:54:36 dev kernel:  </TASK>
Mar 20 00:54:36 dev kernel: ================================================================================
Mar 20 00:54:36 dev kernel: VBoxNetFlt: Successfully started.
Mar 20 00:54:36 dev kernel: VBoxNetAdp: Successfully started.
Mar 20 00:54:40 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=172.217.166.14 DST=172.16.99.63 LEN=151 TOS=0x00 PREC=0x00 TTL=63 ID=25896 DF PROTO>
Mar 20 00:54:40 dev thermald[840]: Manufacturer didn't provide adequate support to run in
Mar 20 00:54:40 dev thermald[840]: optimized configuration on Linux with open source
Mar 20 00:54:40 dev thermald[840]: You may want to disable thermald on this system if you see issue
Mar 20 00:54:40 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=172.217.166.14 DST=172.16.99.63 LEN=151 TOS=0x00 PREC=0x00 TTL=63 ID=25897 DF PROTO>
Mar 20 00:54:41 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=172.217.166.14 DST=172.16.99.63 LEN=151 TOS=0x00 PREC=0x00 TTL=63 ID=25898 DF PROTO>
Mar 20 00:54:41 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=172.217.166.14 DST=172.16.99.63 LEN=151 TOS=0x00 PREC=0x00 TTL=63 ID=25899 DF PROTO>
Mar 20 00:54:42 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=172.217.166.14 DST=172.16.99.63 LEN=151 TOS=0x00 PREC=0x00 TTL=63 ID=25900 DF PROTO>
Mar 20 00:54:42 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=142.250.207.238 DST=172.16.99.63 LEN=267 TOS=0x00 PREC=0x00 TTL=63 ID=30698 DF PROT>
Mar 20 00:54:42 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=152.67.14.48 DST=172.16.99.63 LEN=218 TOS=0x00 PREC=0x00 TTL=63 ID=27880 DF PROTO=T>
Mar 20 00:54:42 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=192.124.249.8 DST=172.16.99.63 LEN=79 TOS=0x00 PREC=0x00 TTL=63 ID=25548 DF PROTO=T>
Mar 20 00:54:42 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=192.124.249.8 DST=172.16.99.63 LEN=64 TOS=0x00 PREC=0x00 TTL=63 ID=25549 DF PROTO=T>
Mar 20 00:54:43 dev lightdm[1639]: gkr-pam: unable to locate daemon control file
Mar 20 00:54:43 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:4c:d5:77:34:22:11:86:dd SRC=fe80:0000:0000:0000:7c74:87d9:061e:0536 DST=fe80:0000:0000:0000:f3b1:bea1:ee08:a436>
Mar 20 00:54:43 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=172.217.166.14 DST=172.16.99.63 LEN=151 TOS=0x00 PREC=0x00 TTL=63 ID=25901 DF PROTO>
Mar 20 00:54:46 dev cinnamon-session[1783]: WARNING: t+1.79960s: Detected that screensaver has appeared on the bus
Mar 20 00:54:47 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=104.115.39.72 DST=172.16.99.63 LEN=40 TOS=0x00 PREC=0x00 TTL=63 ID=53092 DF PROTO=T>
Mar 20 00:54:47 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=104.115.39.72 DST=172.16.99.63 LEN=40 TOS=0x00 PREC=0x00 TTL=63 ID=7711 DF PROTO=TC>
Mar 20 00:54:47 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=104.115.39.72 DST=172.16.99.63 LEN=40 TOS=0x00 PREC=0x00 TTL=63 ID=7712 DF PROTO=TC>
Mar 20 00:54:47 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=104.115.39.72 DST=172.16.99.63 LEN=40 TOS=0x00 PREC=0x00 TTL=63 ID=53093 DF PROTO=T>
Mar 20 00:54:48 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=104.115.39.72 DST=172.16.99.63 LEN=40 TOS=0x00 PREC=0x00 TTL=63 ID=53094 DF PROTO=T>
Mar 20 00:54:48 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=104.115.39.72 DST=172.16.99.63 LEN=40 TOS=0x00 PREC=0x00 TTL=63 ID=7713 DF PROTO=TC>
Mar 20 00:54:49 dev kernel: warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
Mar 20 00:54:49 dev gnome-keyring-daemon[1779]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
Mar 20 00:54:50 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=104.115.39.72 DST=172.16.99.63 LEN=40 TOS=0x00 PREC=0x00 TTL=63 ID=7714 DF PROTO=TC>
Mar 20 00:54:50 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=f0:9e:4a:ac:1f:7f:a0:93:51:d2:16:49:08:00 SRC=104.115.39.72 DST=172.16.99.63 LEN=40 TOS=0x00 PREC=0x00 TTL=63 ID=53095 DF PROTO=T>
Mar 20 00:54:53 dev systemd[1]: kerneloops.service: Found left-over process 3458 (kerneloops) in control group while starting unit. Ignoring.
Mar 20 00:54:53 dev systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 20 00:54:54 dev kernel: kauditd_printk_skb: 16 callbacks suppressed
the lastest shutdown happened, when I left I system on idle running a few containers and when I got back the sytem had automatically shutdown

Code: Select all

Mar 20 22:13:19 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:02:aa:77:ef:db:b3:08:00 SRC=172.16.105.170 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=22142 PROTO=2 
Mar 20 22:13:22 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:02:aa:77:ef:db:b3:08:00 SRC=172.16.105.170 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=11838 PROTO=2 
Mar 20 22:13:45 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=4758 PROTO=2 
Mar 20 22:13:50 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:02:aa:77:ef:db:b3:08:00 SRC=172.16.105.170 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=4143 PROTO=2 
Mar 20 22:13:52 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:02:aa:77:ef:db:b3:08:00 SRC=172.16.105.170 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=11313 PROTO=2 
Mar 20 22:14:47 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=48214 PROTO=2 
Mar 20 22:14:50 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:02:aa:77:ef:db:b3:08:00 SRC=172.16.105.170 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=6070 PROTO=2 
Mar 20 22:15:46 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=7109 PROTO=2 
Mar 20 22:15:50 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:02:aa:77:ef:db:b3:08:00 SRC=172.16.105.170 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=58008 PROTO=2 
Mar 20 22:16:26 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=14232 PROTO=2 
Mar 20 22:16:27 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=42785 PROTO=2 
Mar 20 22:17:01 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=50987 PROTO=2 
Mar 20 22:17:01 dev CRON[549540]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 20 22:17:01 dev CRON[549541]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Mar 20 22:17:01 dev CRON[549540]: pam_unix(cron:session): session closed for user root
Mar 20 22:20:51 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:02:aa:77:ef:db:b3:08:00 SRC=172.16.105.170 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=53135 PROTO=2 
Mar 20 22:22:48 dev systemd-timesyncd[754]: Timed out waiting for reply from 185.125.190.58:123 (ntp.ubuntu.com).
Mar 20 22:22:53 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=55104 PROTO=2 
Mar 20 22:22:54 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=62922 PROTO=2 
Mar 20 22:22:54 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=21527 PROTO=2 
Mar 20 22:22:58 dev systemd-timesyncd[754]: Timed out waiting for reply from 185.125.190.57:123 (ntp.ubuntu.com).
Mar 20 22:23:08 dev systemd-timesyncd[754]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com).
Mar 20 22:23:18 dev systemd-timesyncd[754]: Timed out waiting for reply from 185.125.190.56:123 (ntp.ubuntu.com).
Mar 20 22:23:27 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=26392 PROTO=2 
Mar 20 22:24:08 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=22005 PROTO=2 
Mar 20 22:24:37 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=55150 PROTO=2 
Mar 20 22:25:37 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=61638 PROTO=2 
Mar 20 22:27:36 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=32493 PROTO=2 
Mar 20 22:29:12 dev kernel: perf: interrupt took too long (3965 > 3963), lowering kernel.perf_event_max_sample_rate to 50250
Mar 20 22:30:01 dev CRON[549740]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 20 22:30:01 dev CRON[549741]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Mar 20 22:30:01 dev CRON[549740]: pam_unix(cron:session): session closed for user root
Mar 20 22:30:23 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=38149 PROTO=2 
Mar 20 22:31:14 dev systemd[1]: Started Run anacron jobs.
Mar 20 22:31:14 dev anacron[549759]: Anacron 2.3 started on 2024-03-20
Mar 20 22:31:14 dev anacron[549759]: Normal exit (0 jobs run)
Mar 20 22:31:14 dev systemd[1]: anacron.service: Deactivated successfully.
Mar 20 22:34:07 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=56041 PROTO=2 
Mar 20 22:34:52 dev kernel: [UFW BLOCK] IN=wlp0s20f3 OUT= MAC=01:00:5e:00:00:fb:4e:e0:71:bf:b6:4d:08:00 SRC=172.16.108.205 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=58034 PROTO=2 
I am not sure how to proceed.
User avatar
xenopeek
Level 25
Level 25
Posts: 29615
Joined: Wed Jul 06, 2011 3:58 am

Re: Mint keeps Shutting Down randomly

Post by xenopeek »

I don't see clues in that. Sorry but I'm also not sure about next steps.

I did have VirtualBox kill a virtual machine on me today. It said something afterwards like the system (or the vm?) was running out of memory. It killed the virtual machine outright, without any warning or prompt beforehand. Probably irrelevant.

Do you have another OS on this computer?
Image
dev2
Level 1
Level 1
Posts: 6
Joined: Sun Mar 17, 2024 3:04 pm

Re: Mint keeps Shutting Down randomly

Post by dev2 »

No, I do not have any other OS on this computer and the complete disk is given to mint and system has 16 GB of ram and rarely uses the swap. The shutdown happens at random times, i.e. it can shut down when I have 6 containers running multiple applications open with a good chunk of ram usage (around 10 GB) or when I have a single browser tab open watching YouTube. I have tried to keep an eye on my memory and even CPU usage but can seem to figure out anything.
User avatar
Pjotr
Level 24
Level 24
Posts: 20142
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland) 🇳🇱
Contact:

Re: Mint keeps Shutting Down randomly

Post by Pjotr »

Apparently, your laptop isn't running on the latest BIOS for it. Make sure it does and test again.

Not sure whether that'll help, but it doesn't hurt either, and who knows....
Tip: 10 things to do after installing Linux Mint 21.3 Virginia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.
User avatar
SMG
Level 25
Level 25
Posts: 32007
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Mint keeps Shutting Down randomly

Post by SMG »

dev2 wrote: Mon Mar 18, 2024 1:29 am
With shut down, do you mean the computer powers off completely?
Yes, the Laptop just powers down.
That is usually a sign of a power supply problem.
dev2 wrote: Wed Mar 20, 2024 1:44 pmThe first one didn't show last -x
Why are you running that to check for shutdowns? It's my understanding that is for checking user logins. :?
dev2 wrote: Wed Mar 20, 2024 1:44 pmthere were also no logs as I ran, journalctl -b -1 -e and there was no activity from the time of the shutdown.
That's what happens when power to the laptop is lost (ie. a power supply problem).

Perhaps the updated BIOS/UEFI will help.
Image
A woman typing on a laptop with LM20.3 Cinnamon.
dev2
Level 1
Level 1
Posts: 6
Joined: Sun Mar 17, 2024 3:04 pm

Re: Mint keeps Shutting Down randomly

Post by dev2 »

Ok so, I tried to update the bios of my Lenovo IdeaPad 5, but https://fwupd.org/ didn't support it, so I followed another method I found on the forum that used the Hiren BootCD to extract and patch the BIOS, but that failed midway, and the system wouldn't boot. I took it to a repair shop, and it took them about 2 hours to fix the laptop. They basically downgraded by bios to version FHCN63WW from version FHCN70WW. Haven't had any random shutdown since.
Post Reply

Return to “Hardware Support”