Public bug reported:
I use stress-ng to stress CPU(Xeon E3, CentOS7). During the test, I
found that system clock has been modified to 1970 or 1969 strangely,
but this modification has no effect to rtc. For a tough debug, found
stress-opcode cause this modification, below is the code
((void (*)(void))(ops_begin + mwc8()))();
And I limit test to opcode only, like this :
./stress-ng --opcode 0 --timeout 3m --log-file log/opcode.log
The test also cause different results, like user logout, gibberish
output and so on. Can anyone explain this test, I have read some short
description about opcode in cpu.job, but still question how the test
code work. For the system time is changed, but the test past, how can
I how if the system work correctly or not?
** Affects: stress-ng (Ubuntu)
Importance: Medium
Assignee: Colin Ian King (colin-king)
Status: In Progress
** Changed in: stress-ng (Ubuntu)
Status: New => In Progress
** Changed in: stress-ng (Ubuntu)
Importance: Undecided => Medium
** 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/1714044
Title:
stress-ng opcode test should run with call capabilities disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1714044/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
