Slow Shutdown, Reboot error

English Install/Boot/Login
21

The “unresponsive” part is likely to be your BIOS, with openSUSE not actually involved in the problem.

22

I agree; the unresponsive reboot is unlikely to be an openSUSE issue. Once booted the system seems to operate normally. But a cold boot proceeds without problems. The issue only arises with warm reboot. I don’t know how ‘restart’ works, but it is logical that BIOS (or secure boot) may be involved, so thanks for that. Can you give me a hint about BIOS settings that may cause “unresponsiveness” on warm reboot?

23

That has opened a writhing can of juicy worms.
On the machine BIOS side its simple enough. ACPI is described here. This extract from the specification was found here. Regarding ACPI restart, the author says: “I’ll quote the 2.0 specification on what it does:”

The optional ACPI reset mechanism specifies a standard mechanism that provides a complete system reset. When implemented, this mechanism must reset the entire system. This includes processors, core logic, all buses, and all peripherals. From an OSPM perspective, asserting the reset mechanism is the logical equivalent to power cycling the machine. Upon gaining control after a reset, OSPM will perform actions in like manner to a cold boot.
(My emphasis.)

Linux ‘restart’ process is complicated. I found a 2011 blog article here with an outline of the kernel processes. Way beyond me.

Is this of any assistance:

# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.1 present.
80 structures occupying 3855 bytes.
Table at 0xC3374000.

Handle 0x0000, DMI type 43, 31 bytes
TPM Device
        Vendor ID: IFX
        Specification Version: 2.0      Firmware Revision: 7.63
        Description: SLB9670    Characteristics:
                Family configurable via firmware update
                Family configurable via platform software support
        OEM-specific Information: 0x00000000

Handle 0x0001, DMI type 0, 26 bytes
BIOS Information
        Vendor: HP
        Version: Q01 Ver. 02.07.01
        Release Date: 04/23/2019
        Address: 0xF0000
        Runtime Size: 64 kB
        ROM Size: 32 MB
        Characteristics:
                PCI is supported
                PC Card (PCMCIA) is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                Boot from CD is supported
                Selectable boot is supported
                EDD is supported
                Print screen service is supported (int 5h)
                8042 keyboard services are supported (int 9h)
                Serial services are supported (int 14h)
                Printer services are supported (int 17h)
                ACPI is supported
                USB legacy is supported
                BIOS boot specification is supported
                Function key-initiated network boot is supported
                Targeted content distribution is supported
                UEFI is supported
        BIOS Revision: 7.1
        Firmware Revision: 7.210
24

What about uefi fast boot? Did you disable that option?

25

Some BIOS have a fast boot (or fast POST) setting such that USB devices are not initialized during boot. Make sure you are not using that. Or use a PS/2 keyboard if your computer happens to have a place to plug that in (most newer computers don’t support PS/2 keyboards).

26

Not yet. I have avoided UEFI in the past and don’t know how to safely disable it. I will investigate. Thanks.

27

Thanks. No PS/2 sockets on this machine. I will check BIOS settings for fast boot.

28

Found ‘fast boot’ enabled. Disabled, but reboot issues persist.

It looks like this may be a Linux compatibility issue on a machine designed to run MS OS is a corporate environment. If so, it’s probably out of scope here. Thank-you for your patience and kind assistance.

29

The CLI command should have been “rpm --query --whatprovides /var/log/journal” only.

  • The rpm query failed because, “systemd-logger-234-lp151.26.4.1.x86_64” was taken to be an option to the “/var/log/journal” query.