burnintest v3.3 test issue use environment kernel 4.8.0-58 in ubuntu 16.04.

[ZiMin]

Hi Sir,

Burnintest v3.3 use environment kernel 4.8.0-58 in ubuntu 16.04 destop.

CPU:Apollo Lake N3350,MemoryDR3L 8G 1866MHz.Disk:SATA SSD 32GB.
Run CPU-Maths,2D Graphics,3D Graphics,Disk,Memory and Network.


In run 48 hour, Burnintest v3.3 tool happen auto shut down of situation,
but ubuntu 16.04 has not Crash,import Burnintest command of terminal
no disappear.Again import "./burnintest.sh",Burnintest can run.

Auto stop after set 0 and cycles set 0,It can be run without time limit.
But happen 48 hour uto shut down.

Thanks&Best regards

Zimin

[David (PassMark)]

Can you try with V4 of BurnInTest for Linux.

How long did it run before it crashed?
Was it reproducible?
Did this happen just on one machine out of a batch of machines?
Were there any errors before the crash?

[ZiMin]

My company is not buy Burnintest_V4 version,not run long time.

How long did it run before it crashed? Ans:48 hour.

Was it reproducible?Ans:Yes.

Did this happen just on one machine out of a batch of machines?
Ans:Current test 2pcs,48hour happen crashed,
1pcs again run 27hr is pass,but change environment to ubuntu 14.04 collocation Burnintest v3.3,continue testing.
I am increase other 1pcs test 3hr is pass,continue testing.
I am too increase Bay Trail N2807 1pcs,test environment to ubuntu 16.04 collocation Burnintest v3.3,continue testing.

Were there any errors before the crash?
Ans:No Error,only happen butnintest GUI window disappear,but import Burnintest command of terminal no disappear,system can work.

[ZiMin]

"ubuntu 1604_2.png" is GUI window disappear in after run 48hr.
"ubuntu 1404.png" is GUI window no disappear in after run 48hr,It is testing 95hr PASS.

[Tim (PassMark)]

There is likely a resource issue on the system (eg low memory situation) and Ubuntu has decided to kill the process that is holding the most resources, in this case BurnInTest. This could mean there is a memory leak in a device driver somewhere so the longer that BurnInTest is running the worse the situation gets, particularly if it only happens on certain versions of the same operating system and not others.

You can try disabling or re-configuring the OOM killer process or you could do something to lower the stress on the system, eg don't run the memory test with the main set of tests and run it separately.