From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Peter Walker <peter.walker78@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: ucsi_acpi: "bogus connector number in CCI: 2" flood on Acer Aspire A14-61M
Date: Fri, 20 Nov 2026 15:56:45 +0100 [thread overview]
Message-ID: <awBfrbFPUvcrS1Xg@black.igk.intel.com> (raw)
In-Reply-To: <CAPv=dGA4CoZrBVs7RGDmuXfb5YqPcR5hmYh7uUVsRcShbeT6hg@mail.gmail.com>
On Wed, Nov 18, 2026 at 09:30:30PM +0000, Peter Walker wrote:
> On Wed, Nov 11, 2026 at 03:26:10PM +0100, Heikki Krogerus wrote:
> > Okay, but it would not help in any case. The first problem is that the
> > PPM reports the wrong number of connector, right?
>
> Yes. GET_CAPABILITY reports bNumConnectors 1, while Acer's SSDT31
> declares two connectors under \_SB.UBTC, CR01 and CR02, and port0 is
> bound to CR01. Both USB-C ports are on the left side, and connector 2
> is the rear one: with the charger in it, GET_CONNECTOR_STATUS(2)
> returned 0x000000000000000153851545222b0000 (connected, PD sink, RDO
> 0x53851545) and GET_CONNECTOR_STATUS(1) returned
> 0x00000000000000010000000020000000. Those readings are from 6 Nov.
> The BIOS is still 1.29, the newest Acer offers, and the DSDT and
> SSDT31 are byte-for-byte the same as on 20 Oct.
>
> > That is a pretty obvious FW bug. Did you report that to Acer?
>
> Not until now, sorry. Reported to Acer UK support today, case
> 261119-000931, with the readings and the SSDT31 disassembly.
> I'll let you know what they say, by 3 December either way.
Cool.
> > Can you share the complete dmesg output?
>
> Attached: the kernel log for one whole boot on 7.3.4-ogc8.1.fc45
> (Bazzite), saved with journalctl -k -b, so the lines carry journal
> prefixes. ucsi_acpi and typec_ucsi are the stock modules; the taint
> comes from Bazzite's gcadapter_oc module. MAC addresses are masked.
Thanks!
> The messages started on their own 0.9 s after "UCSI_GET_PDOS failed
> (-70)", with the charger plugged in. On this boot that error was
> logged once, not twice as before. Later in the log the charger is
> unplugged and replugged three times, moved between the two ports, and
> there is one s2idle cycle.
I'll try to take a closer look at this next week. But it sounds like
the PPM is not behaving properly also in this case.
Thanks,
--
heikki
prev parent reply other threads:[~2026-11-20 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 21:53 ucsi_acpi: "bogus connector number in CCI: 2" flood on Acer Aspire A14-61M Peter Walker
2026-11-04 10:17 ` Heikki Krogerus
[not found] ` <CAPv=dGA6ygdQ8StHwht6nPJZyb2FTH0n03txOOWhb4SSHkG9zw@mail.gmail.com>
[not found] ` <CAPv=dGBgnxKoyOrcbKBwym5sm3M9+oO+L5R1do7pP9X6cBDXUg@mail.gmail.com>
2026-11-06 17:50 ` Heikki Krogerus
2026-11-06 21:25 ` Peter Walker
2026-11-11 14:26 ` Heikki Krogerus
2026-11-18 21:30 ` Peter Walker
2026-11-20 14:56 ` Heikki Krogerus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=awBfrbFPUvcrS1Xg@black.igk.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=peter.walker78@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox