Re: [regression] Bug 216426 - USB-C port is incorrectly reporting that it's powered when Dell XPS 15-9500 is unplugged #forregzbot

From: Thorsten Leemhuis
Date: Thu Oct 27 2022 - 06:37:27 EST


[Note: this mail is primarily send for documentation purposes and/or for
regzbot, my Linux kernel regression tracking bot. That's why I removed
most or all folks from the list of recipients, but left any that looked
like a mailing lists. These mails usually contain '#forregzbot' in the
subject, to make them easy to spot and filter out.]

On 30.09.22 13:20, Thorsten Leemhuis wrote:
> On 26.09.22 16:25, Thorsten Leemhuis wrote:
>> On 01.09.22 11:07, Thorsten Leemhuis wrote:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=216426
>>>
>>>> Mattia Orlandi 2022-08-29 17:04:21 UTC
>>>>
>>>> System
>>>> ------
>>>> - Dell XPS 15 9500
>>>> - 5.19.4 kernel
>>>>
>>>> Problem description
>>>> -------------------
>>>> Whenever I plug and then unplug my laptop from AC power using the USB-C port, the system thinks it is still plugged in (i.e., the KDE applet reports "Plugged in but still discharging").
>>>> If I check in Dell's BIOS, it correctly reports when the power supply is plugged/unplugged; `acpi -V` also correctly shows `Adapter 0: off-line`.
>>>>
>>>> On the other hand, `upower -d` incorrectly reports `/org/freedesktop/UPower/devices/line_power_ucsi_source_psy_USBC000o002` as `online: yes`.
>>>> Moreover, `journalctl` reports `ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-110)`.
>>>>
>>>> I'm testing the LTS kernel (5.15.63) and the issue does not occur, so I assume it's a regression bug, possibly introduced in kernel 5.18 (I tried downgrading the kernel to version 5.18.16 and the issue was already present).
>>>
>>> See the ticket for more details. Apologies if I forwarded it to the
>>> wrong folks, I cover a lot of ground and thus sometimes get things
>>> wrong. :-/
>>>
>>> BTW, I'd also like to add the report to the list of tracked regressions
>>> to ensure it's doesn't fall through the cracks in the end:
>>>
>>> #regzbot introduced: v5.15..v5.18
>>> https://bugzilla.kernel.org/show_bug.cgi?id=216426
>>> #regzbot ignore-activity
>> #regzbot introduced: f7090e0ef360d674f0
>
> Looks like nobody yet check if the problem happens with mainline, so
> let's stick to the backport for now:
>
> #regzbot introduced: 0fbb5ce2f4267

#regzbot invalid: not a regression, likely something related to hardware
or firmware https://bugzilla.kernel.org/show_bug.cgi?id=216426#c22