public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Acid Bong" <acidbong@tilde.cafe>
To: "Bagas Sanjaya" <bagasdotme@gmail.com>, <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: Sat, 13 May 2023 13:50:55 +0300	[thread overview]
Message-ID: <CSL3BO4G05T7.TXT503TF8XQC@bong> (raw)
In-Reply-To: <ZE+1pKbfy1l/tTo6@debian.me>

Hi there, hello. A little mid-update.

I bisected almost all range after 6.1.3 and the only untested commits
left are unrelated to my hardware (AMD-specific stuff). I spent a week
with a 6.1.1 kernel and didn't experience a single hang since, which
leads me to a couple of conclusions:

1) it's not a hardware issue after all, since certain versions don't
produce the bug
2) (this one's more an assumption) I might've got the version range
wrong.

I'm gonna try 6.1.2 and 6.1.3 as well (up to 7 more days for each), and,
depending on the output, bisect in a different range (now I regret not
doing it in the beginning).

At the moment the earliest *tested* commit is:
```
[15e7433e1dc202] arm64: dts: qcom: sc8280xp: fix UFS DMA coherency.
```
and it's marked as "bad".

Thank you for your patience.

      parent reply	other threads:[~2023-05-13 10:51 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
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 [this message]

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=CSL3BO4G05T7.TXT503TF8XQC@bong \
    --to=acidbong@tilde.cafe \
    --cc=bagasdotme@gmail.com \
    --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