I did a search on the ACPI BIOS error being reported and I was able to find this kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213023


It looks like that bug is still in 5.15.x. I checked the one AlmaLinux 9.1 VM we have running right now and it is running  5.14.0-162.12.1.el9_1.x86_64.


I'm not sure if that's what's actually causing the system to lock up, but it might be related. I'd probably install AlmaLinux 8 and see if the problem still exists.


Travis Newton

Founder/Owner

Hosting Intellect, LLC

Hosting Intellect, LLC Logo

https://www.hostingintellect.com

From: jdwirtz@cox.net <jdwirtz@cox.net>
Sent: Thursday, March 2, 2023 11:32:49 AM
To: users@lists.almalinux.org
Subject: [AlmaLinux Users] Re: Alma 9 keep server up and running.
 
Don't have kdump enabled... didn't think I would need it.
Not finding any sleep, suspend but found
Mar  2 08:49:25 alma1 kernel: ACPI: PM: Power Resource [WRST]
Mar  2 08:49:25 alma1 kernel: ACPI: PM: Power Resource [DRST]
Mar  2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330)
Mar  2 08:49:25 alma1 kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS03._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
Mar  2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330)
Mar  2 08:49:25 alma1 kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS04._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
Mar  2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330)
Mar  2 08:49:25 alma1 kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
Mar  2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330)
Mar  2 08:49:25 alma1 kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.SS02._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
-----
Mar  2 08:49:25 alma1 kernel: pcieport 0000:00:1c.0: PME: Signaling with IRQ 122
Mar  2 08:49:25 alma1 kernel: pcieport 0000:00:1c.0: AER: enabled with IRQ 122
Mar  2 08:49:25 alma1 kernel: pcieport 0000:00:1c.0: DPC: enabled with IRQ 122
Mar  2 08:49:25 alma1 kernel: pcieport 0000:00:1c.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Mar  2 08:49:25 alma1 kernel: pcieport 0000:00:1c.5: PME: Signaling with IRQ 123
Mar  2 08:49:25 alma1 kernel: pcieport 0000:00:1c.5: AER: enabled with IRQ 123
Mar  2 08:49:25 alma1 kernel: pcieport 0000:00:1c.5: DPC: enabled with IRQ 123
Mar  2 08:49:25 alma1 kernel: pcieport 0000:00:1c.5: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Mar  2 08:49:25 alma1 kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
----Mar  2 08:49:25 alma1 kernel: hub 1-0:1.0: USB hub found
Mar  2 08:49:25 alma1 kernel: hub 1-0:1.0: 8 ports detected
Mar  2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330)
Mar  2 08:49:25 alma1 kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS03._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
Mar  2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330)
Mar  2 08:49:25 alma1 kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS04._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
Mar  2 08:49:25 alma1 kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.14
Mar  2 08:49:25 alma1 kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Mar  2 08:49:25 alma1 kernel: usb usb2: Product: xHCI Host Controller
Mar  2 08:49:25 alma1 kernel: usb usb2: Manufacturer: Linux 5.14.0-162.12.1.el9_1.x86_64 xhci-hcd
Mar  2 08:49:25 alma1 kernel: usb usb2: SerialNumber: 0000:00:14.0
Mar  2 08:49:25 alma1 kernel: hub 2-0:1.0: USB hub found
Mar  2 08:49:25 alma1 kernel: hub 2-0:1.0: 6 ports detected
Mar  2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330)
Mar  2 08:49:25 alma1 kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
Mar  2 08:49:25 alma1 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20211217/psargs-330)
Mar  2 08:49:25 alma1 kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.SS02._PLD due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
Mar  2 08:49:25 alma1 kernel: usbcore: registered new interface driver usbserial_generic
Mar  2 08:49:25 alma1 kernel: usbserial: USB Serial support registered for generic
Mar  2 08:49:25 alma1 kernel: i8042: PNP: No PS/2 controller found.
------
\Mar  2 08:49:31 alma1 systemd[1]: Special handling of early boot iSCSI sessions was skipped because of a failed condition check (ConditionDirectoryNotEmpty=/sys/class/iscsi_session).
Mar  2 08:49:31 alma1 systemd[1]: OSTree Remount OS/ Bind Mounts was skipped because of a failed condition check (ConditionKernelCommandLine=ostree).
Mar  2 08:49:31 alma1 systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
Mar  2 08:49:31 alma1 systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
Mar  2 08:49:31 alma1 systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
Mar  2 08:49:31 alma1 systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed.
Mar  2 08:49:31 alma1 systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
-----
Mar  2 08:49:32 alma1 kernel: EXT4-fs (sda1): recovery complete
Mar  2 08:49:32 alma1 kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none.
Mar  2 08:49:32 alma1 systemd[1]: Mounted /web.
Mar  2 08:49:32 alma1 systemd[1]: Reached target Local File Systems.
Mar  2 08:49:32 alma1 systemd[1]: Rebuild Dynamic Linker Cache was skipped because all trigger condition checks failed.
Mar  2 08:49:32 alma1 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Mar  2 08:49:32 alma1 systemd[1]: Mark the need to relabel after reboot was skipped because of a failed condition check (ConditionPathExists=!/.autorelabel).
Mar  2 08:49:32 alma1 systemd[1]: Set Up Additional Binary Formats was skipped because all trigger condition checks failed.
Mar  2 08:49:32 alma1 systemd[1]: Commit a transient machine-id on disk was skipped because of a failed condition check (ConditionPathIsMountPoint=/etc/machine-id).
Mar  2 08:49:32 alma1 systemd[1]: Starting Create Volatile Files and Directories...
Mar  2 08:49:32 alma1 systemd[1]: Received SIGRTMIN+20 from PID 390 (plymouthd).
Mar  2 08:49:32 alma1 systemd[1]: Finished Tell Plymouth To Write Out Runtime Data.
Mar  2 08:49:32 alma1 systemd[1]: Finished Create Volatile Files and Directories.
Mar  2 08:49:32 alma1 systemd[1]: Mounting RPC Pipe File System...
Mar  2 08:49:32 alma1 systemd[1]: Starting Security Auditing Service...
Mar  2 08:49:32 alma1 systemd[1]: Starting RPC Bind...
Mar  2 08:49:32 alma1 systemd[1]: Rebuild Journal Catalog was skipped because of a failed condition check (ConditionNeedsUpdate=/var).
Mar  2 08:49:32 alma1 systemd[1]: Update is Completed was skipped because all trigger condition checks failed.
Mar  2 08:49:32 alma1 auditd[1021]: audit dispatcher initialized with q_depth=1200 and 1 active plugins
Mar  2 08:49:32 alma1 systemd[1]: Started RPC Bind.
_______________________________________________
AlmaLinux Users mailing list -- users@lists.almalinux.org
To unsubscribe send an email to users-leave@lists.almalinux.org
--
This e-mail and any attached files are confidential and may be legally privileged. If you are not the addressee, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify the sender immediately and then delete this mail.
E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission or changes to transmitted date not specifically approved by the sender.
If this e-mail or attached files contain information which do not relate to our professional activity we do not accept liability for such information.