CachyOS / CachyOS/distribution

[Bug]: Log Spam when using USB-C Cable for Charging

Open
#477 4 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
27
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Kernel

7.1.1-2

### Desktop Environment / Window Manager

KDE Plasma

### CPU

AMD Ryzen AI 7 350

### GPU / Driver

AMD Radeon 860M

### Description

The following line is constantly appearing in the log when plugging in the original USB-C charger:
ucsi_acpi USBC000:00: bogus connector number in CCI: 2
and does not stop appearing even after unplugging the charger.

### Steps to Reproduce

1. Full EC reset clears the issue. (Shut-Down -> press and hold power-key for 30s -> start Laptop)
2. Start journalctl -k -f -g 'ucsi_acpi' in console
3. Original charger on lower USB-C port gives no message.
4. Original charger on upper USB-C port immediately triggers continuous bogus connector number spam.
repeating line in journalctl:
Jun 20 15:09:18 Laptopname kernel: ucsi_acpi USBC000:00: bogus connector number in CCI: 2
this repeats about 2 times per second.
5. Spam continues after unplugging charger until EC reset.

### Expected Behavior

log spam does not start by plugging in the charger.

### Actual Behavior

log spam starts when plugging in the original USB-C Charger.
but only on 1 of 2 of the available USB-C ports.

### Logs / Error Messages

https://paste.cachyos.org/p/a837e5a

### Additional Context

Laptop Model: Acer Aspire A14-61M
BIOS: V1.29, 2026-03-24 (latest)
Kernel: 7.1.1-2-cachyos and 6.18.36-1-cachyos-lts (LTS also affected)

Contributor guide

No contributing guide indexed for this repository

Research direction

No repository file, test, or code entry point is identified. Start by reproducing the issue with `journalctl -k -f -g 'ucsi_acpi'`, compare the affected upper USB-C port with the lower port, and review the linked log and both reported kernel versions. Done would require identifying the source of the repeated `ucsi_acpi` message and defining a verified fix or upstream direction.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.