Announcement

Collapse
No announcement yet.

USB3Test log show “Diagnostics – read failed/Timeout reading”, but No Error count.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • USB3Test log show “Diagnostics – read failed/Timeout reading”, but No Error count.

    USB3Test log file show “Diagnostics – Benchmark Read Failed” and “Diagnostics –Timeout reading benchmark data”, but No Error count.

    Hi,

    I plugin two USB3 loopback into my new MB and run the USB3 test benchmark test.

    After 60 minutes test complete, the USB3 test summary show 0 Error count.
    Click image for larger version  Name:	01 Test Complete.png Views:	0 Size:	125.5 KB ID:	46523

    But I check the log file (USB3_benchmark_1_1211a.zip), there is one set “Diagnostics – Benchmark Read Failed” / “Diagnostics –Timeout reading benchmark data” message in log file.
    Click image for larger version  Name:	02 Test Log.png Views:	0 Size:	286.9 KB ID:	46524

    Above message only happen 1 or 2 times in hour running.
    But the message not count in test program error counter, it still show “0” after test complete.
    So above test log show diagnostics message, is that a real error or just a notification for USB3 Test program?

    Test Configuration
    CPU: Intel i7-8665UE
    OS: WIN10 x64 LTSC (Version 1809/ OS Build: 17763.805)
    RAM: SODIMM DDR4-2400 16GB
    Storage: NVME (M2 2280) 256GB
    USB3 Test program Version: 2.0 ( 1008 )
    USB3 Loopback F/W Version: V2.5
    USB3 Loopback H/W Version: V1.0
    USB3 loopback Driver version: 1.2.3.10

    USB3Test configuration setting: I open two USB3 Test program, each test configuration are same.
    (See 03 Test Configuration.png in USB3_benchmark_1_1211a.zip file)


    Regards

    Harry Wang
    Feb/12/2020
    Attached Files

  • #2
    Hi,

    We just released a new version of the USB3Test which increases the error count when a timeout occurs in benchmark mode.
    The message "Benchmark read failed" is not a USB transfer error and will be changed to "Failed to release benchmark buffer" in the next release.

    Comment


    • #3
      Hi, HamidK

      Thanks for update test tool. I understand this message not represent USB transfer error as per your reply.
      I use this new USB3Tester (V2.0.1009) to test my board again.
      But this new version will count this “Timeout reading benchmark data” as error count.
      (Not you mention before "Failed to release benchmark buffer")
      Click image for larger version

Name:	USB3_benchmark read and write 1217 1.png
Views:	139
Size:	53.1 KB
ID:	46566

      Check the log file “USB3_benchmark read and write 1 1217.txt”, this kind of message will record as “ERROR”.
      I think this message will mislead test engineer and judge the test failed.
      Click image for larger version

Name:	USB3_benchmark read and write 1 log 1217.png
Views:	69
Size:	9.0 KB
ID:	46567
      Log file: USB3_benchmark read and write 1 1217.zip

      Can you update this to not count as error?
      And not show fail message in log file.


      Thanks

      Harry Wang
      Feb/17/2020
      Attached Files

      Comment


      • #4
        Hi, HamidK

        May I have any USB3Test parameter change to prevent this "Failed to release benchmark buffer"?


        Thanks

        Harry Wang
        Mar/16/2020

        Comment


        • #5
          Normally these errors are due to hardware faults. Can you post a screen shot.

          Comment


          • #6
            Hi, David

            Here is photo summary:

            In my first post message (Feb/12/2020), I test USB3 Test program Version: 2.0 (100
            1st photo is test complete screen, Error Count is Zero.
            However, in test log file (2nd photo). (And Log file: USB3_benchmark_1_1211a.zip)
            It show read failed and Timeout reading bechmark data.

            Feb/14, HamidK reply above issue is not USB transfer error
            And there is a test program version update (V2.0.1009) to fix this issue.

            I test this new version (V2.0.1009) but found this program count above log as Error.
            (In my Feb/17 post message first photo)
            I think this Error count will mislead tester to judge board USB error.
            Maybe test program can increase the timeout setting to prevent this message?

            Thanks.

            Harry Wang
            03/23/2020

            Comment


            • #7
              Hi,

              Can you try reducing the transfer size or queue size to see it has any effect?

              Comment


              • #8
                Hi, HamidK

                I try to modify the Transfer and Queue size.
                I test below setting
                1. Transfer size from 2MB to 64KB; Queue size from 64 to 1 -> Generate more error message. (Same timeout error)
                2. Transfer size from 2MB to 64KB; Queue size keep 64 -> Generate more error message. (Same timeout error)
                3. Transfer size from Keep 2MB ; Queue size from 64 to 1-> Generate more error message. (Same timeout error)

                I notice above setting change will increase test frequency. Test programmer test more time than default setting.

                So I try to modify Endpoint Options – Burst Length. Maximal value is 12 (default) and minimal is 1.
                When I reduce this burst length to 5 or below. No Error found.
                And I found the transfer rate is lower at low burst length setting

                Burst length =1, Max Read 2385Mbps, Max Write only 1123Mbps
                Burst length = 5, Max Read 2070Mbps, Max Write speed up to 206xMbps
                Burst length = 12 (default), Max Read 2070Mbps, Max Write speed up to 325xMbps

                Regards,

                Harry Wang
                Mar/30/2020

                Comment


                • #9
                  Hi, HamidK

                  I already test above setting.
                  Can I reduce this burst length to 5 or below to fix this issue?

                  Thanks

                  Harry Wang
                  04/16/2020

                  Comment


                  • #10
                    It should work with the default burst length (12) unless there is a hardware fault. So, we don't recommend reducing the burst length just to get rid of the error.
                    Can you please run loopback test with "check bus error" option enabled to see if there are any low level errors happening in the background?
                    Also please make sure the BIOS and host controller drivers are up-to-date.

                    Comment


                    • #11
                      Dear HamidK

                      I test this USB3Test in loopback mode, Turn on the “Check bus errors”.
                      Test two USB3test simultaneous, test period 1 hr. No error recorder.
                      Click image for larger version

Name:	Loopback 0420.png
Views:	27
Size:	598.0 KB
ID:	47368

                      Regards,

                      Harry Wang
                      04/20/2020

                      Comment


                      • #12
                        Dear HamidK

                        I extend the loopback test period to 12 hrs.
                        Still No error found
                        Click image for larger version

Name:	Loopback 0421.png
Views:	24
Size:	587.6 KB
ID:	47384

                        Regards

                        Harry Wang
                        04/21/2020

                        Comment


                        • #13
                          Your testing shows that there are no low level errors in the background.
                          Our speculation is that the host controller has throughput issues when burst length is 5 or more.

                          Comment

                          Working...
                          X