Linux USB
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Leo Korotkevich <essacult@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: ASUS GU605CX: diagnostic guidance for hard freezes and USB-C power-state changes
Date: Mon, 28 Sep 2026 15:28:51 +0200	[thread overview]
Message-ID: <arprk1YgN3llMaN7@black.igk.intel.com> (raw)
In-Reply-To: <CAEOLtbAXRO7zwWMtmVTG4X9az-ifFXtR1XgP0O7dNaCvZGmc5g@mail.gmail.com>

On Sat, Sep 26, 2026 at 02:45:15PM +0300, Leo Korotkevich wrote:
> Hello,
> 
> Could you recommend low-overhead USB-C/UCSI diagnostics for intermittent
> hard freezes on an ASUS GU605CX, Core Ultra 9 285H, BIOS 311?
> 
> The latest event was on CachyOS 7.2.7-1-cachyos with out-of-tree NVIDIA
> open 615.71.09. The screen froze and local input/VT switching stopped
> responding. The journal ends without a nearby USB error, OOM or panic. I
> have no evidence that UCSI caused it.

You should be able to disable the driver:

        echo "blacklist ucsi_acpi" > /etc/modprobe.d/ucsi.conf

In your case it may be enought to just unload it (modprobe -r
ucsi_acpi). Then just see can you reproduce the issue.

Thanks,

> Freezes recur across Ubuntu/Fedora/CachyOS releases, BIOS/kernel
> versions and performance profiles, Xorg/Wayland and
> dGPU-only/Dynamic-Hybrid modes. I also tried modprobe.blacklist=i915
> through GRUB; freezes continued. They also happen overnight on a
> stationary desk without cable movement. Some coincided with movement of
> the charging plug, while deliberate unplug/replug usually succeeds. They
> have occurred with the OEM ASUS charger and Lenovo/Dell adapters with
> different voltage/power ratings; exact specifications were not recorded.
> The current Apple charger reports a 20 V / 4.7 A PD contract.
> 
> Historical Fedora logs contain 1747 software-reported AC/DC alternations
> on March 9, not verified physical disconnects or a trace of the latest
> freeze. During successful recent reconnections, asusd changed profiles
> and restarted nvidia-powerd. UCSI_GET_PDOS failed (-95) appeared twice,
> but connection recovery succeeded. Brief profile/EPP changes also
> completed.
> 
> ASUS PD_FW 0003 declares firmware version 39 for the resource currently
> reporting ESRT version 1. It remains unapplied; its release note claims
> no freeze fix.
> 
> A bounded collector records power-supply uevents and contract fields. A
> temporary UCSI trace saw no events and has not been validated against a
> physical reconnection.
> 
> Which tracepoints best distinguish PD/PPM failure from normal contract
> changes and the platform's AC/profile reaction, without active
> controller polling? Sanitized excerpts are available.
> 
> Thank you.

-- 
heikki

  reply	other threads:[~2026-09-28 13:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26 11:45 ASUS GU605CX: diagnostic guidance for hard freezes and USB-C power-state changes Leo Korotkevich
2026-09-28 13:28 ` Heikki Krogerus [this message]
2026-09-29  7:22   ` Leo Korotkevich

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=arprk1YgN3llMaN7@black.igk.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=essacult@gmail.com \
    --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