From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Acid Bong <acidbong@tilde.cafe>, regressions@lists.linux.dev
Cc: stable@vger.kernel.org, linux-acpi@vger.kernel.org,
Thorsten Leemhuis <regressions@leemhuis.info>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [REGRESSION] Asus X541UAK hangs on suspend and poweroff (v6.1.6 onward)
Date: Mon, 1 May 2023 19:50:44 +0700 [thread overview]
Message-ID: <ZE+1pKbfy1l/tTo6@debian.me> (raw)
In-Reply-To: <5f445dab-a152-bcaa-4462-1665998c3e2e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
On Fri, Apr 14, 2023 at 02:51:47PM +0700, Bagas Sanjaya wrote:
> On 4/14/23 02:35, Acid Bong wrote:
> > The issue appeared when I was using pf-kernel with genpatches and
> > updated from 6.1-pf2 to 6.1-pf3 (corresponding to vanilla versions 6.1.3
> > -> 6.1.6). I used that fork until 6.2-pf2, but since then (early March)
> > moved to vanilla sources and started following the 6.1.y branch when it
> > was declared LTS. And the issue was present on all of them.
> >
> > The hang was last detected 3 days ago on 6.1.22 and today on 6.1.23.
> >
>
> Have you tried testing latest mainline to see if commits which are
> backported to 6.1.y cause your regression?
>
#regzbot poke
Acid Bong, have you successfully bisected to find the culprit commit?
How about swapping the hardware? I'm poking because the thread looks
stale for a while.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-01 12:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 19:35 [REGRESSION] Asus X541UAK hangs on suspend and poweroff (v6.1.6 onward) Acid Bong
2023-04-14 7:51 ` Bagas Sanjaya
2023-04-14 8:15 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-14 9:07 ` Acid Bong
2023-04-14 18:51 ` Acid Bong
2023-04-15 7:37 ` Bagas Sanjaya
2023-04-15 8:06 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-15 20:51 ` Bjorn Helgaas
2023-05-16 10:26 ` Acid Bong
2023-05-16 19:32 ` Bjorn Helgaas
2023-04-17 7:37 ` Acid Bong
2023-04-17 10:56 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-01 12:50 ` Bagas Sanjaya [this message]
2023-05-01 21:02 ` Acid Bong
2023-05-03 4:31 ` Bagas Sanjaya
2023-06-09 11:09 ` Acid Bong
2023-06-09 16:55 ` Bjorn Helgaas
2023-06-14 8:53 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-05-13 10:50 ` Acid Bong
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=ZE+1pKbfy1l/tTo6@debian.me \
--to=bagasdotme@gmail.com \
--cc=acidbong@tilde.cafe \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@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