Linux USB
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 222021] Not charging via USB C after Kernel update "underpowered" Dell XPS + workaround
Date: Fri, 09 Oct 2026 15:41:39 +0000	[thread overview]
Message-ID: <bug-222021-208809-uvyILYxNTP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222021-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=222021

--- Comment #5 from SpliNter (splint.em85@gmail.com) ---
Update: I'm now on 7.2.9-1-cachyos (not vanilla mainline, so I
haven't tested 7.3-rc yet).
On hotplug the charger now ends upcharging, but the state is unstable for a few
seconds.
udevadmmonitor -s power_supply after plugging in the original Dell adapter
shows within ~6 s: 4 change events for ucsi-source-psy-USBC000:003,
1 for AC and 2 for BAT0 (I saw "not charging" briefly, then charging,
flipping twice).

dmesg shows "ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)" not only
at boot but on plug-in as well; the latest one (409.498) is logged
right after the AC change event at 409.34, so it coincides with the
hotplug.
Earlier today it stayed "not charging" on the same kernel
(at about 70% battery, it is allowed to charge up to 80%), so the problem is
intermittent.

I'm about to test mainline and patch today and report back.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2026-10-09 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 17:52 [Bug 222021] New: Not charging via USB C after Kernel update "underpowered" Dell XPS + workaround bugzilla-daemon
2026-09-18  6:17 ` [Bug 222021] " bugzilla-daemon
2026-09-18 16:18 ` bugzilla-daemon
2026-09-18 16:20 ` bugzilla-daemon
2026-09-19  8:00 ` bugzilla-daemon
2026-10-09 15:41 ` bugzilla-daemon [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=bug-222021-208809-uvyILYxNTP@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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