public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Acid Bong" <acidbong@tilde.cafe>
To: <regressions@leemhuis.info>
Cc: <acidbong@tilde.cafe>, <bagasdotme@gmail.com>,
	<linux-acpi@vger.kernel.org>, <regressions@lists.linux.dev>,
	<stable@vger.kernel.org>
Subject: Re: [REGRESSION] Asus X541UAK hangs on suspend and poweroff (v6.1.6 onward)
Date: Mon, 17 Apr 2023 10:37:49 +0300	[thread overview]
Message-ID: <CRYTB8JBZ2LK.BAFK0AHDHPNA@bong> (raw)
In-Reply-To: <b2edf1ed-2777-03ef-4d5e-e355a6074f78@leemhuis.info>

So, I followed your advice and used the sources (6.3-rc6). Compiled even
two versions: with my config (cf. head letter) and the Arch Linux one
(I'm using Gentoo, but it still fits well), both updated with
`olddefconfig`. Just to make sure that the problem is independent from
the config.

Good news: I experienced the hanging 3 times with both kernels
yesterday.

Two of them were on the custom kernel, and they were of the rare kind -
they occured on shutdown. It goes normally, init disables the services,
unmounts the filesystems, turns off the screen, but then - no response
and the LED and the fan are still on. Another couple of shutdowns went
normal, so the issue it still irregular.

One happened later on the Arch-based one and after a suspend.

/var/log/kern.log showed nothing specific in all cases.

Bad news: it seems, the fix hasn't arrived yet.

How do I proceed next?

--

P.S. On the `pci=nomsi` case: I don't consider it being related to the
issue we're discussing. For me it seems like a hardware issue that can
be bypassed by reconfiguration.

  parent reply	other threads:[~2023-04-17  7:39 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 [this message]
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

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=CRYTB8JBZ2LK.BAFK0AHDHPNA@bong \
    --to=acidbong@tilde.cafe \
    --cc=bagasdotme@gmail.com \
    --cc=linux-acpi@vger.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