[Bug 98289] [BDW] kms_flip / vblank-vs-suspend-interruptible is failing

[bugzilla-daemon at freedesktop.org]

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

--- Comment #10 from Tomeu Vizoso <tomeu at tomeuvizoso.net> ---
(In reply to Carlos Santa from comment #6)
>
> (kms_flip:1128) CRITICAL: Failed assertion: es->current_seq - es->last_seq
> <= 150
> (kms_flip:1128) CRITICAL: Last errno: 4, Interrupted system call
> (kms_flip:1128) CRITICAL: unexpected vblank seq 2022, should be < 164
> ****  END  ****
> Subtest vblank-vs-suspend-interruptible: FAIL (44.647s)

Can you try running this?

sudo sh -c "echo `date '+%s' -d '+ 60 seconds'` >
/sys/class/rtc/rtc0/wakealarm"

And immediately after, check any of:

* You get several "hpet1: lost 7161 rtc interrupts" messages in the kernel log

* top shows that one core is busy dealing with interrupts ("hi" field)

* perf top shows that rtc_cmos_read takes about 70% of the total CPU time,
followed by hpet_rtc_interrupt.

This is what I'm seeing in one of the machines I have here and would be useful
to know if it's the same you are observing.

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