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: Wed, 3 May 2023 11:31:13 +0700 [thread overview]
Message-ID: <ZFHjkb75lgzKRhRr@debian.me> (raw)
In-Reply-To: <CSB8TSV6LXJ8.7SHI9VM2YMAR@bong>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
On Tue, May 02, 2023 at 12:02:26AM +0300, Acid Bong wrote:
> Hi there, and thank you for the reminder.
>
> Bisecting, unfortunately, takes a long time: I'm only trying out the 7th
> commit, 15e7433e1dc2 (previous 6 marked as bad). The bug, as noted in
> the head, doesn't have any (strict) patterns and takes randomly long
> times: some kernels hung on the next day after compilation, one took 5
> days. I'm not excluding a possibility that I might've got the versions
> wrong and the bug occured on the update from 6.1-pf1 to 6.1-pf2 (6.1 and
> 6.1.3; could be unrelated, but I saw a bunch of commits related to i915
> and Skylake).
OK, try keep updating on bisection process.
> What exactly do you mean by "swapping the hardware"? I'm already sure
> it's not related to my storage, because a month ago I replaced my faulty
> HDD with an SSD, but the bug still remained. Unfortunately, I don't have
> spare PCs or resources to purchase new hardware.
In case of laptops, I mean buying out new laptop (maybe with similar
hardware specs as your current one) and try reproducing the regression
there.
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-03 4:31 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
2023-05-01 21:02 ` Acid Bong
2023-05-03 4:31 ` Bagas Sanjaya [this message]
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=ZFHjkb75lgzKRhRr@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;
as well as URLs for NNTP newsgroup(s).