Bug 100114 - [BDW][BAT] kms_pipe_crc_basic/suspend-read-crc-pipe-c fails on CI due to e1000e driver failing to suspend
Summary: [BDW][BAT] kms_pipe_crc_basic/suspend-read-crc-pipe-c fails on CI due to e100...
Status: CLOSED DUPLICATE of bug 99847
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-08 12:46 UTC by Jani Saarinen
Modified: 2017-07-24 22:39 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Jani Saarinen 2017-03-08 12:46:06 UTC 
On CI BDW-5557u tests fails. 
https://intel-gfx-ci.01.org/CI/CI_DRM_2233/fi-bdw-5557u/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html

Documenting for CI.
Comment 1 Jani Saarinen 2017-03-08 14:05:46 UTC 
rtcwake: write error
(kms_pipe_crc_basic:8912) igt-aux-CRITICAL: Test assertion failure function suspend_via_rtcwake, file igt_aux.c:705:
(kms_pipe_crc_basic:8912) igt-aux-CRITICAL: Failed assertion: system(cmd) == 0
(kms_pipe_crc_basic:8912) igt-aux-CRITICAL: This failure means that something is wrong with the rtcwake tool or how your distro is set up. This is not a i915.ko or i-g-t bug.
Subtest suspend-read-crc-pipe-C failed.
Comment 2 Chris Wilson 2017-03-08 14:12:08 UTC 
Look in the dmesg for the actual error.
Comment 3 Jani Saarinen 2017-03-08 14:54:32 UTC 
Dmesg:
https://intel-gfx-ci.01.org/CI/CI_DRM_2233/fi-bdw-5557u/dmesg-during.log

Error:
[  405.412246] pci_pm_suspend(): e1000e_pm_suspend+0x0/0x50 [e1000e] returns -2
[  405.412250] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2
[  405.412255] PM: Device 0000:00:19.0 failed to suspend async: error -2
Comment 4 Jani Saarinen 2017-03-08 15:21:38 UTC 
I guess dup of 99847
Comment 5 Jani Saarinen 2017-03-08 15:22:06 UTC 

*** This bug has been marked as a duplicate of bug 99847 ***

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.