archive mirror
 help / color / mirror / Atom feed
From: PGNet Dev <>
Subject: Re: Patch "Revert "ACPI: resources: Add checks for ACPI IRQ override"" has been added to the 5.13-stable tree
Date: Mon, 9 Aug 2021 08:15:11 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 7/31/21 2:56 AM, wrote:
> This is a note to let you know that I've just added the patch titled
>      Revert "ACPI: resources: Add checks for ACPI IRQ override"
> to the 5.13-stable tree which can be found at:
> The filename of the patch is:
>       revert-acpi-resources-add-checks-for-acpi-irq-override.patch
> and it can be found in the queue-5.13 subdirectory.
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <> know about it.
>  From e0eef3690dc66b3ecc6e0f1267f332403eb22bea Mon Sep 17 00:00:00 2001
> From: Hui Wang <>
> Date: Wed, 28 Jul 2021 23:19:58 +0800
> Subject: Revert "ACPI: resources: Add checks for ACPI IRQ override"
> From: Hui Wang <>
> commit e0eef3690dc66b3ecc6e0f1267f332403eb22bea upstream.

Confirming that this^ revert resolves the reported non-boot regression

System does boot cleanly; but, then REboots @ 60 seconds.

It's a known bug, with fix already in 5.13.9/stable:

  Revert "watchdog: iTCO_wdt: Account for rebooting on second timeout"

, causing TCO watchdog auto-reboot @ 60 secs.

Although particularly nasty on servers with /boot on RAID, breaking arrays if watchdog boots before arrays correctly assembled, iiuc, it's UN-related

With interim workaround

  edit /etc/modprobe.d/blacklist.conf

+	blacklist iTCO_wdt
+	blacklist iTCO_vendor_support

for this second issue in place, 5.13.8 boots & appears stable.

       reply	other threads:[~2021-08-09 12:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-08-09 12:15 ` PGNet Dev [this message]
2021-08-09 12:20   ` Patch "Revert "ACPI: resources: Add checks for ACPI IRQ override"" has been added to the 5.13-stable tree Greg KH
2021-08-09 12:41     ` PGNet Dev

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).