Tweet
I am having a recurring issue when using the BurnIn test software. I am getting an error in the 2D graphics test that says: “No operations reported in timeout period”. The test indicated It failed, but if I run the test again in the same device it finishes the same test with no errors.
The error seems to happen almost immediately too, as it shows a log entry that says: “2D Graphics, Surface lost: restoring” and it repeats this same log entry several times each second until the end of the test. In three devices that I have found the error, it appeared in the first 0 to 3 cycles of the 2D graphics test.
The logs for one of the devices looked like this:
It then repeated the same log note until the test ended. For some reason, it seems like the software gets stuck in an operation and shows an error because of that.
I am not sure what to take of this error, since it is not reliably showing up even in the same devices that saw the error before. How can I find the root cause of this issue?
The error seems to happen almost immediately too, as it shows a log entry that says: “2D Graphics, Surface lost: restoring” and it repeats this same log entry several times each second until the end of the test. In three devices that I have found the error, it appeared in the first 0 to 3 cycles of the 2D graphics test.
The logs for one of the devices looked like this:
| LOG NOTE: 2016-11-04 11:06:33, Status, Main Tests started |
| LOG NOTE: 2016-11-04 11:06:33, CPU, SSE4a test(s) selected, but CPU feature not detected |
| LOG NOTE: 2016-11-04 11:06:34, Video, Video test starting: Duty cycle = 50. Test on primary monitor (0). (x,y) = (310,400). WxH = 300x200. |
| LOG NOTE: 2016-11-04 11:06:59, 2D Graphics, Surface lost: Restoring. |
| LOG NOTE: 2016-11-04 11:06:59, 2D Graphics, Surface lost: Restoring. |
I am not sure what to take of this error, since it is not reliably showing up even in the same devices that saw the error before. How can I find the root cause of this issue?
Comment