From: PGNet Dev <pgnet.dev@gmail.com>
To: gregkh@linuxfoundation.org
Cc: hui.wang@canonical.com, rafael.j.wysocki@intel.com,
stable@vger.kernel.org, regressions@lists.linux.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:41:01 -0400 [thread overview]
Message-ID: <a64b85a6-cc26-afc3-4d6a-85c7a366576b@gmail.com> (raw)
In-Reply-To: <YREdlli29GUfvaUx@kroah.com>
On 8/9/21 8:20 AM, Greg KH wrote:
> On Mon, Aug 09, 2021 at 08:15:11AM -0400, PGNet Dev wrote:
>> On 7/31/21 2:56 AM, gregkh@linuxfoundation.org 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:
>>> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>>
>>> 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 <stable@vger.kernel.org> know about it.
>>>
>>>
>>> From e0eef3690dc66b3ecc6e0f1267f332403eb22bea Mon Sep 17 00:00:00 2001
>>> From: Hui Wang <hui.wang@canonical.com>
>>> Date: Wed, 28 Jul 2021 23:19:58 +0800
>>> Subject: Revert "ACPI: resources: Add checks for ACPI IRQ override"
>>>
>>> From: Hui Wang <hui.wang@canonical.com>
>>>
>>> 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"
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-5.13.y&id=02db470b866fd06d8951
>>
>> , 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.
>
> I do not understand, am I missing something in the queue for the next
> 5.13 release that needs to be applied?
no.
just confirming this^ revert, landed in 5.13.8, _works_ to fix non-boot.
system _does_ bump into 60-sec REboot.
wasn't sure it's related to this^ or not ...
the fix for this _next_ issue appears already in 5.13.9/stable (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-5.13.y&id=02db470b866fd06d8951)
The module blacklist workaround works for 5.13.8.
i.e., as it stands, 5.13.8 is usable (here), iff the iTCO mod blacklist workaround is applied.
5.13.9 is expected to resolved it.
prev parent reply other threads:[~2021-08-09 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16277146132219@kroah.com>
2021-08-09 12:15 ` Patch "Revert "ACPI: resources: Add checks for ACPI IRQ override"" has been added to the 5.13-stable tree PGNet Dev
2021-08-09 12:20 ` Greg KH
2021-08-09 12:41 ` PGNet Dev [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=a64b85a6-cc26-afc3-4d6a-85c7a366576b@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=rafael.j.wysocki@intel.com \
--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).