stuck on 'Reached target SHUTDOWN' pc still running

shinoq · 01-20-2022, 11:45 AM

Hi,
after update kernel from 5.11 to Linux 5.13.0-27-generic on Ubuntu 20.04.3 LTS system is stuck after shutdown on black screen with console cursor flashing in left right corner. I have tried grub or deamon fix. Tried to wait but it never shuts down. Also left grub line GRUB_CMDLINE_LINUX_DEFAULT="" to see logs as they process but not working on shutdown/restart, keeps freezing. Only pressing power button for 5 seconds works.

Here are my logs from journalctl -rb -1 command:

https://paste.ubuntu.com/p/VgdFxJXYcY/

hardware:
AMD Ryzen 5 4500U with Radeon Graphics Renoir
chipset: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge
MB: ASUSTeK COMPUTER INC. PN50
wifi: intel AX200
ethernet: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

I managed to install other kernels and boot on kernel 5.11 but it's not booting up properly, only one monitor works and no networking at all. It happens same up to kernel Linux 5.13.0-23-generic, once I boot from Linux 5.13.0-25-generic it's all good, just no reboot nor shutdown. Do I really need to reinstall :/

mrmazda · 01-20-2022, 02:58 PM

That log contains 61 lines with the string "fail" in it, most seem to be related to Gnome or dbus. Try this: boot by appending 3 to the end of the line beginning with "linu" after striking the E key at the Grub menu, then proceeding with boot. Log in when a shell login prompt appears, then do "sudo systemctl reboot". Does reboot succeed promptly?

shinoq · 01-20-2022, 05:17 PM

Hey, thanks for replay,
here is what I get after hitting E in GRUB and also two new lines appeared after getting shutdown target in the attachments. Thank you for any insight.

mrmazda · 01-20-2022, 05:43 PM

After hitting the E key you should see several lines, one of which begins with linu. It probably wraps. At the end of the wrapped line you need a space and a 3 added before proceeding with boot.

shinoq · 01-21-2022, 02:20 AM

Looks like it's a fresh bug:
https://bugs.launchpad.net/ubuntu/+s...3/+bug/1958519

I can;'t find anything after hitting E in GRUB. Also when I try to run 5.11.0-46-generic it is rebooting/shutting down, however one of my monitors is not working ( I have one connected via hdmi and one via DP, the hdmi is not being detected) and no networking detected either, like I had no chipset on the system at all....

mrmazda · 01-21-2022, 02:41 AM

Quote:

Originally Posted by shinoq

I can;'t find anything after hitting E in GRUB.

Are you familiar with what a working Grub menu should look or work like? Is what you expect what you see after POST completes? Is the highlight in the Grub menu on any Ubuntu menu entry when striking E?

shinoq · 01-21-2022, 02:49 AM

Quote:

Originally Posted by mrmazda

Are you familiar with what a working Grub menu should look or work like? Is what you expect what you see after POST completes? Is the highlight in the Grub menu on any Ubuntu menu entry when striking E?

No never seen Grub before this issue. It's the same on each menu entry. What is more annoying I can't boot 5.11 since it;s not booting up properly, no hdmi or lan detected... so basically I have no working kernel at all. It's like that up to 5.13.0-23. When booting up from 5.13.0-25 or 5.13.0-27 all detected but no shutdown/restart. Thinking about installing 5.08 or so...

mrmazda · 01-21-2022, 12:16 PM

It sounds like you're not reaching a Grub menu, and that's why E doesn't produce an expected response. Yet, you write about using different kernels, some of which boot normally. What exactly do you see when POST completes? Do you have auto login configured, and/or Grub menu to not automatically appear?

No LAN detected and only one monitor detected can happen when you install a kernel without accompanying kernel modules. For each linux-image you need linux-modules and possibly also linux-modules-extra installed at the same time. Lack of detection can also happen when your hardware is newer than your operating system's original release date, and thus isn't supported.

What is output from sudo efibootmgr?

shinoq · 01-21-2022, 01:56 PM

So I am such a newb I was hitting E before selecting menu entry of kernel version

I managed to put '3' at the end of the line which started with linux. It booted into black login screen, I logged into and used sudo systemctl restart gdm to enable GUI, all worked but nothing has changed.
This is the output of sudo efibootmgr

BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002
Boot0002* ubuntu

Can I install missing modules for kernel? I recently installed few kernels to test using sudo apt-get install linux-image-5.11.0-46-generic and so on, not sure if it also install modules.

[edit]
looks like I am missing modules extra for 5.11:
linux-base/focal-updates,focal-updates,now 4.5ubuntu3.7 all [installed,automatic]
linux-firmware/focal-updates,focal-updates,now 1.187.25 all [installed,automatic]
linux-generic-hwe-20.04/focal-updates,focal-security,now 5.13.0.27.29~20.04.13 amd64 [installed]
linux-headers-5.13.0-25-generic/focal-updates,focal-security,now 5.13.0-25.26~20.04.1 amd64 [installed,automatic]
linux-headers-5.13.0-27-generic/focal-updates,focal-security,now 5.13.0-27.29~20.04.1 amd64 [installed,automatic]
linux-headers-generic-hwe-20.04/focal-updates,focal-security,now 5.13.0.27.29~20.04.13 amd64 [installed,automatic]
linux-hwe-5.13-headers-5.13.0-25/focal-updates,focal-updates,focal-security,focal-security,now 5.13.0-25.26~20.04.1 all [installed,automatic]
linux-hwe-5.13-headers-5.13.0-27/focal-updates,focal-updates,focal-security,focal-security,now 5.13.0-27.29~20.04.1 all [installed,automatic]
linux-image-5.11.0-46-generic/focal-updates,focal-security,now 5.11.0-46.51~20.04.1 amd64 [installed]
linux-image-5.13.0-21-generic/focal-updates,focal-security,now 5.13.0-21.21~20.04.1 amd64 [installed]
linux-image-5.13.0-22-generic/focal-updates,focal-security,now 5.13.0-22.22~20.04.1 amd64 [installed]
linux-image-5.13.0-23-generic/focal-updates,focal-security,now 5.13.0-23.23~20.04.2 amd64 [installed]
linux-image-5.13.0-25-generic/focal-updates,focal-security,now 5.13.0-25.26~20.04.1 amd64 [installed,automatic]
linux-image-5.13.0-27-generic/focal-updates,focal-security,now 5.13.0-27.29~20.04.1 amd64 [installed,automatic]
linux-image-generic-hwe-20.04/focal-updates,focal-security,now 5.13.0.27.29~20.04.13 amd64 [installed,automatic]
linux-modules-5.11.0-46-generic/focal-updates,focal-security,now 5.11.0-46.51~20.04.1 amd64 [installed,automatic]
linux-modules-5.13.0-21-generic/focal-updates,focal-security,now 5.13.0-21.21~20.04.1 amd64 [installed,automatic]
linux-modules-5.13.0-22-generic/focal-updates,focal-security,now 5.13.0-22.22~20.04.1 amd64 [installed,automatic]
linux-modules-5.13.0-23-generic/focal-updates,focal-security,now 5.13.0-23.23~20.04.2 amd64 [installed,automatic]
linux-modules-5.13.0-25-generic/focal-updates,focal-security,now 5.13.0-25.26~20.04.1 amd64 [installed,automatic]
linux-modules-5.13.0-27-generic/focal-updates,focal-security,now 5.13.0-27.29~20.04.1 amd64 [installed,automatic]
linux-modules-extra-5.13.0-25-generic/focal-updates,focal-security,now 5.13.0-25.26~20.04.1 amd64 [installed,automatic]
linux-modules-extra-5.13.0-27-generic/focal-updates,focal-security,now 5.13.0-27.29~20.04.1 amd64 [installed,automatic]
linux-sound-base/focal,focal,now 1.0.25+dfsg-0ubuntu5 all [installed,automatic]

How can I install specific modules? can't find it on the web :/
Thanks
Thanks

mrmazda · 01-21-2022, 05:23 PM

Quote:

Originally Posted by shinoq

Code:

# sudo efibootmgr
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002
Boot0002* ubuntu

OK here.

Quote:

Can I install missing modules for kernel? I recently installed few kernels to test using sudo apt-get install linux-image-5.11.0-46-generic and so on, not sure if it also install modules.
...
linux-image-5.11.0-46-generic/focal-updates,focal-security,now 5.11.0-46.51~20.04.1 amd64 [installed]
linux-modules-5.11.0-46-generic/focal-updates,focal-security,now 5.11.0-46.51~20.04.1 amd64 [installed,automatic]
...
How can I install specific modules? can't find it on the web :/

I don't know why you have modules extra for some and not others. All distros I'm aware of package modules in groups; some in a group of one, others in more than one group. To add modules-extra for 5.11, do:

Code:

sudo apt install linux-modules-extra-5.11.0-46-generic

What was your reason for installing all those kernels? You only need one.

I have here:

Code:

# inxi -Sy
System:
  Host: ara88 Kernel: 5.4.0-96-generic x86_64 bits: 64
    Desktop: Trinity R14.1.0 Distro: Ubuntu 20.04.3 LTS (Focal Fossa)
# inxi -Gayz
 Graphics:
  Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu
    v: kernel alternate: radeon bus-ID: 00:01.0 chip-ID: 1002:1313
    class-ID: 0300
  Display: x11 server: X.Org 1.20.13 driver: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa alternate: ati display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1200 s-dpi: 120 s-size: 812x254mm (32.0x10.0")
    s-diag: 851mm (33.5")
  Monitor-1: DisplayPort-0 res: 1920x1200 hz: 60 dpi: 94
    size: 519x324mm (20.4x12.8") diag: 612mm (24.1")
  Monitor-2: HDMI-A-0 res: 1920x1080 hz: 60 dpi: 305
    size: 160x90mm (6.3x3.5") diag: 184mm (7.2")
  OpenGL: renderer: AMD KAVERI (DRM 3.35.0 5.4.0-96-generic LLVM 12.0.0)
    v: 4.6 Mesa 21.0.3 direct render: Yes

uteck · 01-21-2022, 08:54 PM

This link has some help:
https://askubuntu.com/questions/1029...ck-at-shutdown
Might help you even with 20.04.

On side note, back in the day my Linux guru ran a firewall this way. The network card and iptables rules were still running even at the hanging shutdown, so if anyone tried stuff the system was read-only so hacking was difficult. It still passed traffic and worked as a fireall, but was otherwise unusable until the power button was pressed and rebooted.

shinoq · 01-22-2022, 02:12 AM

Quote:

Originally Posted by mrmazda

What was your reason for installing all those kernels?

I was running on 5.11 and few days ago updater upgraded kernel to 5.13, that was the starting point of reboot/shutdown issues and I started to troubleshooting and installing kernels to test.

mrmazda · 01-22-2022, 02:31 AM

If it was mine I'd boot the 5.11 kernel to apt purge each of the 5.13 kernels and modules, then check how things stand before deciding how to proceed. Also paste here output from cat /etc/apt/sources.list.

shinoq · 01-22-2022, 02:38 PM

After installing modules-extra all fine on Linux 5.11.0-46-generic. Thank you so much

Now how can I use apt purge to remove all other kernels?
==================================================================================================== ==========
this is the output:
cat /etc/apt/sources.list
# deb cdrom:[Ubuntu 20.04 LTS _Focal Fossa_ - Release amd64 (20200423)]/ focal main restricted

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://gb.archive.ubuntu.com/ubuntu/ focal main restricted
# deb-src http://gb.archive.ubuntu.com/ubuntu/ focal main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://gb.archive.ubuntu.com/ubuntu/ focal-updates main restricted
# deb-src http://gb.archive.ubuntu.com/ubuntu/ focal-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://gb.archive.ubuntu.com/ubuntu/ focal universe
# deb-src http://gb.archive.ubuntu.com/ubuntu/ focal universe
deb http://gb.archive.ubuntu.com/ubuntu/ focal-updates universe
# deb-src http://gb.archive.ubuntu.com/ubuntu/ focal-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://gb.archive.ubuntu.com/ubuntu/ focal multiverse
# deb-src http://gb.archive.ubuntu.com/ubuntu/ focal multiverse
deb http://gb.archive.ubuntu.com/ubuntu/ focal-updates multiverse
# deb-src http://gb.archive.ubuntu.com/ubuntu/ focal-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://gb.archive.ubuntu.com/ubuntu/ focal-backports main restricted universe multiverse
# deb-src http://gb.archive.ubuntu.com/ubuntu/ focal-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu focal partner
# deb-src http://archive.canonical.com/ubuntu focal partner

deb http://security.ubuntu.com/ubuntu focal-security main restricted
# deb-src http://security.ubuntu.com/ubuntu focal-security main restricted
deb http://security.ubuntu.com/ubuntu focal-security universe
# deb-src http://security.ubuntu.com/ubuntu focal-security universe
deb http://security.ubuntu.com/ubuntu focal-security multiverse
# deb-src http://security.ubuntu.com/ubuntu focal-security multiverse

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

mrmazda · 01-23-2022, 01:33 AM

I'm guessing you may have needed to enable backports when your PC was new in order to have support for hardware newer than the distro supports by default, thus the reason why the 5.11 kernel. All my 20.04.x installations are running on stock 5.4.x kernels. Purging a kernel is a simple operation for apt, apt-get, aptitude or any of the GUI software managers. Here it would be:

Code:

sudo apt purge linux-image-5.13.0-21-generic

Then repeat for each installed kernel you wish removed.