Hi Colin,
the patch in comment #2 does not work on my system with 128 CPUs. I still got
the BUG: soft lockup, and eventually kill my ssh session.
I think the workaround is making the client (sender) wait for the main process
done with creating all the stressor's instances.
--
You received
** Changed in: linux
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968361
Title:
rawsock test BUG: soft lockup
To manage notifications about this bug go to:
Work-aound committed to stress-ng:
commit 69328da97f04745a9da2890c90c131c2322f81e2 (HEAD -> master)
Author: Colin Ian King
Date: Wed Apr 27 08:49:12 2022 +
stress-rawsock: make client wait for server to start
--
You received this bug notification because you are a member of Ubuntu
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968361
Title:
rawsock test BUG: soft lockup
To manage notifications about this bug go to:
** Changed in: linux
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968361
Title:
rawsock test BUG: soft lockup
To manage notifications about this bug go to:
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: stress-ng
Importance: Undecided => Low
** Changed in: stress-ng
Assignee: (unassigned) => Colin Ian King (colin-king)
** Bug watch
