** Changed in: stress-ng
Status: In Progress => Fix Released
** Changed in: stress-ng
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: stress-ng
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages,
I believe it is ok to say this bug is fix already. Thanks Colin.
** Changed in: stress-ng
Assignee: Ike Panhc (ikepanhc) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
For more information, test V0.15.00 to V0.15.04 for 300 times each[1], I
can reproduce on V0.15.00 and V0.15.01 only.
console output are attached.
--
[1]
#!/bin/bash
for i in `cat gittag.txt`; do
echo $i
cd /home/ubuntu/stress-ng
make clean
git reset
Thanks Colin,
For your information, I ran a loop test[1] on each of stress-ng tags
since V0.12.00, with 100 times lockofd run and see the return value.
This issue starts to be seen since V0.12.09 (or maybe early because the
reprudce chance is very low). Full console log is attached for your
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999731
Title:
disk stress test failing with code 7
Status in
** Changed in: stress-ng (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999731
Title:
disk stress test failing with code 7
Status
The log was attached
** Attachment added: "stress-ng_0.15.04-1~j_amd64_log.txt"
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1999731/+attachment/5647719/+files/stress-ng_0.15.04-1~j_amd64_log.txt
--
You received this bug notification because you are a member of Kernel
Packages,
Test with stress-ng_0.15.04-1~j_amd64 + ubunut 22.04(5.15.0-58-generic)
+ Micron_7450_MTFDKCB3T8TFR -> Passed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999731
Title:
disk stress
Thanks cking, I have trouble finding a machine stably reproducing this
issue.
I will run >100 times test on V0.15.04 and V0.15.03. If V0.15.04 is much
more stable, we can switch to V0.15.04 to avoid this issue.
Many thanks.
--
You received this bug notification because you are a member of
the updated stress-ng is available from the stress-ng ppa:
https://launchpad.net/~colin-king/+archive/ubuntu/stress-ng/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999731
Title:
stress-ng V0.15.04 has been released with a fix for this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999731
Title:
disk stress test failing with code 7
Status in Stress-ng:
I managed to corner the bug, the termination signal on timeout was
killing the contention process with SIGKILL and this was killing the
bogo-op increment mid increment causing the internal state to be
inconsistent on the bogo-op counter. I've pushed a fix to the main repo:
commit
Hi Colin,
I have attached a test run that reproduces this issue on Focal. The
dmesg file is located in the following location:
attachment_files/com.canonical.certification__dmesg_attachment
** Attachment added: "submission_201902-26829_297719.tar.xz"
Hi Ike,
I'm having difficulty reproducing this.
1. Please attach the dmesg log to the bug report when this fails
2. What file system is being used?
3. Does this occur with the latest version of stress-ng
- one can use the packages from
Here is the fail log with stress-ng 0.15.01-1~f1 on d05-5 with `--vmstat
1`
** Attachment added: "faillog.txt"
https://bugs.launchpad.net/stress-ng/+bug/1999731/+attachment/5639246/+files/faillog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
Running 5.4.0-135.152 kernel on
d05-2 with stress-ng 0.11.07-1ubuntu2 -> 10/10 passed
d05-2 with stress-ng 0.14.06-0~202210291239~ubuntu20.04.1 -> 10/10 passed
d05-5 with stress-ng 0.15.01-1~f1 -> 9/10 passed
and on d05-5 with stress-ng 0.14.06-0~202210291239~ubuntu20.04.1 I see
failure
Thanks cking and David,
I am running 0.11.07-1ubuntu2 from archive,
0.14.06-0~202210291239~ubuntu20.04.1 from ppa:hardware-
certification/public and 0.15.01-1~f1 from ppa:colin-king/stress-ng with
5.4.0-135.152 kernel to see if stress-ng version matters.
If not, next step is to test on kernels.
Test with stress-ng_0.13.12-2ubuntu1_amd64.deb -> Passed
27 Dec 03:53: Running stress-ng locka stressor for 240 seconds...
stress-ng: info: [3300189] setting to a 240 second (4 mins, 0.00 secs) run per
stressor
stress-ng: info: [3300189] dispatching hogs: 176 locka
stress-ng: info: [3300189]
It may be worth using stress-ng from https://launchpad.net/~colin-
king/+archive/ubuntu/stress-ng or building it from source using:
git clone https://github.com/ColinIanKing/stress-ng
cd stress-ng
git checkout V0.15.00
make clean
make
and then running:
./stress-ng --lockofd 0 -t 300 --vmstat 1
Return value 7 is "EXIT_METRICS_UNTRUSTWORTHY", this may mean the
stressor may have been killed manually and/or it terminated abruptly
causing it to be unable to store the bogo/ops metrics in a shared memory
segment reliably.
Only two commits have changed in the lockofd stressor since Aug 2022:
So far we are not sure this is because of kernel update or stress-ng
update. I am going to correct all failure information and see if there
are hints within.
The stress-ng we use is from ppa:hardware-certification/public and
kernel is from Ubuntu archive.
** Changed in: stress-ng (Ubuntu)
21 matches
Mail list logo
