[ ?.8475311[ T335] ucsi_acpi USECAAA:A8: error -ETIMEDOUT: PPM init failed

English Install/Boot/Login
1 
Operating System: openSUSE Tumbleweed 20241121
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.8-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: MINIPC PN52

When starting Tumbleweed, this message appears. Is this a real bug or just a cosmetic defect?
​​I haven’t noticed that it causes any problems other than slow startup. Slow startup can also be caused by
[ 36.8237141[ T641] Bluetooth: hci@: Failed to claim iso interface
but there is already a bug report for this.

2

Errors containing …acpi… are typically innocuous BIOS defects. Is a BIOS update available?

Simple search for ucsi_acpi on Bugzilla produced 15 open hits, so if you look through them you might find something related.

3

I’ll check the BIOS status soon.

I didn’t find/understand that any of those bugs apply to this problem.

I tried to get a coredump using the instructions on the page below, but I couldn’t get any text out.

Nov 25 00:39:10 localhost kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
Nov 25 00:39:39 localhost systemd-coredump[684]: Process 528 (plymouthd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Nov 25 00:39:39 localhost systemd-coredump[684]: Failed to connect to coredump service: No such file or directory
Nov 25 00:39:39 localhost systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV
Nov 25 00:39:39 localhost systemd[1]: plymouth-start.service: Failed with result 'core-dump'.
Nov 25 00:39:39 localhost systemd[1]: Finished Plymouth switch root service.
Nov 25 00:39:39 localhost systemd[1]: Starting Switch Root...

localhost:~ # systemd-coredumpctl list
 systemd-coredumpctl: command not found
localhost:~ #
4 
# inxi -S
System:
  Host: ara88 Kernel: 6.6.58-1-longterm arch: x86_64 bits: 64
  Console: pty pts/0 Distro: openSUSE Tumbleweed 20241124
# which systemd-coredumpctl
which: no systemd-coredumpctl in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin)
# which coredumpctl
/usr/bin/coredumpctl
#
5

I don’t know but I see a similar message on a system here:

Operating System: openSUSE Tumbleweed 20241122
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.8-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × 13th Gen Intel® Core™ i7-1360P
Graphics Processor: Mesa Intel® Iris® Xe Graphics

> journalctl --no-hostname --full --utc -b 0 --no-pager | grep ucsi
Nov 25 16:33:14 kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
>

I did some internet searches and as fas as I understand it is related to USB-C ports (thunderbolt3+ ?) which allow to connect a display. But I do not have any hardware to test this any further.

Nevertheless that system works flawless.

6

I wonder what the computer is doing during that 30 minutes. This “feature” came because of a recent update.

Nov 25 00:39:10 localhost kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
Nov 25 00:39:39 localhost systemd-coredump[684]: Process 528 (plymouthd) of user 0 terminated abnormally with signal 11/SEGV, processing...

I’m testing with older packages.

7

How can I compare (find differences) between those two software?

https://paste.opensuse.org/pastes/8a98d112e813

This is the first software on my computer that writes that log:
Operating System: openSUSE Tumbleweed 20241118
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.8-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: MINIPC PN52

This software works ok:
Operating System: openSUSE Tumbleweed 20241117
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.8-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: MINIPC PN52
8

BIOS is updated, no help…

9

Is that not 30 sec.? Could be related to this bug.

However I can’t imagin that the ucsi_acpi problem has anything to do with the 30 sec. delay.

10

Sorry, my mistake. Of course it’s about 30 seconds.

As I said, this error message appeared when I updated to openSUSE Tumbleweed 20241118. The previous software did not have this error message, so openSUSE Tumbleweed 20241117 was OK. There is really something wrong here and it bothers me that the computer freezes for 30 seconds.

11

30 sec delay patched away.

Bugzilla id=1233532

Patch: “I can confirmed that removing the splash=silent from the grub boot menu eliminates the big delay in the boot process in my system”

With Yast this done:
splash=silent quiet security=apparmor
quiet security=apparmor

12

So your 30 sec delay is gone?

Do you still see the ucsi_acpi error?

sudo journalctl -b 0 | grep ucsi
13

Yes, the 30 sec delay is gone, but I still see ucsi_acpi error:

localhost:~ # 
localhost:~ # journalctl -b 0 | grep ucsi
Nov 27 20:22:04 localhost kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
localhost:~ # 
localhost:~ #

I have a journalctl text file is needed.

14

That is great!

I opened a bug report this morning. It would help if you would join in (you can use your login credentials from the forum) and provide your log file.

15

I added some logs to bug 1233803. I failed to write an explanation for the above bug because it got lost somewhere. If possible, I would prefer to use direct terminal commands.

But what if I should also add the output of the dmesg and hwinfo commands?

16

Great that you are joining in!

You can do (as user “root” in a konsole)

dmesg -H > dmesg.txt

and

hwinfo > hwinfo.txt

and then upload the two file dmesg.txt and hwinfo.txt in bugzilla as attachments.