From: David Miller <davem@davemloft.net>
To: brking@linux.vnet.ibm.com
Cc: siva.kallam@broadcom.com, prashant@broadcom.com,
mchan@broadcom.com, benjamin.kun@broadcom.com,
netdev@vger.kernel.org, maurosr@linux.vnet.ibm.com,
muvic@linux.vnet.ibm.com, brking@pobox.com,
stable@vger.kernel.org
Subject: Re: [PATCH] tg3: Fix rx hang on MTU change with 5717/5719
Date: Tue, 19 Dec 2017 10:25:40 -0500 (EST) [thread overview]
Message-ID: <20171219.102540.514500547389365802.davem@davemloft.net> (raw)
In-Reply-To: <1513372910-32121-1-git-send-email-brking@linux.vnet.ibm.com>
From: Brian King <brking@linux.vnet.ibm.com>
Date: Fri, 15 Dec 2017 15:21:50 -0600
> This fixes a hang issue seen when changing the MTU size from 1500 MTU
> to 9000 MTU on both 5717 and 5719 chips. In discussion with Broadcom,
> they've indicated that these chipsets have the same phy as the 57766
> chipset, so the same workarounds apply. This has been tested by IBM
> on both Power 8 and Power 9 systems as well as by Broadcom on x86
> hardware and has been confirmed to resolve the hang issue.
>
> Cc: stable <stable@vger.kernel.org>
> Signed-off-by: Brian King <brking@linux.vnet.ibm.com>
Applied and queued up for -stable.
Please do not add explicit CC: stable tags for networking patches, as
documented in Documentation/networking/netdev-FAQ.txt
Thank you.
next prev parent reply other threads:[~2017-12-19 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 21:21 [PATCH] tg3: Fix rx hang on MTU change with 5717/5719 Brian King
2017-12-19 15:25 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-17 4:26 Siva Reddy Kallam
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=20171219.102540.514500547389365802.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benjamin.kun@broadcom.com \
--cc=brking@linux.vnet.ibm.com \
--cc=brking@pobox.com \
--cc=maurosr@linux.vnet.ibm.com \
--cc=mchan@broadcom.com \
--cc=muvic@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=prashant@broadcom.com \
--cc=siva.kallam@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