mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Armin Wolf <W_Armin@gmx.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ACPI: OSL: Poweroff when encountering a fatal ACPI error
Date: Thu, 26 Feb 2026 07:35:47 +0100	[thread overview]
Message-ID: <6825e6b2-802b-4cd2-b2c5-b4eab67b00e4@gmx.de> (raw)
In-Reply-To: <CAJZ5v0g6w_2+4oUytzxHtAhsJczK9pe84ZfXPeOcjKqU0k_GkQ@mail.gmail.com>

Am 25.02.26 um 22:28 schrieb Rafael J. Wysocki:

> On Wed, Feb 25, 2026 at 12:06 AM Armin Wolf <W_Armin@gmx.de> wrote:
>> Am 04.02.26 um 22:29 schrieb Armin Wolf:
>>
>>> The ACPI spec states that the operating system should respond
>>> to a fatal ACPI error by "performing a controlled OS shutdown in
>>> a timely fashion". Comply with the ACPI specification by powering
>>> off the system when ACPICA signals a fatal ACPI error. Users can
>>> still disable this behavior by using the acpi.poweroff_on_fatal
>>> kernel option to work around firmware bugs.
>> Any updates on this?
> I was about to apply it, but then I thought that I was not sure about
> the Kconfig option.
>
>   I don't see much value in it TBH.  If you agree, I'll just apply the
> patch without that part.
>
> Thanks!

You can drop the Kconfig option if you want.

Thanks,
Armin Wolf


  reply	other threads:[~2026-02-26  6:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04 21:29 Armin Wolf
2026-02-24 23:05 ` Armin Wolf
2026-02-25 21:28   ` Rafael J. Wysocki
2026-02-26  6:35     ` Armin Wolf [this message]
2026-02-26 18:46       ` Rafael J. Wysocki
2026-02-27 19:50         ` Armin Wolf
2026-02-27 19:55           ` Armin Wolf
2026-02-27 20:39             ` Rafael J. Wysocki
2026-03-01 17:59               ` Armin Wolf

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=6825e6b2-802b-4cd2-b2c5-b4eab67b00e4@gmx.de \
    --to=w_armin@gmx.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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

all inboxes | Powered by JetHome®