Bug 88080 - [IVB]igt/kms_pipe_crc_basic/hang-read-crc-pipe-B timeout
Summary: [IVB]igt/kms_pipe_crc_basic/hang-read-crc-pipe-B timeout
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-06 02:15 UTC by lu hua
Modified: 2016-10-07 08:52 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description lu hua 2015-01-06 02:15:52 UTC
==System Environment==
--------------------------
Regression: not sure

Non-working platforms: IVB

==kernel==
--------------------------
drm-intel-nightly/07d0c831d9207c937595f081c8fddbddbf53756f
commit 07d0c831d9207c937595f081c8fddbddbf53756f
Author: Jani Nikula <jani.nikula@intel.com>
Date:   Tue Dec 30 15:02:01 2014 +0200

    drm-intel-nightly: 2014y-12m-30d-13h-01m-34s UTC integration manifest

==Bug detailed description==
-----------------------------
Run automation, it's timeout, but I am unable to reproduce it if run binary.bug 83519 track BSW. file this bug to track IVB.
igt/kms_pipe_crc_basic/hang-read-crc-pipe-C is timeout too. 

output:
IGT-Version: 1.9-gcb512b6 (x86_64) (Linux: 3.19.0-rc2_drm-intel-nightly_07d0c8_20150105_debug+ x86_64)
hang-read-crc-pipe-B: Testing connector VGA-1 using pipe B
Subtest hang-read-crc-pipe-B: TIMEOUT (11.322s)

==Reproduce steps==
---------------------------- 
1. run full igt.
Comment 1 Thomas Wood 2015-04-22 10:14:22 UTC
The timeout behaviour of the tests has been changed in commit cff102e (lib: use test failure status for igt_set_timeout). Please re-test with this commit.
Comment 2 ye.tian 2015-04-23 03:41:56 UTC
Tested it on the latest nightly kernel(b9fe35) and latest igt (e1ce5eac3), I manually run this case,it can be successful,Run automation, it was blocked by bug 90123.

output:
---------------------
[root@x-ivb9 tests]# time ./kms_pipe_crc_basic
IGT-Version: 1.10-ge1ce5ea (x86_64) (Linux: 4.0.0_drm-intel-nightly_b9fe35_20150421+ x86_64)
Subtest bad-pipe: SUCCESS (0.000s)
Subtest bad-source: SUCCESS (0.000s)
Subtest bad-nb-words-1: SUCCESS (0.000s)
Subtest bad-nb-words-3: SUCCESS (0.000s)
read-crc-pipe-A: Testing connector VGA-1 using pipe A
Subtest read-crc-pipe-A: SUCCESS (0.349s)
read-crc-pipe-A-frame-sequence: Testing connector VGA-1 using pipe A
Subtest read-crc-pipe-A-frame-sequence: SUCCESS (0.345s)
rtcwake: wakeup from "mem" using /dev/rtc0 at Thu Apr 23 03:25:59 2015
suspend-read-crc-pipe-A: Testing connector VGA-1 using pipe A
Subtest suspend-read-crc-pipe-A: SUCCESS (1.834s)
hang-read-crc-pipe-A: Testing connector VGA-1 using pipe A
Subtest hang-read-crc-pipe-A: SUCCESS (6.366s)
read-crc-pipe-B: Testing connector VGA-1 using pipe B
Subtest read-crc-pipe-B: SUCCESS (0.346s)
read-crc-pipe-B-frame-sequence: Testing connector VGA-1 using pipe B
Subtest read-crc-pipe-B-frame-sequence: SUCCESS (0.346s)
rtcwake: wakeup from "mem" using /dev/rtc0 at Thu Apr 23 03:26:25 2015
suspend-read-crc-pipe-B: Testing connector VGA-1 using pipe B
Subtest suspend-read-crc-pipe-B: SUCCESS (1.832s)
hang-read-crc-pipe-B: Testing connector VGA-1 using pipe B
Subtest hang-read-crc-pipe-B: SUCCESS (6.472s)
read-crc-pipe-C: Testing connector VGA-1 using pipe C
Subtest read-crc-pipe-C: SUCCESS (0.346s)
read-crc-pipe-C-frame-sequence: Testing connector VGA-1 using pipe C
Subtest read-crc-pipe-C-frame-sequence: SUCCESS (0.346s)
rtcwake: wakeup from "mem" using /dev/rtc0 at Thu Apr 23 03:27:05 2015
suspend-read-crc-pipe-C: Testing connector VGA-1 using pipe C
Subtest suspend-read-crc-pipe-C: SUCCESS (1.843s)
hang-read-crc-pipe-C: Testing connector VGA-1 using pipe C
Subtest hang-read-crc-pipe-C: SUCCESS (6.469s)

real    1m46.315s
user    0m0.050s
sys     0m0.734s
Comment 3 Yi Sun 2015-05-18 01:50:07 UTC
bug 90123 has been fixed, and issue during manual running is also gone.
So close this bug.
Comment 4 Jari Tahvanainen 2016-10-07 08:52:22 UTC
Closing verified+fixed.


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.