The fstat stressor is basically just stat'ing a load of files in /dev,
so it looks like an open()... fstat() ... close() or a stat() on a /dev/
entry is causing the kernel some issues. Are you running stress-ng as
root or not?
One way to see what is happening is to log in remotely and run strace on
stress-ng, this will capture the moment when a particular /dev is
accessed.. So run:
strace -f stress-ng --fstat 1
and see where it hangs. This looks like stress-ng has found a kernel
bug, so I'd be interested in seeing what happens, and which kernel you
are running on.
** Changed in: stress-ng (Ubuntu)
Status: New => Incomplete
--
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
