From: "Noam D. Eliyahu" <noam.d.eliyahu@gmail.com>
To: "Pavan Chebbi" <pavan.chebbi@broadcom.com>
Cc: <mchan@broadcom.com>, <netdev@vger.kernel.org>,
"George Shuklin" <george.shuklin@gmail.com>,
"Lenny Szubowicz" <lszubowi@redhat.com>
Subject: Re: [DISCUSS] tg3 reboot handling on Dell T440 (BCM5720)
Date: Fri, 02 Jan 2026 18:22:58 +0200 [thread overview]
Message-ID: <DFE8DLTGB5Q0.1184HJSQ0DHK2@pve> (raw)
In-Reply-To: <CALs4sv0BdhVHawBkkxN2v2o_jqGyFRAe1RVJjGu9d08HM2Jwug@mail.gmail.com>
On Wed Dec 31, 2025 at 5:10 PM IST, Pavan Chebbi wrote:
> OK I now understand. You make a lucid argument. 9fc3bc764334 does
> indicate that the problem it is trying to fix is very much limited to
> R650xs.
Indeed AER suppression is needed only because of the conditional
tg3_power_down.
So both the conditional tg3_power_down and the AER suppression should
be scoped only to the platforms that originally required them.
This preserves the intent of the original commits while avoiding
whitelist maintenance and reflecting the relationship between the two bugs.
> Hence while I am almost sure that your proposal (about adding
> conditional tg3_power_down for R650xs alone) won't break anything for
> cc: George, we need an ack from cc: Lenny, to see if he is OK with an
> unconditional power down, and that he had no other motive to disable
> AER in tg3 config space. In all possible logic, it should just be fine
> because e0efe83ed3252 is fixing 9fc3bc764334.
Sounds great!
I'll wait for an ACK from Lenny confirming that this approach -
limiting both conditional tg3_power_down and AER suppression to the
affected platforms - works for his setups and doesn't need broader
application.
> P.S Sorry for the delayed reply. I am on vacation.
Totally reasonable - between Christmas and the New Year, I haven't been
very active myself.
Wishing everyone a happy and hopefully reboot-hang-free start to the New Year!
If it helps, I can provide a pre-approved patch so George or Lenny can
test it on their hardware before I try to commit one.
Thanks,
Noam D. Eliyahu
prev parent reply other threads:[~2026-01-02 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 17:50 [DISCUSS] tg3 reboot handling on Dell T440 (BCM5720) Noam D. Eliyahu
2025-12-22 5:53 ` Pavan Chebbi
2025-12-24 16:53 ` Noam D. Eliyahu
2025-12-31 15:10 ` Pavan Chebbi
2026-01-02 16:22 ` Noam D. Eliyahu [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=DFE8DLTGB5Q0.1184HJSQ0DHK2@pve \
--to=noam.d.eliyahu@gmail.com \
--cc=george.shuklin@gmail.com \
--cc=lszubowi@redhat.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox