mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-28 11:18:45 +07:00
3d6b72534a
When running in a kdump kernel, it's very likely that due to sync. loss with management firmware the first PCI function to probe and reach the previous unload flow would decide it can reset the chip and continue onward. While doing so, it will only close its own Rx port. On a 4-port device where 2nd port on engine is a 1g-port, the 2nd port would allow ingress traffic after the chip is reset [assuming it was active on the first kernel]. This would later cause a HW attention. This changes driver flow to close both ports' 1g capabilities during the previous driver unload flow prior to the chip reset. Signed-off-by: Yuval Mintz <Yuval.Mintz@qlogic.com> Signed-off-by: Ariel Elior <Ariel.Elior@qlogic.com> Signed-off-by: David S. Miller <davem@davemloft.net> |
||
|---|---|---|
| .. | ||
| bnx2x_cmn.c | ||
| bnx2x_cmn.h | ||
| bnx2x_dcb.c | ||
| bnx2x_dcb.h | ||
| bnx2x_dump.h | ||
| bnx2x_ethtool.c | ||
| bnx2x_fw_defs.h | ||
| bnx2x_fw_file_hdr.h | ||
| bnx2x_hsi.h | ||
| bnx2x_init_ops.h | ||
| bnx2x_init.h | ||
| bnx2x_link.c | ||
| bnx2x_link.h | ||
| bnx2x_main.c | ||
| bnx2x_mfw_req.h | ||
| bnx2x_reg.h | ||
| bnx2x_sp.c | ||
| bnx2x_sp.h | ||
| bnx2x_sriov.c | ||
| bnx2x_sriov.h | ||
| bnx2x_stats.c | ||
| bnx2x_stats.h | ||
| bnx2x_vfpf.c | ||
| bnx2x_vfpf.h | ||
| bnx2x.h | ||
| Makefile | ||