Errors at boot (log from journalctl)

The garuda-inxi:

garuda-inxi
System:
Kernel: 6.1.12-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=509070c5-cd0c-45ce-97d4-ab169da5131f rw rootflags=subvol=@
quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
loglevel=3
Desktop: KDE Plasma v: 5.27.1 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: EXO S.A. product: EXO Smart XQ3h v: N/A
serial: <superuser required>
Mobo: EXO S.A. model: CT15Q5-S serial: <superuser required> UEFI: WEIBU
v: YHSM-BI-15.6-XU133TR120-TA60B-328-C date: 11/23/2021
Battery:
ID-1: BAT0 charge: 15.0 Wh (32.9%) condition: 45.6/45.6 Wh (100.0%)
volts: 7.3 min: N/A model: WB SR 1 WB Lion Battery type: Li-ion
serial: <filter> status: discharging
CPU:
Info: model: 11th Gen Intel Core i3-1115G4 bits: 64 type: MT MCP
arch: Tiger Lake gen: core 11 level: v4 note: check built: 2020
process: Intel 10nm family: 6 model-id: 0x8C (140) stepping: 1
microcode: 0xA6
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 160 KiB desc: d-2x48 KiB; i-2x32 KiB L2: 2.5 MiB desc: 2x1.2 MiB
L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 871 high: 1228 min/max: 400/4100 scaling:
driver: intel_pstate governor: powersave cores: 1: 868 2: 748 3: 1228 4: 643
bogomips: 23961
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Tiger Lake-LP GT2 [UHD Graphics G4] driver: i915 v: kernel
arch: Gen-12.1 process: Intel 10nm built: 2020-21 ports: active: eDP-1
empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:9a78 class-ID: 0300
Device-2: Sunplus Innovation Hy-UXGA-Camera type: USB driver: uvcvideo
bus-ID: 3-7:4 chip-ID: 1bcf:2ced class-ID: 0e02
Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1368x768 s-dpi: 97 s-size: 360x202mm (14.17x7.95")
s-diag: 413mm (16.25")
Monitor-1: eDP-1 model-id: STA 0xafc9 built: 2020 res: 1368x768 hz: 60
dpi: 101 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5")
ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics (TGL GT2)
direct-render: Yes
Audio:
Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel
v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 00:1f.3
chip-ID: 8086:a0c8 class-ID: 0403
Sound API: ALSA v: k6.1.12-zen1-1-zen running: yes
Sound Server-1: PulseAudio v: 16.1 running: no
Sound Server-2: PipeWire v: 0.3.66 running: yes
Network:
Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
vendor: AzureWave driver: ath10k_pci v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 01:00.0 chip-ID: 168c:0042 class-ID: 0280
IF: wlp1s0 state: up mac: <filter>
Device-2: Intel Ethernet I225-V driver: igc v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 port: N/A bus-ID: 02:00.0 chip-ID: 8086:15f3
class-ID: 0200
IF: enp2s0 state: down mac: <filter>
Bluetooth:
Device-1: IMC Networks type: USB driver: btusb v: 0.8 bus-ID: 3-1:2
chip-ID: 13d3:3503 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address: <filter>
Drives:
Local Storage: total: 238.47 GiB used: 5.73 GiB (2.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Patriot model: P210 256GB
size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 3A0 scheme: GPT
Partition:
ID-1: / raw-size: 134.12 GiB size: 134.12 GiB (100.00%) used: 5.7 GiB (4.2%)
fs: btrfs dev: /dev/sda6 maj-min: 8:6
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 27.7 MiB (28.9%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 134.12 GiB size: 134.12 GiB (100.00%)
used: 5.7 GiB (4.2%) fs: btrfs dev: /dev/sda6 maj-min: 8:6
ID-4: /var/log raw-size: 134.12 GiB size: 134.12 GiB (100.00%)
used: 5.7 GiB (4.2%) fs: btrfs dev: /dev/sda6 maj-min: 8:6
ID-5: /var/tmp raw-size: 134.12 GiB size: 134.12 GiB (100.00%)
used: 5.7 GiB (4.2%) fs: btrfs dev: /dev/sda6 maj-min: 8:6
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 7.5 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 46.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 195 Uptime: 23m wakeups: 1 Memory: 7.51 GiB
used: 2.71 GiB (36.1%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 Packages: pm: pacman pkgs: 1205
libs: 340 tools: octopi,paru Shell: fish v: 3.6.0 default: Bash v: 5.1.16
running-in: konsole inxi: 3.3.25
Garuda (2.6.15-1):
System install date:     2023-02-27
Last full system update: 2023-02-27
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

Hi.
I have this errors in the boot:

journalctl -p3

feb 27 18:08:52 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol 
feb 27 18:08:52 archlinux kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS01._PLD due to previous error (AE_NOT_FOUND) (2022>
feb 27 18:08:52 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-330)
feb 27 18:08:52 archlinux kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS02._PLD due to previous error (AE_NOT_FOUND) (2022>
feb 27 18:08:52 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-330)
feb 27 18:08:52 archlinux kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS03._PLD due to previous error (AE_NOT_FOUND) (2022>
feb 27 18:08:52 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-330)
feb 27 18:08:52 archlinux kernel: ACPI Error: Aborting method \_SB.PC00.TXHC.RHUB.SS04._PLD due to previous error (AE_NOT_FOUND) (2022>
feb 27 18:08:53 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol 
feb 27 18:08:53 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-330)
feb 27 18:08:53 archlinux kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (2022>
feb 27 18:08:53 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-330)
feb 27 18:08:53 archlinux kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS05._PLD due to previous error (AE_NOT_FOUND) (2022>
feb 27 18:08:53 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-330)
feb 27 18:08:53 archlinux kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS05._PLD due to previous error (AE_NOT_FOUND) (2022>
feb 27 18:08:53 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-330)
feb 27 18:08:53 archlinux kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS05._PLD due to previous error (AE_NOT_FOUND) (2022>
feb 27 18:08:53 archlinux kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-330)
feb 27 18:08:53 archlinux kernel: ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS05._PLD due to previous error (AE_NOT_FOUND) (2022>
feb 27 18:08:56 nochibook bluetoothd[563]: src/plugin.c:plugin_init() Failed to init vcp plugin
feb 27 18:08:56 nochibook bluetoothd[563]: src/plugin.c:plugin_init() Failed to init mcp plugin

Welcome :slight_smile:

In short, no problem.

Long version
https://forums.linuxmint.com/viewtopic.php?f=42&t=371358
but I think you know that, or did you find something else in your search on the internet?

Did you search before posting?

https://bbs.archlinux.org/viewtopic.php?id=281230

2 Likes

As regards the ACPI errors, you can search the internet, maybe update the BIOS, search in the jungle of kernel boot parameters, maybe using this guide (not limited to!), but I think that they are often due to non-standard BIOS implementations.
I think this article summerizes the point quite well:

2 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.