computer will not shut down

[Headrushindi]

**Distribution POP OS newest

bug description: Upon shutdown the OS will shutdown/ however the computer will not. In fact I have tried several suggested terminal commands and None seem to do any good.

**Steps to reproduce : happens upon every shutdown

Other Notes:Simply trying to find a solution. The system I am running it on is several years old and WAS at one time a video editing system (custom build) AMD graphics 4 gig/ 6 core processor/ 16 gigs ram/ Not an off the shelf build

[mmstick]

Haven't seen this occur on any of the systems in our lab. This is likely due to a firmware bug in your motherboard.

[jmachen]

I am experiencing the same thing. Doesn't happen with any other distro.

Edited to add the following details:

Razer Blade Stealth Intel Core i7-6500U @ 2.5 Ghz 8 GB RAM Pop!_OS 19.04 Intel Motherboard "SKYBAY" BIOS Version 2.02 SMBIOS Version 3.0 Secure Boot Off

Switched over from Ubuntu 19.04, but have also successfully used Ubuntu 16.04+, SuSE, and Linux Mint 17

Desktop shuts down and leaves system at an infinite flashing cursor. Console completely unresponsive to all keyboard input.

[PRich13]

I've got the same behaviour here. It didn't happen on my previous install of pop os but I accidentally uninstalled python which broke a load of stuff so I did a complete fresh install using the Nvidia iso.

[voliveira89]

It's happen to me too on a new Dell Vostro.

[technovasation]

Yeah happening to me as well. Have to hold the power button down to kill the machine.

Dell Xps 13 i7 8th gen 16gb ram 512gb ssd etc

[ShashankaNataraj]

This is happening for me too. What is the update on this?!

Haven't seen this occur on any of the systems in our lab. This is likely due to a firmware bug in your motherboard.

I have tried shutting down with Manjaro, Elementary OS and Ubuntu. All of them are able too shut down and reboot correctly.

[gati3478]

Same here, it's a shame there is no well-documented solution to this

[Chezzy2016]

This is my first post on git hub. I've just had the same issue on my Lenovo all in one desktop. I've been playing with different distros and have installed fedora, manjaro, elementary and the previous distro MX Linux without issue.

After a clean install of Pop OS Nvidia I was unable to shutdown the machine, It would just hang on a blank screen, the only key that would do anything was the esc key, which seemed to restart the shut down process and terminate with a cryptography and cryptswap error.

Editing /etc/crypttab and /etc/fstab and placing a # infront the cryptswap lines to disable it seems to have fixed the problem.

I have a 500GB hybrid drive in the computer and am not sure if the problem is caused by this type of drive, as I have also installed Pop OS on a Lenovo Y70/70 Gaming laptop and a Spectre X360 without issue.

[dantxal]

I was having this problem on my new Oryx Pro, less than 1 month old, and the system was build by System76 so, I dont think I could have done something wrong. I did update the firmware (the one S76 provides). But that didnt fix it

Editing /etc/crypttab and /etc/fstab and placing a # infront the cryptswap lines to disable it seems to have fixed the problem.

Looks like this worked for me. Thank you @Chezzy2016

[codexp]

Happens to me too, on a Lenovo X1 gen2:

Latest Pop!_OS 20.04 LTS 64-bit
Intel® Core™ i7-9750H CPU @ 2.60GHz × 12
16 GB Ram
512 GB SSD

[tdukai]

Same problem Pop OS 20.x LTS on HP laptop. Before I used Ubuntu 18.x LTS on it, worked perfectly. With the new OS hardware shutdown never achieved, leaving the machine idling with a blank screen.

[Carlisle96]

I got the same Problem on Pop OS 20.04. I used 16.04 elementary OS before and worked fine.

X1 Carbon (2017) 5th Generation i7-7500U Default Kernel 5.4.0 in a fresh install ( problem persists with newest mainline kernel )

The Laptop stays frozen with this output:

output.txt

[DarthMarino]

Editing /etc/crypttab and /etc/fstab and placing a # infront the cryptswap lines to disable it seems to have fixed the problem.

This workaround also worked for me. Thank you @Chezzy2016

[mohang13]

I've been struggling with this issue for around a year with my MSI GE62 2QD, tried many solutions nothing worked for me. Finally, the solution by @Chezzy2016 solved it. Thank you.

[luispe]

I get the same problem, any solution please?

Information:

System Information
    Manufacturer: System76
    Product Name: Lemur Pro
    Version: lemp10
    UUID: Not Settable
    Wake-up Type: Reserved
    SKU Number: Not Specified
    Family: Not Specified
System Boot Information
    Status: No errors detected

---

BIOS Information
    Vendor: coreboot
    Version: 2021-02-04_be04aea
    Release Date: 02/01/2021
    ROM Size: 16 MB
    Characteristics:
        PCI is supported
        PC Card (PCMCIA) is supported
        BIOS is upgradeable
        Selectable boot is supported
        ACPI is supported
        Targeted content distribution is supported
    BIOS Revision: 4.13
    Firmware Revision: 0.0

---

Processor Information
    Socket Designation: CPU0
    Type: Central Processor
    Family: Pentium Pro
    Manufacturer: GenuineIntel
Version: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz

uname -r information

5.11.0-7612-generic

The workaround to https://github.com/pop-os/pop/issues/530#issuecomment-553168283 not worked for me :(

[raymondgggg]

Started happening to me when I updated to the latest firmware on my Lemur pro as well.

[groomit]

Same here - Clevo NV41ME on 20.10 used to work fine until recently. https://github.com/pop-os/pop/issues/530#issuecomment-553168283 did not work. When booting into old-kernel-config (F12 bootoption) everything is working fine. Maybe some update broke config? Maybe kernel 5.11 related?

[jsinsf]

+1 same as @raymondgggg Started happening when I updated to the latest firmware on Lemur pro (lemp10).

What's up System76?

[victor-andreescu]

Same as @groomit

[megusta-01]

Have same problem! After fresh install everything worked fine than I modified fstab and installed some apps, and got this problem. With ubuntu, same apps and fstab, I doesn't have this problems!

[DanielMenke]

Same problem here!

[bflanagin]

@jsinsf, @raymondgggg we found and applied a fix for the Lemur (lemp10) can you confirm that its now working with 5.11?

[luispe]

@jsinsf, @raymondgggg we found and applied a fix for the Lemur (lemp10) can you confirm that its now working with 5.11?

I have a Lemur (Lemp10) and 5.11 and if I am connected to an external monitor it does not turn off

[jsinsf]

@bflanagin this is resolved for me. Thanks to you and team for your efforts.

Before the 5.11 resolution, I noticed that powering off from terminal seemed to work fine. It was hit or miss with the power button.

[philip-bonev]

Same behavior here. For me it started after I changed my graphics card from Nvidia 1070 to AMD RX 6700 XT. I removed all the packages related to nvidia driver and the card is working ok. I don't have cryptswap.

[Admiral208]

I am also seeing this issue. Recently installed Pop for the first time on MSI GS60 Ghost 2PC. This appears to only be an issue when using the discrete nvidia graphics card in Hybrid or Nvidia graphics mode. If I am using the integrated graphics mode, shutdown seems to be working normally.

[gkmngrgn]

With the last kernel update (5.15.5-76051505), I reproduced this issue on my ThinkPad X260:

system         20F6007VTX (LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260)
processor      Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
memory         16GiB SODIMM DDR4 Synchronous 2133 MHz (0.5 ns)
bridge         Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers
display        Skylake GT2 [HD Graphics 520]
bus            Sunrise Point-LP USB 3.0 xHCI Controller
bus            xHCI Host Controller
generic        EMV Smartcard Reader
communication  Bluetooth wireless interface
multimedia     Integrated Camera
generic        VFS 5011 fingerprint sensor
bus            xHCI Host Controller
generic        Sunrise Point-LP Thermal subsystem
communication  Sunrise Point-LP CSME HECI #1
storage        Sunrise Point-LP SATA Controller [AHCI mode]
bridge         Sunrise Point-LP PCI Express Root Port #1
generic        RTS522A PCI Express Card Reader
bridge         Sunrise Point-LP PCI Express Root Port #3
network        Wireless 8260
bridge         Sunrise Point-LP LPC Controller
memory         Memory controller
multimedia     Sunrise Point-LP HD Audio
bus            Sunrise Point-LP SMBus
network        Ethernet Connection I219-V
disk           256GB SAMSUNG MZ7TY256

I tried to reproduce the same issue with the old kernel, but it's working well:

Linux anarres 
5.13.0-7620-generic #20~1634827117~20.04~874b071-Ubuntu 
SMP Fri Oct 29 15:53:28 UTC  x86_64 x86_64 x86_64 GNU/Linux

[anika200]

Having same non shutdown issue on System76 Galago Pro Version galu1 with PppOS. Just reboots after you choose shutdown and then goes into suspend. Cant even hold the power button down to turn it off, it just reboots. Tried not mounting the swap as above but of course that has nothing to do with it. Should I be trying a different firmware from Clevo? Is it being worked on? Different OS?

Quick update, I tried reverting to older kernel but I think since I did a release update I can only go back to 5.15.5. I am going to downgrade somehow and see what happens.

[anika200]

Success ! I had to downgrade the kernel to 5.3 for it to work normal again. Luckily when I did the Release-upgrade popos left everything in place from the really old kernel. So in that case you only need one like to revert back.

sudo kernelstub -v -k /boot/vmlinuz-5.3.0-7648-generic -i /boot/initrd.img-5.3.0-7648-generic

[gkmngrgn]

I tested the new kernel:

Linux anarres 
5.15.8-76051508-generic #202112141040~1639505278~20.04~0ede46a-Ubuntu 
SMP Fri Dec 17 19: x86_64 x86_64 x86_64 GNU/Linux

The problem seems still not solved.

[kiwib0y]

I got the same problem with a clean install on 21.10 a couple of days ago. The only workaround for me was to install a custom kernel.

Try this one XanMod Kernel Project. It solved the issue for me.

[Quemoy]

EDIT 1/20/2021: both installations now have trouble shutting down. See new post at bottom.

---

I installed 21.10 first and then 20.04 LTS on a separate drive. Shutdown is working on 20.04 LTS (EDIT: no longer works), but not on 21.10. When shutting down on 21.10, the screen turns into a blinking cursor which eventually becomes solid. The only way to proceed from that point is to do a hard shutdown via the power button.

I did notice at one of the shutdown prompt that there was a warning message along the line of failed to finalize system, ignoring during either a shutdown or reset.

Here are the system info from both installations:

20.04 LTS:

OS: Pop!_OS 20.04 LTS x86_64 
Kernel: 5.13.0-7620-generic 
Uptime: 4 mins 
Packages: 1785 (dpkg) 
Shell: bash 5.0.17 

21.10

OS: Pop!_OS 21.10 x86_64 
Kernel: 5.15.11-76051511-generic 
Uptime: 6 mins 
Packages: 1843 (dpkg) 
Shell: bash 5.1.8 

Components:

CPU: 12th Gen Intel i7-12700K (20) @ 6.300GHz 
Motherboard: ASUS TUF Gaming Z690-PLUS WiFi D4
Memory: 4 x Crucial Ballistix Max DDR4-4400
GPU: NVIDIA GeForce GTX 1660 SUPER 

I then proceeded to install 20.04 LTS to the same drive I installed 21.10 to. I was able to shut down the new installation as well (EDIT: no longer works, both versions cannot shutdown). Seems to be an issue with the new kernel?

[acdcjunior]

I got the same problem. New i9 machine, fresh 21.10 install. Shutdown, via terminal or UI, just hangs everything. Editing the swap, booting from older kernel or removing the wifi drivers, nothing makes difference.

Does anyone know at least how can we get some more info on this? Any kind of kernel log or something that gets written when we request a shutdown (via UI or terminal, anything)?

[gkmngrgn]

I think that nobody on the PopOS team thinks this problem is serious. Indeed I would like to be able to solve it myself, but I haven't found a solution yet. Staying with the old kernel is a temporary solution.

[leviport]

I think that nobody on the PopOS team thinks this problem is serious.

Not true. We just haven't been able to reproduce the issue. If we can't make it happen, finding a fix is extremely difficult.

[acdcjunior]

How about debugging, any tips on that?

PS.: For me, it works (shutdown no longer freezes) when I install XanMod (in my case, it is a fresh 21.10 install), but I'd prefer not to install it.

[leviport]

An excerpt of a journalctl log at time of failed shutdown might contain some clues

[jmbuhr]

I am experiencing the same issue, though I suspect it might be related to trying out one of the new intel 12th gen processors for which I assume I should have waited for the next kernel. But maybe there are more clues in the journalctl output. When I try to shut down the last line I see is: Reached target Shutdown. I copieed the journalctl output starting at that line:

output.txt

[mgerb]

Experiencing the same thing as well. New installation of OS with the following hardware on kernel version Kernel: Linux 5.15.11-76051511-generic:

CPU

12th Gen Intel(R) Core(TM) i7-12700K

MOBO

Manufacturer: ASUSTeK COMPUTER INC.
Product Name: TUF GAMING Z690-PLUS WIFI D4
Version: Rev 1.xx

GPU

NVIDIA Corporation GA102 [GeForce RTX 3080]

[jmbuhr]

This increases my suspicion for the CPU being the culprit. I have the same motherboard chipset. I also noticed that when running on integrated graphics the image on the screen freezes immediately upon trying to shut down and stays like that, while on a dedicated GPU it gets to the point of shutting down the GPU so there is no more image output (but it still stays on).

Can someone recommend a way of trying out the next kernel 5.16 while retaining an easy option to return to the pop-os included one once that is updated?

[DaveWeinstein]

I've been having this problem for a while (Oryx Pro 4). The following just worked:

$ sudo systemctl cancel $ sudo systemctl reboot

It may also be worth noting that over the same period, the network does not come up on a reboot, requiring $ sudo systemctl restart NetworkManager

[Quemoy]

As it turns out, both 20.04 LTS and 21.10 do not shut down correctly now, no matter whether I install on an NVME or SATA drive. Below is what I see on my screen. Sorry for the photo instead of a text log, I do not know where to find the log. The cursor blinks for a few seconds before becoming completely solid and the only way to proceed from the screen is to do a hard shutdown via power button.

Just for reference, my system has the following:

CPU: 12th Gen Intel i7-12700K (20) @ 6.300GHz 
Motherboard: ASUS TUF Gaming Z690-PLUS WiFi D4
Memory: 4 x Crucial Ballistix Max DDR4-4400
GPU: NVIDIA GeForce GTX 1660 SUPER 

[jmbuhr]

After the automatic update to kernel 5.15.15-76051515-generic it now just works. Did this fix it for you as well? I am so happy!

[michielap]

Same here! Works again after the update.

[leviport]

Glad to hear it! I'll close this for now, but it can be reopened if people are still encountering it.

[jean2q]

Hey guys, i'm having the same problem on the newer kernel.

it only turns off when I hold the power button for ~5 seconds

[leviport]

Sounds like that could be hardware-specific, but I'll reopen. Can you share the make and model of computer/motherboard you have?

[jean2q]

Sounds like that could be hardware-specific, but I'll reopen. Can you share the make and model of computer/motherboard you have?

Hey, leviport. Suddently it has started to shutdown normally. I really don't know what happened. My motherboard is Asrock a320m-HD.

Thanks for your attention anyway.

[leviport]

Sure thing, glad it got better

[bonzoycv]

I've been having this problem for a while (Oryx Pro 4). The following just worked:

$ sudo systemctl cancel $ sudo systemctl reboot

It may also be worth noting that over the same period, the network does not come up on a reboot, requiring $ sudo systemctl restart NetworkManager

Thanks, those steps I could resolve the preblem. Worked for me.