From: patchwork-bot+netdevbpf@kernel.org
To: Noam D. Eliyahu <noam.d.eliyahu@gmail.com>
Cc: netdev@vger.kernel.org, pavan.chebbi@broadcom.com,
michael.chan@broadcom.com, kuba@kernel.org, edumazet@kernel.org,
davem@davemloft.net, pabeni@redhat.com, andrew+netdev@lunn.ch,
horms@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] tg3: Invert restart quirk logic to restrict SNP power-down bypass
Date: Thu, 29 Oct 2026 11:40:04 +0000 [thread overview]
Message-ID: <179327400457.1773334.15430060848515366036.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261026220955.473247-1-noam.d.eliyahu@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 27 Oct 2026 00:09:56 +0200 you wrote:
> Commit 9fc3bc764334 ("tg3: power down device only on SYSTEM_POWER_OFF")
> bypassed `tg3_power_down()` on system restarts to prevent reboot hangs and
> NMIs on servers where NICs were initialized via SNP (such as Dell PowerEdge
> R650 and R750).
>
> However, skipping the power-down flow globally causes the ACPI _PTS method
> to trigger fatal PCIe AER events and hangs on other models. Commit
> e0efe83ed325 ("tg3: Disable tg3 PCIe AER on system reboot") attempted to
> mitigate this by adding an AER-disable DMI quirk table. Maintaining a
> growing list of models for a secondary symptom misses the root cause,
> leaving systems like the PowerEdge T440 (sharing the BCM5720 NIC) exposed.
>
> [...]
Here is the summary with links:
- [net] tg3: Invert restart quirk logic to restrict SNP power-down bypass
https://git.kernel.org/netdev/net/c/d7314b51341c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-29 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 22:09 [PATCH net] tg3: Invert restart quirk logic to restrict SNP power-down bypass Noam D. Eliyahu
2026-10-26 22:15 ` netdev-bot+sinfo
2026-10-26 22:42 ` Noam D. Eliyahu
2026-10-27 9:10 ` Pavan Chebbi
2026-10-29 11:40 ` patchwork-bot+netdevbpf [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=179327400457.1773334.15430060848515366036.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=noam.d.eliyahu@gmail.com \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--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