[Bug 103520] [IGT] kms_pipe_crc_basic fails due to PM early wake event detected.

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=103520

--- Comment #5 from krisman at collabora.co.uk ---
(In reply to Elizabeth from comment #4)
> (In reply to krisman from comment #3)
> > (In reply to Elizabeth from comment #0)
> > >
> > If I'm not mistaken, that is from USB.  Do you have any gadgets connected to
> > the box?  Try unplugging those prior to running the test.  Looks like you
> > have a misbehaving gadget.
> Sorry for the delay, I tested without anything besides Ethernet cable
> connected to the laptop. I tried with and without external monitor
> connected, and result keeps being the same, once pass, twice fails with PM
> error message each time it fails.
> 
> $ : sudo -E ./kms_pipe_crc_basic --r suspend-read-crc-pipe-A
> IGT-Version: 1.20-g88d6550 (x86_64) (Linux:
> 4.14.0-drm-intel-qa-ww46-commit-1fc4fe8+ x86_64)
> suspend-read-crc-pipe-A: Testing connector LVDS-1 using pipe A
> suspend-read-crc-pipe-A: Testing connector VGA-1 using pipe A
> suspend-read-crc-pipe-A: Testing connector DP-3 using pipe A
> [cmd] rtcwake: assuming RTC uses UTC ...
> rtcwake: wakeup from "mem" using /dev/rtc0 at Thu Nov 16 07:20:01 2017
> (kms_pipe_crc_basic:3923) igt-core-WARNING: [cmd] rtcwake: write error
> (kms_pipe_crc_basic:3923) igt-aux-CRITICAL: Test assertion failure function
> suspend_via_rtcwake, file igt_aux.c:809:
> (kms_pipe_crc_basic:3923) igt-aux-CRITICAL: Failed assertion: ret == 0
> (kms_pipe_crc_basic:3923) igt-aux-CRITICAL: rtcwake failed with 1
> Check dmesg for further details.
> Stack trace:
>   #0 [__igt_fail_assert+0x101]
>   #1 [igt_system_suspend_autoresume+0x5ae]
>   #2 [<unknown>+0x5ae]
>   #3 [<unknown>+0x5ae]
> Subtest suspend-read-crc-pipe-A failed.
> 
> $ : sudo -E ./kms_pipe_crc_basic --r suspend-read-crc-pipe-A
> IGT-Version: 1.20-g88d6550 (x86_64) (Linux:
> 4.14.0-drm-intel-qa-ww46-commit-1fc4fe8+ x86_64)
> suspend-read-crc-pipe-A: Testing connector LVDS-1 using pipe A
> suspend-read-crc-pipe-A: Testing connector VGA-1 using pipe A
> suspend-read-crc-pipe-A: Testing connector DP-3 using pipe A
> [cmd] rtcwake: assuming RTC uses UTC ...
> rtcwake: wakeup from "mem" using /dev/rtc0 at Thu Nov 16 07:20:08 2017
> suspend-read-crc-pipe-A: Testing connector LVDS-1 using pipe A
> suspend-read-crc-pipe-A: Testing connector VGA-1 using pipe A
> suspend-read-crc-pipe-A: Testing connector DP-3 using pipe A
> Subtest suspend-read-crc-pipe-A: SUCCESS (4.138s)
> 
> $ : dmesg | grep PM:
> [   42.019984] PM: suspend entry (deep)
> [   42.019986] PM: Syncing filesystems ... done.
> [   42.120102] PM: Device 0000:00:1d.0 failed to suspend async: error -16
> [   42.570211] PM: Some devices failed to suspend, or early wake event
> detected
> [   43.011696] PM: suspend exit
> [   48.781766] PM: suspend entry (deep)
> [   48.781769] PM: Syncing filesystems ... done.
> [   49.416702] PM: Saving platform NVS memory
> [   49.484019] PM: Restoring platform NVS memory
> [   50.880846] PM: suspend exit

I would suggest enabling dyn_dbg for xhci and trying again.  Since this is not
graphics related, what is the procedure?  should we create a bug in kernel.org?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20171127/08da4f0b/attachment-0001.html>