Public bug reported:

On my ASUS Vivobook S 14 dual-booting Ubuntu and Windows 11, USB-C
charging sometimes stops working after the system has been suspended and
resumed. The issue does not occur in Windows 11.

During the failure, Linux detects the USB-C power source through UCSI,
but the ACPI AC adapter remains offline:

ucsi-source-psy-USBC000:001:
    online = 1
    status = Charging
    voltage = 20000000 uV
    current = 4500000 uA

ACAD:
    online = 0

BAT1:
    status = Discharging

Thus the UCSI power supply reports a 20 V / 4.5 A (90 W) USB-C power
source, while ACAD reports that no AC power is present and the battery
continues discharging.

The kernel log also repeatedly contains:
ucsi_acpi USBC000:00: failed to re-enable notifications (-110)

and:

ucsi_acpi USBC000:00: ucsi_handle_connector_change:
GET_CONNECTOR_STATUS failed (-110)

These errors appear in connection with suspend/resume.

Interestingly, while the failure was active, unplugging and reconnecting
the charger immediately restored charging without requiring a reboot:

Before unplug:
UCSI = 1
ACAD = 0
BAT1 = Discharging

After replug:
UCSI = 1
ACAD = 1
BAT1 = Charging

Rebooting also reliably restores normal charging.

The problem appears to be related to USB-C/UCSI/ACPI handling after
suspend/resume.

I've attached kernel logs and the output of the command "upower -d" in a
file "charging-bug-report.txt"

ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-7.0.0-29-generic 7.0.0-29.29
ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12
Uname: Linux 7.0.0-29-generic x86_64
ApportVersion: 2.34.1-0ubuntu0.1
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC1:  shailesh   4955 F.... wireplumber
 /dev/snd/controlC0:  shailesh   4955 F.... wireplumber
 /dev/snd/seq:        shailesh   4935 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 11 12:29:46 2026
InstallationDate: Installed on 2026-07-13 (29 days ago)
InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1)
MachineType: ASUSTeK COMPUTER INC. ASUS Vivobook S 14 M5406WA_M5406WA
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=tmux-256color
 XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic 
root=UUID=c39ac997-bd8a-4ac4-82f4-2e17e428eca7 ro quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2026
dmi.bios.release: 5.35
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: M5406WA.316
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M5406WA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.10
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrM5406WA.316:bd01/05/2026:br5.35:efr3.10:svnASUSTeKCOMPUTERINC.:pnASUSVivobookS14M5406WA_M5406WA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5406WA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSVivobookS14:
dmi.product.family: ASUS Vivobook S 14
dmi.product.name: ASUS Vivobook S 14 M5406WA_M5406WA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug resolute wayland-session

** Attachment added: "Kernel Log and Upower State"
   
https://bugs.launchpad.net/bugs/2163222/+attachment/5991199/+files/charging-bug-report.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2163222

Title:
  USB-C charging fails after suspend/resume on ASUS Vivobook S 14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163222/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to