From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: igt-dev@lists.freedesktop.org,
Martin Peres <martin.peres@linux.intel.com>
Subject: Re: [igt-dev] ✗ Fi.CI.IGT: failure for lib/igt_kms: Clear all non-atomic properties in legacy/universal commit correctly.
Date: Fri, 1 Feb 2019 10:56:10 +0100 [thread overview]
Message-ID: <54b5eec4-a7c5-67dd-2670-7af552b59dd7@linux.intel.com> (raw)
In-Reply-To: <20190201092903.GL4038@platvala-desk.ger.corp.intel.com>
Op 01-02-2019 om 10:29 schreef Petri Latvala:
> On Thu, Jan 31, 2019 at 08:25:45PM +0000, Patchwork wrote:
>> == Series Details ==
>>
>> Series: lib/igt_kms: Clear all non-atomic properties in legacy/universal commit correctly.
>> URL : https://patchwork.freedesktop.org/series/56037/
>> State : failure
>>
>> == Summary ==
>>
>> CI Bug Log - changes from CI_DRM_5518_full -> IGTPW_2326_full
>> ====================================================
>>
>> Summary
>> -------
>>
>> **FAILURE**
>>
>> Serious unknown changes coming with IGTPW_2326_full absolutely need to be
>> verified manually.
>>
>> If you think the reported changes have nothing to do with the changes
>> introduced in IGTPW_2326_full, 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/56037/revisions/1/mbox/
>>
>> Possible new issues
>> -------------------
>>
>> Here are the unknown changes that may have been introduced in IGTPW_2326_full:
>>
>> ### IGT changes ###
>>
>> #### Possible regressions ####
>>
>> * igt@kms_vblank@pipe-c-ts-continuation-suspend:
>> - shard-apl: PASS -> DMESG-WARN
>
> <3> [123.565629] [drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
> <3> [123.663710] [drm:lspcon_change_mode.constprop.4 [i915]] *ERROR* Error reading LSPCON mode
> <3> [123.663786] [drm:intel_dp_encoder_reset [i915]] *ERROR* LSPCON resume failed
>
>
> Good old LSPCON. Martin CC'd, not caused by this patch.
>
>
Thanks, pushed. :)
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-02-01 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 8:58 [igt-dev] [PATCH i-g-t] lib/igt_kms: Clear all non-atomic properties in legacy/universal commit correctly Maarten Lankhorst
2019-01-31 9:28 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-01-31 10:26 ` [igt-dev] [PATCH i-g-t] " Petri Latvala
2019-01-31 12:05 ` Maarten Lankhorst
2019-01-31 14:38 ` Kazlauskas, Nicholas
2019-01-31 20:25 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
2019-02-01 9:29 ` Petri Latvala
2019-02-01 9:56 ` Maarten Lankhorst [this message]
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=54b5eec4-a7c5-67dd-2670-7af552b59dd7@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=martin.peres@linux.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