summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/syscall-counts-by-pid.py
diff options
context:
space:
mode:
authorShannon Nelson <snelson@pensando.io>2022-02-18 01:02:49 +0300
committerJakub Kicinski <kuba@kernel.org>2022-02-19 07:37:14 +0300
commit12b1b997c0e5604f1a5c081f51ff67f4c814b7dd (patch)
treeff0b8779d5ae8af03e191d167a24aa121c5f90f7 /tools/perf/scripts/python/syscall-counts-by-pid.py
parent86213f80da1b1d007721cc22e04b5f5d0da33127 (diff)
downloadlinux-12b1b997c0e5604f1a5c081f51ff67f4c814b7dd.tar.xz
ionic: catch transition back to RUNNING with fw_generation 0
In some graceful updates that get initially triggered by the RESET event, especially with older firmware, the fw_generation bits don't change but the fw_status is seen to go to 0 then back to 1. However, the driver didn't perform the restart, remained waiting for fw_generation to change, and got left in limbo. This is because the clearing of idev->fw_status_ready to 0 didn't happen correctly as it was buried in the transition trigger: since the transition down was triggered not here but in the RESET event handler, the clear to 0 didn't happen, so the transition back to 1 wasn't detected. Fix this particular case by bringing the setting of idev->fw_status_ready back out to where it was before. Fixes: 398d1e37f960 ("ionic: add FW_STOPPING state") Signed-off-by: Shannon Nelson <snelson@pensando.io> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions