Public bug reported:
Hi there,
always see hard resets (no logs, no messages) on different machines if
they run the fstat stressor (even one stressor is enough). Cause I see
this behaviour on different systems I assume that this is not hardware
error but a may be a bsic problem of the stressor itself, could it? MOst
of the systems use a RAID controller, but different models, stress-ng is
running on RAID volumes.
Or any ideas how to "debug" what's going on then during a fstat run?
Verbosity does not show me any hint...
Thank you in advance
Martin
** Affects: stress-ng (Ubuntu)
Importance: High
Assignee: Colin Ian King (colin-king)
Status: New
** Changed in: stress-ng (Ubuntu)
Importance: Undecided => High
** Changed in: stress-ng (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493950
Title:
stress-ng is causing a kernel reboot by stat'ing a /dev entry
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1493950/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
