Since the journal log is not of any value, is there another method that you can suggest for me to use to supply troubleshooting information that will enable you to figure out the cause of the problem? On Wed, Aug 23, 2023 at 10:33 AM Andrei Borzenkov wrote:

On Wed, Aug 23, 2023 at 4:59 PM Mark Misulich wrote:

...

Hi, I've had a problem with my desktop computer for some months, in that it doesn't always shut down completely with opensuse. That is, it's an intermittent problem. The computer is set up as a multiboot, and does always shut down when I shut down Windows. Here are the specs for opensuse and the computer.

I'm running: opensuse Tumbleweed 20230819 KDE Plasma Version 5.27.7 KDE Frameworks Version 5.109.0 Qt Version 5.15.10 Kernel Version 6.4.11-1-default (64-bit) Graphics Platform X11

Hardware Processors 8 x Intel Core i7-7700 CPU @ 3.60GHz Memory 62.7 GiB of RAM Graphics Processor Nvidia GeForce GT 1030/PCIe/SSE2 Manufacturer Gigabyte Technology Co. Ltd. Product Name B250M-DS3H

I tried to run this by the forum to get some answers, and you can see that they haven't been able to figure it out. Here's the hyperlink to the thread:

https://forums.opensuse.org/t/tumbleweed-wont-shut-down/166098/31

The last log shows that most filesystem were unmounted and journald stopped. As journald was stopped, no more useful information past this point will be present.

...

I would appreciate the list's help to try and resolve this issue.

https://freedesktop.org/wiki/Software/systemd/Debugging/#diagnosingshutdownp...

On Wed, 2023-08-23 at 17:24 +0300, Andrei Borzenkov wrote:

On Wed, Aug 23, 2023 at 4:59 PM Mark Misulich wrote:

...

Hi, I've had a problem with my desktop computer for some months, in that it doesn't always shut down completely with opensuse. That is, it's an intermittent problem. The computer is set up as a multiboot, and does always shut down when I shut down Windows.  Here are the specs for opensuse and the computer.

I'm running: opensuse Tumbleweed  20230819 KDE Plasma Version      5.27.7 KDE Frameworks Version  5.109.0 Qt Version              5.15.10 Kernel Version          6.4.11-1-default (64-bit) Graphics Platform       X11

Hardware Processors 8 x Intel Core i7-7700 CPU @ 3.60GHz Memory  62.7 GiB of RAM Graphics Processor Nvidia GeForce GT 1030/PCIe/SSE2 Manufacturer Gigabyte Technology Co. Ltd. Product Name B250M-DS3H

I tried to run this by the forum to get some answers, and you can see that they haven't been able to figure it out.  Here's the hyperlink to the thread:

https://forums.opensuse.org/t/tumbleweed-wont-shut-down/166098/31

The last log shows that most filesystem were unmounted and journald stopped. As journald was stopped, no more useful information past this point will be present.

...

I would appreciate the list's help to try and resolve this issue.

https://freedesktop.org/wiki/Software/systemd/Debugging/#diagnosingshutdownp...

Since the journal log is not of any value, is there another method that you can suggest for me to use to supply troubleshooting information that will enable you to figure out the cause of the problem? Did you read the link I posted?

Yes, I did. I still didn't understand what I was supposed to do once I set up a serial console, hence my post asking for commands to use. The first troubleshooting step listed in your link is to force a shutdown or reboot to determine where the problem originates. The problem is an intermittent problem, and it seems to occur for a while, then it doesn't. I haven't had a problem with the computer not shutting down normally since I last posted on this thread, so I haven't been able to use the initial steps reliably to begin the troubleshooting sequence you suggested. Given the amount of time that has transpired since I last posted, I assume that a regular software update of one sort or another has fixed the problem all on its own, without intervention on my part. Thanks for your help, if the problem reoccurs at a future time, I'll start a new thread. Mark

* Mark Misulich [10-02-23 09:36]:

After almost two months of normal shutdowns, the shutdown problem is back. I read David's post above, and also found this forum thread that resolved the problem the same way:

https://forums.opensuse.org/t/disable-plymouth/137775

I went through step one of the thread by disabling chrony-wait with this command with bash as root:

systemctl disable chrony-wait.service

But it didn't resolve the issue, the computer still hangs on shutdown.

I'm unsure as to how to do the next step to pass the kernel parameter

'plymouth.enable=0"

Where do I insert that? Please forgive my lack of knowledge on this point, and provide me with a bit of further instruction.

add it to the kernel line: yast bootloader -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

I had a shutdown attempt of the computer this afternoon where it didn't shut down, and hung on the shutdown with the line after the localhost login displayed and remained displayed so I could write it down. Here is what I saw: localhost login: [ 9211, 806671] [ T1] reboot; Power down On Tue, Oct 10, 2023 at 3:45 AM Mark Misulich wrote:

I've added the plymouth.enable=0 parameter to the kernel line, and the plymouth is gone now. Most times the computer shuts down without a problem, but even without the plymouth it occasionally still fails to shutdown. The last line in the shutdown is "localhost login" and in failure to shutdown that's where the computer hangs. When it shuts down normally, after a few seconds a word appears to the right of 'localhost login' followed by numbers faster than I can read it, then quickly shuts down in a split second.

On Mon, Oct 2, 2023 at 9:43 AM Patrick Shanahan wrote:

...

* Mark Misulich [10-02-23 09:36]:

...

After almost two months of normal shutdowns, the shutdown problem is back. I read David's post above, and also found this forum thread that resolved the problem the same way:

https://forums.opensuse.org/t/disable-plymouth/137775

I went through step one of the thread by disabling chrony-wait with this command with bash as root:

systemctl disable chrony-wait.service

But it didn't resolve the issue, the computer still hangs on shutdown.

I'm unsure as to how to do the next step to pass the kernel parameter

'plymouth.enable=0"

Where do I insert that? Please forgive my lack of knowledge on this point, and provide me with a bit of further instruction.

add it to the kernel line: yast bootloader

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

On 11.10.2023 03:38, Mark Misulich wrote:

I had a shutdown attempt of the computer this afternoon where it didn't shut down, and hung on the shutdown with the line after the localhost login displayed and remained displayed so I could write it down. Here is what I saw: localhost login: [ 9211, 806671] [ T1] reboot; Power down

That is really the last message before kernel turns off the system. It sounds like kernel issue.

On Tue, Oct 10, 2023 at 3:45 AM Mark Misulich wrote:

...

I've added the plymouth.enable=0 parameter to the kernel line, and the plymouth is gone now. Most times the computer shuts down without a problem, but even without the plymouth it occasionally still fails to shutdown. The last line in the shutdown is "localhost login" and in failure to shutdown that's where the computer hangs. When it shuts down normally, after a few seconds a word appears to the right of 'localhost login' followed by numbers faster than I can read it, then quickly shuts down in a split second.

On Mon, Oct 2, 2023 at 9:43 AM Patrick Shanahan wrote:

...

* Mark Misulich [10-02-23 09:36]:

...

After almost two months of normal shutdowns, the shutdown problem is back. I read David's post above, and also found this forum thread that resolved the problem the same way:

https://forums.opensuse.org/t/disable-plymouth/137775

I went through step one of the thread by disabling chrony-wait with this command with bash as root:

systemctl disable chrony-wait.service

But it didn't resolve the issue, the computer still hangs on shutdown.

I'm unsure as to how to do the next step to pass the kernel parameter

'plymouth.enable=0"

Where do I insert that? Please forgive my lack of knowledge on this point, and provide me with a bit of further instruction.

add it to the kernel line: yast bootloader

-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

On 14.10.2023 19:00, David C. Rankin wrote:

On 10/13/23 14:45, Andrei Borzenkov wrote:

...

On 11.10.2023 03:38, Mark Misulich wrote:

...

I had a shutdown attempt of the computer this afternoon where it didn't shut down, and hung on the shutdown with the line after the localhost login  displayed and remained displayed so I could write it down.  Here is what I saw: localhost login: [  9211, 806671] [  T1] reboot; Power down

That is really the last message before kernel turns off the system. It sounds like kernel issue.

I'm curious. I plymouth is installed, even with plymouth.enable=0, is there any part of a plymouth library loaded by the boot-loader or kernel?

No.

I had an attempted shutdown yesterday that didn't shutdown. It had more than the usual message posted, here it is: localhost login: [10495.617 342] [ T1] reboot:Powerdown [10495.6205841] [t1785] asix 1-5:1.0 enp 0s20f0u5: failed to write reg irdex 0x0000: -19 [10495.623670] [ t1785] asix 1-5:1.0 enp0s20f0u5: failed to enable software MIIaccess Hopefully this will provide more information regarding the source of the failure to shutdown problem. Mark On Sun, Oct 15, 2023 at 8:21 AM Rodney Baker wrote:

On Sunday, 15 October 2023 2:30:54 AM ACDT David C. Rankin wrote:

...

On 10/13/23 14:45, Andrei Borzenkov wrote:

...

On 11.10.2023 03:38, Mark Misulich wrote:

...

I had a shutdown attempt of the computer this afternoon where it didn't shut down, and hung on the shutdown with the line after the localhost login displayed and remained displayed so I could write it down. Here is what I saw: localhost login: [ 9211, 806671] [ T1] reboot; Power down

That is really the last message before kernel turns off the system. It sounds like kernel issue.

I'm curious. I plymouth is installed, even with plymouth.enable=0, is there any part of a plymouth library loaded by the boot-loader or kernel?

The reason I ask is I've run into the shutdown hang ever since Leap 42.X on this HP laptop, but uninstalling plymouth completely has cured the issue 100% of the time.

My thought, may be wrong, but if the boot-loader or loads part of plymouth, even though the kernel parameter plymouth.enable=0 is set, could whatever address holds the part of plymouth be responsible for the hang?

That's the only thing I can think of that would make any difference between using "plymouth.enable=0", or "rpm -e plymouth-dracut ... ..."

Thankfully this is a laptop, because unreliable shutdown/reboot kills the ability to remote admin a box quicker than anything else...

I see the same thing on my desktop running an ASUS Prime X299-A motherboard with Intel Core i7-7820X. On shutdown it sometimes stops showing 05 on the q- code display indicating that it's stopped in S5 sleep state instead of shutting down.

Initially I thought it had something to do with a device on the USB bus but I've now seen it happen even without that suspected problem device plugged in.

The annoying thing is that it **sometimes** shuts down correctly, but other times requires me to push and hold the power button to shut it down once it stops in S5 Sleep.

Regards, Rodney.

-- ========================================================================================================== Rodney Baker rodney.baker@outlook.com.au ==========================================================================================================

On Sat, 14 Oct 2023 12:30:21 -0400 Mark Misulich wrote:

On Fri, 2023-10-13 at 22:45 +0300, Andrei Borzenkov wrote:

...

On 11.10.2023 03:38, Mark Misulich wrote:

...

I had a shutdown attempt of the computer this afternoon where it didn't shut down, and hung on the shutdown with the line after the localhost login  displayed and remained displayed so I could write it down.  Here is what I saw: localhost login: [  9211, 806671] [  T1] reboot; Power down

That is really the last message before kernel turns off the system. It sounds like kernel issue.

Ok, if it is a kernel issue, is that something I fix locally because it's exclusive to my computer? Or is it a bug to be submitted for Kernel software writers to repair for all kernels everywhere? I'm just trying to understand the import of the problem you've described.

Is your question hypothetical or do you suffer from the problem? Because if you do there's a problem that affects two people (a bug reporter and a confirmer) whereas if if you don't then it's still David on his lonesome? Yours, An interested observer