All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yadav, Jyoti R" <jyoti.r.yadav@intel.com>
To: "Saarinen, Jani" <jani.saarinen@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Srivatsa, Anusha" <anusha.srivatsa@intel.com>,
	"Deak, Imre" <imre.deak@intel.com>
Subject: Re: ✗ Fi.CI.BAT: failure for Load DMC v1.07 on Icelake (rev2)
Date: Tue, 28 Aug 2018 12:19:57 +0530	[thread overview]
Message-ID: <fb338be7-7fba-6fdb-6b58-6e825d3c609c@intel.com> (raw)
In-Reply-To: <43D4F724E12AB6478FC1572B3FBE89D0762439A8@IRSMSX106.ger.corp.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 5935 bytes --]

Hi Jani,

I am already debugging this issue. Issue got reproduced when we are 
locally running the icl_dmc_ver1_07.bin on ICL HW.

We could not see this issue with previous FW version icl_dmc_ver1_01.bin 
file.

  Already in discussion with DMC FW folks. There are two FW stepping 
integrated in latest release.

1. Stepping { A, *} - > this stepping is mainly for A stepping ICL HW.

2. Stepping {*, *} -> this is the default stepping.

  If we try to load Steeping {A, *}, it is loading fine.

But getting issue with default stepping.

Also we need to add Stepping info for ICL also in driver code to fetch 
the correct FWfor particular HW Stepping.

Working on the same.

Regards

Jyoti


On 8/28/2018 11:18 AM, Saarinen, Jani wrote:
> Hi,
>
>> -----Original Message-----
>> From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf
>> Of Patchwork
>> Sent: tiistai 28. elokuuta 2018 4.10
>> To: Srivatsa, Anusha <anusha.srivatsa@intel.com>
>> Cc: intel-gfx@lists.freedesktop.org
>> Subject: [Intel-gfx] ✗ Fi.CI.BAT: failure for Load DMC v1.07 on Icelake (rev2)
>>
>> == Series Details ==
>>
>> Series: Load DMC v1.07 on Icelake (rev2)
>> URL   : https://patchwork.freedesktop.org/series/48773/
>> State : failure
>>
>> == Summary ==
>>
>> = CI Bug Log - changes from CI_DRM_4713 -> Patchwork_10025 =
>>
>> == Summary - FAILURE ==
>>
>>    Serious unknown changes coming with Patchwork_10025 absolutely need to
>> be
>>    verified manually.
>>
>>    If you think the reported changes have nothing to do with the changes
>>    introduced in Patchwork_10025, please notify your bug team to allow them
>>    to document this new failure mode, which will reduce false positives in CI.
>>
>>    External URL:
>> https://patchwork.freedesktop.org/api/1.0/series/48773/revisions/2/mbox/
>>
>> == Possible new issues ==
>>
>>    Here are the unknown changes that may have been introduced in
>> Patchwork_10025:
>>
>>    === IGT changes ===
>>
>>      ==== Possible regressions ====
>>
>>      igt@drv_module_reload@basic-reload:
>>        {fi-icl-u}:         PASS -> DMESG-WARN +16
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_10025/fi-icl-u/igt@drv_module_reload@basic-reload.html
> Dmesg	
>   [  395.430440] [drm:csr_load_work_fn [i915]] *ERROR* DMC firmware has wrong dmc header length (1 bytes)
> [  395.430515] i915 0000:00:02.0: Failed to load DMC firmware i915/icl_dmc_ver1_07.bin. Disabling runtime power management.
> [  395.430518] i915 0000:00:02.0: DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
> [  396.682262] Setting dangerous option reset - tainting kernel
>
> Sound like issue...Imre?
>>      igt@gem_exec_suspend@basic-s4-devices:
>>        fi-blb-e6850:       PASS -> INCOMPLETE
>>
>>
>> == Known issues ==
>>
>>    Here are the changes found in Patchwork_10025 that come from known
>> issues:
>>
>>    === IGT changes ===
>>
>>      ==== Issues hit ====
>>
>>      igt@drv_selftest@live_hangcheck:
>>        fi-skl-6700hq:      PASS -> DMESG-FAIL (fdo#106560, fdo#107174)
>>
>>      igt@kms_chamelium@dp-edid-read:
>>        fi-kbl-7500u:       PASS -> FAIL (fdo#103841)
>>
>>      igt@kms_frontbuffer_tracking@basic:
>>        {fi-byt-clapper}:   PASS -> FAIL (fdo#103167)
>>
>>      igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b:
>>        {fi-byt-clapper}:   PASS -> FAIL (fdo#107362)
>>
>>      {igt@kms_psr@primary_page_flip}:
>>        fi-cnl-psr:         PASS -> FAIL (fdo#107336)
>>
>>      igt@pm_rpm@basic-pci-d3-state:
>>        fi-glk-dsi:         PASS -> INCOMPLETE (k.org#198133, fdo#103359)
>>
>>      {igt@pm_rpm@module-reload}:
>>        fi-cnl-psr:         PASS -> WARN (fdo#107602)
>>
>>
>>      ==== Possible fixes ====
>>
>>      igt@drv_selftest@live_hangcheck:
>>        fi-cfl-guc:         DMESG-FAIL -> PASS
>>
>>      igt@kms_pipe_crc_basic@read-crc-pipe-b:
>>        {fi-byt-clapper}:   FAIL (fdo#107362) -> PASS
>>
>>      igt@pm_rpm@basic-pci-d3-state:
>>        fi-skl-6770hq:      WARN -> PASS +1
>>
>>
>>    {name}: This element is suppressed. This means it is ignored when
>> computing
>>            the status of the difference (SUCCESS, WARNING, or FAILURE).
>>
>>    fdo#103167 https://bugs.freedesktop.org/show_bug.cgi?id=103167
>>    fdo#103359 https://bugs.freedesktop.org/show_bug.cgi?id=103359
>>    fdo#103841 https://bugs.freedesktop.org/show_bug.cgi?id=103841
>>    fdo#106560 https://bugs.freedesktop.org/show_bug.cgi?id=106560
>>    fdo#107174 https://bugs.freedesktop.org/show_bug.cgi?id=107174
>>    fdo#107336 https://bugs.freedesktop.org/show_bug.cgi?id=107336
>>    fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
>>    fdo#107602 https://bugs.freedesktop.org/show_bug.cgi?id=107602
>>    k.org#198133 https://bugzilla.kernel.org/show_bug.cgi?id=198133
>>
>>
>> == Participating hosts (54 -> 49) ==
>>
>>    Missing    (5): fi-ctg-p8600 fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-hsw-
>> 4200u
>>
>>
>> == Build changes ==
>>
>>      * Linux: CI_DRM_4713 -> Patchwork_10025
>>
>>    CI_DRM_4713: 9261175f56a1b035b9db12e959ba2e8c756924a6 @
>> git://anongit.freedesktop.org/gfx-ci/linux
>>    IGT_4610: c40743d3fce5055682d31610519758dd7379c0f8 @
>> git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
>>    Patchwork_10025: 0b098dc6cfb59c4634719f51ea690ad133639f5e @
>> git://anongit.freedesktop.org/gfx-ci/linux
>>
>>
>> == Linux commits ==
>>
>> 0b098dc6cfb5 firmware/dmc/icl: load v1.07 on icelake.
>>
>> == Logs ==
>>
>> For more details see: https://intel-gfx-ci.01.org/tree/drm-
>> tip/Patchwork_10025/issues.html
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx


[-- Attachment #1.2: Type: text/html, Size: 43729 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-08-28  6:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28  0:38 [PATCH 0/1] Load DMC v1.07 on Icelake Anusha Srivatsa
2018-08-28  0:38 ` [PATCH 1/1] firmware/dmc/icl: load v1.07 on icelake Anusha Srivatsa
2018-09-03 10:00   ` Imre Deak
2018-09-04  5:27     ` Rodrigo Vivi
2018-09-05  9:07       ` Joonas Lahtinen
2018-09-05 10:11         ` Imre Deak
2018-09-05 16:42         ` Rodrigo Vivi
2018-09-06  6:46           ` Jani Nikula
2018-09-06 17:35             ` Rodrigo Vivi
2018-09-07  7:47               ` Joonas Lahtinen
2018-09-07 18:26                 ` Srivatsa, Anusha
2018-09-13 21:22                   ` Rodrigo Vivi
2018-09-06  9:50           ` Joonas Lahtinen
2018-09-05 18:55       ` Srivatsa, Anusha
2018-09-05 19:31         ` Rodrigo Vivi
2018-09-05 19:38           ` Srivatsa, Anusha
2018-08-28  1:09 ` ✗ Fi.CI.BAT: failure for Load DMC v1.07 on Icelake (rev2) Patchwork
2018-08-28  5:48   ` Saarinen, Jani
2018-08-28  6:49     ` Yadav, Jyoti R [this message]
2018-08-31 15:20 ` ✓ Fi.CI.BAT: success " Patchwork
2018-08-31 22:16 ` ✓ 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=fb338be7-7fba-6fdb-6b58-6e825d3c609c@intel.com \
    --to=jyoti.r.yadav@intel.com \
    --cc=anusha.srivatsa@intel.com \
    --cc=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.saarinen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.