Re: ucsi_acpi: "bogus connector number in CCI: 2" flood on Acer Aspire A14-61M

[Heikki Krogerus <heikki.krogerus@linux.intel.com>]

On Fri, Nov 06, 2026 at 09:25:26PM +0000, Peter Walker wrote:
> On Fri, Nov 06, 2026 at 06:50:36PM +0100, Heikki Krogerus wrote:
> > On Wed, Nov 04, 2026 at 11:28:12AM +0100, Peter Walker wrote:
> > > I don't have the laptop with me at the moment, I can run the command you
> > > provided this weekend if that helps?
> >
> > It would help.
> >
> > Please try to avoid top-posting on the mailing list.
> 
> Sorry about that. The laptop has two USB-C ports.
> 
> I tested your patch on 7.2.11-ogc4.1.fc44 (Bazzite): ucsi_acpi.c
> from stable v7.2.11 with the Nitro ANV15-41 line removed, built out
> of tree against the running kernel and loaded in place of the stock
> module. It makes no difference here.
> 
> - "UCSI version is zero, assuming 1.2" is never logged.

Okay, but it would not help in any case. The first problem is that the
PPM reports the wrong number of connector, right?

That is a pretty obvious FW bug. Did you report that to Acer?

We can prepare a quirk where that is fixed, but it means that the FW
may never get fixed. So let's try to get the FW fixed first.

> - At probe, "UCSI_GET_PDOS failed (-70)" is logged twice, as on
> every boot.

This is probable another issue. Let's tackle these one by one.

> - The first "bogus connector number in CCI: 2" came 4.7 s after the
> first of those, and acer_wmi logged a charger unplug 0.3 s later.
> The stock module had been printing them until I unloaded it, about
> 100 s before.
> 
> - From then on they kept coming at 17 every 10 s, the same rate as
> the stock module just before, while the charger went back in, out
> and in again, and across an s2idle cycle. Four were logged during
> the suspend and resume, and the next came 2.4 s after
> "PM: suspend exit".

Can you share the complete dmesg output?

> - port0 never followed the charger: no partner, power_operation_mode
> "default" and ucsi-source-psy-USBC000:001 online=0, whether the
> charger was plugged in or not.
> 
> One correction to my first report: a charger unplug may not be the only
> trigger. Going back through the journal, on 8 of the 20 boots on
> 7.2.x kernels the messages started 3.9-4.6 s after the probe's first
> "UCSI_GET_PDOS failed (-70)", before any charger event was logged.

Thanks,

-- 
heikki