Bug 104550

Summary: [BAT] igt@kms_pipe_crc_basic@suspend-read-crc-pipe-[a|b|c] - rtcwake failed with 1 - pci_pm_suspend(): e1000e_pm_suspend+0x0/0x40 [e1000e] returns -2
Product: DRI Reporter: Marta Löfstedt <marta.lofstedt>
Component: DRM/IntelAssignee: Jani Saarinen <jani.saarinen>
Status: CLOSED WORKSFORME QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: CNL, IVB i915 features: power/suspend-resume

Description Marta Löfstedt 2018-01-09 10:41:35 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3609/fi-ivb-3520m/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3609/fi-ivb-3520m/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3609/fi-ivb-3520m/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html

(kms_pipe_crc_basic:4049) igt-core-WARNING: [cmd] rtcwake: [cmd] write error
(kms_pipe_crc_basic:4049) igt-aux-WARNING: rtcwake failed with 1
Check dmesg for further details.
(kms_pipe_crc_basic:4049) igt-aux-CRITICAL: Test assertion failure function suspend_via_rtcwake, file igt_aux.c:821:
(kms_pipe_crc_basic:4049) igt-aux-CRITICAL: Failed assertion: ret == 0
(kms_pipe_crc_basic:4049) igt-aux-CRITICAL: error: 1 != 0
Subtest suspend-read-crc-pipe-C failed.

From dmesg:
<3>[  395.316767] pci_pm_suspend(): e1000e_pm_suspend+0x0/0x40 [e1000e] returns -2
<3>[  395.316772] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2
<3>[  395.316783] PM: Device 0000:00:19.0 failed to suspend async: error -2
<3>[  395.316884] PM: Some devices failed to suspend, or early wake event detected
Comment 1 Marta Löfstedt 2018-01-19 12:02:50 UTC
created https://bugzilla.kernel.org/show_bug.cgi?id=198519 for this
Comment 2 Marta Löfstedt 2018-02-09 07:22:18 UTC
Last seen  CI_DRM_3609: 2018-01-09 / 219 runs ago
Comment 4 Marta Löfstedt 2018-03-14 06:32:21 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3918/fi-cnl-drrs/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html

<3>[  451.299599] pci_pm_suspend(): e1000e_pm_suspend+0x0/0x40 [e1000e] returns -2
<3>[  451.299606] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2
<3>[  451.299642] PM: Device 0000:00:1f.6 failed to suspend async: error -2
<3>[  451.299714] PM: Some devices failed to suspend, or early wake event detected
Comment 5 Imre Deak 2018-03-19 18:08:50 UTC
One more hint this being an e1000e problem:
[  445.754252] e1000e 0000:00:1f.6 enp0s31f6: Hardware Error
Comment 6 Marta Löfstedt 2018-04-03 12:48:11 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_9/fi-cnl-y3/igt@kms_cursor_crc@cursor-64x64-suspend.html

<3>[  218.537930] pci_pm_suspend(): e1000e_pm_suspend+0x0/0x40 [e1000e] returns -2
<3>[  218.537936] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2
<3>[  218.537951] PM: Device 0000:00:1f.6 failed to suspend async: error -2
<3>[  218.538017] PM: Some devices failed to suspend, or early wake event detected

I will also update the k.org bug
Comment 7 Marta Löfstedt 2018-04-03 12:52:13 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_9/fi-cnl-y3/igt@kms_vblank@pipe-c-ts-continuation-suspend.html

<3>[  109.019792] pci_pm_suspend(): e1000e_pm_suspend+0x0/0x40 [e1000e] returns -2
<3>[  109.019798] dpm_run_callback(): pci_pm_suspend+0x0/0x140 returns -2
<3>[  109.019812] PM: Device 0000:00:1f.6 failed to suspend async: error -2
<3>[  109.019916] PM: Some devices failed to suspend, or early wake event detected
Comment 8 Jani Saarinen 2018-04-18 17:33:01 UTC
pinged again e1000e folks.
Comment 9 Jani Saarinen 2018-05-28 12:39:04 UTC
And pinged again. martin, is this still issue?
Comment 10 Jani Saarinen 2018-05-28 13:36:29 UTC
Not seen on new cibuglog. Maybe not issue anymore?
Comment 11 Jani Saarinen 2018-05-29 06:20:48 UTC
Not seen on new cibuglog, resolving until opened again.
Martin, can you update kernel.org bug?

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.