Mint OS gets stuck while poweroff

S

shubhamfuloria

New Member
Joined
Sep 1, 2021
Messages
25
Reaction score
5
Credits
164
Sometimes when I poweroff my computer, it gets stuck with mint logo. I tried many things on internet, but not able to fix it . I've the kern.log of last time it got stuck. Kindly help me to figure out what's going wrong !
Here is the kernal log ..
Aug 31 21:23:34 shubham kernel: [16064.378408] Freezing user space processes ... (elapsed 0.156 seconds) done.
Aug 31 21:23:34 shubham kernel: [16064.534749] OOM killer disabled.
Aug 31 21:23:34 shubham kernel: [16064.534750] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Aug 31 21:23:34 shubham kernel: [16064.536639] printk: Suspending console(s) (use no_console_suspend to debug)
Aug 31 21:23:34 shubham kernel: [16064.686431] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Aug 31 21:23:34 shubham kernel: [16064.686641] sd 0:0:0:0: [sda] Stopping disk
Aug 31 21:23:34 shubham kernel: [16065.271263] ACPI: EC: interrupt blocked
Aug 31 21:23:34 shubham kernel: [16065.310817] ACPI: Preparing to enter system sleep state S3
Aug 31 21:23:34 shubham kernel: [16065.320382] ACPI: EC: event blocked
Aug 31 21:23:34 shubham kernel: [16065.320384] ACPI: EC: EC stopped
Aug 31 21:23:34 shubham kernel: [16065.320386] PM: Saving platform NVS memory
Aug 31 21:23:34 shubham kernel: [16065.320570] Disabling non-boot CPUs ...
Aug 31 21:23:34 shubham kernel: [16065.322012] smpboot: CPU 1 is now offline
Aug 31 21:23:34 shubham kernel: [16065.324904] smpboot: CPU 2 is now offline
Aug 31 21:23:34 shubham kernel: [16065.329257] smpboot: CPU 3 is now offline
Aug 31 21:23:34 shubham kernel: [16065.332317] ACPI: Low-level resume complete
Aug 31 21:23:34 shubham kernel: [16065.332381] ACPI: EC: EC started
Aug 31 21:23:34 shubham kernel: [16065.332382] PM: Restoring platform NVS memory
Aug 31 21:23:34 shubham kernel: [16065.336041] Enabling non-boot CPUs ...
Aug 31 21:23:34 shubham kernel: [16065.336104] x86: Booting SMP configuration:
Aug 31 21:23:34 shubham kernel: [16065.336106] smpboot: Booting Node 0 Processor 1 APIC 0x2
Aug 31 21:23:34 shubham kernel: [16065.339283] CPU1 is up
Aug 31 21:23:34 shubham kernel: [16065.339325] smpboot: Booting Node 0 Processor 2 APIC 0x1
Aug 31 21:23:34 shubham kernel: [16065.340434] CPU2 is up
Aug 31 21:23:34 shubham kernel: [16065.340469] smpboot: Booting Node 0 Processor 3 APIC 0x3
Aug 31 21:23:34 shubham kernel: [16065.341563] CPU3 is up
Aug 31 21:23:34 shubham kernel: [16065.345269] ACPI: Waking up from system sleep state S3
Aug 31 21:23:34 shubham kernel: [16065.473057] ACPI: EC: interrupt unblocked
Aug 31 21:23:34 shubham kernel: [16065.620107] ACPI: EC: event unblocked
Aug 31 21:23:34 shubham kernel: [16065.621245] sd 0:0:0:0: [sda] Starting disk
Aug 31 21:23:34 shubham kernel: [16065.935388] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Aug 31 21:23:34 shubham kernel: [16065.941973] ata2.00: configured for UDMA/100
Aug 31 21:23:34 shubham kernel: [16066.027918] usb 2-3: reset low-speed USB device number 3 using xhci_hcd
Aug 31 21:23:34 shubham kernel: [16066.443801] usb 2-6: reset full-speed USB device number 5 using xhci_hcd
Aug 31 21:23:34 shubham kernel: [16066.591454] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Aug 31 21:23:34 shubham kernel: [16066.703882] ata1.00: configured for UDMA/133
Aug 31 21:23:34 shubham kernel: [16066.859611] usb 2-2: reset low-speed USB device number 7 using xhci_hcd
Aug 31 21:23:34 shubham kernel: [16067.275539] usb 2-8: reset high-speed USB device number 6 using xhci_hcd
Aug 31 21:23:34 shubham kernel: [16067.551441] usb 2-5: reset high-speed USB device number 4 using xhci_hcd
Aug 31 21:23:34 shubham kernel: [16067.773319] OOM killer enabled.
Aug 31 21:23:34 shubham kernel: [16067.773321] Restarting tasks ...
Aug 31 21:23:34 shubham kernel: [16067.783319] pci_bus 0000:04: Allocating resources
Aug 31 21:23:34 shubham kernel: [16067.783331] pci_bus 0000:06: Allocating resources
Aug 31 21:23:34 shubham kernel: [16067.783353] pci_bus 0000:07: Allocating resources
Aug 31 21:23:34 shubham kernel: [16067.783365] pci_bus 0000:08: Allocating resources
Aug 31 21:23:34 shubham kernel: [16067.783877] pci_bus 0000:04: Allocating resources
Aug 31 21:23:34 shubham kernel: [16067.783892] pci_bus 0000:06: Allocating resources
Aug 31 21:23:34 shubham kernel: [16067.783914] pci_bus 0000:07: Allocating resources
Aug 31 21:23:34 shubham kernel: [16067.783926] pci_bus 0000:08: Allocating resources
Aug 31 21:23:34 shubham kernel: [16067.784933] pci_bus 0000:04: Allocating resources
Aug 31 21:23:34 shubham kernel: [16067.784943] pci_bus 0000:06: Allocating resources
Aug 31 21:23:34 shubham kernel: [16067.784964] pci_bus 0000:07: Allocating resources
Aug 31 21:23:34 shubham kernel: [16067.784975] pci_bus 0000:08: Allocating resources
Aug 31 21:23:34 shubham kernel: [16067.798843] done.
Aug 31 21:23:34 shubham kernel: [16067.808250] Bluetooth: hci0: read Intel version: 3707100100012d0d00
Aug 31 21:23:34 shubham kernel: [16068.023475] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq
Aug 31 21:23:34 shubham kernel: [16068.177031] PM: suspend exit
Aug 31 21:23:34 shubham kernel: [16068.188238] Bluetooth: hci0: unexpected event for opcode 0xfc2f
Aug 31 21:23:34 shubham kernel: [16068.203266] Bluetooth: hci0: Intel firmware patch completed and activated
Aug 31 21:23:36 shubham kernel: [16069.575686] Generic FE-GE Realtek PHY r8169-700:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-700:00, irq=IGNORE)
Aug 31 21:23:36 shubham kernel: [16069.687561] r8169 0000:07:00.0 enp7s0: Link is Down
Aug 31 21:23:42 shubham kernel: [16075.648422] Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7
Aug 31 21:24:42 shubham kernel: [16135.442702] wlp6s0: authenticate with b6:c7:7a:1d:ab:e1
Aug 31 21:24:42 shubham kernel: [16135.444791] wlp6s0: send auth to b6:c7:7a:1d:ab:e1 (try 1/3)
Aug 31 21:24:42 shubham kernel: [16135.448755] wlp6s0: authenticated
Aug 31 21:24:42 shubham kernel: [16135.450038] wlp6s0: associate with b6:c7:7a:1d:ab:e1 (try 1/3)
Aug 31 21:24:42 shubham kernel: [16135.457526] wlp6s0: RX AssocResp from b6:c7:7a:1d:ab:e1 (capab=0x411 status=0 aid=1)
Aug 31 21:24:42 shubham kernel: [16135.458217] wlp6s0: associated
Aug 31 21:24:42 shubham kernel: [16135.593385] IPv6: ADDRCONF(NETDEV_CHANGE): wlp6s0: link becomes ready
Aug 31 21:25:11 shubham kernel: [16164.900997] perf: interrupt took too long (5118 > 5090), lowering kernel.perf_event_max_sample_rate to 39000
Aug 31 21:37:40 shubham kernel: [16912.927356] wlp6s0: deauthenticated from b6:c7:7a:1d:ab:e1 (Reason: 3=DEAUTH_LEAVING)
Aug 31 22:08:47 shubham kernel: [18779.797255] perf: interrupt took too long (6402 > 6397), lowering kernel.perf_event_max_sample_rate to 31000
Aug 31 22:25:17 shubham kernel: [19769.616427] wlp6s0: authenticate with b6:c7:7a:1d:ab:e1
Aug 31 22:25:17 shubham kernel: [19769.618625] wlp6s0: send auth to b6:c7:7a:1d:ab:e1 (try 1/3)
Aug 31 22:25:17 shubham kernel: [19769.623747] wlp6s0: authenticated
Aug 31 22:25:17 shubham kernel: [19769.628175] wlp6s0: associate with b6:c7:7a:1d:ab:e1 (try 1/3)
Aug 31 22:25:17 shubham kernel: [19769.636644] wlp6s0: RX AssocResp from b6:c7:7a:1d:ab:e1 (capab=0x411 status=0 aid=1)
Aug 31 22:25:17 shubham kernel: [19769.637308] wlp6s0: associated
Aug 31 22:52:26 shubham kernel: [21399.523131] perf: interrupt took too long (8163 > 8002), lowering kernel.perf_event_max_sample_rate to 24500
Click to expand...
 


G'day shubhamfuloria , Welcome to Linux.org

Has it not occured to you that we may need to know which particular distro you are running ?....and perhaps the make, model, ram etc etc of your pc/laptop?

Does this only happen randomly ?

Are there any particular apps running at that time?

Maybe change the kernel being used

Try running your distro from a live usb, and see if the problem repeats itself.



Details please.
 
Details of my System
Condobloke said:
G'day shubhamfuloria , Welcome to Linux.org

Has it not occured to you that we may need to know which particular distro you are running ?....and perhaps the make, model, ram etc etc of your pc/laptop?

Does this only happen randomly ?

Are there any particular apps running at that time?

Maybe change the kernel being used

Try running your distro from a live usb, and see if the problem repeats itself.



Details please.
Click to expand...
Details of my PC:
Model : Dell Vostro 3558
Ram: 4GB
Distro Info:
NAME="Linux Mint"
VERSION="20.2 (Uma)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 20.2"
VERSION_ID="20.2"
 
shubhamfuloria said:
Sometimes when I poweroff my computer, it gets stuck with mint logo. I tried many things on internet, but not able to fix it . I've the kern.log of last time it got stuck. Kindly help me to figure out what's going wrong !
Here is the kernal log ..
Click to expand...

Without altering the latencies, the linux kernel collects samples using 'Perf.' This includes interrupting times. A similar notice like this prints if interrupts take too long:

kernel: [ 6491.061361] perf: interrupt took too long (6650 > 6452), lowering kernel.perf_event_max_sample_rate to 30000
Click to expand...

Meaning

In essence, the machine was blocked for a long time on an interrupt. There are a lot of causes for this, including:

  1. The long DISK IO interrupt would be caused by a defective, slow or overloaded disc. Alternatively, a disc or raid controller problem may cause this.
  2. Too long network IO interrupt would most often be triggered by the underoptimal nature of network driver problems. Alternatively, network problems may cause this, although it should be avoided by the theoretical protocol switching.

Troubleshooting

Disk IO statistics (sysstat-sar and/or iostat) may be readily verified and confirmed for disc IO. The network IO will be if the disc IO is not the reason to interrupt slowly. This requires a network and/or kernel check. The problem must be tested.

First of all, check kernel messages in /var/log/ (messages|syslog) and dmasg should be included in the troubleshooting. If the vmxnet driver shows tracebacks, a defective network driver causes the interruption too long. To upgrade to the most current stable kernel, you can contact your network card provider.

If there is no problem with the kernel drivers, the network is most likely to blame, most likely the first hop. This must then be verified on the network side.
 
jizzy said:
Without altering the latencies, the linux kernel collects samples using 'Perf.' This includes interrupting times. A similar notice like this prints if interrupts take too long:



Meaning

In essence, the machine was blocked for a long time on an interrupt. There are a lot of causes for this, including:

  1. The long DISK IO interrupt would be caused by a defective, slow or overloaded disc. Alternatively, a disc or raid controller problem may cause this.
  2. Too long network IO interrupt would most often be triggered by the underoptimal nature of network driver problems. Alternatively, network problems may cause this, although it should be avoided by the theoretical protocol switching.

Troubleshooting

Disk IO statistics (sysstat-sar and/or iostat) may be readily verified and confirmed for disc IO. The network IO will be if the disc IO is not the reason to interrupt slowly. This requires a network and/or kernel check. The problem must be tested.

First of all, check kernel messages in /var/log/ (messages|syslog) and dmasg should be included in the troubleshooting. If the vmxnet driver shows tracebacks, a defective network driver causes the interruption too long. To upgrade to the most current stable kernel, you can contact your network card provider.

If there is no problem with the kernel drivers, the network is most likely to blame, most likely the first hop. This must then be verified on the network side.
Click to expand...

Here is last syslog ..Kindly help me to know the reason of freezing!
Aug 31 23:17:01 shubham CRON[17851]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 31 23:23:44 shubham systemd[1]: fwupd.service: Succeeded.
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4312] dhcp4 (wlp6s0): option dhcp_lease_time => '3600'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4312] dhcp4 (wlp6s0): option domain_name_servers => '192.168.43.1'
Aug 31 23:23:53 shubham dbus-daemon[759]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=760 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4313] dhcp4 (wlp6s0): option expiry => '1630436033'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4313] dhcp4 (wlp6s0): option host_name => 'shubham'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4313] dhcp4 (wlp6s0): option ip_address => '192.168.43.42'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4313] dhcp4 (wlp6s0): option next_server => '192.168.43.1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4314] dhcp4 (wlp6s0): option requested_broadcast_address => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4314] dhcp4 (wlp6s0): option requested_domain_name => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4314] dhcp4 (wlp6s0): option requested_domain_name_servers => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4314] dhcp4 (wlp6s0): option requested_domain_search => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4314] dhcp4 (wlp6s0): option requested_host_name => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4314] dhcp4 (wlp6s0): option requested_interface_mtu => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4315] dhcp4 (wlp6s0): option requested_ms_classless_static_routes => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4315] dhcp4 (wlp6s0): option requested_nis_domain => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4315] dhcp4 (wlp6s0): option requested_nis_servers => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4315] dhcp4 (wlp6s0): option requested_ntp_servers => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4315] dhcp4 (wlp6s0): option requested_rfc3442_classless_static_routes => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4316] dhcp4 (wlp6s0): option requested_root_path => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4316] dhcp4 (wlp6s0): option requested_routers => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4316] dhcp4 (wlp6s0): option requested_static_routes => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4316] dhcp4 (wlp6s0): option requested_subnet_mask => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4316] dhcp4 (wlp6s0): option requested_time_offset => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4317] dhcp4 (wlp6s0): option requested_wpad => '1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4317] dhcp4 (wlp6s0): option routers => '192.168.43.1'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4317] dhcp4 (wlp6s0): option subnet_mask => '255.255.255.0'
Aug 31 23:23:53 shubham NetworkManager[760]: <info> [1630432433.4317] dhcp4 (wlp6s0): state changed extended -> extended
Aug 31 23:23:53 shubham systemd[1]: Starting Network Manager Script Dispatcher Service...
Aug 31 23:23:53 shubham dbus-daemon[759]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug 31 23:23:53 shubham systemd[1]: Started Network Manager Script Dispatcher Service.
Aug 31 23:24:03 shubham systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Aug 31 23:30:01 shubham CRON[18271]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Aug 31 23:31:28 shubham systemd[1]: Started Run anacron jobs.
Aug 31 23:31:28 shubham anacron[18285]: Anacron 2.3 started on 2021-08-31
Aug 31 23:31:28 shubham anacron[18285]: Normal exit (0 jobs run)
Aug 31 23:31:28 shubham systemd[1]: anacron.service: Succeeded.
Aug 31 23:39:02 shubham wpa_supplicant[800]: wlp6s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-29 noise=9999 txrate=72200
Aug 31 23:50:28 shubham NetworkManager[760]: <info> [1630434028.4251] dhcp4 (wlp6s0): option dhcp_lease_time => '3600'
Aug 31 23:50:28 shubham NetworkManager[760]: <info> [1630434028.4252] dhcp4 (wlp6s0): option domain_name_servers => '192.168.43.1'
Aug 31 23:50:28 shubham dbus-daemon[759]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=760 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Aug 31 23:50:28 shubham NetworkManager[760]: <info> [1630434028.4253] dhcp4 (wlp6s0): option expiry => '1630437628'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4253] dhcp4 (wlp6s0): option host_name => 'shubham'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4253] dhcp4 (wlp6s0): option ip_address => '192.168.43.42'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4253] dhcp4 (wlp6s0): option next_server => '192.168.43.1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4253] dhcp4 (wlp6s0): option requested_broadcast_address => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4254] dhcp4 (wlp6s0): option requested_domain_name => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4254] dhcp4 (wlp6s0): option requested_domain_name_servers => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4254] dhcp4 (wlp6s0): option requested_domain_search => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4254] dhcp4 (wlp6s0): option requested_host_name => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4254] dhcp4 (wlp6s0): option requested_interface_mtu => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4255] dhcp4 (wlp6s0): option requested_ms_classless_static_routes => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4255] dhcp4 (wlp6s0): option requested_nis_domain => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4255] dhcp4 (wlp6s0): option requested_nis_servers => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4255] dhcp4 (wlp6s0): option requested_ntp_servers => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4255] dhcp4 (wlp6s0): option requested_rfc3442_classless_static_routes => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4256] dhcp4 (wlp6s0): option requested_root_path => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4256] dhcp4 (wlp6s0): option requested_routers => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4256] dhcp4 (wlp6s0): option requested_static_routes => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4256] dhcp4 (wlp6s0): option requested_subnet_mask => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4256] dhcp4 (wlp6s0): option requested_time_offset => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4257] dhcp4 (wlp6s0): option requested_wpad => '1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4257] dhcp4 (wlp6s0): option routers => '192.168.43.1'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4257] dhcp4 (wlp6s0): option subnet_mask => '255.255.255.0'
Aug 31 23:50:29 shubham NetworkManager[760]: <info> [1630434028.4257] dhcp4 (wlp6s0): state changed extended -> extended
Aug 31 23:50:29 shubham systemd[1]: Starting Network Manager Script Dispatcher Service...
Aug 31 23:50:29 shubham dbus-daemon[759]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug 31 23:50:29 shubham systemd[1]: Started Network Manager Script Dispatcher Service.
Aug 31 23:50:39 shubham systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Sep 1 00:00:14 shubham systemd[1]: Condition check resulted in Rotate log files being skipped.
Sep 1 00:00:14 shubham systemd[1]: Condition check resulted in Daily man-db regeneration being skipped.
Sep 1 00:02:45 shubham systemd[1164]: vte-spawn-ff25dd9e-05d3-494e-829d-225c70a249c8.scope: Succeeded.
Sep 1 00:02:45 shubham systemd[1164]: gnome-terminal-server.service: Succeeded.
Sep 1 00:02:48 shubham dbus-daemon[1194]: [session uid=1000 pid=1194] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.2655' (uid=1000 pid=20490 comm="/usr/bin/gnome-terminal.real " label="unconfined")
Sep 1 00:02:48 shubham systemd[1164]: Starting GNOME Terminal Server...
Sep 1 00:02:48 shubham dbus-daemon[1194]: [session uid=1000 pid=1194] Successfully activated service 'org.gnome.Terminal'
Sep 1 00:02:48 shubham systemd[1164]: Started GNOME Terminal Server.
Sep 1 00:02:49 shubham systemd[1164]: Started VTE child process 20500 launched by gnome-terminal-server process 20493.
Sep 1 00:02:51 shubham systemd[1]: Stopping Session c1 of user shubham.
Sep 1 00:02:52 shubham ModemManager[879]: <info> Caught signal, shutting down...
Sep 1 00:02:54 shubham systemd[1]: Removed slice system-modprobe.slice.
Sep 1 00:02:54 shubham bluetoothd[756]: Terminating
Sep 1 00:02:54 shubham at-spi-bus-launcher[1292]: X connection to :0 broken (explicit kill or server shutdown).
Sep 1 00:02:54 shubham systemd[1]: Removed slice system-systemd\x2dcoredump.slice.
Sep 1 00:02:55 shubham thermald[797]: Terminating ...
Sep 1 00:02:55 shubham systemd[1]: Stopped target Graphical Interface.
Sep 1 00:02:55 shubham blkdeactivate[20509]: Deactivating block devices:
Sep 1 00:02:55 shubham bluetoothd[756]: Endpoint unregistered: sender=:1.32 path=/MediaEndpoint/A2DPSink/sbc
Sep 1 00:02:55 shubham systemd[1]: Stopped target Multi-User System.
Sep 1 00:02:55 shubham bluetoothd[756]: Endpoint unregistered: sender=:1.32 path=/MediaEndpoint/A2DPSource/sbc
Sep 1 00:02:55 shubham systemd[1]: Stopped target Login Prompts.
Sep 1 00:02:55 shubham systemd[1]: Stopped target Sound Card.
Sep 1 00:02:55 shubham thermald[797]: terminating on user request ..
Sep 1 00:02:55 shubham systemd[1]: Stopped target Timers.
Sep 1 00:02:55 shubham systemd[1]: anacron.timer: Succeeded.
Sep 1 00:02:55 shubham systemd[1]: Stopped Trigger anacron every hour.
Sep 1 00:02:55 shubham systemd[1]: apt-daily-upgrade.timer: Succeeded.
Sep 1 00:02:55 shubham systemd[1]: Stopped Daily apt upgrade and clean activities.
Sep 1 00:02:55 shubham systemd[1]: apt-daily.timer: Succeeded.
Sep 1 00:02:55 shubham bluetoothd[756]: Stopping SDP server
Sep 1 00:02:55 shubham systemd[1]: Stopped Daily apt download activities.
Sep 1 00:02:55 shubham bluetoothd[756]: Exit
Sep 1 00:02:55 shubham systemd[1]: e2scrub_all.timer: Succeeded.
Sep 1 00:02:55 shubham systemd[1]: Stopped Periodic ext4 Online Metadata Check for All Filesystems.
Sep 1 00:02:55 shubham systemd[1]: fstrim.timer: Succeeded.
Sep 1 00:02:55 shubham systemd[1]: Stopped Discard unused blocks once a week.
Sep 1 00:02:55 shubham systemd[1]: fwupd-refresh.timer: Succeeded.
Sep 1 00:02:55 shubham systemd[1]: Stopped Refresh fwupd metadata regularly.
Sep 1 00:02:55 shubham systemd[1]: logrotate.timer: Succeeded.
Sep 1 00:02:55 shubham systemd[1]: Stopped Daily rotation of log files.
Sep 1 00:02:55 shubham systemd[1]: man-db.timer: Succeeded.
Sep 1 00:02:55 shubham systemd[1]: Stopped Daily man-db regeneration.
Sep 1 00:02:55 shubham systemd[1]: motd-news.timer: Succeeded.
Sep 1 00:02:55 shubham systemd[1]: Stopped Message of the Day.
Sep 1 00:02:55 shubham systemd[1]: systemd-tmpfiles-clean.timer: Succeeded.
Sep 1 00:02:55 shubham systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Sep 1 00:02:55 shubham systemd[1]: lvm2-lvmpolld.socket: Succeeded.
Sep 1 00:02:55 shubham systemd[1]: Closed LVM2 poll daemon socket.
Sep 1 00:02:55 shubham systemd[1]: systemd-rfkill.socket: Succeeded.
Sep 1 00:02:55 shubham systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Sep 1 00:02:55 shubham systemd[1]: Stopping Modem Manager...
Sep 1 00:02:55 shubham systemd[1]: Stopping Accounts Service...
Sep 1 00:02:55 shubham systemd[1]: Stopping ACPI event daemon...
Sep 1 00:02:55 shubham systemd[1]: Stopping Save/Restore Sound Card State...
Sep 1 00:02:55 shubham systemd[1]: Stopping Availability of block devices...
Sep 1 00:02:55 shubham systemd[1]: Stopping Bluetooth service...
Sep 1 00:02:55 shubham systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Sep 1 00:02:55 shubham systemd[1]: Stopping Regular background program processing daemon...
Sep 1 00:02:55 shubham systemd[1]: Stopping Make remote CUPS printers available locally...
Sep 1 00:02:55 shubham systemd[1]: Stopping Create final runtime dir for shutdown pivot root...
Click to expand...
 
Running dmesg may help too as that log you posted has a lot of output. Anyway:
I can't tell you how to fix it but I do know of a temporary fix.

Press CTRL + ALT + F1 or F2 to get a terminal.
Once your in the terminal type:

sudo shutdown -h now

And than press Enter.

Your machine should shut down.
 
You must log in or register to reply here.

Members online

Total: 812 (members: 5, guests: 807)

Latest posts

Top