From: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
To: "Deak, Imre" <imre.deak@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Sarvela, Tomi P" <tomi.p.sarvela@intel.com>,
"Latvala, Petri" <petri.latvala@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/icl+: Fix hotplug interrupt disabling after storm detection
Date: Fri, 12 Jun 2020 20:13:44 +0000 [thread overview]
Message-ID: <b2d4a626e2f046b8863277a29655e08f@intel.com> (raw)
In-Reply-To: <20200612132020.GC15242@ideak-desk.fi.intel.com>
Filed https://gitlab.freedesktop.org/drm/intel/-/issues/2029 and re-reported.
-----Original Message-----
From: Imre Deak <imre.deak@intel.com>
Sent: Friday, June 12, 2020 4:20 PM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana <lakshminarayana.vudum@intel.com>; Sarvela, Tomi P <tomi.p.sarvela@intel.com>; Latvala, Petri <petri.latvala@intel.com>
Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915/icl+: Fix hotplug interrupt disabling after storm detection
On Fri, Jun 12, 2020 at 01:04:19PM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/icl+: Fix hotplug interrupt disabling after storm detection
> URL : https://patchwork.freedesktop.org/series/78258/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_8621 -> Patchwork_17937
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_17937 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_17937, please notify your bug team to allow them
> to document this new failure mode, which will reduce false positives in CI.
>
> External URL:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17937/index.html
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_17937:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@runner@aborted:
> - fi-bdw-5557u: NOTRUN -> [FAIL][1]
> [1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17937/fi-bdw-5557u/
> igt@runner@aborted.html
This is on an unrelated platform. It looks like a network problem after
resuming:
[149.557805] [117/171] (880s left) kms_pipe_crc_basic (suspend-read-crc-pipe-a) Starting subtest: suspend-read-crc-pipe-A Subtest suspend-read-crc-pipe-A: SUCCESS (2.860s) [191.138997] Aborting: Ping host did not respond to ping, network down [191.140340] Closing watchdogs
So jenkins timing out after 50 seconds, even though the machine is still up for 5 minutes after suspend-read-crc-pipe-A completes. The network connection seems to be up as well:
<7>[ 134.716964] [IGT] kms_pipe_crc_basic: starting subtest suspend-read-crc-pipe-A ...
<7>[ 137.578228] [IGT] kms_pipe_crc_basic: exiting, ret=0 <6>[ 137.588883] Console: switching to colour frame buffer device 240x67 <6>[ 142.597964] e1000e 0000:00:19.0 enp0s25: NIC Link is Up 10 Mbps Full Duplex, Flow Control: None <6>[ 439.818733] kworker/dying (178) used greatest stack depth: 11424 bytes left
> Known issues
> ------------
>
> Here are the changes found in Patchwork_17937 that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@kms_cursor_legacy@basic-flip-after-cursor-legacy:
> - fi-icl-u2: [PASS][2] -> [DMESG-WARN][3] ([i915#1982])
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8621/fi-icl-u2/igt@kms_cursor_legacy@basic-flip-after-cursor-legacy.html
> [3]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17937/fi-icl-u2/igt
> @kms_cursor_legacy@basic-flip-after-cursor-legacy.html
>
>
> #### Possible fixes ####
>
> * igt@i915_pm_backlight@basic-brightness:
> - fi-whl-u: [DMESG-WARN][4] ([i915#95]) -> [PASS][5]
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8621/fi-whl-u/igt@i915_pm_backlight@basic-brightness.html
> [5]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17937/fi-whl-u/igt@
> i915_pm_backlight@basic-brightness.html
>
> * igt@i915_pm_rpm@module-reload:
> - fi-glk-dsi: [DMESG-WARN][6] ([i915#1982]) -> [PASS][7]
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8621/fi-glk-dsi/igt@i915_pm_rpm@module-reload.html
> [7]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17937/fi-glk-dsi/ig
> t@i915_pm_rpm@module-reload.html
>
> * igt@i915_selftest@live@execlists:
> - fi-icl-y: [DMESG-FAIL][8] ([i915#1993]) -> [PASS][9]
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8621/fi-icl-y/igt@i915_selftest@live@execlists.html
> [9]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17937/fi-icl-y/igt@
> i915_selftest@live@execlists.html
>
> * igt@kms_busy@basic@flip:
> - fi-kbl-x1275: [DMESG-WARN][10] ([i915#62] / [i915#92] / [i915#95]) -> [PASS][11]
> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8621/fi-kbl-x1275/igt@kms_busy@basic@flip.html
> [11]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17937/fi-kbl-x1275/
> igt@kms_busy@basic@flip.html
>
> * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
> - fi-icl-u2: [DMESG-WARN][12] ([i915#1982]) -> [PASS][13]
> [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8621/fi-icl-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
> [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17937/fi-icl-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
> - fi-bsw-kefka: [DMESG-WARN][14] ([i915#1982]) -> [PASS][15]
> [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8621/fi-bsw-kefka/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
> [15]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17937/fi-bsw-kefka/
> igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
>
> * igt@kms_cursor_legacy@basic-flip-after-cursor-legacy:
> - fi-icl-guc: [DMESG-WARN][16] ([i915#1982]) -> [PASS][17]
> [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8621/fi-icl-guc/igt@kms_cursor_legacy@basic-flip-after-cursor-legacy.html
> [17]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17937/fi-icl-guc/ig
> t@kms_cursor_legacy@basic-flip-after-cursor-legacy.html
>
>
> #### Warnings ####
>
> * igt@kms_cursor_legacy@basic-flip-before-cursor-legacy:
> - fi-kbl-x1275: [DMESG-WARN][18] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][19] ([i915#62] / [i915#92]) +4 similar issues
> [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8621/fi-kbl-x1275/igt@kms_cursor_legacy@basic-flip-before-cursor-legacy.html
> [19]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17937/fi-kbl-x1275/
> igt@kms_cursor_legacy@basic-flip-before-cursor-legacy.html
>
> * igt@kms_flip@basic-flip-vs-wf_vblank@a-dp1:
> - fi-kbl-x1275: [DMESG-WARN][20] ([i915#62] / [i915#92]) -> [DMESG-WARN][21] ([i915#62] / [i915#92] / [i915#95]) +1 similar issue
> [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8621/fi-kbl-x1275/igt@kms_flip@basic-flip-vs-wf_vblank@a-dp1.html
> [21]:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17937/fi-kbl-x1275/
> igt@kms_flip@basic-flip-vs-wf_vblank@a-dp1.html
>
>
> [i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
> [i915#1993]: https://gitlab.freedesktop.org/drm/intel/issues/1993
> [i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
> [i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
> [i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
>
>
> Participating hosts (49 -> 43)
> ------------------------------
>
> Additional (1): fi-tgl-u2
> Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus
>
>
> Build changes
> -------------
>
> * Linux: CI_DRM_8621 -> Patchwork_17937
>
> CI-20190529: 20190529
> CI_DRM_8621: acd803311fbd1e6adc38d10ca382a60c6c190be9 @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_5708: f66c71e29de50bae880bc81ceb0517d4e3e2dfd8 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
> Patchwork_17937: a09f4bc8ddb9cfad0f18bdaccada93f9e98d5c54 @
> git://anongit.freedesktop.org/gfx-ci/linux
>
>
> == Linux commits ==
>
> a09f4bc8ddb9 drm/i915/icl+: Fix hotplug interrupt disabling after
> storm detection
>
> == Logs ==
>
> For more details see:
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17937/index.html
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-06-12 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 12:17 [Intel-gfx] [PATCH] drm/i915/icl+: Fix hotplug interrupt disabling after storm detection Imre Deak
2020-06-12 13:04 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2020-06-12 13:20 ` Imre Deak
2020-06-12 20:13 ` Vudum, Lakshminarayana [this message]
2020-06-12 13:18 ` [Intel-gfx] [PATCH] " Ville Syrjälä
2020-06-15 6:59 ` Imre Deak
2020-06-12 20:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-06-12 22:07 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2d4a626e2f046b8863277a29655e08f@intel.com \
--to=lakshminarayana.vudum@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=petri.latvala@intel.com \
--cc=tomi.p.sarvela@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox