Attachment 133156 Details for Bug 101990 – Tests Log (BSW)

Tests Log (BSW)

BSW-1Pm03.log (text/plain), 3.48 KB, created by Hector Velazquez on 2017-07-31 17:56:48 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Hector Velazquez

Created: 2017-07-31 17:56:48 UTC

Size: 3.48 KB

patch

obsolete

>IGT-Version: 1.19-gf145475 (x86_64) (Linux: 4.13.0-rc2-drm-tip-ww30-commit-1eb8669+ x86_64)
>(pm_rps:1364) igt-core-DEBUG: Test requirement passed: !igt_run_in_simulation()
>(pm_rps:1364) drmtest-DEBUG: Test requirement passed: !(fd<0)
>(pm_rps:1364) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
>(pm_rps:1364) drmtest-DEBUG: Test requirement passed: is_i915_device(fd) && has_known_intel_chipset(fd)
>(pm_rps:1364) ioctl-wrappers-DEBUG: Test requirement passed: err == 0
>(pm_rps:1364) DEBUG: Test requirement passed: gem_can_store_dword(drm_fd, 0)
>(pm_rps:1364) DEBUG: Test requirement passed: junk->filp
>(pm_rps:1364) DEBUG: Test requirement passed: junk->filp
>(pm_rps:1364) DEBUG: Test requirement passed: junk->filp
>(pm_rps:1364) DEBUG: Test requirement passed: junk->filp
>(pm_rps:1364) DEBUG: Test requirement passed: junk->filp
>(pm_rps:1364) DEBUG: Test requirement passed: junk->filp
>(pm_rps:1364) igt-core-DEBUG: Starting subtest: reset
>(pm_rps:1364) drmtest-DEBUG: Test requirement passed: !(fd<0)
>(pm_rps:1365) DEBUG: load helper sent 18731 dword writes
>(pm_rps:1364) DEBUG: Apply low load...
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=200  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=200  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: Waited 0 msec to stabilize cur
>(pm_rps:1364) DEBUG: Reset gpu...
>(pm_rps:1364) drmtest-DEBUG: Test requirement passed: !(fd<0)
>(pm_rps:1364) ioctl-wrappers-DEBUG: Test requirement passed: gem_has_ring(fd, ring)
>(pm_rps:1364) ioctl-wrappers-DEBUG: Test requirement passed: has_ban_period || has_bannable
>(pm_rps:1364) igt-gt-DEBUG: Test requirement passed: has_gpu_reset(fd)
>(pm_rps:1364) igt-gt-DEBUG: Test requirement passed: ctx == 0 || ring == I915_EXEC_RENDER
>(pm_rps:1364) drmtest-DEBUG: Test requirement passed: is_i915_device(fd) && has_known_intel_chipset(fd)
>(pm_rps:1364) ioctl-wrappers-DEBUG: Test requirement passed: err == 0
>(pm_rps:1364) igt-dummyload-DEBUG: Test requirement passed: nengine
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=700  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: Apply low load again...
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=700  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=700  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: Waited 0 msec to stabilize cur
>(pm_rps:1364) DEBUG: Removing load...
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=700  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=700  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=700  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=700  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=700  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=700  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=700  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=700  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: gt freq (MHz):  cur=200  min=200  max=700  RP0=700  RP1=400  RPn=200
>(pm_rps:1364) DEBUG: Required 2000 msec to reach cur=idle
>Stack trace:
>  #0 [__igt_fail_assert+0x101]
>  #1 [waitboost+0x196]
>  #2 [<unknown>+0x196]
>Subtest reset: FAIL (22.005s)
>(pm_rps:1364) igt-core-DEBUG: Exiting with status code 99
>(pm_rps:1364) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'

Actions: View

Attachments on bug 101990: 133156 | 133248

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.