View previous topic :: View next topic |
Author |
Message |
Ryba n00b
Joined: 24 Dec 2010 Posts: 20
|
Posted: Tue Apr 09, 2024 1:34 pm Post subject: System stuck on shutdown |
|
|
Hi. I have an issue when system gets stuck, and when it does it looks like this
https://imgur.com/a/OeyniHt
I don't always get this screen, depending on how i initiate shutdown
I have no idea how to fix or even start to investigate this issue, would be grateful for any suggestions |
|
Back to top |
|
|
kgdrenefort Guru
Joined: 19 Sep 2023 Posts: 312 Location: Somewhere in the 77
|
Posted: Thu Apr 11, 2024 9:36 am Post subject: |
|
|
Hello,
I never used OpenRC, but the first error is:
Code: | openrc-settingsd start-stop-daemon: no matching process found |
I think this is a good start.
Could you also use this command and give us the outputed link :
Code: | wgetpaste /var/log/dmesg |
If you don't have the package wgetpaste, please install it. Also if dmesg is not at the location above, adapt it.
Could you also please provide us:
- Profile in use
- Kernel version (with uname)
Regards,
GASPARD DE RENEFORT Kévin _________________ Traduction wiki, pour praticiper.
Custom logos/biz card/website. |
|
Back to top |
|
|
kgdrenefort Guru
Joined: 19 Sep 2023 Posts: 312 Location: Somewhere in the 77
|
Posted: Thu Apr 11, 2024 9:47 am Post subject: |
|
|
I forgot something that might be important:
How do you shutdown your system ? With a command (which one) ? With a DE (KDE, GNOME… Which one ?).
Regards,
GASPARD DE RENEFORT Kévin _________________ Traduction wiki, pour praticiper.
Custom logos/biz card/website. |
|
Back to top |
|
|
Ryba n00b
Joined: 24 Dec 2010 Posts: 20
|
Posted: Mon Apr 15, 2024 11:21 am Post subject: |
|
|
https://bpa.st/XLUA
Code: |
localhost ~ # eselect profile show
Current /etc/portage/make.profile symlink:
default/linux/amd64/17.1/desktop/gnome
localhost ~ # uname -a
Linux localhost.localdomain 6.8.2-gentoo-x86_64 #1 SMP PREEMPT_DYNAMIC Tue Apr 2 12:16:20 -00 2024 x86_64 Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz GenuineIntel GNU/Linux
localhost ~ #
|
I usually shutdown with GNOME. but command gives similar results (i may or may not get that screen, but system hangs all the same)
I also tried shutting down every daemon manually with rc-config stop and after that system shut down normally.
At this point i suspect either display-manager (because i don't always get that screen) or nix-daemon (because overlay) |
|
Back to top |
|
|
Goverp Advocate
Joined: 07 Mar 2007 Posts: 2167
|
Posted: Mon Apr 15, 2024 2:41 pm Post subject: |
|
|
IIUC, the screen grab says that:
Code: | /etc/NetworkManager/dispatcher.d/10-openrc-status |
fails and that seems to leave a number of processes (such as display-manager-setup) waiting for its shutdown.
There also seems to be some foul-up involving containers and cgroups.
Does any of that make sense with your manually stopping services and getting a successful shutdown? For example, messages when you close NetworkManager. _________________ Greybeard |
|
Back to top |
|
|
Goverp Advocate
Joined: 07 Mar 2007 Posts: 2167
|
Posted: Mon Apr 15, 2024 3:04 pm Post subject: |
|
|
The bloody details from syslog:
Code: | Apr 15 15:11:06 ryzen kernel: kernel: 000000004cbf3f24 kernel_size: 0xd60400
Apr 15 15:11:06 ryzen kernel: Loaded purgatory at 0x82f2fb000
Apr 15 15:11:06 ryzen kernel: Loaded boot_param, command line and misc at 0x82f2f9000 bufsz=0x1440 memsz=0x2000
Apr 15 15:11:06 ryzen kernel: Loaded 64bit kernel at 0x82c000000 bufsz=0xd5c400 memsz=0x2f54000
Apr 15 15:11:06 ryzen kernel: Final command line is: rootfstype=f2fs root=LABEL=gentoo fsck.f2fs=-a settimeout mdadm net.ifnames=0 amd_pstate.shared_mem=1 amd_pstate=guided delayacct
Apr 15 15:11:06 ryzen kernel: E820 memmap:
Apr 15 15:11:06 ryzen kernel: 0000000000000000-000000000009ffff (1)
Apr 15 15:11:06 ryzen kernel: 00000000000a0000-00000000000fffff (2)
Apr 15 15:11:06 ryzen kernel: 0000000000100000-0000000009d1efff (1)
Apr 15 15:11:06 ryzen kernel: 0000000009d1f000-0000000009ffffff (2)
Apr 15 15:11:06 ryzen kernel: 000000000a000000-000000000a1fffff (1)
Apr 15 15:11:06 ryzen kernel: 000000000a200000-000000000a20dfff (4)
Apr 15 15:11:06 ryzen kernel: 000000000a20e000-00000000bd816017 (1)
Apr 15 15:11:06 ryzen kernel: 00000000bd816018-00000000bd833057 (128)
Apr 15 15:11:06 ryzen kernel: 00000000bd833058-00000000bd834017 (1)
Apr 15 15:11:06 ryzen kernel: 00000000bd834018-00000000bd842067 (128)
Apr 15 15:11:06 ryzen kernel: 00000000bd842068-00000000c327ffff (1)
Apr 15 15:11:06 ryzen kernel: 00000000c3280000-00000000c3280fff (2)
Apr 15 15:11:06 ryzen kernel: 00000000c3281000-00000000ca2fdfff (1)
Apr 15 15:11:06 ryzen kernel: 00000000ca2fe000-00000000ca704fff (2)
Apr 15 15:11:06 ryzen kernel: 00000000ca705000-00000000ca87bfff (3)
Apr 15 15:11:06 ryzen kernel: 00000000ca87c000-00000000cac7cfff (4)
Apr 15 15:11:06 ryzen kernel: 00000000cac7d000-00000000cb9fefff (2)
Apr 15 15:11:06 ryzen kernel: 00000000cb9ff000-00000000ccffffff (1)
Apr 15 15:11:06 ryzen kernel: 00000000cd000000-00000000cfffffff (2)
Apr 15 15:11:06 ryzen kernel: 00000000f0000000-00000000f7ffffff (2)
Apr 15 15:11:06 ryzen kernel: 00000000fd200000-00000000fd2fffff (2)
Apr 15 15:11:06 ryzen kernel: 00000000fd400000-00000000fd5fffff (2)
Apr 15 15:11:06 ryzen kernel: 00000000fea00000-00000000fea0ffff (2)
Apr 15 15:11:06 ryzen kernel: 00000000feb80000-00000000fec01fff (2)
Apr 15 15:11:06 ryzen kernel: 00000000fec10000-00000000fec10fff (2)
Apr 15 15:11:06 ryzen kernel: 00000000fed00000-00000000fed00fff (2)
Apr 15 15:11:06 ryzen kernel: 00000000fed40000-00000000fed44fff (2)
Apr 15 15:11:06 ryzen kernel: 00000000fed80000-00000000fed8ffff (2)
Apr 15 15:11:06 ryzen kernel: 00000000fedc2000-00000000fedcffff (2)
Apr 15 15:11:06 ryzen kernel: 00000000fedd4000-00000000fedd5fff (2)
Apr 15 15:11:06 ryzen kernel: 00000000ff000000-00000000ffffffff (2)
Apr 15 15:11:06 ryzen kernel: 0000000100000000-000000082f2fffff (1)
Apr 15 15:11:06 ryzen kernel: 000000082f300000-000000082fffffff (2)
Apr 15 15:11:06 ryzen kernel: nr_segments = 3
Apr 15 15:11:06 ryzen kernel: segment[0]: buf=0x00000000771f7896 bufsz=0x4000 mem=0x82f2fb000 memsz=0x5000
Apr 15 15:11:06 ryzen kernel: segment[1]: buf=0x00000000725471e2 bufsz=0x1440 mem=0x82f2f9000 memsz=0x2000
Apr 15 15:11:06 ryzen kernel: segment[2]: buf=0x00000000f0656f7a bufsz=0xd5c400 mem=0x82c000000 memsz=0x2f54000
Apr 15 15:11:06 ryzen kernel: kexec_file_load: type:0, start:0x82f2fb1f0 head:0x1a1fc4002 flags:0x4 |
After which it simply reboots in the usual long-winded way. _________________ Greybeard |
|
Back to top |
|
|
|