From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Myrrh Periwinkle <myrrhperiwinkle@qtmlabs.xyz>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
stable@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [stable 6.6.y] commit e613904fa419 causes suspend regression
Date: Tue, 19 May 2026 11:51:20 +0200 [thread overview]
Message-ID: <2026051935-flashing-relearn-8444@gregkh> (raw)
In-Reply-To: <agwu9NGf128-YQST@google.com>
On Tue, May 19, 2026 at 06:44:07PM +0900, Sergey Senozhatsky wrote:
> On (26/05/19 11:29), Greg Kroah-Hartman wrote:
> > > We've identified 6.6.y stable commit e613904fa419 (usb: typec: ucsi:
> > > Update power_supply on power role change) (commit 7616f006db07017 upstream)
> > > as a root-cause of suspend failures on some of our laptops. It seems
> > > that ucsi_port_psy_changed() causes:
> > >
> > > [ 309.858915] PM: last active wakeup source: ucsi-source-psy-cros_ec_ucsi.3.auto2
> > > [ 309.858917] PM: PM: Last active Wakeup Source: ucsi-source-psy-cros_ec_ucsi.3.auto2
> > >
> > > which prevent laptop from entering suspend. Reverting the commit in
> > > question fixes the issue.
> > >
> >
> > Ok, and what should we do?
>
> I suppose what you usually do with stable regressions?
Get the reporter to fix them, great! :)
> > Is this issue also in 7.0.y?
>
> We don't have any boards on 7.0.y unfortunately. 6.6.y is the most recent
> we use, but I'd expect 7.0 to regress as well.
Wonderful, please send a revert for mainline and we will be glad to
apply that and backport it properly to the needed stable kernels.
thanks,
greg k-h
next prev parent reply other threads:[~2026-05-19 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 4:51 [stable 6.6.y] commit e613904fa419 causes suspend regression Sergey Senozhatsky
2026-05-19 9:29 ` Greg Kroah-Hartman
2026-05-19 9:44 ` Sergey Senozhatsky
2026-05-19 9:51 ` Greg Kroah-Hartman [this message]
2026-05-19 12:01 ` Myrrh Periwinkle
2026-05-20 2:08 ` Sergey Senozhatsky
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=2026051935-flashing-relearn-8444@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=myrrhperiwinkle@qtmlabs.xyz \
--cc=senozhatsky@chromium.org \
--cc=stable@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