From: Bjoern Doebel <doebel@amazon.de>
To: <stable@vger.kernel.org>, Marc Zyngier <maz@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw@amazon.co.uk>,
"Ali Saidi" <alisaidi@amazon.com>,
David Arinzon <darinzon@amazon.com>,
"Zeev Zilberman" <zeev@amazon.com>
Cc: Bjoern Doebel <doebel@amazon.de>
Subject: Re: [PATCH] irqchip/gic-v3-its: Reconfigure ITS from software state on resume
Date: Thu, 2 Jul 2026 11:57:15 +0000 [thread overview]
Message-ID: <akZPM6SeJiM8th0N@amazon.de> (raw)
In-Reply-To: <20260507183102.1897629-1-doebel@amazon.de>
Hi all,
gentle ping on this one.
Since the original posting I've re-validated the fix against current
mainline:
- It still applies cleanly to v7.2-rc1 (and to v7.1.0).
- I reproduced the original failure on *stock* v7.2-rc1. On EC2
Graviton instances, hibernation resume fails 100% of the time: the
ITS comes back reset, MAPD/MAPTI are never replayed, and the ENA
NIC silently loses its LPIs:
ena 0000:00:05.0: ... didn't receive a MSI-X interrupt (cmd 3)
ena 0000:00:05.0: Failed to create IO CQ. error: -62
The instance then has no networking after resume.
- With this patch applied, the same kernel survives hibernate/resume
cleanly: 9/9 cycles with zero failures, across all three Graviton
generations (Graviton 2/3/4, i.e. Neoverse N1/V1/V2), networking
fully restored on every resume.
As described in the previous message, this is the fallout from 713335b6ee29
("irqchip/gic-v3-its: Implement .msi_teardown() callback"): device
teardown no longer happens across a suspend/resume that keeps the MSI
domain, so the ITS is never reprogrammed and drops interrupts after the
hardware has been reset.
Could you take a look when you get a chance?
Thanks,
Bjoern
Amazon Web Services Development Center Germany GmbH
Tamara-Danz-Str. 13
10243 Berlin
Geschaeftsfuehrung: Christof Hellmis, Andreas Stieger
Eingetragen am Amtsgericht Charlottenburg unter HRB 257764 B
Sitz: Berlin
Ust-ID: DE 365 538 597
next prev parent reply other threads:[~2026-07-02 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 18:31 [PATCH] irqchip/gic-v3-its: Reconfigure ITS from software state on resume Bjoern Doebel
2026-07-02 11:57 ` Bjoern Doebel [this message]
2026-07-02 15:13 ` Thomas Gleixner
2026-07-08 10:26 ` Marc Zyngier
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=akZPM6SeJiM8th0N@amazon.de \
--to=doebel@amazon.de \
--cc=alisaidi@amazon.com \
--cc=darinzon@amazon.com \
--cc=dwmw@amazon.co.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=zeev@amazon.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.