jinengandhi-intel

We continue to see the issue as of Feb 21st. Copied are a few console links from opensource-CI where the errors were seen: https://localhost:8080/job/graphene-20.04/2237/testReport/LibOS.shim.test.ltp/test_ltp/test_direct___test_ltp_waitpid04_/ https://localhost:8080/job/graphene-20.04/2256/testReport/LibOS.shim.test.ltp/test_ltp/test_direct___test_ltp_waitpid04_/ https://localhost:8080/job/graphene-20.04/2251/testReport/LibOS.shim.test.ltp/test_ltp/test_direct___test_ltp_kill09_/

> What's the issue here? Why would writing anything to stderr be considered an error? Debug logging is often done this way. @boryspoplawski in my past experience you would want...

@dimakuv the change is not helping, pytorch still fails with the same memory fault error at the same T115. I have pinged you the machine details and the workspace details...

Dmitrii, these machines were enabled recently in the CI and we see the issues only on them. On all other 5.12, 5.13 configurations we don't see any issues with this...

Let us know if you need access to the machine for a quick check. We can walk through the issue and the workspace.

We can run this test with the commit and one before that to confirm, if this is indeed the commit causing the issue.

I was trying to setup a new machine with 5.11 upstream kernel and Ubuntu 20.04 and I faced this same issue even there, was able to resolve with ```mount -o...

Dmitrii, we had agreed that the 2419 issue could be related to the stress-ng version, wasn't asked to test the chmod test. For latest version of stress-ng we need to...

Jenkins, test this please

Jenkins, retest Jenkins-SGX-18.04-apps please (Michal also had a job failure on this machine, as per him the machine is broken with SGX.)