Comment 6 for bug 1814095

Terry,

We've had a lot of discussion over this bug. It does not have
a reliable reproducer, and I have not yet received any acks
on testing of the above.

Our thinking was that it was still better to patch it since
it has been seen by the mainline driver as well and we'd like
to avoid a re-occurrence of the situation.

The need is to have the fix be available in the Xenial official
bits, for sure (rather than providing a temporary test kernel
via our ppa or something, for instance).

FWIW, here are the boards in question:
enum board_idx {
        BCM57301,
        BCM57417_NPAR,
        BCM58700,
        BCM57311,
        BCM57312,
        BCM57402,
        BCM57402_NPAR,
        BCM57407,
        BCM57412,
        BCM57414,
        BCM57416,
        BCM57417,
        BCM57412_NPAR,
        BCM57314,
        BCM57417_SFP,
        BCM57416_SFP,
        BCM57404_NPAR,
        BCM57406_NPAR,
        BCM57407_SFP,
        BCM57407_NPAR,
        BCM57414_NPAR,
        BCM57416_NPAR,
        BCM57452,
        BCM57454,
        NETXTREME_E_VF,
        NETXTREME_C_VF,
};

Per conversation with Brad and Jay, it was agreed that patching
the bnxt_en_bpo driver only with this fix was the way to go,
despite the lack of a reproducer, rather than pulling in an
entire new driver from Broadcom as also potentially mulled over.

The FW version the issue was hit on:
firmware-version: 20.8.163/1.8.4 pkg 20.08.04.03

But it might be best to test with latest available
firmware (214.0.166/1.9.2 pkg 21.40.16.6 or later).

Not sure if that helps? Let me know if I can address anything
else.