diff options
author | Hao Lan <lanhao@huawei.com> | 2024-10-25 17:29:32 +0800 |
---|---|---|
committer | Paolo Abeni <pabeni@redhat.com> | 2024-10-31 11:15:42 +0100 |
commit | 3e0f7cc887b77603182dceca4d3a6e84f6a40d0a (patch) | |
tree | 099c9ecaa5af986152d04821c0770642e20b4f9f /net/key | |
parent | f2c14899caba76da93ff3fff46b4d5a8f43ce07e (diff) | |
download | lwn-3e0f7cc887b77603182dceca4d3a6e84f6a40d0a.tar.gz lwn-3e0f7cc887b77603182dceca4d3a6e84f6a40d0a.zip |
net: hns3: fixed reset failure issues caused by the incorrect reset type
When a reset type that is not supported by the driver is input, a reset
pending flag bit of the HNAE3_NONE_RESET type is generated in
reset_pending. The driver does not have a mechanism to clear this type
of error. As a result, the driver considers that the reset is not
complete. This patch provides a mechanism to clear the
HNAE3_NONE_RESET flag and the parameter of
hnae3_ae_ops.set_default_reset_request is verified.
The error message:
hns3 0000:39:01.0: cmd failed -16
hns3 0000:39:01.0: hclge device re-init failed, VF is disabled!
hns3 0000:39:01.0: failed to reset VF stack
hns3 0000:39:01.0: failed to reset VF(4)
hns3 0000:39:01.0: prepare reset(2) wait done
hns3 0000:39:01.0 eth4: already uninitialized
Use the crash tool to view struct hclgevf_dev:
struct hclgevf_dev {
...
default_reset_request = 0x20,
reset_level = HNAE3_NONE_RESET,
reset_pending = 0x100,
reset_type = HNAE3_NONE_RESET,
...
};
Fixes: 720bd5837e37 ("net: hns3: add set_default_reset_request in the hnae3_ae_ops")
Signed-off-by: Hao Lan <lanhao@huawei.com>
Signed-off-by: Jijie Shao <shaojijie@huawei.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'net/key')
0 files changed, 0 insertions, 0 deletions