The dev test could randomly hit the kernel bug due to the chaotic racy
access of devices by this stressor. One could try and use --no-rand-seed
to use the same base random seed for more repeatable testing.
The dev stressor does report the device being accessed in argv[], this
can be observed when using ps -ef, for example one will see output
something like:
root 596457 596449 57 00:05 pts/0 00:00:03
stress-ng-dev:/dev/input/mice
root 596458 596451 36 00:05 pts/0 00:00:02
stress-ng-dev:/dev/input/event2
root 596459 596450 25 00:05 pts/0 00:00:01
stress-ng-dev:/dev/input/mouse2
root 596461 596453 3 00:05 pts/0 00:00:00 stress-ng-dev:/dev/psaux
root 596462 596452 21 00:05 pts/0 00:00:01
stress-ng-dev:/dev/vhost-vsock
root 596474 596454 5 00:05 pts/0 00:00:00
stress-ng-dev:/dev/input/mouse2
root 596483 596455 55 00:05 pts/0 00:00:03
stress-ng-dev:/dev/input/event2
root 596484 596456 22 00:05 pts/0 00:00:01 stress-ng-dev:/dev/psaux
...showing the stress-ng-dev stressor followed by the name of the device
being exercised. If these processes are hung then it will show which
device was being accessed when the process hung.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1998738
Title:
dev test from ubuntu_stress_smoke_tests cause kernel oops on F-5.4
xilinx ZCU106
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1998738/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
