[hns-1126]net: hns3: re-schedule reset task while VF reset fail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kunpeng920 |
Fix Released
|
Undecided
|
Unassigned | ||
Ubuntu-18.04 |
Won't Fix
|
Undecided
|
Unassigned | ||
Ubuntu-18.04-hwe |
Fix Released
|
Undecided
|
Unassigned | ||
Ubuntu-19.04 |
Won't Fix
|
Undecided
|
Unassigned | ||
Ubuntu-19.10 |
Fix Released
|
Undecided
|
Unassigned | ||
Upstream-kernel |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
"[Bug Description]
The VF reset may fail for some probabilistic reasons,
such as wait for hardware reset timeout, wait for mailbox
response timeout, so this patch tries to re-schedule the
reset task when the number of reset failing is under
HCLGEVF_
[Steps to Reproduce]
1.load PF & VF drvier
2.run VF & PF & Global reset
[Actual Results]
VF reset fail
[ 5425.748305] hns3 0000:7d:03.0: Reset done
[ 5425.789478] hns3 0000:7d:02.7: cleaned 2, need to clean 1
[ 5425.789478] hns3 0000:7d:02.7: cleaned 2, need to clean 1
[ 5426.141472] hns3 0000:7d:03.2: cleaned 2, need to clean 1
[ 5426.141472] hns3 0000:7d:03.2: cleaned 2, need to clean 1
[ 5426.269472] hns3 0000:7d:03.3: cleaned 2, need to clean 1
[ 5426.269472] hns3 0000:7d:03.3: cleaned 2, need to clean 1
[ 5431.769468] hns3 0000:7d:03.0: VF could not get mbx resp(=0) from PF in 500 tries
[ 5431.769468] hns3 0000:7d:03.0: VF could not get mbx resp(=0) from PF in 500 tries
[ 5431.784456] hns3 0000:7d:03.0: notify nic client failed 4(-5)
[ 5431.784456] hns3 0000:7d:03.0: notify nic client failed 4(-5)
[ 5431.795957] hns3 0000:7d:03.0: failed to reset VF stack
[ 5431.795957] hns3 0000:7d:03.0: failed to reset VF stack
[ 5431.806436] hns3 0000:7d:03.0: The firmware version is b0620130
[ 5431.806436] hns3 0000:7d:03.0: The firmware version is b0620130
[ 5431.818284] hns3 0000:7d:03.0: failed to reset VF
[ 5431.818284] hns3 0000:7d:03.0: failed to reset VF
[ 5431.827694] hns3 0000:7d:03.0: VF stack reset failed -5.
[ 5431.827694] hns3 0000:7d:03.0: VF stack reset failed -5.
[ 5431.876199] hns3 0000:7d:03.4: The firmware version is b0620130
[ 5431.876199] hns3 0000:7d:03.4: The firmware version is b0620130
[ 5431.888292] hns3 0000:7d:03.4: Reset done
[ 5431.888292] hns3 0000:7d:03.4: Reset done
[ 5431.959848] hns3 0000:7d:03.1: The firmware version is b0620130
[ 5431.959848] hns3 0000:7d:03.1: The firmware version is b0620130
[ 5431.971923] hns3 0000:7d:03.1: Reset done
[ 5431.971923] hns3 0000:7d:03.1: Reset done
[ 5432.043704] hns3 0000:7d:01.4: The firmware version is b0620130
[ 5432.043704] hns3 0000:7d:01.4: The firmware version is b0620130
[ 5432.055777] hns3 0000:7d:01.4: Reset done
[ 5432.055777] hns3 0000:7d:01.4: Reset done
[ 5432.078777] hns3 0000:7d:00.0: cleaned 3, need to clean 2
[ 5432.078777] hns3 0000:7d:00.0: cleaned 3, need to clean 2
[ 5432.128093] hns3 0000:7d:01.6: The firmware version is b0620130
[ 5432.128093] hns3 0000:7d:01.6: The firmware version is b0620130
[ 5432.140157] hns3 0000:7d:01.6: Reset done
[ 5432.140157] hns3 0000:7d:01.6: Reset done
[ 5432.211889] hns3 0000:7d:01.3: The firmware version is b0620130
[Expected Results]
VF reset ok
[Reproducibility]
Inevitably
[Additional information]
Hardware: D06
Firmware: NA
Kernel: NA
[Resolution]
This patch also add a function hclgevf_
net: hns3: re-schedule reset task while VF reset fail
no longer affects: | kunpeng920/ubuntu-20.04 |
Changed in kunpeng920: | |
status: | New → Fix Committed |
Changed in kunpeng920: | |
status: | Fix Committed → Triaged |
Changed in kunpeng920: | |
status: | Triaged → Fix Committed |
Changed in kunpeng920: | |
status: | Fix Committed → Fix Released |
Can not cherry-pick or backport to 4.15 kernel. There is no "struct hclgevf_rst_stats" in 4.15 kernel.