summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-04-09 20:19:47 -0700
committerJakub Kicinski <kuba@kernel.org>2026-04-09 20:19:48 -0700
commit8832e5791d73c8db5d962091b3ac6d7530cde65a (patch)
treee454dec0398b5b3933b9acc5251c4984bca93d43 /tools/perf/scripts/python/stackcollapse.py
parentb02e3c4c80c91693b05c82751149d05d921bccb9 (diff)
parent5393b2b5bee2ac51a0043dc7f4ac3475f053d08d (diff)
Merge branch 'net-bcmgenet-fix-queue-lock-up'
Justin Chen says: ==================== net: bcmgenet: fix queue lock up We have been seeing reports of logs like this. [ 41.761198] bcmgenet 1001300000.ethernet eth0: NETDEV WATCHDOG: CPU: 0: transmit queue 2 timed out 10039 ms [ 43.745198] bcmgenet 1001300000.ethernet eth0: NETDEV WATCHDOG: CPU: 0: transmit queue 2 timed out 12023 ms [ 45.729198] bcmgenet 1001300000.ethernet eth0: NETDEV WATCHDOG: CPU: 0: transmit queue 2 timed out 14007 ms We have two issues. The persistent queue timeouts and the eventual lock up of the entire transmit. We address the lock up issue first. The queue timeouts are due to a fundamental design issue not a bug perse. Timeouts still persist, but we should no longer lock up. ==================== Link: https://patch.msgid.link/20260406175756.134567-1-justin.chen@broadcom.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions