Commit 12a8541d authored by Yuval Mintz's avatar Yuval Mintz Committed by David S. Miller

bnx2x: Delay during kdump load

In a kdump environment interfaces might be re-loaded without a proper
unload sequence in the previous running kernel.
bnx2x management FW and driver maintains a `pulse' that notifies the FW
that the driver is still up and running.

Driver load on the kdump kernel should be performed only after the pulse
has been out-of-sync long enough for the management FW to identify that
the driver has crashed, on which point it will perform some necessary
cleanup of the HW.

In today's distros kdump loading is quite fast, sometimes too fast for our
FW to get out-of-sync. This patch delays the bnx2x's probe during kdump
to allow a proper re-load on the kdump kernel.
Signed-off-by: default avatarYuval Mintz <Yuval.Mintz@qlogic.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent e913fb27
...@@ -13368,6 +13368,12 @@ static int bnx2x_init_one(struct pci_dev *pdev, ...@@ -13368,6 +13368,12 @@ static int bnx2x_init_one(struct pci_dev *pdev,
bool is_vf; bool is_vf;
int cnic_cnt; int cnic_cnt;
/* Management FW 'remembers' living interfaces. Allow it some time
* to forget previously living interfaces, allowing a proper re-load.
*/
if (is_kdump_kernel())
msleep(5000);
/* An estimated maximum supported CoS number according to the chip /* An estimated maximum supported CoS number according to the chip
* version. * version.
* We will try to roughly estimate the maximum number of CoSes this chip * We will try to roughly estimate the maximum number of CoSes this chip
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment