From: Oskar Ray-Frayssinet <rayfraytech@gmail.com>
To: pavan.chebbi@broadcom.com
Cc: mchan@broadcom.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, lszubowi@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Oskar Ray-Frayssinet <rayfraytech@gmail.com>
Subject: [PATCH net v2] tg3: Add PowerEdge R740xd to AER quirk list
Date: Sun, 5 Apr 2026 00:50:23 +0200 [thread overview]
Message-ID: <20260404225023.1254-1-rayfraytech@gmail.com> (raw)
The PowerEdge R740xd is a variant of the R740 that also triggers
a fatal PCIe AER event during system reboot. Add it to the DMI
list to apply the same workaround.
Fixes: e0efe83ed325 ("tg3: Disable tg3 PCIe AER on system reboot")
Signed-off-by: Oskar Ray-Frayssinet <rayfraytech@gmail.com>
---
v2: Also add "R740XD vSAN Ready Node" DMI name as reported in
bugzilla #221279 by Thomas Berger
v1: Add "PowerEdge R740xd" DMI name
drivers/net/ethernet/broadcom/tg3.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/drivers/net/ethernet/broadcom/tg3.c b/drivers/net/ethernet/broadcom/tg3.c
index 73a4b569b03e..2b95c97e8161 100644
--- a/drivers/net/ethernet/broadcom/tg3.c
+++ b/drivers/net/ethernet/broadcom/tg3.c
@@ -18216,6 +18216,18 @@ static const struct dmi_system_id tg3_restart_aer_quirk_table[] = {
DMI_MATCH(DMI_PRODUCT_NAME, "PowerEdge R740"),
},
},
+ {
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
+ DMI_MATCH(DMI_PRODUCT_NAME, "PowerEdge R740xd"),
+ },
+ },
+ {
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
+ DMI_MATCH(DMI_PRODUCT_NAME, "R740XD vSAN Ready Node"),
+ },
+ },
{
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
--
2.43.0
next reply other threads:[~2026-04-04 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 22:50 Oskar Ray-Frayssinet [this message]
2026-04-04 23:03 ` [PATCH net v2] tg3: Add PowerEdge R740xd to AER quirk list Andrew Lunn
2026-04-05 10:56 ` Oskar Ray-Frayssinet
2026-04-05 23:49 ` Andrew Lunn
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=20260404225023.1254-1-rayfraytech@gmail.com \
--to=rayfraytech@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lszubowi@redhat.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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.