Announcement

Collapse
No announcement yet.

sound show no operations reported in timeout period

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

  • sound show no operations reported in timeout period

    burn-in test v5.3_1036
    network =>pass
    sound =>pass

    burn-in test v6.0_1001
    network =>waiting for packet
    (cyde:1328 , error:2 , operation:10,628 million)

    sound=>no operations reported in timeout period
    (cyde:654 , error:1 , operation:1104 million)

    can you tell me the difference of v5.3 and v6.0 in network and sound,thank you very much.

  • #2
    The main differences are:
    - Sound: the test file names no longer require a full path, making BurnInTest more portable on USB drive installations. There were no changes to the core of the sound test (loopback and playback).
    - There were no changes to the core of the network test.

    I would first suspect that the error relates to an increased load on the system from other tests run at the same time.

    Can you send me a trace 2 level activity log, *.trace, (see Preferences->Logging) showing the test run and the errors. Our email is:
    help [at] passmark [dot] com

    Does the Sound test have this problem when only running the sound test?
    Does the Network test have this problem when only running the Network test?

    Regards,
    Ian

    Comment


    • #3
      VISTA 32 bit + BurnInTest v6.0 32bit =>fail

      the same NB:

      VISTA 64 bit + BurnInTest v6.0 64bit =>pass

      VISTA 32 bit + BurnInTest v6.0 32bit =>fail
      network =>timeout waiting for packet
      sound=>no operations reported in timeout period

      ******************
      DETAILED EVENT LOG
      ******************
      LOG NOTE: 2009-03-05 13:48:47, Status, Main Tests started
      LOG NOTE: 2009-03-05 13:48:48, CPU, 3DNow! SSE4.2 SSE4a test(s) selected, but CPU feature not detected
      LOG NOTE: 2009-03-05 13:48:48, 3D Graphics, 3D test starting: Duty cycle = 50. Test on primary monitor (0). (x,y) = (0,600). WxH = 300x200.
      WARNING : 2009-03-05 14:12:47, Sound, No operations reported in timeout period
      LOG NOTE: 2009-03-05 14:41:24, Network 1, User set Network timeout exceeded.
      SERIOUS : 2009-03-05 14:41:28, Network, Timeout waiting for packet
      LOG NOTE: 2009-03-05 14:45:12, Status, Test run stopped

      # PassMark Software
      # BurnInTest v6.0
      # Error Classifications
      #_________________________________________________ _________
      #
      # Configuring Error Classifications
      #
      # Each of the standard errors detected by BurnInTest can configured
      # to include a customer specific string and error classification.
      # The file BITErrorClassification.txt (this file that stored in the
      # software directory) contains the error text and classification used
      # by BurnInTest.
      #
      # The file is formatted as a Comma Separated File with four fields:
      #
      # 1. Error number ?this must not be changed by the customer;
      # 2. Error description text ?this may be changed. This must be a
      # sting enclosed by quotes;
      # 3. Error classification ?this may be changed. This must be one
      # of the following text values (not in quotes):
      # CRITICAL, SERIOUS, WARNING, or INFORMATION
      #
      # A number of errors may be configured to be ignored (not reported
      # as errors), as they may be considered elow the radar? These are
      # configured by setting the Error classification to NONE. These are:
      # ?138,"Warning: Could not lock parallel port",WARNING,PP
      # ?146,"Frame could not be displayed and was skipped",INFORMATION,
      # ?160,"Butterfly seeking test not supported for this disk",INFORMATION,
      # ?182,"Video Playback is dropping samples",WARNING,
      # Other errors may not be configured to be ignored in this way.
      # 4. Customer comment ?this is optional and may be changed ?it is
      # ignored by BurnInTest.
      #
      #
      # Notes:
      # (i) BurnInTest must be restarted after making changes to this file.
      # (ii) You need to run BurnInTest with sufficient privileges to save
      # this file in the BurnInTest directory.
      # (iii) A comment is indicated by a "#" at the start of the line.
      # (iv) This file may be deleted on uninstalling BurnInTest or installing
      # a new version of BurnInTest. It is recommended that you keep a
      # separate copy of this file.
      #_________________________________________________ _________
      #
      # PassMark BurnInTest,,,
      # Error message text and classification,,,
      #
      0,"No errors",NONE,
      1,"Incorrect mathematical addition",SERIOUS,
      2,"Incorrect mathematical subtraction",SERIOUS,
      3,"Incorrect mathematical division",SERIOUS,
      4,"Incorrect mathematical multiply",SERIOUS,
      5,"Incorrect MMX addition",SERIOUS,
      6,"Incorrect MMX subtraction",SERIOUS,
      7,"Incorrect MMX multiplication",SERIOUS,
      8,"Failed Windows call - Line Drawing",SERIOUS,
      9,"Failed Windows call - Bitmaps",SERIOUS,
      10,"Failed Windows call - Shapes",SERIOUS,
      11,"No free memory for buffer",INFORMATION,Disk tests
      12,"Not enough free disk space",INFORMATION,
      13,"Test file could not be created. Check access privileges.",INFORMATION,
      14,"Error while writing to the disk",SERIOUS,
      15,"Test file could not be re-opened",WARNING,
      16,"Error while reading from the disk",SERIOUS,
      17,"Data Verify failure",SERIOUS,
      18,"CD Media is not ready to be played",INFORMATION,OLD
      19,"Could not find CD in Drive",INFORMATION,OLD
      20,"",NONE,Floppy disk OLD
      21,"Error initializing DirectX",WARNING,3D
      22,"Unknown DirectX error",SERIOUS,
      23,"Warning: Switching to reference rasteriser",WARNING,
      24,"Error loading DirectX .dll",INFORMATION,
      25,"Error creating DirectX textures",WARNING,
      26,"Error initializing DirectX device",WARNING,
      27,"Could not find the default printer",WARNING,Printer
      28,"Could not open the default printer",SERIOUS,
      29,"Could not send page to printer",SERIOUS,
      30,"Error verifying data in RAM",SERIOUS,
      31,"Error connecting to network",WARNING,Network
      32,"Could not create a network socket",SERIOUS,
      33,"Could not set socket timeouts",SERIOUS,
      34,"Could not resolve host name, check settings",SERIOUS,
      35,"Could not allocate memory for packets",SERIOUS,
      36,"Timeout sending packet",SERIOUS,
      37,"Timeout waiting for packet",SERIOUS,
      38,"Error sending packet",SERIOUS,
      39,"Error receiving packet",SERIOUS,
      40,"Got someone else's packet",WARNING,
      41,"Bad packet. Length incorrect",SERIOUS,
      42,"Could not set CD Time format",WARNING,Additional CD ROM Errors
      43,"Could not get number of audio tracks",WARNING,
      44,"Could not play the audio track",WARNING,
      45,"CD-ROM failed to return status information",SERIOUS,
      46,"Can not detect audio information on CD",WARNING,
      47,"No audio media in CD-ROM",WARNING,
      48,"No permission to open RAW network socket",WARNING,More Network
      49,"Networking functions aren't available (ws2_32.dll)",WARNING,
      50,"COM port is already in use by another program",SERIOUS,Serial port
      51,"The requested COM port could not be found",SERIOUS,
      52,"Error while opening COM port",SERIOUS,
      53,"Error getting current COM port configuration",SERIOUS,
      54,"Error while setting new COM port configuration",SERIOUS,
      55,"Corruption. Data received didn't match data sent",CRITICAL,
      56,"Error while setting current COM port timeouts",SERIOUS,
      57,"Error while sending data to the COM port",CRITICAL,
      58,"Error while receiving from the COM port. Check plug is connected.",CRITICAL,
      59,"",NONE,Spare
      60,"Error loading Parallel port device driver. Check administrator privileges.",WARNING,Parallel port
      61,"Corruption. Data received didn't match data sent. Check plug is connected.",SERIOUS,
      62,"Error while sending data to the parallel port",SERIOUS,
      63,"Error while receiving data from the parallel port",SERIOUS,
      64,"Could not detect the parallel port selected",WARNING,
      65,"Could not access the tape drive selected",SERIOUS,Tape drive
      66,"Error while formatting tape partition",SERIOUS,
      67,"Error while loading (rewinding) tape",SERIOUS,
      68,"Error while locking tape in drive",SERIOUS,
      69,"Tape device is not ready to start test",SERIOUS,
      70,"No media in tape drive",INFORMATION,
      71,"No free memory for write buffer",WARNING,
      72,"Error while seeking to new position on tape",SERIOUS,
      73,"Future expansion",NONE,
      74,"Error while writing to tape",SERIOUS,
      .........

      Comment


      • #4
        VISTA 32 bit + BurnInTest v5.3 32bit =>pass

        the same sample:

        VISTA 64 bit + BurnInTest v5.3 64bit =>pass

        VISTA 32 bit + BurnInTest v5.3 32bit =>pass

        Comment


        • #5
          Thanks, but if you have not already, could you please send me a trace 2 level activity log with periodic logging set to 1 minute, *.trace, (see Preferences->Logging), showing the test run and the errors (only for the error case). Our email is:
          help [at] passmark [dot] com

          Does the Sound test have this problem when only running the sound test?
          Does the Network test have this problem when only running the Network test?

          Thanks.
          Ian

          Comment


          • #6
            only running the sound test?=>pass

            Does the Sound test have this problem when only running the sound test?
            =>pass
            Does the Network test have this problem when only running the Network test?
            =>pass

            Comment


            • #7
              Log and trace was mailed already to your mail

              Log and trace was mailed already to your mail : help@passmark.com

              Remark:The burn-in test AP will lag(standstill) about 5~10 second
              ,before error message appear

              Comment


              • #8
                As the errors do not seem to occur when running the individual tests then it is most likely a load or test interaction issue. If BurnInTest is not responding for a few seconds before the error occurs, then this could be caused by a system resource allocation issue, and could cause the Network problem. I would check you don't have any major applications running in the background (like anti-virus, or malicious apps). If you are running the tests at more than the default 50%, then I would also try reducing the duty cycle levels (load levels).

                The .trace file you sent only shows the Network error. A small number of these errors can occur if there is response is not received in a timeout period, this can be impacted by load. As you only get 1 timeout error, I would try a longer timeout duration in Preferences->Network.


                Can you email a log showing both errors?

                Thanks.
                Ian

                Comment


                • #9
                  below method can avoid :network and sound error message

                  below method can avoid :network and sound error message

                  1. uninstall vista hotfix:Windows6.0-KB946723-v2-x86.msu
                  Windows6.0-KB946988-x86.msu
                  Windows6.0-KB948643-x86.msu
                  Windows6.0-KB949201-v2-x86.msu
                  Windows6.0-KB950570-x86.msu
                  Windows6.0-KB951126-v3-x86.msu
                  Windows6.0-KB951880-v3-x86.msu
                  Windows6.0-KB953026-x86.msu
                  Windows6.0-KB954589-v2-x86.msu
                  Windows6.0-KB956388-x86.msu
                  Windows6.0-KB958092-x86.msu
                  Windows6.0-KB958865-x86.msu
                  Windows6.0-KB959520-x86.msu
                  Windows6.0-KB961317-x86.msu

                  2. don't install 3D MARK 2006 at the same NB
                  (include:OpenAL sound library, Directx 9.0c , visual C++ 2005 redist)

                  3. run as Administrator(click right key of mouse at burn-in icon )

                  Will above-mentioned hotfix and AP, to execute method conflict with burnIn test 6.0?

                  Comment


                  • #10
                    sound Log and trace was mailed already to your mail

                    sound Log and trace was mailed already to your mail : help@passmark.com

                    Comment


                    • #11
                      We are not aware of any incompatibilities with any of the items you noted.

                      Your logs show that the system is running out of memory resources. It is not clear why this is happening. I would first suspect that this is a memory leak in a Windows component (maybe a component in one of the
                      Hotfixes you noted), that when exercised over time, eventually means the system runs out of available memory.

                      When you get this problem, can you look in Task manager, select the Processes tab, select View->Select Columns and check "Commit Size", then sort on Memory Commit size. Can you send me a screen shot showing say the 10 top processes memory usage.

                      If you remove the RAM test, the problem will probably only occur after a very long time. Please try this as wwll.

                      We will do more testing on our side.

                      Thanks.
                      Ian

                      Comment


                      • #12
                        As the errors do not seem to occur when running the individual tests then it is most likely a load or test interaction issue.
                        If BurnInTest is not responding for a few seconds before the error occurs, then this could be caused by a system resource allocation issue,
                        and could cause the Network problem. I would check you don't have any major applications running in the background (like anti-virus, or malicious apps).
                        If you are running the tests at more than the default 50%, then I would also try reducing the duty cycle levels (load levels).

                        why burnIn test v5.3 or vista 64 bit without the issue at the same sample.

                        1. running the tests at the default 50%
                        2. don't have any major applications running in the background
                        3. network a longer timeout duration =>buyer can't accept.
                        (because burnIn test v5.3 or vista 64 bit without the issue)

                        can you provide other solution?thanks

                        Comment


                        • #13
                          Your logs show that the system is running out of memory resources. It is not clear why this is happening. I would first suspect that this is a memory leak in a Windows component (maybe a component in one of the
                          Hotfixes you noted), that when exercised over time, eventually means the system runs out of available memory.

                          So, the job is to identify which component is not fully releasing memory, such that the system eventually runs out of memory, and the test fails.

                          If the problem is a Windows component (e.g. .dll, .sys), and you say the problem does not occur after you remove a set of Hotfixes (and a 3rd party application), then I would conclude (for now) that one of the Windows components in the 32-bit Hotfix's you removed has a resource leak (uses memory and does not give it all back when it is finished with it).


                          As BurnInTest V6.0 does not show the problem on 64-bit Vista, then I would first suspect that the problem is in a 32-bit system component, but not the 64-bit build of that component. Also, for now I think the problem is not in BurnInTest 6.0, but rather, that a change from BurnInTest v5.3 to v6.0 has led to the problem being provoked only in v6.0 due to a change in the test mechanism.


                          To resolve the problem, you should run tests that try to narrow down where the problem is. I would start by confirming that the problem does not exist on a 32-bit Vista system that does not have the Hotfix's. If this is the case, I would then put the Hotfix's back on one at a time and re-test for each one to identify which one causes the problem. If this does not work then you could try to remove BurnInTest tests until you get the smallest test set you can that provokes this problem (e.g. remove the disk test and run the test, remove the 2D test etc.), as this should help narrow down the component that is failing.

                          As I mentioned, we will do more testing on our side.


                          Regards,
                          Ian

                          Comment


                          • #14
                            Error message of sound and network arise from memory test

                            Error message of sound and network arise from memory test

                            Because 4 items's memory test of BurnInTest 6.0 use up all RAM

                            Up to now,to Ascertain intel Montevina & AMD PUMA(HP TouchSmart tx2-1000) Platform will have this issue with BurnInTest 6.0
                            ,but Othe Platform without the issue

                            why BurnInTest v5.3 without the issue?
                            Because BurnInTest v5.3 do not run the memory test 4 items.

                            to refer to the picture.
                            http://picasaweb.google.com.tw/jesse...eat=directlink

                            would you tell me why BurnIntest v5.3 without running the 4 items memory test.
                            and the solution of this issue

                            Comment


                            • #15
                              Thanks for the screenshot of task manager. The memory test in V6.0 changed quite significantly from V5 to V6. The BurnInTest standard memory test now uses 4 processes to test RAM, it did not do this in V5. This is by design. What you see for the memory test looks normal.
                              What does not look normal is the committed memory of 1.8GB for bit.exe.

                              It does look like BurnInTest is using something that is not releasing memory and hence the system runs out of memory.

                              It does not look to be related to the memory test (as it does not run in bit.exe). However, running the memory test will probably make the problem occur much more quickly as the system will run out of memory sooner with the memory test.

                              So, I still think it is a system component memory leak being provoked by BurnInTest.

                              Further to the steps I suggested in my last post, you should also try to reduce the BurnInTest tests to see which tests lead to the problem (I would keep the memory test in to make the problem occur more quickly). Please let me know the minimum test set as that will also speed up our testing.

                              Regards,
                              Ian

                              Comment

                              Working...
                              X