On Wed, 2023-08-23 at 17:24 +0300, Andrei Borzenkov wrote:
On Wed, Aug 23, 2023 at 4:59 PM Mark Misulich <munguanaweza@gmail.com> 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