drm/i915/dp_mst: Fix disabling MST on a port
PATCH 1/3 drm/i915/dp_mst: Fix disabling MST on a port
Currently MST on a port can get enabled/disabled from the hotplug work and get disabled from the short pulse work in a racy way. Fix this by relying on the MST state checking in the hotplug work and just schedule a hotplug work from the short pulse handler if some problem happened during the MST interrupt handling.
This removes the explicit MST disabling in case of an AUX failure, but if AUX fails, then probably the detection will also fail during the scheduled hotplug work and it's not guaranteed that we'll see intermittent errors anyway.
While at it also simplify the error checking of the MST interrupt handler.
--- drivers/gpu/drm/i915/display/intel_dp.c | 33 +++---------------------- 1 file changed, 4 insertions(+), 29 deletions(-)
drivers/gpu/drm/i915/display/intel_dp.c +4 -29
@@ -5604,7 +5604,7 @@ intel_dp_check_mst_status(struct intel_dp *intel_dp) } } -return need_retrain; +return need_retrain ? -EINVAL :0 ; } static bool
@@ -7255,35 +7255,10 @@ intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) }if (intel_dp->is_mst) { -switch (intel_dp_check_mst_status (intel_dp)) { -case -EINVAL : -/* -* If we were in MST mode, and device is not -* there, get out of MST mode -*/ -drm_dbg_kms (&i915->drm, -"MST device may have disappeared %d vs %d\n" , - intel_dp->is_mst, - intel_dp->mst_mgr.mst_state); - intel_dp->is_mst = false; -drm_dp_mst_topology_mgr_set_mst (&intel_dp->mst_mgr, - intel_dp->is_mst); - -return IRQ_NONE ; -case 1 : -return IRQ_NONE ; -default : -break ; - } - } - -if (!intel_dp->is_mst) { -bool handled; - - handled =intel_dp_short_pulse (intel_dp); - -if (!handled) +if (intel_dp_check_mst_status (intel_dp) <0 )return IRQ_NONE ; + }else if (!intel_dp_short_pulse (intel_dp)) { +return IRQ_NONE ; }return IRQ_HANDLED ;
Signature · 6 lines
2.23.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/3 drm/dp_mst: Sanitize mgr->qlock locking in drm_dp_mst_wait_tx_reply()
Make the locking look symmetric with the unlocking.
--- drivers/gpu/drm/drm_dp_mst_topology.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/drm_dp_mst_topology.c +1 -1
@@ -1183,7 +1183,7 @@ static int drm_dp_mst_wait_tx_reply(struct drm_dp_mst_branch *mstb, ret =wait_event_timeout (mgr->tx_waitq,check_txmsg_state (mgr, txmsg), (4 *HZ )); -mutex_lock (&mstb->mgr->qlock); +mutex_lock (&mgr->qlock);if (ret >0 ) {if (txmsg->state ==DRM_DP_SIDEBAND_TX_TIMEOUT ) { ret = -EIO ;
Signature · 6 lines
2.23.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH 2/3] drm/dp_mst: Sanitize mgr->qlock locking in drm_dp_mst_wait_tx_reply()
Quoted 2 lines · Imre Deak
Make the locking look symmetric with the unlocking.
Quoted 10 lines
Signed-off-by Imre Deak <[email protected]>--- drivers/gpu/drm/drm_dp_mst_topology.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/gpu/drm/drm_dp_mst_topology.c +0
-0
drivers/gpu/drm/drm_dp_mst_topology.c static int drm_dp_mst_wait_tx_reply(struct drm_dp_mst_branch *mstb, · line 1189
Quoted 8 lines
drivers/gpu/drm/drm_dp_mst_topology.c +1
-1@@ -1183,7 +1183,7 @@ static int drm_dp_mst_wait_tx_reply(struct drm_dp_mst_branch *mstb, ret =wait_event_timeout (mgr->tx_waitq,check_txmsg_state (mgr, txmsg), (4 *HZ )); -mutex_lock (&mstb->mgr->qlock); +mutex_lock (&mgr->qlock);if (ret >0 ) {if (txmsg->state ==DRM_DP_SIDEBAND_TX_TIMEOUT ) { ret = -EIO ;
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH 3/3 drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses
In reply to Imre DeakSome TypeC -> native DP adapters, at least the Club CAC-1557 adapter, incorrectly filter out HPD short pulses with a duration less than ~540 usec, leading to MST probe failures.
According to the DP alt mode specification adapters should forward short pulses with a duration greater than 250 usec. According to the DP specificatin DP sources should detect short pulses in the 500 usec -> 2 ms range. Based on this filtering out short pulses with a duration less than 540 usec is incorrect.
To make such adapters work add support for a driver polling on MST inerrupt flags, and wire this up in the i915 driver. The sink can clear an interrupt it raised after 110 ms if the source doesn't respond, so use a 50 ms poll period to avoid missing an interrupt. Polling of the MST interrupt flags is explicitly allowed by the DP specification.
This fixes MST probe failures I saw using this adapter and a DELL U2515H monitor.
--- drivers/gpu/drm/drm_dp_mst_topology.c | 18 +++++++++++++++--- drivers/gpu/drm/i915/display/intel_dp_mst.c | 15 +++++++++++++++ include/drm/drm_dp_mst_helper.h | 1 + 3 files changed, 31 insertions(+), 3 deletions(-)
drivers/gpu/drm/drm_dp_mst_topology.c +15 -3
@@ -1178,11 +1178,23 @@ static int drm_dp_mst_wait_tx_reply(struct drm_dp_mst_branch *mstb, struct drm_dp_sideband_msg_tx *txmsg) {struct drm_dp_mst_topology_mgr *mgr = mstb->mgr; +unsigned long wait_expires = jiffies +msecs_to_jiffies (4000 );int ret; - ret =wait_event_timeout (mgr->tx_waitq, -check_txmsg_state (mgr, txmsg), - (4 *HZ )); +for (;;) { + ret =wait_event_timeout (mgr->tx_waitq, +check_txmsg_state (mgr, txmsg), + mgr->cbs->update_hpd_irq_state ? +msecs_to_jiffies (50 ) : + wait_expires); + +if (ret || !mgr->cbs->update_hpd_irq_state || +time_after (jiffies, wait_expires)) +break ; + + mgr->cbs->update_hpd_irq_state (mgr); + } +mutex_lock (&mgr->qlock);if (ret >0 ) {if (txmsg->state ==DRM_DP_SIDEBAND_TX_TIMEOUT ) {
drivers/gpu/drm/i915/display/intel_dp_mst.c +15 -0
@@ -765,8 +765,23 @@ static struct drm_connector *intel_dp_add_mst_connector(struct drm_dp_mst_topoloreturn NULL ; } +static void +intel_dp_mst_update_hpd_irq_state (struct drm_dp_mst_topology_mgr *mgr) +{ + struct intel_dp *intel_dp = container_of(mgr, struct intel_dp, mst_mgr); +struct intel_digital_port *dig_port =dp_to_dig_port (intel_dp); +struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); + +spin_lock_irq (&i915->irq_lock); + i915->hotplug.short_port_mask |=BIT (dig_port->base.port); +spin_unlock_irq (&i915->irq_lock); + +queue_work (i915->hotplug.dp_wq, &i915->hotplug.dig_port_work); +} +static const struct drm_dp_mst_topology_cbs mst_cbs = { .add_connector = intel_dp_add_mst_connector, + .update_hpd_irq_state = intel_dp_mst_update_hpd_irq_state, }; static struct intel_dp_mst_encoder *
include/drm/drm_dp_mst_helper.h +1 -0
@@ -475,6 +475,7 @@ struct drm_dp_mst_topology_mgr;struct drm_dp_mst_topology_cbs {/* create a connector for a port */ struct drm_connector *(*add_connector)(struct drm_dp_mst_topology_mgr *mgr,struct drm_dp_mst_port *port,const char *path); +void (*update_hpd_irq_state)(struct drm_dp_mst_topology_mgr *mgr); };#define DP_MAX_PAYLOAD (sizeof(unsigned long) * 8)
Signature · 6 lines
2.23.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH v2 3/3 drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses
Some TypeC -> native DP adapters, at least the Club CAC-1557 adapter, incorrectly filter out HPD short pulses with a duration less than ~540 usec, leading to MST probe failures.
According to the DP alt mode specification adapters should forward short pulses with a duration greater than 250 usec. According to the DP specificatin DP sources should detect short pulses in the 500 usec -> 2 ms range. Based on this filtering out short pulses with a duration less than 540 usec is incorrect.
To make such adapters work add support for a driver polling on MST inerrupt flags, and wire this up in the i915 driver. The sink can clear an interrupt it raised after 110 ms if the source doesn't respond, so use a 50 ms poll period to avoid missing an interrupt. Polling of the MST interrupt flags is explicitly allowed by the DP specification.
This fixes MST probe failures I saw using this adapter and a DELL U2515H monitor.
v2:
- Fix the wait event timeout for the no-poll case.
--- drivers/gpu/drm/drm_dp_mst_topology.c | 19 ++++++++++++++++--- drivers/gpu/drm/i915/display/intel_dp_mst.c | 15 +++++++++++++++ include/drm/drm_dp_mst_helper.h | 1 + 3 files changed, 32 insertions(+), 3 deletions(-)
drivers/gpu/drm/drm_dp_mst_topology.c +16 -3
@@ -1178,11 +1178,24 @@ static int drm_dp_mst_wait_tx_reply(struct drm_dp_mst_branch *mstb, struct drm_dp_sideband_msg_tx *txmsg) {struct drm_dp_mst_topology_mgr *mgr = mstb->mgr; +unsigned long wait_timeout =msecs_to_jiffies (4000 ); +unsigned long wait_expires = jiffies + wait_timeout;int ret; - ret =wait_event_timeout (mgr->tx_waitq, -check_txmsg_state (mgr, txmsg), - (4 *HZ )); +for (;;) { + ret =wait_event_timeout (mgr->tx_waitq, +check_txmsg_state (mgr, txmsg), + mgr->cbs->update_hpd_irq_state ? +msecs_to_jiffies (50 ) : + wait_timeout); + +if (ret || !mgr->cbs->update_hpd_irq_state || +time_after (jiffies, wait_expires)) +break ; + + mgr->cbs->update_hpd_irq_state (mgr); + } +mutex_lock (&mgr->qlock);if (ret >0 ) {if (txmsg->state ==DRM_DP_SIDEBAND_TX_TIMEOUT ) {
drivers/gpu/drm/i915/display/intel_dp_mst.c +15 -0
@@ -765,8 +765,23 @@ static struct drm_connector *intel_dp_add_mst_connector(struct drm_dp_mst_topoloreturn NULL ; } +static void +intel_dp_mst_update_hpd_irq_state (struct drm_dp_mst_topology_mgr *mgr) +{ + struct intel_dp *intel_dp = container_of(mgr, struct intel_dp, mst_mgr); +struct intel_digital_port *dig_port =dp_to_dig_port (intel_dp); +struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); + +spin_lock_irq (&i915->irq_lock); + i915->hotplug.short_port_mask |=BIT (dig_port->base.port); +spin_unlock_irq (&i915->irq_lock); + +queue_work (i915->hotplug.dp_wq, &i915->hotplug.dig_port_work); +} +static const struct drm_dp_mst_topology_cbs mst_cbs = { .add_connector = intel_dp_add_mst_connector, + .update_hpd_irq_state = intel_dp_mst_update_hpd_irq_state, }; static struct intel_dp_mst_encoder *
include/drm/drm_dp_mst_helper.h +1 -0
@@ -475,6 +475,7 @@ struct drm_dp_mst_topology_mgr;struct drm_dp_mst_topology_cbs {/* create a connector for a port */ struct drm_connector *(*add_connector)(struct drm_dp_mst_topology_mgr *mgr,struct drm_dp_mst_port *port,const char *path); +void (*update_hpd_irq_state)(struct drm_dp_mst_topology_mgr *mgr); };#define DP_MAX_PAYLOAD (sizeof(unsigned long) * 8)
Signature · 6 lines
2.23.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH v2 3/3] drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses
Quoted 8 lines · Imre Deak
Some TypeC -> native DP adapters, at least the Club CAC-1557 adapter, incorrectly filter out HPD short pulses with a duration less than ~540 usec, leading to MST probe failures.
According to the DP alt mode specification adapters should forward short pulses with a duration greater than 250 usec. According to the DP specificatin DP sources should detect short pulses in the 500 usec -> 2 ms range.
IIRC it was 250 usec -> 2 ms as well in the DP spec.
500 usec -> 1 ms is the duration of the short hpd
the signalling side should use.
Quoted 37 lines
Based on this filtering out short pulses with a
duration less than 540 usec is incorrect.To make such adapters work add support for a driver polling on MST inerrupt flags, and wire this up in the i915 driver. The sink can clear an interrupt it raised after 110 ms if the source doesn't respond, so use a 50 ms poll period to avoid missing an interrupt. Polling of the MST interrupt flags is explicitly allowed by the DP specification.
This fixes MST probe failures I saw using this adapter and a DELL U2515H monitor.
v2:
- Fix the wait event timeout for the no-poll case.Signed-off-by Imre Deak <[email protected]>--- drivers/gpu/drm/drm_dp_mst_topology.c | 19 ++++++++++++++++--- drivers/gpu/drm/i915/display/intel_dp_mst.c | 15 +++++++++++++++ include/drm/drm_dp_mst_helper.h | 1 + 3 files changed, 32 insertions(+), 3 deletions(-)drivers/gpu/drm/drm_dp_mst_topology.c +2
-3@@ -1178,11 +1178,24 @@ static int drm_dp_mst_wait_tx_reply(struct drm_dp_mst_branch *mstb, struct drm_dp_sideband_msg_tx *txmsg) {struct drm_dp_mst_topology_mgr *mgr = mstb->mgr; +unsigned long wait_timeout =msecs_to_jiffies (4000 ); +unsigned long wait_expires = jiffies + wait_timeout;int ret; - ret =wait_event_timeout (mgr->tx_waitq, -check_txmsg_state (mgr, txmsg), - (4 *HZ ));
drivers/gpu/drm/drm_dp_mst_topology.c static int drm_dp_mst_wait_tx_reply(struct drm_dp_mst_branch *mstb, · line 1194
Quoted 10 lines
drivers/gpu/drm/drm_dp_mst_topology.c +10
-0+for (;;) { + ret =wait_event_timeout (mgr->tx_waitq, +check_txmsg_state (mgr, txmsg), + mgr->cbs->update_hpd_irq_state ? +msecs_to_jiffies (50 ) : + wait_timeout); + +if (ret || !mgr->cbs->update_hpd_irq_state || +time_after (jiffies, wait_expires)) +break ;
First I thought this was changing the behaviour when the callback isn't provided, but then I noticed the ?: stuff for the timeout.
I think this stuff deserves a comment to explain why we would ever do such a thing instead of simply waiting like we did before.
Quoted 17 lines
drivers/gpu/drm/drm_dp_mst_topology.c +4
-0+ + mgr->cbs->update_hpd_irq_state (mgr); + } +mutex_lock (&mgr->qlock);if (ret >0 ) {if (txmsg->state ==DRM_DP_SIDEBAND_TX_TIMEOUT ) {drivers/gpu/drm/i915/display/intel_dp_mst.c +2
-0@@ -765,8 +765,23 @@ static struct drm_connector *intel_dp_add_mst_connector(struct drm_dp_mst_topoloreturn NULL ; } +static void +intel_dp_mst_update_hpd_irq_state (struct drm_dp_mst_topology_mgr *mgr)
drivers/gpu/drm/i915/display/intel_dp_mst.c static struct drm_connector *intel_dp_add_mst_connector(struct drm_dp_mst_topolo · line 779
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_dp_mst.c +10
-0+{ + struct intel_dp *intel_dp = container_of(mgr, struct intel_dp, mst_mgr); +struct intel_digital_port *dig_port =dp_to_dig_port (intel_dp); +struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); + +spin_lock_irq (&i915->irq_lock); + i915->hotplug.short_port_mask |=BIT (dig_port->base.port); +spin_unlock_irq (&i915->irq_lock); + +queue_work (i915->hotplug.dp_wq, &i915->hotplug.dig_port_work);
I might suggest putting this code right next to intel_hpd_irq_handler() so that people can actually see it when working on the hotplug code.
Quoted 13 lines
drivers/gpu/drm/i915/display/intel_dp_mst.c +3
-0+} +static const struct drm_dp_mst_topology_cbs mst_cbs = { .add_connector = intel_dp_add_mst_connector, + .update_hpd_irq_state = intel_dp_mst_update_hpd_irq_state, }; static struct intel_dp_mst_encoder *include/drm/drm_dp_mst_helper.h +0
-0
include/drm/drm_dp_mst_helper.h struct drm_dp_mst_topology_mgr; · line 478
Quoted 4 lines
include/drm/drm_dp_mst_helper.h +1
-0@@ -475,6 +475,7 @@ struct drm_dp_mst_topology_mgr;struct drm_dp_mst_topology_cbs {/* create a connector for a port */ struct drm_connector *(*add_connector)(struct drm_dp_mst_topology_mgr *mgr,struct drm_dp_mst_port *port,const char *path); +void (*update_hpd_irq_state)(struct drm_dp_mst_topology_mgr *mgr);
I guess a bit of docs for this might be nice. Maybe s/update/poll/ might make the intention more clear? Not sure.
Quoted 10 lines
include/drm/drm_dp_mst_helper.h +0
-0};#define DP_MAX_PAYLOAD (sizeof(unsigned long) * 8)Signature · 6 lines
2.23.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 6 lines
Ville Syrjälä Intel _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Intel-gfx] [PATCH v2 3/3] drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses
Quoted 10 lines · Ville Syrjälä
Quoted 8 lines · Imre Deak
Some TypeC -> native DP adapters, at least the Club CAC-1557 adapter, incorrectly filter out HPD short pulses with a duration less than ~540 usec, leading to MST probe failures.
According to the DP alt mode specification adapters should forward short pulses with a duration greater than 250 usec. According to the DP specificatin DP sources should detect short pulses in the 500 usec -> 2 ms range.
Quoted 4 lines
IIRC it was 250 usec -> 2 ms as well in the DP spec.
500 usec -> 1 ms is the duration of the short hpd
the signalling side should use.
Ah, correct (and this is what makes actually sense). For reference it's described under "5.1.4 Source Device Behavior upon HPD Pulse Detection"
Quoted 51 lines
Quoted 37 lines
Based on this filtering out short pulses with a
duration less than 540 usec is incorrect.To make such adapters work add support for a driver polling on MST inerrupt flags, and wire this up in the i915 driver. The sink can clear an interrupt it raised after 110 ms if the source doesn't respond, so use a 50 ms poll period to avoid missing an interrupt. Polling of the MST interrupt flags is explicitly allowed by the DP specification.
This fixes MST probe failures I saw using this adapter and a DELL U2515H monitor.
v2:
- Fix the wait event timeout for the no-poll case.Signed-off-by Imre Deak <[email protected]>--- drivers/gpu/drm/drm_dp_mst_topology.c | 19 ++++++++++++++++--- drivers/gpu/drm/i915/display/intel_dp_mst.c | 15 +++++++++++++++ include/drm/drm_dp_mst_helper.h | 1 + 3 files changed, 32 insertions(+), 3 deletions(-)drivers/gpu/drm/drm_dp_mst_topology.c +2
-3@@ -1178,11 +1178,24 @@ static int drm_dp_mst_wait_tx_reply(struct drm_dp_mst_branch *mstb, struct drm_dp_sideband_msg_tx *txmsg) {struct drm_dp_mst_topology_mgr *mgr = mstb->mgr; +unsigned long wait_timeout =msecs_to_jiffies (4000 ); +unsigned long wait_expires = jiffies + wait_timeout;int ret; - ret =wait_event_timeout (mgr->tx_waitq, -check_txmsg_state (mgr, txmsg), - (4 *HZ ));drivers/gpu/drm/drm_dp_mst_topology.c static int drm_dp_mst_wait_tx_reply(struct drm_dp_mst_branch *mstb, · line 1194
Quoted 10 lines
drivers/gpu/drm/drm_dp_mst_topology.c +10
-0+for (;;) { + ret =wait_event_timeout (mgr->tx_waitq, +check_txmsg_state (mgr, txmsg), + mgr->cbs->update_hpd_irq_state ? +msecs_to_jiffies (50 ) : + wait_timeout); + +if (ret || !mgr->cbs->update_hpd_irq_state || +time_after (jiffies, wait_expires)) +break ;First I thought this was changing the behaviour when the callback isn't provided, but then I noticed the ?: stuff for the timeout.
Quoted 2 lines
I think this stuff deserves a comment to explain why we would ever do such a thing instead of simply waiting like we did before.
Ok, will add a compact form of the commit log explanation.
Quoted 16 lines
Quoted 16 lines
drivers/gpu/drm/drm_dp_mst_topology.c +4
-0+ + mgr->cbs->update_hpd_irq_state (mgr); + } +mutex_lock (&mgr->qlock);if (ret >0 ) {if (txmsg->state ==DRM_DP_SIDEBAND_TX_TIMEOUT ) {drivers/gpu/drm/i915/display/intel_dp_mst.c +0
-0@@ -765,8 +765,23 @@ static struct drm_connector *intel_dp_add_mst_connector(struct drm_dp_mst_topoloreturn NULL ; }
Quoted 15 lines
drivers/gpu/drm/i915/display/intel_dp_mst.c static struct drm_connector *intel_dp_add_mst_connector(struct drm_dp_mst_topolo · line 779
Quoted 12 lines
drivers/gpu/drm/i915/display/intel_dp_mst.c +12
-0+static void +intel_dp_mst_update_hpd_irq_state (struct drm_dp_mst_topology_mgr *mgr) +{ + struct intel_dp *intel_dp = container_of(mgr, struct intel_dp, mst_mgr); +struct intel_digital_port *dig_port =dp_to_dig_port (intel_dp); +struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); + +spin_lock_irq (&i915->irq_lock); + i915->hotplug.short_port_mask |=BIT (dig_port->base.port); +spin_unlock_irq (&i915->irq_lock); + +queue_work (i915->hotplug.dp_wq, &i915->hotplug.dig_port_work);I might suggest putting this code right next to
intel_hpd_irq_handler()so that people can actually see it when working on the hotplug code.
Ok.
Quoted 8 lines
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_dp_mst.c +3
-0+} +static const struct drm_dp_mst_topology_cbs mst_cbs = { .add_connector = intel_dp_add_mst_connector, + .update_hpd_irq_state = intel_dp_mst_update_hpd_irq_state, };
Quoted 13 lines
include/drm/drm_dp_mst_helper.h struct drm_dp_mst_topology_mgr; · line 478
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_dp_mst.c +0
-0static struct intel_dp_mst_encoder *include/drm/drm_dp_mst_helper.h +1
-0@@ -475,6 +475,7 @@ struct drm_dp_mst_topology_mgr;struct drm_dp_mst_topology_cbs {/* create a connector for a port */ struct drm_connector *(*add_connector)(struct drm_dp_mst_topology_mgr *mgr,struct drm_dp_mst_port *port,const char *path); +void (*update_hpd_irq_state)(struct drm_dp_mst_topology_mgr *mgr);I guess a bit of docs for this might be nice. Maybe s/update/poll/ might make the intention more clear? Not sure.
Ok.
Quoted 15 lines
Quoted 11 lines
include/drm/drm_dp_mst_helper.h +0
-0};#define DP_MAX_PAYLOAD (sizeof(unsigned long) * 8)Signature · 6 lines
2.23.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfxSignature · 2 lines
Ville Syrjälä Intel
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH v3 3/3 drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses
In reply to Imre DeakSome TypeC -> native DP adapters, at least the Club 3D CAC-1557 adapter, incorrectly filter out HPD short pulses with a duration less than ~540 usec, leading to MST probe failures.
According to the DP Standard 2.0 section 5.1.4:
- DP sinks should generate short pulses in the 500 usec -> 1 msec range
- DP sources should detect short pulses in the 250 usec -> 2 msec range
According to the DP Alt Mode on TypeC Standard section 3.9.2, adapters should detect and forward short pulses according to how sources should detect them as specified in the DP Standard (250 usec -> 2 msec).
Based on the above filtering out short pulses with a duration less than 540 usec is incorrect.
To make such adapters work add support for a driver polling on MST inerrupt flags, and wire this up in the i915 driver. The sink can clear an interrupt it raised after 110 msec if the source doesn't respond, so use a 50 msec poll period to avoid missing an interrupt. Polling of the MST interrupt flags is explicitly allowed by the DP Standard.
This fixes MST probe failures I saw using this adapter and a DELL U2515H monitor.
v2:
- Fix the wait event timeout for the no-poll case.
v3 (Ville):
- Fix the short pulse duration limits in the commit log prescribed by the DP Standard.
- Add code comment explaining why/how polling is used.
- Factor out a helper to schedule the port's hpd irq handler and move it to the rest of hotplug handlers.
- Document the new MST callback.
- s/update_hpd_irq_state/poll_hpd_irq/
--- drivers/gpu/drm/drm_dp_mst_topology.c | 32 ++++++++++++++++++-- drivers/gpu/drm/i915/display/intel_dp_mst.c | 10 ++++++ drivers/gpu/drm/i915/display/intel_hotplug.c | 18 +++++++++++ drivers/gpu/drm/i915/display/intel_hotplug.h | 2 ++ include/drm/drm_dp_mst_helper.h | 9 ++++++ 5 files changed, 68 insertions(+), 3 deletions(-)
drivers/gpu/drm/drm_dp_mst_topology.c +29 -3
@@ -1178,11 +1178,37 @@ static int drm_dp_mst_wait_tx_reply(struct drm_dp_mst_branch *mstb, struct drm_dp_sideband_msg_tx *txmsg) {struct drm_dp_mst_topology_mgr *mgr = mstb->mgr; +unsigned long wait_timeout =msecs_to_jiffies (4000 ); +unsigned long wait_expires = jiffies + wait_timeout;int ret; - ret =wait_event_timeout (mgr->tx_waitq, -check_txmsg_state (mgr, txmsg), - (4 *HZ )); +for (;;) { +/* +* If the driver provides a way for this, change to +* poll-waiting for the MST reply interrupt if we didn't receive +* it for 50 msec. This would cater for cases where the HPD +* pulse signal got lost somewhere, even though the sink raised +* the corresponding MST interrupt correctly. One example is the +* Club 3D CAC-1557 TypeC -> DP adapter which for some reason +* filters out short pulses with a duration less than ~540 usec. +* +* The poll period is 50 msec to avoid missing an interrupt +* after the sink has cleared it (after a 110msec timeout +* since it raised the interrupt). +*/ + ret =wait_event_timeout (mgr->tx_waitq, +check_txmsg_state (mgr, txmsg), + mgr->cbs->poll_hpd_irq ? +msecs_to_jiffies (50 ) : + wait_timeout); + +if (ret || !mgr->cbs->poll_hpd_irq || +time_after (jiffies, wait_expires)) +break ; + + mgr->cbs->poll_hpd_irq (mgr); + } +mutex_lock (&mgr->qlock);if (ret >0 ) {if (txmsg->state ==DRM_DP_SIDEBAND_TX_TIMEOUT ) {
drivers/gpu/drm/i915/display/intel_dp_mst.c +10 -0
@@ -33,6 +33,7 @@#include "intel_connector.h" #include "intel_ddi.h" #include "intel_display_types.h" +#include "intel_hotplug.h" #include "intel_dp.h" #include "intel_dp_mst.h" #include "intel_dpio_phy.h"
@@ -765,8 +766,17 @@ static struct drm_connector *intel_dp_add_mst_connector(struct drm_dp_mst_topoloreturn NULL ; } +static void +intel_dp_mst_poll_hpd_irq (struct drm_dp_mst_topology_mgr *mgr) +{ + struct intel_dp *intel_dp = container_of(mgr, struct intel_dp, mst_mgr); + +intel_hpd_trigger_irq (dp_to_dig_port (intel_dp)); +} +static const struct drm_dp_mst_topology_cbs mst_cbs = { .add_connector = intel_dp_add_mst_connector, + .poll_hpd_irq = intel_dp_mst_poll_hpd_irq, }; static struct intel_dp_mst_encoder *
drivers/gpu/drm/i915/display/intel_hotplug.c +18 -0
@@ -347,6 +347,24 @@ static void i915_digport_work_func(struct work_struct *work) } } +/** +* intel_hpd_trigger_irq - trigger an hpd irq event for a port +* @dig_port: digital port +* +* Trigger an HPD interrupt event for the given port, emulating a short pulse +* generated by the sink, and schedule the dig port work to handle it. +*/ +void intel_hpd_trigger_irq (struct intel_digital_port *dig_port) +{ +struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); + +spin_lock_irq (&i915->irq_lock); + i915->hotplug.short_port_mask |=BIT (dig_port->base.port); +spin_unlock_irq (&i915->irq_lock); + +queue_work (i915->hotplug.dp_wq, &i915->hotplug.dig_port_work); +} +/* * Handle hotplug events outside the interrupt handler proper. */
drivers/gpu/drm/i915/display/intel_hotplug.h +2 -0
@@ -10,6 +10,7 @@struct drm_i915_private ;struct intel_connector ; +struct intel_digital_port ;struct intel_encoder ;enum port ;
@@ -18,6 +19,7 @@ enum intel_hotplug_state intel_encoder_hotplug(struct intel_encoder *encoder, struct intel_connector *connector);void intel_hpd_irq_handler (struct drm_i915_private *dev_priv,u32 pin_mask,u32 long_mask); +void intel_hpd_trigger_irq (struct intel_digital_port *dig_port);void intel_hpd_init (struct drm_i915_private *dev_priv);void intel_hpd_init_work (struct drm_i915_private *dev_priv);void intel_hpd_cancel_work (struct drm_i915_private *dev_priv);
include/drm/drm_dp_mst_helper.h +9 -0
@@ -475,6 +475,15 @@ struct drm_dp_mst_topology_mgr;struct drm_dp_mst_topology_cbs {/* create a connector for a port */ struct drm_connector *(*add_connector)(struct drm_dp_mst_topology_mgr *mgr,struct drm_dp_mst_port *port,const char *path); +/* +* Checks for any pending MST interrupts, passing them to MST core for +* processing, the same way an HPD IRQ pulse handler would do this. +* If provided MST core calls this callback from a poll-waiting loop +* when waiting for MST down message replies. The driver is expected +* to guard against a race between this callback and the driver's HPD +* IRQ pulse handler. +*/ +void (*poll_hpd_irq)(struct drm_dp_mst_topology_mgr *mgr); };#define DP_MAX_PAYLOAD (sizeof(unsigned long) * 8)
Signature · 6 lines
2.23.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH v3 3/3] drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses
Quoted 35 lines · Imre Deak
Some TypeC -> native DP adapters, at least the Club 3D CAC-1557 adapter, incorrectly filter out HPD short pulses with a duration less than ~540 usec, leading to MST probe failures.
According to the DP Standard 2.0 section 5.1.4:
- DP sinks should generate short pulses in the 500 usec -> 1 msec range
- DP sources should detect short pulses in the 250 usec -> 2 msec rangeAccording to the DP Alt Mode on TypeC Standard section 3.9.2, adapters should detect and forward short pulses according to how sources should detect them as specified in the DP Standard (250 usec -> 2 msec).
Based on the above filtering out short pulses with a duration less than 540 usec is incorrect.
To make such adapters work add support for a driver polling on MST inerrupt flags, and wire this up in the i915 driver. The sink can clear an interrupt it raised after 110 msec if the source doesn't respond, so use a 50 msec poll period to avoid missing an interrupt. Polling of the MST interrupt flags is explicitly allowed by the DP Standard.
This fixes MST probe failures I saw using this adapter and a DELL U2515H monitor.
v2:
- Fix the wait event timeout for the no-poll case.
v3 (Ville):
- Fix the short pulse duration limits in the commit log prescribed by the DP Standard.
- Add code comment explaining why/how polling is used.
- Factor out a helper to schedule the port's hpd irq handler and move it to the rest of hotplug handlers.
- Document the new MST callback.
- s/update_hpd_irq_state/poll_hpd_irq/
Quoted 2 lines
Cc Ville Syrjälä <[email protected]>Signed-off-by Imre Deak <[email protected]>
lgtm
Quoted 154 lines
--- drivers/gpu/drm/drm_dp_mst_topology.c | 32 ++++++++++++++++++-- drivers/gpu/drm/i915/display/intel_dp_mst.c | 10 ++++++ drivers/gpu/drm/i915/display/intel_hotplug.c | 18 +++++++++++ drivers/gpu/drm/i915/display/intel_hotplug.h | 2 ++ include/drm/drm_dp_mst_helper.h | 9 ++++++ 5 files changed, 68 insertions(+), 3 deletions(-)drivers/gpu/drm/drm_dp_mst_topology.c +29
-3@@ -1178,11 +1178,37 @@ static int drm_dp_mst_wait_tx_reply(struct drm_dp_mst_branch *mstb, struct drm_dp_sideband_msg_tx *txmsg) {struct drm_dp_mst_topology_mgr *mgr = mstb->mgr; +unsigned long wait_timeout =msecs_to_jiffies (4000 ); +unsigned long wait_expires = jiffies + wait_timeout;int ret; - ret =wait_event_timeout (mgr->tx_waitq, -check_txmsg_state (mgr, txmsg), - (4 *HZ )); +for (;;) { +/* +* If the driver provides a way for this, change to +* poll-waiting for the MST reply interrupt if we didn't receive +* it for 50 msec. This would cater for cases where the HPD +* pulse signal got lost somewhere, even though the sink raised +* the corresponding MST interrupt correctly. One example is the +* Club 3D CAC-1557 TypeC -> DP adapter which for some reason +* filters out short pulses with a duration less than ~540 usec. +* +* The poll period is 50 msec to avoid missing an interrupt +* after the sink has cleared it (after a 110msec timeout +* since it raised the interrupt). +*/ + ret =wait_event_timeout (mgr->tx_waitq, +check_txmsg_state (mgr, txmsg), + mgr->cbs->poll_hpd_irq ? +msecs_to_jiffies (50 ) : + wait_timeout); + +if (ret || !mgr->cbs->poll_hpd_irq || +time_after (jiffies, wait_expires)) +break ; + + mgr->cbs->poll_hpd_irq (mgr); + } +mutex_lock (&mgr->qlock);if (ret >0 ) {if (txmsg->state ==DRM_DP_SIDEBAND_TX_TIMEOUT ) {drivers/gpu/drm/i915/display/intel_dp_mst.c +10
-0@@ -33,6 +33,7 @@#include "intel_connector.h" #include "intel_ddi.h" #include "intel_display_types.h" +#include "intel_hotplug.h" #include "intel_dp.h" #include "intel_dp_mst.h" #include "intel_dpio_phy.h" @@ -765,8 +766,17 @@ static struct drm_connector *intel_dp_add_mst_connector(struct drm_dp_mst_topoloreturn NULL ; } +static void +intel_dp_mst_poll_hpd_irq (struct drm_dp_mst_topology_mgr *mgr) +{ + struct intel_dp *intel_dp = container_of(mgr, struct intel_dp, mst_mgr); + +intel_hpd_trigger_irq (dp_to_dig_port (intel_dp)); +} +static const struct drm_dp_mst_topology_cbs mst_cbs = { .add_connector = intel_dp_add_mst_connector, + .poll_hpd_irq = intel_dp_mst_poll_hpd_irq, }; static struct intel_dp_mst_encoder *drivers/gpu/drm/i915/display/intel_hotplug.c +18
-0@@ -347,6 +347,24 @@ static void i915_digport_work_func(struct work_struct *work) } } +/** +* intel_hpd_trigger_irq - trigger an hpd irq event for a port +* @dig_port: digital port +* +* Trigger an HPD interrupt event for the given port, emulating a short pulse +* generated by the sink, and schedule the dig port work to handle it. +*/ +void intel_hpd_trigger_irq (struct intel_digital_port *dig_port) +{ +struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); + +spin_lock_irq (&i915->irq_lock); + i915->hotplug.short_port_mask |=BIT (dig_port->base.port); +spin_unlock_irq (&i915->irq_lock); + +queue_work (i915->hotplug.dp_wq, &i915->hotplug.dig_port_work); +} +/* * Handle hotplug events outside the interrupt handler proper. */ drivers/gpu/drm/i915/display/intel_hotplug.h +2
-0@@ -10,6 +10,7 @@struct drm_i915_private ;struct intel_connector ; +struct intel_digital_port ;struct intel_encoder ;enum port ;@@ -18,6 +19,7 @@ enum intel_hotplug_state intel_encoder_hotplug(struct intel_encoder *encoder, struct intel_connector *connector);void intel_hpd_irq_handler (struct drm_i915_private *dev_priv,u32 pin_mask,u32 long_mask); +void intel_hpd_trigger_irq (struct intel_digital_port *dig_port);void intel_hpd_init (struct drm_i915_private *dev_priv);void intel_hpd_init_work (struct drm_i915_private *dev_priv);void intel_hpd_cancel_work (struct drm_i915_private *dev_priv);include/drm/drm_dp_mst_helper.h +9
-0@@ -475,6 +475,15 @@ struct drm_dp_mst_topology_mgr;struct drm_dp_mst_topology_cbs {/* create a connector for a port */ struct drm_connector *(*add_connector)(struct drm_dp_mst_topology_mgr *mgr,struct drm_dp_mst_port *port,const char *path); +/* +* Checks for any pending MST interrupts, passing them to MST core for +* processing, the same way an HPD IRQ pulse handler would do this. +* If provided MST core calls this callback from a poll-waiting loop +* when waiting for MST down message replies. The driver is expected +* to guard against a race between this callback and the driver's HPD +* IRQ pulse handler. +*/ +void (*poll_hpd_irq)(struct drm_dp_mst_topology_mgr *mgr); };#define DP_MAX_PAYLOAD (sizeof(unsigned long) * 8)Signature · 1 line
2.23.1
Signature · 6 lines
Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH v3 3/3] drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses
In reply to Imre DeakHi Dave, Lyude,
are you ok to merge this patchset via the drm-intel-next-queued tree?
--Imre
Quoted 196 lines · Imre Deak
Some TypeC -> native DP adapters, at least the Club 3D CAC-1557 adapter, incorrectly filter out HPD short pulses with a duration less than ~540 usec, leading to MST probe failures.
According to the DP Standard 2.0 section 5.1.4:
- DP sinks should generate short pulses in the 500 usec -> 1 msec range
- DP sources should detect short pulses in the 250 usec -> 2 msec rangeAccording to the DP Alt Mode on TypeC Standard section 3.9.2, adapters should detect and forward short pulses according to how sources should detect them as specified in the DP Standard (250 usec -> 2 msec).
Based on the above filtering out short pulses with a duration less than 540 usec is incorrect.
To make such adapters work add support for a driver polling on MST inerrupt flags, and wire this up in the i915 driver. The sink can clear an interrupt it raised after 110 msec if the source doesn't respond, so use a 50 msec poll period to avoid missing an interrupt. Polling of the MST interrupt flags is explicitly allowed by the DP Standard.
This fixes MST probe failures I saw using this adapter and a DELL U2515H monitor.
v2:
- Fix the wait event timeout for the no-poll case.
v3 (Ville):
- Fix the short pulse duration limits in the commit log prescribed by the DP Standard.
- Add code comment explaining why/how polling is used.
- Factor out a helper to schedule the port's hpd irq handler and move it to the rest of hotplug handlers.
- Document the new MST callback.
- s/update_hpd_irq_state/poll_hpd_irq/Cc Ville Syrjälä <[email protected]>Signed-off-by Imre Deak <[email protected]>--- drivers/gpu/drm/drm_dp_mst_topology.c | 32 ++++++++++++++++++-- drivers/gpu/drm/i915/display/intel_dp_mst.c | 10 ++++++ drivers/gpu/drm/i915/display/intel_hotplug.c | 18 +++++++++++ drivers/gpu/drm/i915/display/intel_hotplug.h | 2 ++ include/drm/drm_dp_mst_helper.h | 9 ++++++ 5 files changed, 68 insertions(+), 3 deletions(-)drivers/gpu/drm/drm_dp_mst_topology.c +29
-3@@ -1178,11 +1178,37 @@ static int drm_dp_mst_wait_tx_reply(struct drm_dp_mst_branch *mstb, struct drm_dp_sideband_msg_tx *txmsg) {struct drm_dp_mst_topology_mgr *mgr = mstb->mgr; +unsigned long wait_timeout =msecs_to_jiffies (4000 ); +unsigned long wait_expires = jiffies + wait_timeout;int ret; - ret =wait_event_timeout (mgr->tx_waitq, -check_txmsg_state (mgr, txmsg), - (4 *HZ )); +for (;;) { +/* +* If the driver provides a way for this, change to +* poll-waiting for the MST reply interrupt if we didn't receive +* it for 50 msec. This would cater for cases where the HPD +* pulse signal got lost somewhere, even though the sink raised +* the corresponding MST interrupt correctly. One example is the +* Club 3D CAC-1557 TypeC -> DP adapter which for some reason +* filters out short pulses with a duration less than ~540 usec. +* +* The poll period is 50 msec to avoid missing an interrupt +* after the sink has cleared it (after a 110msec timeout +* since it raised the interrupt). +*/ + ret =wait_event_timeout (mgr->tx_waitq, +check_txmsg_state (mgr, txmsg), + mgr->cbs->poll_hpd_irq ? +msecs_to_jiffies (50 ) : + wait_timeout); + +if (ret || !mgr->cbs->poll_hpd_irq || +time_after (jiffies, wait_expires)) +break ; + + mgr->cbs->poll_hpd_irq (mgr); + } +mutex_lock (&mgr->qlock);if (ret >0 ) {if (txmsg->state ==DRM_DP_SIDEBAND_TX_TIMEOUT ) {drivers/gpu/drm/i915/display/intel_dp_mst.c +10
-0@@ -33,6 +33,7 @@#include "intel_connector.h" #include "intel_ddi.h" #include "intel_display_types.h" +#include "intel_hotplug.h" #include "intel_dp.h" #include "intel_dp_mst.h" #include "intel_dpio_phy.h" @@ -765,8 +766,17 @@ static struct drm_connector *intel_dp_add_mst_connector(struct drm_dp_mst_topoloreturn NULL ; } +static void +intel_dp_mst_poll_hpd_irq (struct drm_dp_mst_topology_mgr *mgr) +{ + struct intel_dp *intel_dp = container_of(mgr, struct intel_dp, mst_mgr); + +intel_hpd_trigger_irq (dp_to_dig_port (intel_dp)); +} +static const struct drm_dp_mst_topology_cbs mst_cbs = { .add_connector = intel_dp_add_mst_connector, + .poll_hpd_irq = intel_dp_mst_poll_hpd_irq, }; static struct intel_dp_mst_encoder *drivers/gpu/drm/i915/display/intel_hotplug.c +18
-0@@ -347,6 +347,24 @@ static void i915_digport_work_func(struct work_struct *work) } } +/** +* intel_hpd_trigger_irq - trigger an hpd irq event for a port +* @dig_port: digital port +* +* Trigger an HPD interrupt event for the given port, emulating a short pulse +* generated by the sink, and schedule the dig port work to handle it. +*/ +void intel_hpd_trigger_irq (struct intel_digital_port *dig_port) +{ +struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); + +spin_lock_irq (&i915->irq_lock); + i915->hotplug.short_port_mask |=BIT (dig_port->base.port); +spin_unlock_irq (&i915->irq_lock); + +queue_work (i915->hotplug.dp_wq, &i915->hotplug.dig_port_work); +} +/* * Handle hotplug events outside the interrupt handler proper. */ drivers/gpu/drm/i915/display/intel_hotplug.h +2
-0@@ -10,6 +10,7 @@struct drm_i915_private ;struct intel_connector ; +struct intel_digital_port ;struct intel_encoder ;enum port ;@@ -18,6 +19,7 @@ enum intel_hotplug_state intel_encoder_hotplug(struct intel_encoder *encoder, struct intel_connector *connector);void intel_hpd_irq_handler (struct drm_i915_private *dev_priv,u32 pin_mask,u32 long_mask); +void intel_hpd_trigger_irq (struct intel_digital_port *dig_port);void intel_hpd_init (struct drm_i915_private *dev_priv);void intel_hpd_init_work (struct drm_i915_private *dev_priv);void intel_hpd_cancel_work (struct drm_i915_private *dev_priv);include/drm/drm_dp_mst_helper.h +9
-0@@ -475,6 +475,15 @@ struct drm_dp_mst_topology_mgr;struct drm_dp_mst_topology_cbs {/* create a connector for a port */ struct drm_connector *(*add_connector)(struct drm_dp_mst_topology_mgr *mgr,struct drm_dp_mst_port *port,const char *path); +/* +* Checks for any pending MST interrupts, passing them to MST core for +* processing, the same way an HPD IRQ pulse handler would do this. +* If provided MST core calls this callback from a poll-waiting loop +* when waiting for MST down message replies. The driver is expected +* to guard against a race between this callback and the driver's HPD +* IRQ pulse handler. +*/ +void (*poll_hpd_irq)(struct drm_dp_mst_topology_mgr *mgr); };#define DP_MAX_PAYLOAD (sizeof(unsigned long) * 8)Signature · 6 lines
2.23.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Lyude Paul
Reviewed-byRe: [Intel-gfx] [PATCH v3 3/3] drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses
Hi! Awesome patch series!
Also re merging via drm-intel-next-queued - I think that should be fine, fwiw merging via drm-misc-next might be another option (I've definitely done this in the past for series that touched MST and drivers, but I don't have a hard preference either way).
Quoted 207 lines · Imre Deak
Hi Dave, Lyude,
are you ok to merge this patchset via the drm-intel-next-queued tree?
--Imre
Quoted 200 lines · Imre Deak
Some TypeC -> native DP adapters, at least the Club 3D CAC-1557 adapter, incorrectly filter out HPD short pulses with a duration less than ~540 usec, leading to MST probe failures.
According to the DP Standard 2.0 section 5.1.4:
- DP sinks should generate short pulses in the 500 usec -> 1 msec range
- DP sources should detect short pulses in the 250 usec -> 2 msec rangeAccording to the DP Alt Mode on TypeC Standard section 3.9.2, adapters should detect and forward short pulses according to how sources should detect them as specified in the DP Standard (250 usec -> 2 msec).
Based on the above filtering out short pulses with a duration less than 540 usec is incorrect.
To make such adapters work add support for a driver polling on MST inerrupt flags, and wire this up in the i915 driver. The sink can clear an interrupt it raised after 110 msec if the source doesn't respond, so use a 50 msec poll period to avoid missing an interrupt. Polling of the MST interrupt flags is explicitly allowed by the DP Standard.
This fixes MST probe failures I saw using this adapter and a DELL U2515H monitor.
v2:
- Fix the wait event timeout for the no-poll case.
v3 (Ville):
- Fix the short pulse duration limits in the commit log prescribed by the DP Standard.
- Add code comment explaining why/how polling is used.
- Factor out a helper to schedule the port's hpd irq handler and move it to the rest of hotplug handlers.
- Document the new MST callback.
- s/update_hpd_irq_state/poll_hpd_irq/Cc Ville Syrjälä <[email protected]>Signed-off-by Imre Deak <[email protected]>--- drivers/gpu/drm/drm_dp_mst_topology.c | 32 ++++++++++++++++++-- drivers/gpu/drm/i915/display/intel_dp_mst.c | 10 ++++++ drivers/gpu/drm/i915/display/intel_hotplug.c | 18 +++++++++++ drivers/gpu/drm/i915/display/intel_hotplug.h | 2 ++ include/drm/drm_dp_mst_helper.h | 9 ++++++ 5 files changed, 68 insertions(+), 3 deletions(-)drivers/gpu/drm/drm_dp_mst_topology.c +29
-3@@ -1178,11 +1178,37 @@ static int drm_dp_mst_wait_tx_reply(structdrm_dp_mst_branch *mstb, struct drm_dp_sideband_msg_tx *txmsg) { struct drm_dp_mst_topology_mgr *mgr = mstb->mgr; +unsigned long wait_timeout =msecs_to_jiffies (4000 ); +unsigned long wait_expires = jiffies + wait_timeout;int ret; - ret =wait_event_timeout (mgr->tx_waitq, -check_txmsg_state (mgr, txmsg), - (4 *HZ )); +for (;;) { +/* +* If the driver provides a way for this, change to +* poll-waiting for the MST reply interrupt if we didn't receive +* it for 50 msec. This would cater for cases where the HPD +* pulse signal got lost somewhere, even though the sink raised +* the corresponding MST interrupt correctly. One example is the +* Club 3D CAC-1557 TypeC -> DP adapter which for some reason +* filters out short pulses with a duration less than ~540 usec. +* +* The poll period is 50 msec to avoid missing an interrupt +* after the sink has cleared it (after a 110msec timeout +* since it raised the interrupt). +*/ + ret =wait_event_timeout (mgr->tx_waitq, +check_txmsg_state (mgr, txmsg), + mgr->cbs->poll_hpd_irq ? +msecs_to_jiffies (50 ) : + wait_timeout); + +if (ret || !mgr->cbs->poll_hpd_irq || +time_after (jiffies, wait_expires)) +break ; + + mgr->cbs->poll_hpd_irq (mgr); + } +mutex_lock (&mgr->qlock);if (ret >0 ) {drivers/gpu/drm/drm_dp_mst_topology.c +0
-0if (txmsg->state ==DRM_DP_SIDEBAND_TX_TIMEOUT ) {drivers/gpu/drm/i915/display/intel_dp_mst.c +10
-0@@ -33,6 +33,7 @@#include "intel_connector.h" #include "intel_ddi.h" #include "intel_display_types.h" +#include "intel_hotplug.h" #include "intel_dp.h" #include "intel_dp_mst.h" #include "intel_dpio_phy.h" @@ -765,8 +766,17 @@ static struct drm_connector *intel_dp_add_mst_connector(struct drm_dp_mst_topoloreturn NULL ; } +static void +intel_dp_mst_poll_hpd_irq (struct drm_dp_mst_topology_mgr *mgr) +{ + struct intel_dp *intel_dp = container_of(mgr, struct intel_dp, mst_mgr); + +intel_hpd_trigger_irq (dp_to_dig_port (intel_dp)); +} +static const struct drm_dp_mst_topology_cbs mst_cbs = { .add_connector = intel_dp_add_mst_connector, + .poll_hpd_irq = intel_dp_mst_poll_hpd_irq, };static struct
intel_dp_mst_encoder*drivers/gpu/drm/i915/display/intel_hotplug.c +5
-0@@ -347,6 +347,24 @@ static void i915_digport_work_func(struct work_struct *work) } } +/** +* intel_hpd_trigger_irq - trigger an hpd irq event for a port +* @dig_port: digital port +* +* Trigger an HPD interrupt event for the given port, emulating a short pulse
+ * generated by the sink, and schedule the dig port work to handle it.
+ */drivers/gpu/drm/i915/display/intel_hotplug.c +11
-0+void intel_hpd_trigger_irq (struct intel_digital_port *dig_port) +{ +struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); + +spin_lock_irq (&i915->irq_lock); + i915->hotplug.short_port_mask |=BIT (dig_port->base.port); +spin_unlock_irq (&i915->irq_lock); + +queue_work (i915->hotplug.dp_wq, &i915->hotplug.dig_port_work); +} +/* * Handle hotplug events outside the interrupt handler proper. */ drivers/gpu/drm/i915/display/intel_hotplug.h +2
-0@@ -10,6 +10,7 @@struct drm_i915_private ;struct intel_connector ; +struct intel_digital_port ;struct intel_encoder ;enum port ;@@ -18,6 +19,7 @@ enum intel_hotplug_state intel_encoder_hotplug(structintel_encoder *encoder, struct intel_connector *connector);void intel_hpd_irq_handler (struct drm_i915_private *dev_priv,u32 pin_mask,u32 long_mask); +void intel_hpd_trigger_irq (struct intel_digital_port *dig_port);void intel_hpd_init (struct drm_i915_private *dev_priv);void
intel_hpd_init_work(struct drm_i915_private *dev_priv); voidintel_hpd_cancel_work(struct drm_i915_private *dev_priv);include/drm/drm_dp_mst_helper.h +9
-0@@ -475,6 +475,15 @@ struct drm_dp_mst_topology_mgr;struct drm_dp_mst_topology_cbs {/* create a connector for a port */ struct drm_connector *(*add_connector)(struct drm_dp_mst_topology_mgr *mgr,struct drm_dp_mst_port *port,const char *path); +/* +* Checks for any pending MST interrupts, passing them to MST core for +* processing, the same way an HPD IRQ pulse handler would do this. +* If provided MST core calls this callback from a poll-waiting loop +* when waiting for MST down message replies. The driver is expected +* to guard against a race between this callback and the driver's HPD +* IRQ pulse handler. +*/ +void (*poll_hpd_irq)(struct drm_dp_mst_topology_mgr *mgr); };
Quoted 8 lines
Quoted 8 lines
#define
DP_MAX_PAYLOAD(sizeof(unsigned long) * 8)Signature · 6 lines
2.23.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Intel-gfx] [PATCH v3 3/3] drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses
Quoted 3 lines · Lyude Paul
Hi! Awesome patch series!
Reviewed-by Lyude Paul <[email protected]>
Thanks.
Quoted 4 lines
Also re merging via drm-intel-next-queued - I think that should be fine, fwiw merging via drm-misc-next might be another option (I've definitely done this in the past for series that touched MST and drivers, but I don't have a hard preference either way).
Ok, if no objections I'll merge 2/3 via drm-misc-next, that seems to make more sense.
Could you also take a look at
https://patchwork.freedesktop.org/series/78100/
I should've CC'd you.
Quoted 208 lines · Imre Deak
Quoted 207 lines
Hi Dave, Lyude,
are you ok to merge this patchset via the drm-intel-next-queued tree?
--Imre
Quoted 200 lines · Imre Deak
Some TypeC -> native DP adapters, at least the Club 3D CAC-1557 adapter, incorrectly filter out HPD short pulses with a duration less than ~540 usec, leading to MST probe failures.
According to the DP Standard 2.0 section 5.1.4:
- DP sinks should generate short pulses in the 500 usec -> 1 msec range
- DP sources should detect short pulses in the 250 usec -> 2 msec rangeAccording to the DP Alt Mode on TypeC Standard section 3.9.2, adapters should detect and forward short pulses according to how sources should detect them as specified in the DP Standard (250 usec -> 2 msec).
Based on the above filtering out short pulses with a duration less than 540 usec is incorrect.
To make such adapters work add support for a driver polling on MST inerrupt flags, and wire this up in the i915 driver. The sink can clear an interrupt it raised after 110 msec if the source doesn't respond, so use a 50 msec poll period to avoid missing an interrupt. Polling of the MST interrupt flags is explicitly allowed by the DP Standard.
This fixes MST probe failures I saw using this adapter and a DELL U2515H monitor.
v2:
- Fix the wait event timeout for the no-poll case.
v3 (Ville):
- Fix the short pulse duration limits in the commit log prescribed by the DP Standard.
- Add code comment explaining why/how polling is used.
- Factor out a helper to schedule the port's hpd irq handler and move it to the rest of hotplug handlers.
- Document the new MST callback.
- s/update_hpd_irq_state/poll_hpd_irq/Cc Ville Syrjälä <[email protected]>Signed-off-by Imre Deak <[email protected]>--- drivers/gpu/drm/drm_dp_mst_topology.c | 32 ++++++++++++++++++-- drivers/gpu/drm/i915/display/intel_dp_mst.c | 10 ++++++ drivers/gpu/drm/i915/display/intel_hotplug.c | 18 +++++++++++ drivers/gpu/drm/i915/display/intel_hotplug.h | 2 ++ include/drm/drm_dp_mst_helper.h | 9 ++++++ 5 files changed, 68 insertions(+), 3 deletions(-)drivers/gpu/drm/drm_dp_mst_topology.c +29
-3@@ -1178,11 +1178,37 @@ static int drm_dp_mst_wait_tx_reply(structdrm_dp_mst_branch *mstb, struct drm_dp_sideband_msg_tx *txmsg) { struct drm_dp_mst_topology_mgr *mgr = mstb->mgr; +unsigned long wait_timeout =msecs_to_jiffies (4000 ); +unsigned long wait_expires = jiffies + wait_timeout;int ret; - ret =wait_event_timeout (mgr->tx_waitq, -check_txmsg_state (mgr, txmsg), - (4 *HZ )); +for (;;) { +/* +* If the driver provides a way for this, change to +* poll-waiting for the MST reply interrupt if we didn't receive +* it for 50 msec. This would cater for cases where the HPD +* pulse signal got lost somewhere, even though the sink raised +* the corresponding MST interrupt correctly. One example is the +* Club 3D CAC-1557 TypeC -> DP adapter which for some reason +* filters out short pulses with a duration less than ~540 usec. +* +* The poll period is 50 msec to avoid missing an interrupt +* after the sink has cleared it (after a 110msec timeout +* since it raised the interrupt). +*/ + ret =wait_event_timeout (mgr->tx_waitq, +check_txmsg_state (mgr, txmsg), + mgr->cbs->poll_hpd_irq ? +msecs_to_jiffies (50 ) : + wait_timeout); + +if (ret || !mgr->cbs->poll_hpd_irq || +time_after (jiffies, wait_expires)) +break ; + + mgr->cbs->poll_hpd_irq (mgr); + } +mutex_lock (&mgr->qlock);if (ret >0 ) {drivers/gpu/drm/drm_dp_mst_topology.c +0
-0if (txmsg->state ==DRM_DP_SIDEBAND_TX_TIMEOUT ) {drivers/gpu/drm/i915/display/intel_dp_mst.c +10
-0@@ -33,6 +33,7 @@#include "intel_connector.h" #include "intel_ddi.h" #include "intel_display_types.h" +#include "intel_hotplug.h" #include "intel_dp.h" #include "intel_dp_mst.h" #include "intel_dpio_phy.h" @@ -765,8 +766,17 @@ static struct drm_connector *intel_dp_add_mst_connector(struct drm_dp_mst_topoloreturn NULL ; } +static void +intel_dp_mst_poll_hpd_irq (struct drm_dp_mst_topology_mgr *mgr) +{ + struct intel_dp *intel_dp = container_of(mgr, struct intel_dp, mst_mgr); + +intel_hpd_trigger_irq (dp_to_dig_port (intel_dp)); +} +static const struct drm_dp_mst_topology_cbs mst_cbs = { .add_connector = intel_dp_add_mst_connector, + .poll_hpd_irq = intel_dp_mst_poll_hpd_irq, };static struct
intel_dp_mst_encoder*drivers/gpu/drm/i915/display/intel_hotplug.c +5
-0@@ -347,6 +347,24 @@ static void i915_digport_work_func(struct work_struct *work) } } +/** +* intel_hpd_trigger_irq - trigger an hpd irq event for a port +* @dig_port: digital port +* +* Trigger an HPD interrupt event for the given port, emulating a short pulse
+ * generated by the sink, and schedule the dig port work to handle it.
+ */drivers/gpu/drm/i915/display/intel_hotplug.c +11
-0+void intel_hpd_trigger_irq (struct intel_digital_port *dig_port) +{ +struct drm_i915_private *i915 =to_i915 (dig_port->base.base.dev); + +spin_lock_irq (&i915->irq_lock); + i915->hotplug.short_port_mask |=BIT (dig_port->base.port); +spin_unlock_irq (&i915->irq_lock); + +queue_work (i915->hotplug.dp_wq, &i915->hotplug.dig_port_work); +} +/* * Handle hotplug events outside the interrupt handler proper. */ drivers/gpu/drm/i915/display/intel_hotplug.h +2
-0@@ -10,6 +10,7 @@struct drm_i915_private ;struct intel_connector ; +struct intel_digital_port ;struct intel_encoder ;enum port ;@@ -18,6 +19,7 @@ enum intel_hotplug_state intel_encoder_hotplug(structintel_encoder *encoder, struct intel_connector *connector);void intel_hpd_irq_handler (struct drm_i915_private *dev_priv,u32 pin_mask,u32 long_mask); +void intel_hpd_trigger_irq (struct intel_digital_port *dig_port);void intel_hpd_init (struct drm_i915_private *dev_priv);void
intel_hpd_init_work(struct drm_i915_private *dev_priv); voidintel_hpd_cancel_work(struct drm_i915_private *dev_priv);include/drm/drm_dp_mst_helper.h +9
-0@@ -475,6 +475,15 @@ struct drm_dp_mst_topology_mgr;struct drm_dp_mst_topology_cbs {/* create a connector for a port */ struct drm_connector *(*add_connector)(struct drm_dp_mst_topology_mgr *mgr,struct drm_dp_mst_port *port,const char *path); +/* +* Checks for any pending MST interrupts, passing them to MST core for +* processing, the same way an HPD IRQ pulse handler would do this. +* If provided MST core calls this callback from a poll-waiting loop +* when waiting for MST down message replies. The driver is expected +* to guard against a race between this callback and the driver's HPD +* IRQ pulse handler. +*/ +void (*poll_hpd_irq)(struct drm_dp_mst_topology_mgr *mgr); };
Quoted 9 lines
Quoted 8 lines
Quoted 8 lines
#define
DP_MAX_PAYLOAD(sizeof(unsigned long) * 8)Signature · 6 lines
2.23.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 5 lines · Imre Deak
Currently MST on a port can get enabled/disabled from the hotplug work and get disabled from the short pulse work in a racy way. Fix this by relying on the MST state checking in the hotplug work and just schedule a hotplug work from the short pulse handler if some problem happened during the MST interrupt handling.
Nice
Quoted 9 lines
This removes the explicit MST disabling in case of an AUX failure, but if AUX fails, then probably the detection will also fail during the scheduled hotplug work and it's not guaranteed that we'll see intermittent errors anyway.
While at it also simplify the error checking of the MST interrupt handler.
Quoted 47 lines
Signed-off-by Imre Deak <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 33 +++---------------------- 1 file changed, 4 insertions(+), 29 deletions(-)drivers/gpu/drm/i915/display/intel_dp.c +1
-26@@ -5604,7 +5604,7 @@ intel_dp_check_mst_status(struct intel_dp *intel_dp) } } -return need_retrain; +return need_retrain ? -EINVAL :0 ; } static bool@@ -7255,35 +7255,10 @@ intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) }if (intel_dp->is_mst) { -switch (intel_dp_check_mst_status (intel_dp)) { -case -EINVAL : -/* -* If we were in MST mode, and device is not -* there, get out of MST mode -*/ -drm_dbg_kms (&i915->drm, -"MST device may have disappeared %d vs %d\n" , - intel_dp->is_mst, - intel_dp->mst_mgr.mst_state); - intel_dp->is_mst = false; -drm_dp_mst_topology_mgr_set_mst (&intel_dp->mst_mgr, - intel_dp->is_mst); - -return IRQ_NONE ; -case 1 : -return IRQ_NONE ; -default : -break ; - } - } - -if (!intel_dp->is_mst) { -bool handled; -
drivers/gpu/drm/i915/display/intel_dp.c intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) · line 7264
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_dp.c +3
-3- handled =intel_dp_short_pulse (intel_dp); - -if (!handled) +if (intel_dp_check_mst_status (intel_dp) <0 )return IRQ_NONE ; + }else if (!intel_dp_short_pulse (intel_dp)) { +return IRQ_NONE ; }return IRQ_HANDLED ;
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915/dp_mst: Fix disabling MST on a port
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: series starting with [1/3] drm/i915/dp_mst: Fix disabling MST on a port
URL : https://patchwork.freedesktop.org/series/77969/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip 1fa53eafe47a drm/i915/dp_mst: Fix disabling MST on a port 6474c11029fb drm/dp_mst: Sanitize mgr->qlock locking in drm_dp_mst_wait_tx_reply() 7a10916bbf7e drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses -:13: WARNING:TYPO_SPELLING: 'specificatin' may be misspelled - perhaps 'specification'? #13: specificatin DP sources should detect short pulses in the
total: 0 errors, 1 warnings, 0 checks, 56 lines checked
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915/dp_mst: Fix disabling MST on a port
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: series starting with [1/3] drm/i915/dp_mst: Fix disabling MST on a port
URL : https://patchwork.freedesktop.org/series/77969/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8579 -> Patchwork_17858
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/index.html
Known issues
------------
Here are the changes found in Patchwork_17858 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_cursor_legacy@basic-flip-after-cursor-atomic:
- fi-icl-u2: [PASS][1] -> [DMESG-WARN][2] ([i915#1982])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-icl-u2/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/fi-icl-u2/igt@[email protected]
#### Possible fixes ####
* igt@i915_module_load@reload:
- fi-byt-n2820: [DMESG-WARN][3] ([i915#1982]) -> [PASS][4] +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-byt-n2820/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/fi-byt-n2820/igt@[email protected]
* igt@i915_pm_rpm@basic-pci-d3-state:
- {fi-tgl-dsi}: [DMESG-WARN][5] ([i915#1982]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-tgl-dsi/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/fi-tgl-dsi/igt@[email protected]
- fi-tgl-y: [DMESG-WARN][7] ([i915#1982]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-tgl-y/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/fi-tgl-y/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-bsw-kefka: [DMESG-WARN][9] ([i915#1982]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-bsw-kefka/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/fi-bsw-kefka/igt@[email protected]
* {igt@kms_flip@basic-flip-vs-wf_vblank@b-dvi-d1}:
- fi-bwr-2160: [FAIL][11] ([i915#1928]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-bwr-2160/igt@kms_flip@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/fi-bwr-2160/igt@kms_flip@[email protected]
* {igt@kms_flip@basic-flip-vs-wf_vblank@c-edp1}:
- fi-icl-u2: [DMESG-WARN][13] ([i915#1982]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-icl-u2/igt@kms_flip@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/fi-icl-u2/igt@kms_flip@[email protected]
#### Warnings ####
* igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence:
- fi-kbl-x1275: [DMESG-WARN][15] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][16] ([i915#62] / [i915#92]) +3 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-kbl-x1275/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/fi-kbl-x1275/igt@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-kbl-x1275: [DMESG-WARN][17] ([i915#62] / [i915#92]) -> [DMESG-WARN][18] ([i915#62] / [i915#92] / [i915#95])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-kbl-x1275/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/fi-kbl-x1275/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#1928]: https://gitlab.freedesktop.org/drm/intel/issues/1928
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[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 (51 -> 44)
------------------------------
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-kbl-7560u fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_8579 -> Patchwork_17858
CI-20190529: 20190529
CI_DRM_8579: 289eb12c88c49a4ac8d325dc457d8878c7f5bdc0 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5694: a9b6c4c74bfddf7d3d2da3be08804fe315945cea @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17858: 7a10916bbf7e8b6d18f552c3d6135250da4caa20 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
7a10916bbf7e drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses 6474c11029fb drm/dp_mst: Sanitize mgr->qlock locking in drm_dp_mst_wait_tx_reply() 1fa53eafe47a drm/i915/dp_mst: Fix disabling MST on a port
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev2)
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: series starting with [1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev2)
URL : https://patchwork.freedesktop.org/series/77969/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip 240b4ea78683 drm/i915/dp_mst: Fix disabling MST on a port 36ebc90ef54b drm/dp_mst: Sanitize mgr->qlock locking in drm_dp_mst_wait_tx_reply() 10ec0f0a95d1 drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses -:13: WARNING:TYPO_SPELLING: 'specificatin' may be misspelled - perhaps 'specification'? #13: specificatin DP sources should detect short pulses in the
total: 0 errors, 1 warnings, 0 checks, 57 lines checked
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev2)
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: series starting with [1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev2)
URL : https://patchwork.freedesktop.org/series/77969/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8579 -> Patchwork_17861
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/index.html
Known issues
------------
Here are the changes found in Patchwork_17861 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-bsw-kefka: [PASS][1] -> [DMESG-WARN][2] ([i915#1982])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-bsw-kefka/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/fi-bsw-kefka/igt@[email protected]
* igt@kms_chamelium@hdmi-crc-fast:
- fi-kbl-7500u: [PASS][3] -> [FAIL][4] ([i915#1372])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-kbl-7500u/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/fi-kbl-7500u/igt@[email protected]
* igt@kms_pipe_crc_basic@read-crc-pipe-c:
- fi-tgl-y: [PASS][5] -> [DMESG-WARN][6] ([i915#1982])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-tgl-y/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/fi-tgl-y/igt@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-glk-dsi: [PASS][7] -> [DMESG-WARN][8] ([i915#1982])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-glk-dsi/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/fi-glk-dsi/igt@[email protected]
#### Possible fixes ####
* igt@i915_module_load@reload:
- fi-byt-n2820: [DMESG-WARN][9] ([i915#1982]) -> [PASS][10] +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-byt-n2820/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/fi-byt-n2820/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-tgl-y: [DMESG-WARN][11] ([i915#1982]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-tgl-y/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/fi-tgl-y/igt@[email protected]
- fi-bsw-n3050: [DMESG-WARN][13] ([i915#1982]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-bsw-n3050/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/fi-bsw-n3050/igt@[email protected]
* {igt@kms_flip@basic-flip-vs-wf_vblank@b-dvi-d1}:
- fi-bwr-2160: [FAIL][15] ([i915#1928]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-bwr-2160/igt@kms_flip@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/fi-bwr-2160/igt@kms_flip@[email protected]
#### Warnings ####
* igt@kms_cursor_legacy@basic-flip-after-cursor-legacy:
- fi-kbl-x1275: [DMESG-WARN][17] ([i915#62] / [i915#92]) -> [DMESG-WARN][18] ([i915#62] / [i915#92] / [i915#95]) +2 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-kbl-x1275/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/fi-kbl-x1275/igt@[email protected]
* igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a-frame-sequence:
- fi-kbl-x1275: [DMESG-WARN][19] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][20] ([i915#62] / [i915#92]) +2 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/fi-kbl-x1275/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/fi-kbl-x1275/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#1372]: https://gitlab.freedesktop.org/drm/intel/issues/1372
[i915#1928]: https://gitlab.freedesktop.org/drm/intel/issues/1928
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[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 (51 -> 44)
------------------------------
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-kbl-7560u fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_8579 -> Patchwork_17861
CI-20190529: 20190529
CI_DRM_8579: 289eb12c88c49a4ac8d325dc457d8878c7f5bdc0 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5694: a9b6c4c74bfddf7d3d2da3be08804fe315945cea @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17861: 10ec0f0a95d1ed7b600df217f021788844964bc8 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
10ec0f0a95d1 drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses 36ebc90ef54b drm/dp_mst: Sanitize mgr->qlock locking in drm_dp_mst_wait_tx_reply() 240b4ea78683 drm/i915/dp_mst: Fix disabling MST on a port
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/3] drm/i915/dp_mst: Fix disabling MST on a port
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: series starting with [1/3] drm/i915/dp_mst: Fix disabling MST on a port
URL : https://patchwork.freedesktop.org/series/77969/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8579_full -> Patchwork_17858_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_17858_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_reloc@basic-write-gtt-active:
- shard-tglb: [PASS][1] -> [DMESG-WARN][2] ([i915#402])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-tglb6/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-tglb7/igt@[email protected]
* igt@gem_sync@basic-all:
- shard-glk: [PASS][3] -> [DMESG-WARN][4] ([i915#118] / [i915#95])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-glk6/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-glk4/igt@[email protected]
* igt@gem_tiled_partial_pwrite_pread@writes-after-reads:
- shard-apl: [PASS][5] -> [DMESG-WARN][6] ([i915#95]) +19 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl2/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-apl3/igt@[email protected]
* igt@i915_suspend@debugfs-reader:
- shard-skl: [PASS][7] -> [INCOMPLETE][8] ([i915#69])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl6/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-skl6/igt@[email protected]
* igt@kms_big_fb@x-tiled-32bpp-rotate-180:
- shard-skl: [PASS][9] -> [DMESG-WARN][10] ([i915#1982]) +10 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl1/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-skl2/igt@[email protected]
* igt@kms_big_fb@y-tiled-32bpp-rotate-90:
- shard-apl: [PASS][11] -> [DMESG-WARN][12] ([i915#1982]) +2 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl4/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-apl1/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-suspend:
- shard-apl: [PASS][13] -> [DMESG-WARN][14] ([i915#180])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl1/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-apl1/igt@[email protected]
* igt@kms_cursor_legacy@cursorb-vs-flipa-toggle:
- shard-glk: [PASS][15] -> [DMESG-FAIL][16] ([i915#1925] / [i915#1926])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-glk9/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-glk6/igt@[email protected]
* igt@kms_cursor_legacy@pipe-b-torture-move:
- shard-iclb: [PASS][17] -> [DMESG-WARN][18] ([i915#128])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-iclb1/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-iclb4/igt@[email protected]
* igt@kms_flip_tiling@flip-yf-tiled:
- shard-skl: [PASS][19] -> [FAIL][20] ([fdo#108145])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl7/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-skl5/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-wc:
- shard-snb: [PASS][21] -> [SKIP][22] ([fdo#109271])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-snb1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-wc.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-snb6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-wc:
- shard-iclb: [PASS][23] -> [DMESG-WARN][24] ([i915#1982])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-iclb8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-wc.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-iclb5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@fbc-badstride:
- shard-glk: [PASS][25] -> [DMESG-WARN][26] ([i915#1982]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-glk4/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-glk5/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-move:
- shard-tglb: [PASS][27] -> [DMESG-WARN][28] ([i915#1982]) +1 similar issue
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-tglb5/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-tglb3/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-cpu:
- shard-skl: [PASS][29] -> [FAIL][30] ([i915#49])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl7/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-cpu.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-skl5/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-cpu.html
* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [PASS][31] -> [FAIL][32] ([i915#1188]) +1 similar issue
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl9/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-skl8/igt@[email protected]
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes:
- shard-kbl: [PASS][33] -> [DMESG-WARN][34] ([i915#180]) +2 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-kbl4/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-kbl7/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:
- shard-skl: [PASS][35] -> [FAIL][36] ([fdo#108145] / [i915#265]) +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl7/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-skl5/igt@[email protected]
* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [PASS][37] -> [SKIP][38] ([fdo#109441]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-iclb8/igt@kms_psr@psr2_primary_page_flip.html
* igt@kms_setmode@basic:
- shard-apl: [PASS][39] -> [FAIL][40] ([i915#31])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl6/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-apl3/igt@[email protected]
* igt@syncobj_wait@single-wait-all-signaled:
- shard-kbl: [PASS][41] -> [DMESG-WARN][42] ([i915#93] / [i915#95]) +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-kbl7/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-kbl4/igt@[email protected]
#### Possible fixes ####
* igt@gem_exec_whisper@basic-contexts-forked-all:
- shard-glk: [DMESG-WARN][43] ([i915#118] / [i915#95]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-glk7/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-glk9/igt@[email protected]
* igt@gem_workarounds@suspend-resume-context:
- shard-apl: [DMESG-WARN][45] ([i915#180]) -> [PASS][46] +2 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl6/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-apl7/igt@[email protected]
* igt@kms_big_fb@y-tiled-8bpp-rotate-0:
- shard-apl: [DMESG-WARN][47] ([i915#1982]) -> [PASS][48] +1 similar issue
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl2/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-apl3/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-256x256-onscreen:
- shard-tglb: [DMESG-WARN][49] ([i915#402]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-tglb2/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-tglb8/igt@[email protected]
* igt@kms_cursor_edge_walk@pipe-a-64x64-top-edge:
- shard-apl: [DMESG-WARN][51] ([i915#95]) -> [PASS][52] +8 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl1/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-apl2/igt@[email protected]
* {igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1}:
- shard-skl: [FAIL][53] ([i915#46]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl5/igt@kms_flip@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-skl2/igt@kms_flip@[email protected]
* {igt@kms_flip@plain-flip-fb-recreate-interruptible@a-dp1}:
- shard-kbl: [DMESG-WARN][55] ([i915#1982]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-kbl1/igt@kms_flip@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-kbl2/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [DMESG-WARN][57] ([i915#93] / [i915#95]) -> [PASS][58] +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-kbl2/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-kbl1/igt@[email protected]
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes:
- shard-skl: [INCOMPLETE][59] ([i915#69]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl8/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-skl9/igt@[email protected]
* igt@kms_plane@plane-position-hole-pipe-a-planes:
- shard-skl: [DMESG-WARN][61] ([i915#1982]) -> [PASS][62] +10 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl4/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-skl4/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [FAIL][63] ([fdo#108145] / [i915#265]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl2/igt@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-skl8/igt@[email protected]
* igt@kms_plane_scaling@pipe-a-scaler-with-clipping-clamping:
- shard-iclb: [DMESG-WARN][65] ([i915#1982]) -> [PASS][66] +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-iclb3/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-iclb3/igt@[email protected]
* igt@kms_psr2_su@page_flip:
- shard-iclb: [SKIP][67] ([fdo#109642] / [fdo#111068]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-iclb1/igt@kms_psr2_su@page_flip.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-iclb2/igt@kms_psr2_su@page_flip.html
* igt@kms_psr@psr2_cursor_mmap_gtt:
- shard-iclb: [SKIP][69] ([fdo#109441]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-iclb6/igt@kms_psr@psr2_cursor_mmap_gtt.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_gtt.html
* igt@kms_setmode@basic:
- shard-skl: [FAIL][71] ([i915#31]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl8/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-skl5/igt@[email protected]
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-kbl: [DMESG-WARN][73] ([i915#180]) -> [PASS][74] +5 similar issues
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-kbl3/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-kbl6/igt@[email protected]
* {igt@perf@blocking-parameterized}:
- shard-tglb: [FAIL][75] ([i915#1542]) -> [PASS][76]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-tglb7/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-tglb2/igt@[email protected]
#### Warnings ####
* igt@kms_content_protection@atomic:
- shard-apl: [TIMEOUT][77] ([i915#1319] / [i915#1635]) -> [TIMEOUT][78] ([i915#1319])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl6/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-apl2/igt@[email protected]
* igt@kms_content_protection@atomic-dpms:
- shard-apl: [TIMEOUT][79] ([i915#1319]) -> [TIMEOUT][80] ([i915#1319] / [i915#1635])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl1/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-apl4/igt@[email protected]
* igt@kms_content_protection@legacy:
- shard-apl: [TIMEOUT][81] ([i915#1319] / [i915#1635]) -> [FAIL][82] ([fdo#110321] / [fdo#110336])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl3/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-apl6/igt@[email protected]
* igt@kms_content_protection@srm:
- shard-apl: [FAIL][83] ([fdo#110321]) -> [TIMEOUT][84] ([i915#1319] / [i915#1635])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl2/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-apl4/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc:
- shard-tglb: [DMESG-WARN][85] ([i915#1982]) -> [DMESG-WARN][86] ([i915#1982] / [i915#402])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-tglb7/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-tglb7/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-mmap-cpu:
- shard-apl: [DMESG-FAIL][87] ([i915#49] / [i915#95]) -> [FAIL][88] ([i915#49])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-mmap-cpu.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/shard-apl4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-mmap-cpu.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#128]: https://gitlab.freedesktop.org/drm/intel/issues/128
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1925]: https://gitlab.freedesktop.org/drm/intel/issues/1925
[i915#1926]: https://gitlab.freedesktop.org/drm/intel/issues/1926
[i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#46]: https://gitlab.freedesktop.org/drm/intel/issues/46
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58
[i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_8579 -> Patchwork_17858
CI-20190529: 20190529
CI_DRM_8579: 289eb12c88c49a4ac8d325dc457d8878c7f5bdc0 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5694: a9b6c4c74bfddf7d3d2da3be08804fe315945cea @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17858: 7a10916bbf7e8b6d18f552c3d6135250da4caa20 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17858/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev2)
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: series starting with [1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev2)
URL : https://patchwork.freedesktop.org/series/77969/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8579_full -> Patchwork_17861_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_17861_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_tiled_partial_pwrite_pread@writes-after-reads:
- shard-apl: [PASS][1] -> [DMESG-WARN][2] ([i915#95]) +16 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl2/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-apl3/igt@[email protected]
* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-apl: [PASS][3] -> [DMESG-WARN][4] ([i915#180]) +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl1/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-apl6/igt@[email protected]
* igt@kms_color@pipe-c-ctm-0-25:
- shard-skl: [PASS][5] -> [DMESG-WARN][6] ([i915#1982]) +9 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl4/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-skl2/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-size-change:
- shard-skl: [PASS][7] -> [FAIL][8] ([i915#54])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl2/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-skl1/igt@[email protected]
* igt@kms_cursor_legacy@cursorb-vs-flipa-toggle:
- shard-glk: [PASS][9] -> [DMESG-FAIL][10] ([i915#1925] / [i915#1926])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-glk9/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-glk7/igt@[email protected]
* igt@kms_flip_tiling@flip-yf-tiled:
- shard-skl: [PASS][11] -> [FAIL][12] ([fdo#108145])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl7/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-skl7/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-badstride:
- shard-glk: [PASS][13] -> [DMESG-WARN][14] ([i915#1982])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-glk4/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-glk5/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-cpu:
- shard-skl: [PASS][15] -> [FAIL][16] ([i915#49])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl7/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-cpu.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-skl7/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-cpu.html
* igt@kms_pipe_crc_basic@read-crc-pipe-c-frame-sequence:
- shard-skl: [PASS][17] -> [FAIL][18] ([i915#53])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl2/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-skl1/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:
- shard-skl: [PASS][19] -> [FAIL][20] ([fdo#108145] / [i915#265])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl7/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-skl7/igt@[email protected]
* igt@kms_setmode@basic:
- shard-apl: [PASS][21] -> [FAIL][22] ([i915#31])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl6/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-apl8/igt@[email protected]
* igt@syncobj_wait@single-wait-all-signaled:
- shard-kbl: [PASS][23] -> [DMESG-WARN][24] ([i915#93] / [i915#95]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-kbl7/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-kbl7/igt@[email protected]
#### Possible fixes ####
* {igt@gem_ctx_isolation@preservation-s3@bcs0}:
- shard-kbl: [FAIL][25] ([fdo#103375]) -> [PASS][26]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-kbl6/igt@gem_ctx_isolation@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-kbl6/igt@gem_ctx_isolation@[email protected]
* {igt@gem_ctx_isolation@preservation-s3@vcs0}:
- shard-kbl: [INCOMPLETE][27] ([i915#1780]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-kbl6/igt@gem_ctx_isolation@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-kbl6/igt@gem_ctx_isolation@[email protected]
* {igt@gem_exec_reloc@basic-concurrent0}:
- shard-glk: [FAIL][29] ([i915#1930]) -> [PASS][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-glk4/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-glk5/igt@[email protected]
* {igt@gem_exec_schedule@implicit-write-read@rcs0}:
- shard-snb: [INCOMPLETE][31] ([i915#82]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-snb5/igt@gem_exec_schedule@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-snb4/igt@gem_exec_schedule@[email protected]
* igt@gem_exec_whisper@basic-contexts-forked-all:
- shard-glk: [DMESG-WARN][33] ([i915#118] / [i915#95]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-glk7/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-glk2/igt@[email protected]
* igt@gem_workarounds@suspend-resume-context:
- shard-apl: [DMESG-WARN][35] ([i915#180]) -> [PASS][36] +2 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl6/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-apl3/igt@[email protected]
* igt@i915_suspend@sysfs-reader:
- shard-apl: [TIMEOUT][37] ([i915#1635]) -> [PASS][38] +2 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl4/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-apl7/igt@[email protected]
* igt@kms_big_fb@y-tiled-8bpp-rotate-0:
- shard-apl: [DMESG-WARN][39] ([i915#1982]) -> [PASS][40] +1 similar issue
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl2/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-apl3/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-256x256-onscreen:
- shard-tglb: [DMESG-WARN][41] ([i915#402]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-tglb2/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-tglb1/igt@[email protected]
* {igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1}:
- shard-skl: [FAIL][43] ([i915#46]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl5/igt@kms_flip@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-skl5/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc:
- shard-kbl: [DMESG-WARN][45] ([i915#93] / [i915#95]) -> [PASS][46] +1 similar issue
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-kbl3/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc.html
- shard-tglb: [DMESG-WARN][47] ([i915#1982]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-tglb7/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-tglb3/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-shrfb-draw-mmap-wc.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes:
- shard-skl: [INCOMPLETE][49] ([i915#69]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl8/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-skl4/igt@[email protected]
* igt@kms_plane@plane-position-hole-pipe-a-planes:
- shard-skl: [DMESG-WARN][51] ([i915#1982]) -> [PASS][52] +8 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-skl4/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-skl2/igt@[email protected]
* igt@kms_plane_scaling@pipe-a-scaler-with-clipping-clamping:
- shard-iclb: [DMESG-WARN][53] ([i915#1982]) -> [PASS][54] +1 similar issue
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-iclb3/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-iclb5/igt@[email protected]
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-kbl: [DMESG-WARN][55] ([i915#180]) -> [PASS][56] +5 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-kbl3/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-kbl4/igt@[email protected]
* {igt@perf@blocking-parameterized}:
- shard-tglb: [FAIL][57] ([i915#1542]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-tglb7/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-tglb7/igt@[email protected]
* igt@vgem_basic@dmabuf-mmap:
- shard-apl: [DMESG-WARN][59] ([i915#95]) -> [PASS][60] +6 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl2/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-apl3/igt@[email protected]
#### Warnings ####
* igt@gem_ctx_bad_destroy@invalid-pad:
- shard-apl: [TIMEOUT][61] ([i915#1635]) -> [DMESG-WARN][62] ([i915#95])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl4/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-apl7/igt@[email protected]
* igt@i915_pm_dc@dc6-dpms:
- shard-tglb: [FAIL][63] ([i915#454]) -> [SKIP][64] ([i915#468])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-tglb5/igt@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-tglb2/igt@[email protected]
* igt@i915_pm_rpm@sysfs-read:
- shard-snb: [SKIP][65] ([fdo#109271]) -> [INCOMPLETE][66] ([i915#82])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-snb4/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-snb4/igt@[email protected]
* igt@kms_content_protection@atomic:
- shard-apl: [TIMEOUT][67] ([i915#1319] / [i915#1635]) -> [TIMEOUT][68] ([i915#1319])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl6/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-apl8/igt@[email protected]
* igt@kms_content_protection@atomic-dpms:
- shard-apl: [TIMEOUT][69] ([i915#1319]) -> [TIMEOUT][70] ([i915#1319] / [i915#1635])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl1/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-apl6/igt@[email protected]
* igt@kms_content_protection@srm:
- shard-apl: [FAIL][71] ([fdo#110321]) -> [TIMEOUT][72] ([i915#1319] / [i915#1635])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl2/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-apl8/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [DMESG-WARN][73] ([i915#93] / [i915#95]) -> [DMESG-WARN][74] ([i915#180] / [i915#93] / [i915#95])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-kbl2/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-kbl3/igt@[email protected]
* igt@kms_vblank@pipe-d-query-idle-hang:
- shard-apl: [TIMEOUT][75] ([i915#1635] / [i915#1640]) -> [SKIP][76] ([fdo#109271])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8579/shard-apl4/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/shard-apl7/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#1640]: https://gitlab.freedesktop.org/drm/intel/issues/1640
[i915#1780]: https://gitlab.freedesktop.org/drm/intel/issues/1780
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1925]: https://gitlab.freedesktop.org/drm/intel/issues/1925
[i915#1926]: https://gitlab.freedesktop.org/drm/intel/issues/1926
[i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930
[i915#198]: https://gitlab.freedesktop.org/drm/intel/issues/198
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#46]: https://gitlab.freedesktop.org/drm/intel/issues/46
[i915#468]: https://gitlab.freedesktop.org/drm/intel/issues/468
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#53]: https://gitlab.freedesktop.org/drm/intel/issues/53
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_8579 -> Patchwork_17861
CI-20190529: 20190529
CI_DRM_8579: 289eb12c88c49a4ac8d325dc457d8878c7f5bdc0 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5694: a9b6c4c74bfddf7d3d2da3be08804fe315945cea @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17861: 10ec0f0a95d1ed7b600df217f021788844964bc8 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17861/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 56 lines · Imre Deak
Currently MST on a port can get enabled/disabled from the hotplug work and get disabled from the short pulse work in a racy way. Fix this by relying on the MST state checking in the hotplug work and just schedule a hotplug work from the short pulse handler if some problem happened during the MST interrupt handling.
This removes the explicit MST disabling in case of an AUX failure, but if AUX fails, then probably the detection will also fail during the scheduled hotplug work and it's not guaranteed that we'll see intermittent errors anyway.
While at it also simplify the error checking of the MST interrupt handler.
Signed-off-by Imre Deak <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 33 +++---------------------- 1 file changed, 4 insertions(+), 29 deletions(-)drivers/gpu/drm/i915/display/intel_dp.c +1
-21@@ -5604,7 +5604,7 @@ intel_dp_check_mst_status(struct intel_dp *intel_dp) } } -return need_retrain; +return need_retrain ? -EINVAL :0 ; } static bool@@ -7255,35 +7255,10 @@ intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) }if (intel_dp->is_mst) { -switch (intel_dp_check_mst_status (intel_dp)) { -case -EINVAL : -/* -* If we were in MST mode, and device is not -* there, get out of MST mode -*/ -drm_dbg_kms (&i915->drm, -"MST device may have disappeared %d vs %d\n" , - intel_dp->is_mst, - intel_dp->mst_mgr.mst_state); - intel_dp->is_mst = false; -drm_dp_mst_topology_mgr_set_mst (&intel_dp->mst_mgr, - intel_dp->is_mst); - -return IRQ_NONE ; -case 1 : -return IRQ_NONE ; -default : -break ; - }
drivers/gpu/drm/i915/display/intel_dp.c intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) · line 7259
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_dp.c +1
-8- } - -if (!intel_dp->is_mst) { -bool handled; - - handled =intel_dp_short_pulse (intel_dp); - -if (!handled) +if (intel_dp_check_mst_status (intel_dp) <0 )return IRQ_NONE ;
Since we no longer need the tristate return, can you follow up with a conversion to bool return? I'd vote to make it match the semantics of intel_dp_short_pulse() so we get one step closer to unifying the hpd_irq handling across the board.
Quoted 12 lines
drivers/gpu/drm/i915/display/intel_dp.c +2
-0+ }else if (!intel_dp_short_pulse (intel_dp)) { +return IRQ_NONE ; }return IRQ_HANDLED ;Signature · 6 lines
2.23.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 6 lines
Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 64 lines · Ville Syrjälä
Quoted 63 lines · Imre Deak
Currently MST on a port can get enabled/disabled from the hotplug work and get disabled from the short pulse work in a racy way. Fix this by relying on the MST state checking in the hotplug work and just schedule a hotplug work from the short pulse handler if some problem happened during the MST interrupt handling.
This removes the explicit MST disabling in case of an AUX failure, but if AUX fails, then probably the detection will also fail during the scheduled hotplug work and it's not guaranteed that we'll see intermittent errors anyway.
While at it also simplify the error checking of the MST interrupt handler.
Signed-off-by Imre Deak <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 33 +++---------------------- 1 file changed, 4 insertions(+), 29 deletions(-)drivers/gpu/drm/i915/display/intel_dp.c +1
-28@@ -5604,7 +5604,7 @@ intel_dp_check_mst_status(struct intel_dp *intel_dp) } } -return need_retrain; +return need_retrain ? -EINVAL :0 ; } static bool@@ -7255,35 +7255,10 @@ intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) }if (intel_dp->is_mst) { -switch (intel_dp_check_mst_status (intel_dp)) { -case -EINVAL : -/* -* If we were in MST mode, and device is not -* there, get out of MST mode -*/ -drm_dbg_kms (&i915->drm, -"MST device may have disappeared %d vs %d\n" , - intel_dp->is_mst, - intel_dp->mst_mgr.mst_state); - intel_dp->is_mst = false; -drm_dp_mst_topology_mgr_set_mst (&intel_dp->mst_mgr, - intel_dp->is_mst); - -return IRQ_NONE ; -case 1 : -return IRQ_NONE ; -default : -break ; - } - } - -if (!intel_dp->is_mst) { -bool handled; - - handled =intel_dp_short_pulse (intel_dp); -
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_dp.c intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) · line 7259
Quoted 3 lines
drivers/gpu/drm/i915/display/intel_dp.c +1
-1-if (!handled) +if (intel_dp_check_mst_status (intel_dp) <0 )return IRQ_NONE ;Since we no longer need the tristate return, can you follow up with a conversion to bool return? I'd vote to make it match the semantics of
intel_dp_short_pulse()so we get one step closer to unifying thehpd_irqhandling across the board.
Ok, makes sense.
Quoted 5 lines
Quoted 5 lines
drivers/gpu/drm/i915/display/intel_dp.c +2
-0+ }else if (!intel_dp_short_pulse (intel_dp)) { +return IRQ_NONE ; }
Quoted 12 lines
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_dp.c +0
-0return IRQ_HANDLED ;Signature · 6 lines
2.23.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfxSignature · 2 lines
Ville Syrjälä Intel
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v2 1/3 drm/i915/dp_mst: Fix disabling MST on a port
In reply to Imre DeakCurrently MST on a port can get enabled/disabled from the hotplug work and get disabled from the short pulse work in a racy way. Fix this by relying on the MST state checking in the hotplug work and just schedule a hotplug work from the short pulse handler if some problem happened during the MST interrupt handling.
This removes the explicit MST disabling in case of an AUX failure, but if AUX fails, then probably the detection will also fail during the scheduled hotplug work and it's not guaranteed that we'll see intermittent errors anyway.
While at it also simplify the error checking of the MST interrupt handler.
v2:
- Convert intel_dp_check_mst_status() to return bool. (Ville)
- Change the intel_dp->is_mst check to an assert, since after this patch the condition can't change after we checked it previously.
- Document the return value from intel_dp_check_mst_status().
--- drivers/gpu/drm/i915/display/intel_dp.c | 67 ++++++++++--------------- 1 file changed, 27 insertions(+), 40 deletions(-)
drivers/gpu/drm/i915/display/intel_dp.c +27 -40
@@ -5556,35 +5556,47 @@ static void intel_dp_handle_test_request(struct intel_dp *intel_dp) "Could not write test response to sink\n"); } -static int +/** +* intel_dp_check_mst_status - service any pending MST interrupts, check link status +* @intel_dp: Intel DP struct +* +* Read any pending MST interrupts, call MST core to handle these and ack the +* interrupts. Check if the main and AUX link state is ok. +* +* Returns: +* - %true if pending interrupts were serviced (or no interrupts were +* pending) w/o detecting an error condition. +* - %false if an error condition - like AUX failure or a loss of link - is +* detected, which needs servicing from the hotplug work. +*/ +static bool intel_dp_check_mst_status (struct intel_dp *intel_dp) {struct drm_i915_private *i915 =dp_to_i915 (intel_dp); -bool need_retrain = false; - -if (!intel_dp->is_mst) -return -EINVAL ; +bool link_ok = true; +drm_WARN_ON_ONCE (&i915->drm, !intel_dp->is_mst);drm_WARN_ON_ONCE (&i915->drm, intel_dp->active_mst_links <0 );for (;;) {u8 esi[DP_DPRX_ESI_LEN ] = {}; -bool bret, handled; +bool handled;int retry; - bret =intel_dp_get_sink_irq_esi (intel_dp, esi); -if (!bret) { +if (!intel_dp_get_sink_irq_esi (intel_dp, esi)) {drm_dbg_kms (&i915->drm,"failed to get ESI - device may have failed\n" ); -return -EINVAL ; + link_ok = false; + +break ; }/* check link status - esi[10] = 0x200c */ -if (intel_dp->active_mst_links >0 && !need_retrain && +if (intel_dp->active_mst_links >0 && link_ok && !drm_dp_channel_eq_ok (&esi[10 ], intel_dp->lane_count)) {drm_dbg_kms (&i915->drm,"channel EQ not ok, retraining\n" ); - need_retrain = true; + link_ok = false; }drm_dbg_kms (&i915->drm,"got esi %3ph\n" , esi);
@@ -5604,7 +5616,7 @@ intel_dp_check_mst_status(struct intel_dp *intel_dp) } } -return need_retrain; +return link_ok; } static bool
@@ -7255,35 +7267,10 @@ intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) }if (intel_dp->is_mst) { -switch (intel_dp_check_mst_status (intel_dp)) { -case -EINVAL : -/* -* If we were in MST mode, and device is not -* there, get out of MST mode -*/ -drm_dbg_kms (&i915->drm, -"MST device may have disappeared %d vs %d\n" , - intel_dp->is_mst, - intel_dp->mst_mgr.mst_state); - intel_dp->is_mst = false; -drm_dp_mst_topology_mgr_set_mst (&intel_dp->mst_mgr, - intel_dp->is_mst); - -return IRQ_NONE ; -case 1 : -return IRQ_NONE ; -default : -break ; - } - } - -if (!intel_dp->is_mst) { -bool handled; - - handled =intel_dp_short_pulse (intel_dp); - -if (!handled) +if (!intel_dp_check_mst_status (intel_dp))return IRQ_NONE ; + }else if (!intel_dp_short_pulse (intel_dp)) { +return IRQ_NONE ; }return IRQ_HANDLED ;
Signature · 6 lines
2.23.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH v3 1/3 drm/i915/dp_mst: Fix disabling MST on a port
Currently MST on a port can get enabled/disabled from the hotplug work and get disabled from the short pulse work in a racy way. Fix this by relying on the MST state checking in the hotplug work and just schedule a hotplug work from the short pulse handler if some problem happened during the MST interrupt handling.
This removes the explicit MST disabling in case of an AUX failure, but if AUX fails, then probably the detection will also fail during the scheduled hotplug work and it's not guaranteed that we'll see intermittent errors anyway.
While at it also simplify the error checking of the MST interrupt handler.
v2:
- Convert intel_dp_check_mst_status() to return bool. (Ville)
- Change the intel_dp->is_mst check to an assert, since after this patch the condition can't change after we checked it previously.
- Document the return value from intel_dp_check_mst_status(). v3:
- Remove the intel_dp->is_mst check from intel_dp_check_mst_status(). There is no point in checking the same condition twice, even though there is a chance that the hotplug work running concurrently changes it.
--- drivers/gpu/drm/i915/display/intel_dp.c | 66 ++++++++++--------------- 1 file changed, 26 insertions(+), 40 deletions(-)
drivers/gpu/drm/i915/display/intel_dp.c +26 -40
@@ -5556,14 +5556,24 @@ static void intel_dp_handle_test_request(struct intel_dp *intel_dp) "Could not write test response to sink\n"); } -static int +/** +* intel_dp_check_mst_status - service any pending MST interrupts, check link status +* @intel_dp: Intel DP struct +* +* Read any pending MST interrupts, call MST core to handle these and ack the +* interrupts. Check if the main and AUX link state is ok. +* +* Returns: +* - %true if pending interrupts were serviced (or no interrupts were +* pending) w/o detecting an error condition. +* - %false if an error condition - like AUX failure or a loss of link - is +* detected, which needs servicing from the hotplug work. +*/ +static bool intel_dp_check_mst_status (struct intel_dp *intel_dp) {struct drm_i915_private *i915 =dp_to_i915 (intel_dp); -bool need_retrain = false; - -if (!intel_dp->is_mst) -return -EINVAL ; +bool link_ok = true;drm_WARN_ON_ONCE (&i915->drm, intel_dp->active_mst_links <0 );
@@ -5591,22 +5601,23 @@ intel_dp_check_mst_status(struct intel_dp *intel_dp)for (;;) {u8 esi[DP_DPRX_ESI_LEN ] = {}; -bool bret, handled; +bool handled;int retry; - bret =intel_dp_get_sink_irq_esi (intel_dp, esi); -if (!bret) { +if (!intel_dp_get_sink_irq_esi (intel_dp, esi)) {drm_dbg_kms (&i915->drm,"failed to get ESI - device may have failed\n" ); -return -EINVAL ; + link_ok = false; + +break ; }/* check link status - esi[10] = 0x200c */ -if (intel_dp->active_mst_links >0 && !need_retrain && +if (intel_dp->active_mst_links >0 && link_ok && !drm_dp_channel_eq_ok (&esi[10 ], intel_dp->lane_count)) {drm_dbg_kms (&i915->drm,"channel EQ not ok, retraining\n" ); - need_retrain = true; + link_ok = false; }drm_dbg_kms (&i915->drm,"got esi %3ph\n" , esi);
@@ -5626,7 +5637,7 @@ intel_dp_check_mst_status(struct intel_dp *intel_dp) } } -return need_retrain; +return link_ok; } static bool
@@ -7277,35 +7288,10 @@ intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) }if (intel_dp->is_mst) { -switch (intel_dp_check_mst_status (intel_dp)) { -case -EINVAL : -/* -* If we were in MST mode, and device is not -* there, get out of MST mode -*/ -drm_dbg_kms (&i915->drm, -"MST device may have disappeared %d vs %d\n" , - intel_dp->is_mst, - intel_dp->mst_mgr.mst_state); - intel_dp->is_mst = false; -drm_dp_mst_topology_mgr_set_mst (&intel_dp->mst_mgr, - intel_dp->is_mst); - -return IRQ_NONE ; -case 1 : -return IRQ_NONE ; -default : -break ; - } - } - -if (!intel_dp->is_mst) { -bool handled; - - handled =intel_dp_short_pulse (intel_dp); - -if (!handled) +if (!intel_dp_check_mst_status (intel_dp))return IRQ_NONE ; + }else if (!intel_dp_short_pulse (intel_dp)) { +return IRQ_NONE ; }return IRQ_HANDLED ;
Signature · 6 lines
2.23.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH RESEND v3 1/3 drm/i915/dp_mst: Fix disabling MST on a port
In reply to Imre DeakCurrently MST on a port can get enabled/disabled from the hotplug work and get disabled from the short pulse work in a racy way. Fix this by relying on the MST state checking in the hotplug work and just schedule a hotplug work from the short pulse handler if some problem happened during the MST interrupt handling.
This removes the explicit MST disabling in case of an AUX failure, but if AUX fails, then probably the detection will also fail during the scheduled hotplug work and it's not guaranteed that we'll see intermittent errors anyway.
While at it also simplify the error checking of the MST interrupt handler.
v2:
- Convert intel_dp_check_mst_status() to return bool. (Ville)
- Change the intel_dp->is_mst check to an assert, since after this patch the condition can't change after we checked it previously.
- Document the return value from intel_dp_check_mst_status(). v3:
- Remove the intel_dp->is_mst check from intel_dp_check_mst_status(). There is no point in checking the same condition twice, even though there is a chance that the hotplug work running concurrently changes it.
--- drivers/gpu/drm/i915/display/intel_dp.c | 66 ++++++++++--------------- 1 file changed, 26 insertions(+), 40 deletions(-)
drivers/gpu/drm/i915/display/intel_dp.c +26 -40
@@ -5556,35 +5556,46 @@ static void intel_dp_handle_test_request(struct intel_dp *intel_dp) "Could not write test response to sink\n"); } -static int +/** +* intel_dp_check_mst_status - service any pending MST interrupts, check link status +* @intel_dp: Intel DP struct +* +* Read any pending MST interrupts, call MST core to handle these and ack the +* interrupts. Check if the main and AUX link state is ok. +* +* Returns: +* - %true if pending interrupts were serviced (or no interrupts were +* pending) w/o detecting an error condition. +* - %false if an error condition - like AUX failure or a loss of link - is +* detected, which needs servicing from the hotplug work. +*/ +static bool intel_dp_check_mst_status (struct intel_dp *intel_dp) {struct drm_i915_private *i915 =dp_to_i915 (intel_dp); -bool need_retrain = false; - -if (!intel_dp->is_mst) -return -EINVAL ; +bool link_ok = true;drm_WARN_ON_ONCE (&i915->drm, intel_dp->active_mst_links <0 );for (;;) {u8 esi[DP_DPRX_ESI_LEN ] = {}; -bool bret, handled; +bool handled;int retry; - bret =intel_dp_get_sink_irq_esi (intel_dp, esi); -if (!bret) { +if (!intel_dp_get_sink_irq_esi (intel_dp, esi)) {drm_dbg_kms (&i915->drm,"failed to get ESI - device may have failed\n" ); -return -EINVAL ; + link_ok = false; + +break ; }/* check link status - esi[10] = 0x200c */ -if (intel_dp->active_mst_links >0 && !need_retrain && +if (intel_dp->active_mst_links >0 && link_ok && !drm_dp_channel_eq_ok (&esi[10 ], intel_dp->lane_count)) {drm_dbg_kms (&i915->drm,"channel EQ not ok, retraining\n" ); - need_retrain = true; + link_ok = false; }drm_dbg_kms (&i915->drm,"got esi %3ph\n" , esi);
@@ -5604,7 +5615,7 @@ intel_dp_check_mst_status(struct intel_dp *intel_dp) } } -return need_retrain; +return link_ok; } static bool
@@ -7255,35 +7266,10 @@ intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) }if (intel_dp->is_mst) { -switch (intel_dp_check_mst_status (intel_dp)) { -case -EINVAL : -/* -* If we were in MST mode, and device is not -* there, get out of MST mode -*/ -drm_dbg_kms (&i915->drm, -"MST device may have disappeared %d vs %d\n" , - intel_dp->is_mst, - intel_dp->mst_mgr.mst_state); - intel_dp->is_mst = false; -drm_dp_mst_topology_mgr_set_mst (&intel_dp->mst_mgr, - intel_dp->is_mst); - -return IRQ_NONE ; -case 1 : -return IRQ_NONE ; -default : -break ; - } - } - -if (!intel_dp->is_mst) { -bool handled; - - handled =intel_dp_short_pulse (intel_dp); - -if (!handled) +if (!intel_dp_check_mst_status (intel_dp))return IRQ_NONE ; + }else if (!intel_dp_short_pulse (intel_dp)) { +return IRQ_NONE ; }return IRQ_HANDLED ;
Signature · 6 lines
2.23.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 132 lines · Imre Deak
Currently MST on a port can get enabled/disabled from the hotplug work and get disabled from the short pulse work in a racy way. Fix this by relying on the MST state checking in the hotplug work and just schedule a hotplug work from the short pulse handler if some problem happened during the MST interrupt handling.
This removes the explicit MST disabling in case of an AUX failure, but if AUX fails, then probably the detection will also fail during the scheduled hotplug work and it's not guaranteed that we'll see intermittent errors anyway.
While at it also simplify the error checking of the MST interrupt handler.
v2:
- Convertintel_dp_check_mst_status()to return bool. (Ville)
- Change theintel_dp->is_mstcheck to an assert, since after this patch the condition can't change after we checked it previously.
- Document the return value fromintel_dp_check_mst_status(). v3:
- Remove theintel_dp->is_mstcheck fromintel_dp_check_mst_status(). There is no point in checking the same condition twice, even though there is a chance that the hotplug work running concurrently changes it.Cc José Roberto de Souza <[email protected]>Cc Ville Syrjälä <[email protected]>Reviewed-by José Roberto de Souza <[email protected]> (v1)Signed-off-by Imre Deak <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 66 ++++++++++--------------- 1 file changed, 26 insertions(+), 40 deletions(-)drivers/gpu/drm/i915/display/intel_dp.c +23
-36@@ -5556,35 +5556,46 @@ static void intel_dp_handle_test_request(struct intel_dp *intel_dp) "Could not write test response to sink\n"); } -static int +/** +* intel_dp_check_mst_status - service any pending MST interrupts, check link status +* @intel_dp: Intel DP struct +* +* Read any pending MST interrupts, call MST core to handle these and ack the +* interrupts. Check if the main and AUX link state is ok. +* +* Returns: +* - %true if pending interrupts were serviced (or no interrupts were +* pending) w/o detecting an error condition. +* - %false if an error condition - like AUX failure or a loss of link - is +* detected, which needs servicing from the hotplug work. +*/ +static bool intel_dp_check_mst_status (struct intel_dp *intel_dp) {struct drm_i915_private *i915 =dp_to_i915 (intel_dp); -bool need_retrain = false; - -if (!intel_dp->is_mst) -return -EINVAL ; +bool link_ok = true;drm_WARN_ON_ONCE (&i915->drm, intel_dp->active_mst_links <0 );for (;;) {u8 esi[DP_DPRX_ESI_LEN ] = {}; -bool bret, handled; +bool handled;int retry; - bret =intel_dp_get_sink_irq_esi (intel_dp, esi); -if (!bret) { +if (!intel_dp_get_sink_irq_esi (intel_dp, esi)) {drm_dbg_kms (&i915->drm,"failed to get ESI - device may have failed\n" ); -return -EINVAL ; + link_ok = false; + +break ; }/* check link status - esi[10] = 0x200c */ -if (intel_dp->active_mst_links >0 && !need_retrain && +if (intel_dp->active_mst_links >0 && link_ok && !drm_dp_channel_eq_ok (&esi[10 ], intel_dp->lane_count)) {drm_dbg_kms (&i915->drm,"channel EQ not ok, retraining\n" ); - need_retrain = true; + link_ok = false; }drm_dbg_kms (&i915->drm,"got esi %3ph\n" , esi);@@ -5604,7 +5615,7 @@ intel_dp_check_mst_status(struct intel_dp *intel_dp) } } -return need_retrain; +return link_ok; } static bool@@ -7255,35 +7266,10 @@ intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) }if (intel_dp->is_mst) { -switch (intel_dp_check_mst_status (intel_dp)) { -case -EINVAL : -/* -* If we were in MST mode, and device is not -* there, get out of MST mode -*/ -drm_dbg_kms (&i915->drm, -"MST device may have disappeared %d vs %d\n" , - intel_dp->is_mst, - intel_dp->mst_mgr.mst_state); - intel_dp->is_mst = false; -drm_dp_mst_topology_mgr_set_mst (&intel_dp->mst_mgr, - intel_dp->is_mst); - -return IRQ_NONE ; -case 1 : -return IRQ_NONE ; -default : -break ; - } - } - -if (!intel_dp->is_mst) { -bool handled;
drivers/gpu/drm/i915/display/intel_dp.c intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) · line 7274
Quoted 10 lines
drivers/gpu/drm/i915/display/intel_dp.c +3
-4- - handled =intel_dp_short_pulse (intel_dp); - -if (!handled) +if (!intel_dp_check_mst_status (intel_dp))return IRQ_NONE ; + }else if (!intel_dp_short_pulse (intel_dp)) { +return IRQ_NONE ; }
Now it don't need the braces but this is minor.
drivers/gpu/drm/i915/display/intel_dp.c intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) · line 7275
Quoted 1 line
drivers/gpu/drm/i915/display/intel_dp.c +0
-0return IRQ_HANDLED ;
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 137 lines · Jose
Quoted 136 lines · Imre Deak
Currently MST on a port can get enabled/disabled from the hotplug work and get disabled from the short pulse work in a racy way. Fix this by relying on the MST state checking in the hotplug work and just schedule a hotplug work from the short pulse handler if some problem happened during the MST interrupt handling.
This removes the explicit MST disabling in case of an AUX failure, but if AUX fails, then probably the detection will also fail during the scheduled hotplug work and it's not guaranteed that we'll see intermittent errors anyway.
While at it also simplify the error checking of the MST interrupt handler.
v2:
- Convertintel_dp_check_mst_status()to return bool. (Ville)
- Change theintel_dp->is_mstcheck to an assert, since after this patch the condition can't change after we checked it previously.
- Document the return value fromintel_dp_check_mst_status(). v3:
- Remove theintel_dp->is_mstcheck fromintel_dp_check_mst_status(). There is no point in checking the same condition twice, even though there is a chance that the hotplug work running concurrently changes it.Cc José Roberto de Souza <[email protected]>Cc Ville Syrjälä <[email protected]>Reviewed-by José Roberto de Souza <[email protected]> (v1)Signed-off-by Imre Deak <[email protected]>--- drivers/gpu/drm/i915/display/intel_dp.c | 66 ++++++++++--------------- 1 file changed, 26 insertions(+), 40 deletions(-)drivers/gpu/drm/i915/display/intel_dp.c +23
-40@@ -5556,35 +5556,46 @@ static void intel_dp_handle_test_request(struct intel_dp *intel_dp) "Could not write test response to sink\n"); } -static int +/** +* intel_dp_check_mst_status - service any pending MST interrupts, check link status +* @intel_dp: Intel DP struct +* +* Read any pending MST interrupts, call MST core to handle these and ack the +* interrupts. Check if the main and AUX link state is ok. +* +* Returns: +* - %true if pending interrupts were serviced (or no interrupts were +* pending) w/o detecting an error condition. +* - %false if an error condition - like AUX failure or a loss of link - is +* detected, which needs servicing from the hotplug work. +*/ +static bool intel_dp_check_mst_status (struct intel_dp *intel_dp) {struct drm_i915_private *i915 =dp_to_i915 (intel_dp); -bool need_retrain = false; - -if (!intel_dp->is_mst) -return -EINVAL ; +bool link_ok = true;drm_WARN_ON_ONCE (&i915->drm, intel_dp->active_mst_links <0 );for (;;) {u8 esi[DP_DPRX_ESI_LEN ] = {}; -bool bret, handled; +bool handled;int retry; - bret =intel_dp_get_sink_irq_esi (intel_dp, esi); -if (!bret) { +if (!intel_dp_get_sink_irq_esi (intel_dp, esi)) {drm_dbg_kms (&i915->drm,"failed to get ESI - device may have failed\n" ); -return -EINVAL ; + link_ok = false; + +break ; }/* check link status - esi[10] = 0x200c */ -if (intel_dp->active_mst_links >0 && !need_retrain && +if (intel_dp->active_mst_links >0 && link_ok && !drm_dp_channel_eq_ok (&esi[10 ], intel_dp->lane_count)) {drm_dbg_kms (&i915->drm,"channel EQ not ok, retraining\n" ); - need_retrain = true; + link_ok = false; }drm_dbg_kms (&i915->drm,"got esi %3ph\n" , esi);@@ -5604,7 +5615,7 @@ intel_dp_check_mst_status(struct intel_dp *intel_dp) } } -return need_retrain; +return link_ok; } static bool@@ -7255,35 +7266,10 @@ intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) }if (intel_dp->is_mst) { -switch (intel_dp_check_mst_status (intel_dp)) { -case -EINVAL : -/* -* If we were in MST mode, and device is not -* there, get out of MST mode -*/ -drm_dbg_kms (&i915->drm, -"MST device may have disappeared %d vs %d\n" , - intel_dp->is_mst, - intel_dp->mst_mgr.mst_state); - intel_dp->is_mst = false; -drm_dp_mst_topology_mgr_set_mst (&intel_dp->mst_mgr, - intel_dp->is_mst); - -return IRQ_NONE ; -case 1 : -return IRQ_NONE ; -default : -break ; - } - } - -if (!intel_dp->is_mst) { -bool handled; - - handled =intel_dp_short_pulse (intel_dp); - -if (!handled)
Quoted 8 lines
drivers/gpu/drm/i915/display/intel_dp.c intel_dp_hpd_pulse(struct intel_digital_port *intel_dig_port, bool long_hpd) · line 7274
Quoted 6 lines
drivers/gpu/drm/i915/display/intel_dp.c +3
-0+if (!intel_dp_check_mst_status (intel_dp))return IRQ_NONE ; + }else if (!intel_dp_short_pulse (intel_dp)) { +return IRQ_NONE ; }Now it don't need the braces but this is minor.
Without the braces it wouldn't be correct.
Quoted 4 lines
Reviewed-by José Roberto de Souza <[email protected]>Quoted 1 line
drivers/gpu/drm/i915/display/intel_dp.c +0
-0return IRQ_HANDLED ;
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v2,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev4)
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: series starting with [v2,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev4)
URL : https://patchwork.freedesktop.org/series/77969/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8585 -> Patchwork_17876
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/index.html
Known issues
------------
Here are the changes found in Patchwork_17876 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-bsw-kefka: [PASS][1] -> [DMESG-WARN][2] ([i915#1982])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/fi-bsw-kefka/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/fi-bsw-kefka/igt@[email protected]
* igt@i915_pm_rpm@module-reload:
- fi-glk-dsi: [PASS][3] -> [DMESG-WARN][4] ([i915#1982])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/fi-glk-dsi/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/fi-glk-dsi/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@execlists:
- fi-icl-y: [DMESG-FAIL][5] ([i915#1993]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/fi-icl-y/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/fi-icl-y/igt@i915_selftest@[email protected]
* igt@kms_busy@basic@flip:
- fi-kbl-x1275: [DMESG-WARN][7] ([i915#62] / [i915#92] / [i915#95]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/fi-kbl-x1275/igt@kms_busy@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/fi-kbl-x1275/igt@kms_busy@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- fi-icl-u2: [DMESG-WARN][9] ([i915#1982]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/fi-icl-u2/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/fi-icl-u2/igt@[email protected]
* igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a:
- fi-tgl-y: [DMESG-WARN][11] ([i915#1982]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/fi-tgl-y/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/fi-tgl-y/igt@[email protected]
* igt@kms_pipe_crc_basic@read-crc-pipe-c:
- {fi-tgl-dsi}: [DMESG-WARN][13] ([i915#1982]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/fi-tgl-dsi/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/fi-tgl-dsi/igt@[email protected]
#### Warnings ####
* igt@gem_exec_suspend@basic-s0:
- fi-kbl-x1275: [DMESG-WARN][15] ([i915#62] / [i915#92]) -> [DMESG-WARN][16] ([i915#62] / [i915#92] / [i915#95]) +5 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/fi-kbl-x1275/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/fi-kbl-x1275/igt@[email protected]
* igt@kms_force_connector_basic@force-edid:
- fi-kbl-x1275: [DMESG-WARN][17] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][18] ([i915#62] / [i915#92]) +4 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/fi-kbl-x1275/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/fi-kbl-x1275/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[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 (50 -> 44)
------------------------------
Additional (1): fi-kbl-7560u
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_8585 -> Patchwork_17876
CI-20190529: 20190529
CI_DRM_8585: 3aef9a510cfe66ba71ed397e91c517402f7c26ac @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5695: 53e8c878a6fb5708e63c99403691e8960b86ea9c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17876: 510b25246e2201dfbad5a4a34e0cec24f91db43e @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
510b25246e22 drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses fb42f8a70d4f drm/dp_mst: Sanitize mgr->qlock locking in drm_dp_mst_wait_tx_reply() 90c80197a498 drm/i915/dp_mst: Fix disabling MST on a port
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [v2,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev4)
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: series starting with [v2,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev4)
URL : https://patchwork.freedesktop.org/series/77969/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8585_full -> Patchwork_17876_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_17876_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_param@basic:
- shard-apl: [PASS][1] -> [DMESG-WARN][2] ([i915#95]) +13 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-apl2/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-apl1/igt@[email protected]
* igt@gem_exec_nop@basic-series:
- shard-hsw: [PASS][3] -> [INCOMPLETE][4] ([i915#61])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-hsw8/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-hsw6/igt@[email protected]
* igt@gem_exec_whisper@basic-queues-all:
- shard-glk: [PASS][5] -> [DMESG-WARN][6] ([i915#118] / [i915#95]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-glk8/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-glk8/igt@[email protected]
* igt@i915_selftest@mock@requests:
- shard-glk: [PASS][7] -> [INCOMPLETE][8] ([i915#58] / [k.org#198133])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-glk1/igt@i915_selftest@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-glk8/igt@i915_selftest@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [PASS][9] -> [DMESG-WARN][10] ([i915#180])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-kbl3/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-kbl6/igt@[email protected]
* igt@kms_cursor_legacy@all-pipes-torture-bo:
- shard-hsw: [PASS][11] -> [DMESG-WARN][12] ([i915#128])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-hsw4/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-hsw5/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move:
- shard-kbl: [PASS][13] -> [DMESG-WARN][14] ([i915#93] / [i915#95])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-kbl2/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-kbl6/igt@[email protected]
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes:
- shard-apl: [PASS][15] -> [DMESG-WARN][16] ([i915#180])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-apl1/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-apl4/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [PASS][17] -> [FAIL][18] ([fdo#108145] / [i915#265])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-skl10/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-skl4/igt@[email protected]
* igt@kms_plane_scaling@pipe-c-plane-scaling:
- shard-skl: [PASS][19] -> [DMESG-WARN][20] ([i915#1982]) +7 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-skl8/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-skl1/igt@[email protected]
* igt@kms_psr@psr2_primary_mmap_gtt:
- shard-iclb: [PASS][21] -> [SKIP][22] ([fdo#109441]) +2 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-iclb2/igt@kms_psr@psr2_primary_mmap_gtt.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-iclb3/igt@kms_psr@psr2_primary_mmap_gtt.html
* igt@kms_universal_plane@universal-plane-gen9-features-pipe-c:
- shard-tglb: [PASS][23] -> [DMESG-WARN][24] ([i915#1982]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-tglb6/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-tglb7/igt@[email protected]
* igt@perf@blocking:
- shard-skl: [PASS][25] -> [FAIL][26] ([i915#1542])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-skl6/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-skl9/igt@[email protected]
#### Possible fixes ####
* {igt@gem_ctx_isolation@preservation-s3@rcs0}:
- shard-apl: [DMESG-WARN][27] ([i915#180]) -> [PASS][28] +1 similar issue
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-apl4/igt@gem_ctx_isolation@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-apl3/igt@gem_ctx_isolation@[email protected]
* {igt@gem_exec_schedule@implicit-boths@bcs0}:
- shard-snb: [INCOMPLETE][29] ([i915#82]) -> [PASS][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-snb4/igt@gem_exec_schedule@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-snb1/igt@gem_exec_schedule@[email protected]
* {igt@gem_exec_schedule@preempt@bcs0}:
- shard-tglb: [DMESG-WARN][31] ([i915#402]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-tglb8/igt@gem_exec_schedule@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-tglb2/igt@gem_exec_schedule@[email protected]
* igt@kms_big_fb@linear-64bpp-rotate-0:
- shard-glk: [DMESG-FAIL][33] ([i915#118] / [i915#95]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-glk8/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-glk9/igt@[email protected]
* igt@kms_big_fb@x-tiled-32bpp-rotate-180:
- shard-skl: [DMESG-WARN][35] ([i915#1982]) -> [PASS][36] +4 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-skl1/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-skl7/igt@[email protected]
* igt@kms_color@pipe-c-ctm-red-to-blue:
- shard-kbl: [DMESG-WARN][37] ([i915#93] / [i915#95]) -> [PASS][38] +2 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-kbl1/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-kbl3/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-128x42-offscreen:
- shard-skl: [FAIL][39] ([i915#54]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-skl5/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-skl2/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-64x21-random:
- shard-kbl: [DMESG-FAIL][41] ([i915#54] / [i915#95]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-kbl4/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-kbl4/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-suspend:
- shard-kbl: [DMESG-WARN][43] ([i915#180]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-kbl6/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-kbl7/igt@[email protected]
* igt@kms_cursor_edge_walk@pipe-b-256x256-left-edge:
- shard-glk: [DMESG-WARN][45] ([i915#1982]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-glk5/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-glk9/igt@[email protected]
* igt@kms_cursor_legacy@pipe-c-torture-move:
- shard-hsw: [DMESG-WARN][47] ([i915#128]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-hsw7/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-hsw1/igt@[email protected]
* igt@kms_cursor_legacy@short-flip-after-cursor-atomic-transitions-varying-size:
- shard-tglb: [DMESG-WARN][49] ([i915#1982]) -> [PASS][50] +1 similar issue
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-tglb7/igt@kms_cursor_legacy@short-flip-after-cursor-atomic-transitions-varying-size.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-tglb3/igt@kms_cursor_legacy@short-flip-after-cursor-atomic-transitions-varying-size.html
- shard-apl: [DMESG-WARN][51] ([i915#1982]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-apl3/igt@kms_cursor_legacy@short-flip-after-cursor-atomic-transitions-varying-size.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-apl8/igt@kms_cursor_legacy@short-flip-after-cursor-atomic-transitions-varying-size.html
* igt@kms_draw_crc@draw-method-rgb565-mmap-gtt-xtiled:
- shard-kbl: [TIMEOUT][53] -> [PASS][54] +1 similar issue
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-kbl4/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-kbl1/igt@[email protected]
* {igt@kms_flip@plain-flip-fb-recreate-interruptible@b-edp1}:
- shard-skl: [FAIL][55] ([i915#1928]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-skl9/igt@kms_flip@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-skl6/igt@kms_flip@[email protected]
* {igt@kms_getfb@getfb2-handle-protection}:
- shard-apl: [DMESG-WARN][57] ([i915#95]) -> [PASS][58] +20 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-apl7/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-apl2/igt@[email protected]
* igt@kms_hdr@bpc-switch-suspend:
- shard-skl: [FAIL][59] ([i915#1188]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-skl5/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-skl7/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-constant-alpha-min:
- shard-skl: [FAIL][61] ([fdo#108145] / [i915#265]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-skl6/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-skl10/igt@[email protected]
* igt@kms_psr@psr2_cursor_render:
- shard-iclb: [SKIP][63] ([fdo#109441]) -> [PASS][64] +2 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-iclb8/igt@kms_psr@psr2_cursor_render.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-iclb2/igt@kms_psr@psr2_cursor_render.html
* {igt@perf_pmu@enable-race@vecs0}:
- shard-glk: [DMESG-WARN][65] ([i915#118] / [i915#95]) -> [PASS][66] +2 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-glk7/igt@perf_pmu@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-glk7/igt@perf_pmu@[email protected]
#### Warnings ####
* igt@i915_pm_dc@dc6-psr:
- shard-tglb: [FAIL][67] ([i915#454]) -> [SKIP][68] ([i915#468])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-tglb8/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-tglb2/igt@[email protected]
* igt@kms_ccs@pipe-c-crc-primary-basic:
- shard-kbl: [TIMEOUT][69] -> [SKIP][70] ([fdo#109271]) +1 similar issue
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-kbl4/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-kbl1/igt@[email protected]
* igt@kms_color_chamelium@pipe-c-ctm-limited-range:
- shard-kbl: [INCOMPLETE][71] -> [SKIP][72] ([fdo#109271] / [fdo#111827])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-kbl4/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-kbl1/igt@[email protected]
* igt@kms_content_protection@atomic-dpms:
- shard-apl: [FAIL][73] ([fdo#110321] / [fdo#110336]) -> [TIMEOUT][74] ([i915#1319] / [i915#1635])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-apl4/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-apl7/igt@[email protected]
* igt@kms_content_protection@legacy:
- shard-apl: [TIMEOUT][75] ([i915#1319] / [i915#1635]) -> [FAIL][76] ([fdo#110321] / [fdo#110336])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-apl1/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-apl4/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-apl: [TIMEOUT][77] ([i915#1319] / [i915#1635]) -> [DMESG-FAIL][78] ([fdo#110321] / [i915#95]) +1 similar issue
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-apl4/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-apl3/igt@[email protected]
* igt@kms_content_protection@srm:
- shard-kbl: [DMESG-FAIL][79] ([fdo#110321] / [i915#95]) -> [TIMEOUT][80] ([i915#1319])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-kbl2/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-kbl7/igt@[email protected]
* igt@kms_draw_crc@draw-method-rgb565-mmap-gtt-xtiled:
- shard-glk: [INCOMPLETE][81] ([i915#58] / [k.org#198133]) -> [TIMEOUT][82] ([i915#1958])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-glk6/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-glk6/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [DMESG-WARN][83] ([i915#1982]) -> [DMESG-FAIL][84] ([fdo#108145] / [i915#1982])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8585/shard-skl2/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/shard-skl7/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#128]: https://gitlab.freedesktop.org/drm/intel/issues/128
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1928]: https://gitlab.freedesktop.org/drm/intel/issues/1928
[i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#468]: https://gitlab.freedesktop.org/drm/intel/issues/468
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58
[i915#61]: https://gitlab.freedesktop.org/drm/intel/issues/61
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_8585 -> Patchwork_17876
CI-20190529: 20190529
CI_DRM_8585: 3aef9a510cfe66ba71ed397e91c517402f7c26ac @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5695: 53e8c878a6fb5708e63c99403691e8960b86ea9c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17876: 510b25246e2201dfbad5a4a34e0cec24f91db43e @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17876/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev5)
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: series starting with [v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev5)
URL : https://patchwork.freedesktop.org/series/77969/
State : failure
== Summary ==
Applying: drm/i915/dp_mst: Fix disabling MST on a port
error: sha1 information is lacking or useless (drivers/gpu/drm/i915/display/intel_dp.c).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 drm/i915/dp_mst: Fix disabling MST on a port
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [RESEND,v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev6)
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: series starting with [RESEND,v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev6)
URL : https://patchwork.freedesktop.org/series/77969/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8590 -> Patchwork_17882
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/index.html
Known issues
------------
Here are the changes found in Patchwork_17882 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-byt-j1900: [PASS][1] -> [DMESG-WARN][2] ([i915#1982])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/fi-byt-j1900/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/fi-byt-j1900/igt@[email protected]
#### Possible fixes ####
* igt@i915_module_load@reload:
- fi-byt-j1900: [DMESG-WARN][3] ([i915#1982]) -> [PASS][4] +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/fi-byt-j1900/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/fi-byt-j1900/igt@[email protected]
- fi-byt-n2820: [DMESG-WARN][5] ([i915#1982]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/fi-byt-n2820/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/fi-byt-n2820/igt@[email protected]
* igt@i915_pm_rpm@module-reload:
- fi-apl-guc: [DMESG-WARN][7] ([i915#1982]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/fi-apl-guc/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/fi-apl-guc/igt@[email protected]
* igt@i915_selftest@live@active:
- fi-whl-u: [DMESG-FAIL][9] ([i915#666]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/fi-whl-u/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/fi-whl-u/igt@i915_selftest@[email protected]
* igt@kms_busy@basic@flip:
- fi-kbl-x1275: [DMESG-WARN][11] ([i915#62] / [i915#92] / [i915#95]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/fi-kbl-x1275/igt@kms_busy@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/fi-kbl-x1275/igt@kms_busy@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-tgl-y: [DMESG-WARN][13] ([i915#1982]) -> [PASS][14] +1 similar issue
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/fi-tgl-y/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/fi-tgl-y/igt@[email protected]
- fi-icl-guc: [DMESG-WARN][15] ([i915#1982]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/fi-icl-guc/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/fi-icl-guc/igt@[email protected]
#### Warnings ####
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- fi-kbl-x1275: [DMESG-WARN][17] ([i915#62] / [i915#92]) -> [DMESG-WARN][18] ([i915#62] / [i915#92] / [i915#95]) +4 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/fi-kbl-x1275/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/fi-kbl-x1275/igt@[email protected]
* igt@kms_force_connector_basic@force-edid:
- fi-kbl-x1275: [DMESG-WARN][19] ([i915#62] / [i915#92] / [i915#95]) -> [DMESG-WARN][20] ([i915#62] / [i915#92]) +5 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/fi-kbl-x1275/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/fi-kbl-x1275/igt@[email protected]
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#666]: https://gitlab.freedesktop.org/drm/intel/issues/666
[i915#92]: https://gitlab.freedesktop.org/drm/intel/issues/92
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (50 -> 43)
------------------------------
Additional (1): fi-kbl-7560u
Missing (8): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-bsw-kefka fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_8590 -> Patchwork_17882
CI-20190529: 20190529
CI_DRM_8590: 91c6f0274b54c89679cd23f6fc65e9fe5922971f @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5695: 53e8c878a6fb5708e63c99403691e8960b86ea9c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17882: 23fe5e3ae83585e3d4ad9ecdfea368dd42ff6dfb @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
23fe5e3ae835 drm/i915/dp_mst: Work around out-of-spec adapters filtering short pulses ceb861eabe52 drm/dp_mst: Sanitize mgr->qlock locking in drm_dp_mst_wait_tx_reply() ba27048a7abb drm/i915/dp_mst: Fix disabling MST on a port
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [RESEND,v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev6)
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: series starting with [RESEND,v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev6)
URL : https://patchwork.freedesktop.org/series/77969/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8590_full -> Patchwork_17882_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_17882_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_17882_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_17882_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_draw_crc@draw-method-rgb565-mmap-gtt-xtiled:
- shard-snb: [PASS][1] -> [TIMEOUT][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]
#### Warnings ####
* igt@kms_plane_scaling@pipe-b-scaler-with-clipping-clamping:
- shard-snb: [SKIP][3] ([fdo#109271]) -> [TIMEOUT][4] +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* {igt@gem_exec_reloc@basic-concurrent16}:
- shard-snb: [FAIL][5] ([i915#1930]) -> [TIMEOUT][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]
* {igt@kms_chamelium@vga-hpd-enable-disable-mode}:
- shard-snb: [SKIP][7] ([fdo#109271] / [fdo#111827]) -> [TIMEOUT][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_17882_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_whisper@basic-forked-all:
- shard-glk: [PASS][9] -> [DMESG-WARN][10] ([i915#118] / [i915#95])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk7/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk2/igt@[email protected]
* igt@gem_mmap_gtt@cpuset-big-copy-odd:
- shard-iclb: [PASS][11] -> [DMESG-WARN][12] ([i915#1982])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/igt@[email protected]
* igt@gem_workarounds@suspend-resume:
- shard-apl: [PASS][13] -> [DMESG-WARN][14] ([i915#180])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/igt@[email protected]
* igt@kms_big_fb@linear-32bpp-rotate-180:
- shard-skl: [PASS][15] -> [DMESG-WARN][16] ([i915#1982]) +9 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl5/igt@[email protected]
* igt@kms_big_fb@linear-64bpp-rotate-180:
- shard-glk: [PASS][17] -> [DMESG-FAIL][18] ([i915#118] / [i915#95]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk2/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk8/igt@[email protected]
* igt@kms_big_fb@x-tiled-16bpp-rotate-0:
- shard-glk: [PASS][19] -> [DMESG-WARN][20] ([i915#1982])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk5/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk4/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-256x85-offscreen:
- shard-apl: [PASS][21] -> [DMESG-WARN][22] ([i915#95]) +17 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl4/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl8/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [PASS][23] -> [DMESG-WARN][24] ([i915#180]) +4 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move:
- shard-kbl: [PASS][25] -> [DMESG-WARN][26] ([i915#93] / [i915#95])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl1/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-cpu:
- shard-skl: [PASS][27] -> [FAIL][28] ([i915#49])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl9/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl9/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:
- shard-skl: [PASS][29] -> [FAIL][30] ([fdo#108145] / [i915#265]) +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl2/igt@[email protected]
* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-snb: [PASS][31] -> [SKIP][32] ([fdo#109271]) +1 similar issue
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb2/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]
* igt@kms_psr@psr2_cursor_blt:
- shard-iclb: [PASS][33] -> [SKIP][34] ([fdo#109441]) +3 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb2/igt@kms_psr@psr2_cursor_blt.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb4/igt@kms_psr@psr2_cursor_blt.html
* igt@kms_universal_plane@universal-plane-gen9-features-pipe-c:
- shard-kbl: [PASS][35] -> [DMESG-WARN][36] ([i915#1982])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/igt@[email protected]
* igt@syncobj_wait@invalid-multi-wait-unsubmitted-submitted:
- shard-tglb: [PASS][37] -> [DMESG-WARN][38] ([i915#402])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-tglb6/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-tglb7/igt@[email protected]
#### Possible fixes ####
* {igt@gem_ctx_isolation@preservation-s3@rcs0}:
- shard-apl: [DMESG-WARN][39] ([i915#180]) -> [PASS][40] +2 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@gem_ctx_isolation@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/igt@gem_ctx_isolation@[email protected]
* igt@gem_exec_whisper@basic-queues-forked-all:
- shard-glk: [DMESG-WARN][41] ([i915#118] / [i915#95]) -> [PASS][42] +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk9/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk9/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-kbl: [DMESG-WARN][43] ([i915#1436] / [i915#716]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl1/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]
* igt@i915_suspend@debugfs-reader:
- shard-kbl: [INCOMPLETE][45] ([i915#155]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl6/igt@[email protected]
* igt@kms_color@pipe-c-ctm-red-to-blue:
- shard-kbl: [DMESG-WARN][47] ([i915#93] / [i915#95]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl7/igt@[email protected]
* igt@kms_color@pipe-d-ctm-0-5:
- shard-tglb: [DMESG-WARN][49] ([i915#1149] / [i915#402]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-tglb2/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-tglb1/igt@[email protected]
* igt@kms_cursor_legacy@all-pipes-torture-move:
- shard-skl: [DMESG-WARN][51] ([i915#128]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl10/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl3/igt@[email protected]
* {igt@kms_flip@2x-flip-vs-suspend@ab-hdmi-a1-hdmi-a2}:
- shard-glk: [DMESG-WARN][53] ([i915#1982]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk6/igt@kms_flip@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk8/igt@kms_flip@[email protected]
* igt@kms_flip_tiling@flip-x-tiled:
- shard-apl: [DMESG-WARN][55] ([i915#95]) -> [PASS][56] +26 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl7/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/igt@[email protected]
* igt@kms_hdr@bpc-switch-suspend:
- shard-skl: [FAIL][57] ([i915#1188]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl10/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl3/igt@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- shard-kbl: [DMESG-WARN][59] ([i915#180]) -> [PASS][60] +3 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]
* igt@kms_plane@plane-panning-bottom-right-pipe-c-planes:
- shard-skl: [DMESG-WARN][61] ([i915#1982]) -> [PASS][62] +2 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl5/igt@[email protected]
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [SKIP][63] ([fdo#109441]) -> [PASS][64] +2 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@kms_psr@psr2_primary_mmap_cpu.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_setmode@basic:
- shard-apl: [FAIL][65] ([i915#31]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl6/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/igt@[email protected]
- shard-kbl: [FAIL][67] ([i915#31]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl6/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]
* {igt@perf@polling-parameterized}:
- shard-hsw: [FAIL][69] ([i915#1542]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-hsw6/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-hsw5/igt@[email protected]
#### Warnings ####
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-snb: [SKIP][71] ([fdo#109271]) -> [INCOMPLETE][72] ([i915#82]) +1 similar issue
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb2/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb5/igt@[email protected]
- shard-iclb: [SKIP][73] ([i915#658]) -> [SKIP][74] ([i915#588])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/igt@[email protected]
* igt@kms_content_protection@atomic:
- shard-apl: [FAIL][75] ([fdo#110321] / [fdo#110336]) -> [TIMEOUT][76] ([i915#1319] / [i915#1635])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl6/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/igt@[email protected]
* igt@kms_content_protection@legacy:
- shard-kbl: [DMESG-FAIL][77] ([fdo#110321]) -> [TIMEOUT][78] ([i915#1319] / [i915#1958])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-apl: [DMESG-FAIL][79] ([fdo#110321] / [i915#95]) -> [TIMEOUT][80] ([i915#1319] / [i915#1635]) +1 similar issue
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/igt@[email protected]
* igt@kms_content_protection@srm:
- shard-kbl: [DMESG-FAIL][81] ([fdo#110321] / [i915#95]) -> [TIMEOUT][82] ([i915#1319])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [DMESG-WARN][83] ([i915#180] / [i915#93] / [i915#95]) -> [DMESG-WARN][84] ([i915#93] / [i915#95])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl7/igt@[email protected]
- shard-apl: [DMESG-WARN][85] ([i915#180] / [i915#95]) -> [DMESG-WARN][86] ([i915#95])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl4/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl8/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [DMESG-WARN][87] ([i915#1982]) -> [DMESG-FAIL][88] ([fdo#108145] / [i915#1982])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl2/igt@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl2/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1149]: https://gitlab.freedesktop.org/drm/intel/issues/1149
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#128]: https://gitlab.freedesktop.org/drm/intel/issues/128
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1928]: https://gitlab.freedesktop.org/drm/intel/issues/1928
[i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#46]: https://gitlab.freedesktop.org/drm/intel/issues/46
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#588]: https://gitlab.freedesktop.org/drm/intel/issues/588
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_8590 -> Patchwork_17882
CI-20190529: 20190529
CI_DRM_8590: 91c6f0274b54c89679cd23f6fc65e9fe5922971f @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5695: 53e8c878a6fb5708e63c99403691e8960b86ea9c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17882: 23fe5e3ae83585e3d4ad9ecdfea368dd42ff6dfb @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [RESEND,v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev6)
Quoted 40 lines · Patchwork
== Series Details ==
Series: series starting with [RESEND,v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev6)
URL : https://patchwork.freedesktop.org/series/77969/
State : failure== Summary ==
CI Bug Log - changes from
CI_DRM_8590_full->Patchwork_17882_full
====================================================Summary
-------**FAILURE**
Serious unknown changes coming with
Patchwork_17882_fullabsolutely need to be verified manually.If you think the reported changes have nothing to do with the changes introduced in
Patchwork_17882_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.Possible new issues
-------------------Here are the unknown changes that may have been introduced in
Patchwork_17882_full:### IGT changes ###
#### Possible regressions ####
* igt@kms_draw_crc@draw-method-rgb565-mmap-gtt-xtiled:
- shard-snb: [PASS][1] -> [TIMEOUT][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]
Quoted 6 lines
#### Warnings ####
* igt@kms_plane_scaling@pipe-b-scaler-with-clipping-clamping:
- shard-snb: [SKIP][3] ([fdo#109271]) -> [TIMEOUT][4] +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]
Both of the above are unrelated, since there's only a VGA output connected to shard-snb1. Both tests time out because an earlier failure:
<7>[ 96.713236] [IGT] gem_exec_reloc: starting subtest basic-concurrent16 <5>[ 216.856564] [IGT] Per-test timeout exceeded. Killing the current test with SIGQUIT.
<6>[ 216.880307] gem_exec_reloc S12784 1625 1624 0x00000000 <4>[ 216.880311] Call Trace: <4>[ 216.880317] __schedule+0x2ff/0x8d0 <4>[ 216.880325] schedule+0x37/0xe0 <4>[ 216.880328] schedule_timeout+0x1aa/0x2e0 <4>[ 216.880390] ? mock_breadcrumbs_smoketest+0x290/0x290 [i915] <4>[ 216.880394] ? find_held_lock+0x2d/0x90 <4>[ 216.880442] ? hwsp_seqno+0x5b/0xd0 [i915] <4>[ 216.880449] io_schedule_timeout+0x14/0x40 <4>[ 216.880502] i915_request_wait+0x159/0x550 [i915] <4>[ 216.880548] ? __i915_request_await_external+0x40/0x40 [i915] <4>[ 216.880593] i915_gem_object_wait+0xb2/0x540 [i915] <4>[ 216.880640] i915_gem_wait_ioctl+0x113/0x2d0 [i915] <4>[ 216.880683] ? i915_gem_object_wait+0x540/0x540 [i915] <4>[ 216.880688] drm_ioctl_kernel+0xb0/0xf0 <4>[ 216.880694] drm_ioctl+0x305/0x3c0 <4>[ 216.880737] ? i915_gem_object_wait+0x540/0x540 [i915] <4>[ 216.880750] ksys_ioctl+0x7b/0x90 <4>[ 216.880755] __x64_sys_ioctl+0x11/0x20 <4>[ 216.880757] do_syscall_64+0x4f/0x220 <4>[ 216.880760] entry_SYSCALL_64_after_hwframe+0x49/0xb3
Quoted 282 lines
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* {igt@gem_exec_reloc@basic-concurrent16}:
- shard-snb: [FAIL][5] ([i915#1930]) -> [TIMEOUT][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]* {igt@kms_chamelium@vga-hpd-enable-disable-mode}:
- shard-snb: [SKIP][7] ([fdo#109271] / [fdo#111827]) -> [TIMEOUT][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]Known issues
------------Here are the changes found in
Patchwork_17882_fullthat come from known issues:### IGT changes ###
#### Issues hit ####
* igt@gem_exec_whisper@basic-forked-all:
- shard-glk: [PASS][9] -> [DMESG-WARN][10] ([i915#118] / [i915#95])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk7/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk2/igt@[email protected]* igt@gem_mmap_gtt@cpuset-big-copy-odd:
- shard-iclb: [PASS][11] -> [DMESG-WARN][12] ([i915#1982])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/igt@[email protected]* igt@gem_workarounds@suspend-resume:
- shard-apl: [PASS][13] -> [DMESG-WARN][14] ([i915#180])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/igt@[email protected]* igt@kms_big_fb@linear-32bpp-rotate-180:
- shard-skl: [PASS][15] -> [DMESG-WARN][16] ([i915#1982]) +9 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl5/igt@[email protected]* igt@kms_big_fb@linear-64bpp-rotate-180:
- shard-glk: [PASS][17] -> [DMESG-FAIL][18] ([i915#118] / [i915#95]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk2/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk8/igt@[email protected]* igt@kms_big_fb@x-tiled-16bpp-rotate-0:
- shard-glk: [PASS][19] -> [DMESG-WARN][20] ([i915#1982])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk5/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk4/igt@[email protected]* igt@kms_cursor_crc@pipe-c-cursor-256x85-offscreen:
- shard-apl: [PASS][21] -> [DMESG-WARN][22] ([i915#95]) +17 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl4/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl8/igt@[email protected]* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [PASS][23] -> [DMESG-WARN][24] ([i915#180]) +4 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/igt@[email protected]* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move:
- shard-kbl: [PASS][25] -> [DMESG-WARN][26] ([i915#93] / [i915#95])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl1/igt@[email protected]* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-cpu:
- shard-skl: [PASS][27] -> [FAIL][28] ([i915#49])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl9/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl9/igt@[email protected]* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:
- shard-skl: [PASS][29] -> [FAIL][30] ([fdo#108145] / [i915#265]) +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl2/igt@[email protected]* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-snb: [PASS][31] -> [SKIP][32] ([fdo#109271]) +1 similar issue
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb2/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]* igt@kms_psr@psr2_cursor_blt:
- shard-iclb: [PASS][33] -> [SKIP][34] ([fdo#109441]) +3 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb2/igt@kms_psr@psr2_cursor_blt.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb4/igt@kms_psr@psr2_cursor_blt.html* igt@kms_universal_plane@universal-plane-gen9-features-pipe-c:
- shard-kbl: [PASS][35] -> [DMESG-WARN][36] ([i915#1982])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/igt@[email protected]* igt@syncobj_wait@invalid-multi-wait-unsubmitted-submitted:
- shard-tglb: [PASS][37] -> [DMESG-WARN][38] ([i915#402])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-tglb6/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-tglb7/igt@[email protected]#### Possible fixes ####
* {igt@gem_ctx_isolation@preservation-s3@rcs0}:
- shard-apl: [DMESG-WARN][39] ([i915#180]) -> [PASS][40] +2 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@gem_ctx_isolation@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/igt@gem_ctx_isolation@[email protected]* igt@gem_exec_whisper@basic-queues-forked-all:
- shard-glk: [DMESG-WARN][41] ([i915#118] / [i915#95]) -> [PASS][42] +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk9/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk9/igt@[email protected]* igt@gen9_exec_parse@allowed-all:
- shard-kbl: [DMESG-WARN][43] ([i915#1436] / [i915#716]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl1/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]* igt@i915_suspend@debugfs-reader:
- shard-kbl: [INCOMPLETE][45] ([i915#155]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl6/igt@[email protected]* igt@kms_color@pipe-c-ctm-red-to-blue:
- shard-kbl: [DMESG-WARN][47] ([i915#93] / [i915#95]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl7/igt@[email protected]* igt@kms_color@pipe-d-ctm-0-5:
- shard-tglb: [DMESG-WARN][49] ([i915#1149] / [i915#402]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-tglb2/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-tglb1/igt@[email protected]* igt@kms_cursor_legacy@all-pipes-torture-move:
- shard-skl: [DMESG-WARN][51] ([i915#128]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl10/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl3/igt@[email protected]* {igt@kms_flip@2x-flip-vs-suspend@ab-hdmi-a1-hdmi-a2}:
- shard-glk: [DMESG-WARN][53] ([i915#1982]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk6/igt@kms_flip@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk8/igt@kms_flip@[email protected]* igt@kms_flip_tiling@flip-x-tiled:
- shard-apl: [DMESG-WARN][55] ([i915#95]) -> [PASS][56] +26 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl7/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/igt@[email protected]* igt@kms_hdr@bpc-switch-suspend:
- shard-skl: [FAIL][57] ([i915#1188]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl10/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl3/igt@[email protected]* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- shard-kbl: [DMESG-WARN][59] ([i915#180]) -> [PASS][60] +3 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]* igt@kms_plane@plane-panning-bottom-right-pipe-c-planes:
- shard-skl: [DMESG-WARN][61] ([i915#1982]) -> [PASS][62] +2 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl5/igt@[email protected]* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [SKIP][63] ([fdo#109441]) -> [PASS][64] +2 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@kms_psr@psr2_primary_mmap_cpu.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html* igt@kms_setmode@basic:
- shard-apl: [FAIL][65] ([i915#31]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl6/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/igt@[email protected]
- shard-kbl: [FAIL][67] ([i915#31]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl6/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]* {igt@perf@polling-parameterized}:
- shard-hsw: [FAIL][69] ([i915#1542]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-hsw6/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-hsw5/igt@[email protected]#### Warnings ####
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-snb: [SKIP][71] ([fdo#109271]) -> [INCOMPLETE][72] ([i915#82]) +1 similar issue
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb2/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb5/igt@[email protected]
- shard-iclb: [SKIP][73] ([i915#658]) -> [SKIP][74] ([i915#588])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/igt@[email protected]* igt@kms_content_protection@atomic:
- shard-apl: [FAIL][75] ([fdo#110321] / [fdo#110336]) -> [TIMEOUT][76] ([i915#1319] / [i915#1635])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl6/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/igt@[email protected]* igt@kms_content_protection@legacy:
- shard-kbl: [DMESG-FAIL][77] ([fdo#110321]) -> [TIMEOUT][78] ([i915#1319] / [i915#1958])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/igt@[email protected]* igt@kms_content_protection@lic:
- shard-apl: [DMESG-FAIL][79] ([fdo#110321] / [i915#95]) -> [TIMEOUT][80] ([i915#1319] / [i915#1635]) +1 similar issue
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/igt@[email protected]* igt@kms_content_protection@srm:
- shard-kbl: [DMESG-FAIL][81] ([fdo#110321] / [i915#95]) -> [TIMEOUT][82] ([i915#1319])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [DMESG-WARN][83] ([i915#180] / [i915#93] / [i915#95]) -> [DMESG-WARN][84] ([i915#93] / [i915#95])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl7/igt@[email protected]
- shard-apl: [DMESG-WARN][85] ([i915#180] / [i915#95]) -> [DMESG-WARN][86] ([i915#95])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl4/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl8/igt@[email protected]* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [DMESG-WARN][87] ([i915#1982]) -> [DMESG-FAIL][88] ([fdo#108145] / [i915#1982])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl2/igt@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl2/igt@[email protected]{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1149]: https://gitlab.freedesktop.org/drm/intel/issues/1149
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#128]: https://gitlab.freedesktop.org/drm/intel/issues/128
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1928]: https://gitlab.freedesktop.org/drm/intel/issues/1928
[i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#46]: https://gitlab.freedesktop.org/drm/intel/issues/46
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#588]: https://gitlab.freedesktop.org/drm/intel/issues/588
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95Participating hosts (11 -> 11)
------------------------------No changes in participating hosts
Build changes
-------------* Linux:
CI_DRM_8590->Patchwork_17882CI-20190529: 20190529
CI_DRM_8590:91c6f0274b54c89679cd23f6fc65e9fe5922971f@git://anongit.freedesktop.org/gfx-ci/linux
IGT_5695:53e8c878a6fb5708e63c99403691e8960b86ea9c@git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17882:23fe5e3ae83585e3d4ad9ecdfea368dd42ff6dfb@git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509:fdc5a4ca11124ab8413c7988896eec4c97336694@git://anongit.freedesktop.org/piglit
Quoted 3 lines
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [RESEND,v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev6)
Imre, I have addressed and re-reported.
Lakshmi.
-----Original Message-----
From: Imre Deak <[email protected]>
Sent: Friday, June 5, 2020 2:50 PM
To: [email protected]
Cc: Vudum, Lakshminarayana <[email protected]>
Subject: Re: ✗ Fi.CI.IGT: failure for series starting with [RESEND,v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev6)
Quoted 42 lines · Patchwork
== Series Details ==
Series: series starting with [RESEND,v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev6)
URL : https://patchwork.freedesktop.org/series/77969/
State : failure== Summary ==
CI Bug Log - changes from
CI_DRM_8590_full->Patchwork_17882_full
====================================================Summary
-------**FAILURE**
Serious unknown changes coming with
Patchwork_17882_fullabsolutely need to be verified manually.If you think the reported changes have nothing to do with the changes introduced in
Patchwork_17882_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.Possible new issues
-------------------Here are the unknown changes that may have been introduced in
Patchwork_17882_full:### IGT changes ###
#### Possible regressions ####
* igt@kms_draw_crc@draw-method-rgb565-mmap-gtt-xtiled:
- shard-snb: [PASS][1] -> [TIMEOUT][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[2]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/ig
t@[email protected]
Quoted 8 lines
#### Warnings ####
* igt@kms_plane_scaling@pipe-b-scaler-with-clipping-clamping:
- shard-snb: [SKIP][3] ([fdo#109271]) -> [TIMEOUT][4] +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[4]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/ig
t@[email protected]
Both of the above are unrelated, since there's only a VGA output connected to shard-snb1. Both tests time out because an earlier failure:
<7>[ 96.713236] [IGT] gem_exec_reloc: starting subtest basic-concurrent16 <5>[ 216.856564] [IGT] Per-test timeout exceeded. Killing the current test with SIGQUIT.
<6>[ 216.880307] gem_exec_reloc S12784 1625 1624 0x00000000 <4>[ 216.880311] Call Trace: <4>[ 216.880317] __schedule+0x2ff/0x8d0 <4>[ 216.880325] schedule+0x37/0xe0 <4>[ 216.880328] schedule_timeout+0x1aa/0x2e0 <4>[ 216.880390] ? mock_breadcrumbs_smoketest+0x290/0x290 [i915] <4>[ 216.880394] ? find_held_lock+0x2d/0x90 <4>[ 216.880442] ? hwsp_seqno+0x5b/0xd0 [i915] <4>[ 216.880449] io_schedule_timeout+0x14/0x40 <4>[ 216.880502] i915_request_wait+0x159/0x550 [i915] <4>[ 216.880548] ? __i915_request_await_external+0x40/0x40 [i915] <4>[ 216.880593] i915_gem_object_wait+0xb2/0x540 [i915] <4>[ 216.880640] i915_gem_wait_ioctl+0x113/0x2d0 [i915] <4>[ 216.880683] ? i915_gem_object_wait+0x540/0x540 [i915] <4>[ 216.880688] drm_ioctl_kernel+0xb0/0xf0 <4>[ 216.880694] drm_ioctl+0x305/0x3c0 <4>[ 216.880737] ? i915_gem_object_wait+0x540/0x540 [i915] <4>[ 216.880750] ksys_ioctl+0x7b/0x90 <4>[ 216.880755] __x64_sys_ioctl+0x11/0x20 <4>[ 216.880757] do_syscall_64+0x4f/0x220 <4>[ 216.880760] entry_SYSCALL_64_after_hwframe+0x49/0xb3
Quoted 361 lines
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* {igt@gem_exec_reloc@basic-concurrent16}:
- shard-snb: [FAIL][5] ([i915#1930]) -> [TIMEOUT][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[6]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/ig
t@[email protected]* {igt@kms_chamelium@vga-hpd-enable-disable-mode}:
- shard-snb: [SKIP][7] ([fdo#109271] / [fdo#111827]) -> [TIMEOUT][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[8]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/ig
t@[email protected]Known issues
------------Here are the changes found in
Patchwork_17882_fullthat come from known issues:### IGT changes ###
#### Issues hit ####
* igt@gem_exec_whisper@basic-forked-all:
- shard-glk: [PASS][9] -> [DMESG-WARN][10] ([i915#118] / [i915#95])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk7/igt@[email protected]
[10]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk2/ig
t@[email protected]* igt@gem_mmap_gtt@cpuset-big-copy-odd:
- shard-iclb: [PASS][11] -> [DMESG-WARN][12] ([i915#1982])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@[email protected]
[12]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/i
gt@[email protected]* igt@gem_workarounds@suspend-resume:
- shard-apl: [PASS][13] -> [DMESG-WARN][14] ([i915#180])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@[email protected]
[14]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/ig
t@[email protected]* igt@kms_big_fb@linear-32bpp-rotate-180:
- shard-skl: [PASS][15] -> [DMESG-WARN][16] ([i915#1982]) +9 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[16]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl5/ig
t@[email protected]* igt@kms_big_fb@linear-64bpp-rotate-180:
- shard-glk: [PASS][17] -> [DMESG-FAIL][18] ([i915#118] / [i915#95]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk2/igt@[email protected]
[18]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk8/ig
t@[email protected]* igt@kms_big_fb@x-tiled-16bpp-rotate-0:
- shard-glk: [PASS][19] -> [DMESG-WARN][20] ([i915#1982])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk5/igt@[email protected]
[20]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk4/ig
t@[email protected]* igt@kms_cursor_crc@pipe-c-cursor-256x85-offscreen:
- shard-apl: [PASS][21] -> [DMESG-WARN][22] ([i915#95]) +17 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl4/igt@[email protected]
[22]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl8/ig
t@[email protected]* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [PASS][23] -> [DMESG-WARN][24] ([i915#180]) +4 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[24]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/ig
t@[email protected]* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move:
- shard-kbl: [PASS][25] -> [DMESG-WARN][26] ([i915#93] / [i915#95])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[26]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl1/ig
t@[email protected]* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-cpu:
- shard-skl: [PASS][27] -> [FAIL][28] ([i915#49])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl9/igt@[email protected]
[28]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl9/ig
t@[email protected]* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:
- shard-skl: [PASS][29] -> [FAIL][30] ([fdo#108145] / [i915#265]) +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[30]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl2/ig
t@[email protected]* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-snb: [PASS][31] -> [SKIP][32] ([fdo#109271]) +1 similar issue
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb2/igt@[email protected]
[32]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/ig
t@[email protected]* igt@kms_psr@psr2_cursor_blt:
- shard-iclb: [PASS][33] -> [SKIP][34] ([fdo#109441]) +3 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb2/igt@kms_psr@psr2_cursor_blt.html
[34]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb4/i
gt@kms_psr@psr2_cursor_blt.html* igt@kms_universal_plane@universal-plane-gen9-features-pipe-c:
- shard-kbl: [PASS][35] -> [DMESG-WARN][36] ([i915#1982])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[36]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/ig
t@[email protected]* igt@syncobj_wait@invalid-multi-wait-unsubmitted-submitted:
- shard-tglb: [PASS][37] -> [DMESG-WARN][38] ([i915#402])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-tglb6/igt@[email protected]
[38]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-tglb7/i
gt@[email protected]#### Possible fixes ####
* {igt@gem_ctx_isolation@preservation-s3@rcs0}:
- shard-apl: [DMESG-WARN][39] ([i915#180]) -> [PASS][40] +2 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@gem_ctx_isolation@[email protected]
[40]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/ig
t@gem_ctx_isolation@[email protected]* igt@gem_exec_whisper@basic-queues-forked-all:
- shard-glk: [DMESG-WARN][41] ([i915#118] / [i915#95]) -> [PASS][42] +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk9/igt@[email protected]
[42]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk9/ig
t@[email protected]* igt@gen9_exec_parse@allowed-all:
- shard-kbl: [DMESG-WARN][43] ([i915#1436] / [i915#716]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl1/igt@[email protected]
[44]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/ig
t@[email protected]* igt@i915_suspend@debugfs-reader:
- shard-kbl: [INCOMPLETE][45] ([i915#155]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[46]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl6/ig
t@[email protected]* igt@kms_color@pipe-c-ctm-red-to-blue:
- shard-kbl: [DMESG-WARN][47] ([i915#93] / [i915#95]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[48]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl7/ig
t@[email protected]* igt@kms_color@pipe-d-ctm-0-5:
- shard-tglb: [DMESG-WARN][49] ([i915#1149] / [i915#402]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-tglb2/igt@[email protected]
[50]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-tglb1/i
gt@[email protected]* igt@kms_cursor_legacy@all-pipes-torture-move:
- shard-skl: [DMESG-WARN][51] ([i915#128]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl10/igt@[email protected]
[52]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl3/ig
t@[email protected]* {igt@kms_flip@2x-flip-vs-suspend@ab-hdmi-a1-hdmi-a2}:
- shard-glk: [DMESG-WARN][53] ([i915#1982]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk6/igt@kms_flip@[email protected]
[54]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk8/ig
t@kms_flip@[email protected]* igt@kms_flip_tiling@flip-x-tiled:
- shard-apl: [DMESG-WARN][55] ([i915#95]) -> [PASS][56] +26 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl7/igt@[email protected]
[56]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/ig
t@[email protected]* igt@kms_hdr@bpc-switch-suspend:
- shard-skl: [FAIL][57] ([i915#1188]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl10/igt@[email protected]
[58]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl3/ig
t@[email protected]* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- shard-kbl: [DMESG-WARN][59] ([i915#180]) -> [PASS][60] +3 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[60]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/ig
t@[email protected]* igt@kms_plane@plane-panning-bottom-right-pipe-c-planes:
- shard-skl: [DMESG-WARN][61] ([i915#1982]) -> [PASS][62] +2 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[62]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl5/ig
t@[email protected]* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [SKIP][63] ([fdo#109441]) -> [PASS][64] +2 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@kms_psr@psr2_primary_mmap_cpu.html
[64]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/i
gt@kms_psr@psr2_primary_mmap_cpu.html* igt@kms_setmode@basic:
- shard-apl: [FAIL][65] ([i915#31]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl6/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/igt@[email protected]
- shard-kbl: [FAIL][67] ([i915#31]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl6/igt@[email protected]
[68]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/ig
t@[email protected]* {igt@perf@polling-parameterized}:
- shard-hsw: [FAIL][69] ([i915#1542]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-hsw6/igt@[email protected]
[70]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-hsw5/ig
t@[email protected]#### Warnings ####
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-snb: [SKIP][71] ([fdo#109271]) -> [INCOMPLETE][72] ([i915#82]) +1 similar issue
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb2/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb5/igt@[email protected]
- shard-iclb: [SKIP][73] ([i915#658]) -> [SKIP][74] ([i915#588])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@[email protected]
[74]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/i
gt@[email protected]* igt@kms_content_protection@atomic:
- shard-apl: [FAIL][75] ([fdo#110321] / [fdo#110336]) -> [TIMEOUT][76] ([i915#1319] / [i915#1635])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl6/igt@[email protected]
[76]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/ig
t@[email protected]* igt@kms_content_protection@legacy:
- shard-kbl: [DMESG-FAIL][77] ([fdo#110321]) -> [TIMEOUT][78] ([i915#1319] / [i915#1958])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[78]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/ig
t@[email protected]* igt@kms_content_protection@lic:
- shard-apl: [DMESG-FAIL][79] ([fdo#110321] / [i915#95]) -> [TIMEOUT][80] ([i915#1319] / [i915#1635]) +1 similar issue
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@[email protected]
[80]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/ig
t@[email protected]* igt@kms_content_protection@srm:
- shard-kbl: [DMESG-FAIL][81] ([fdo#110321] / [i915#95]) -> [TIMEOUT][82] ([i915#1319])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[82]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/ig
t@[email protected]* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [DMESG-WARN][83] ([i915#180] / [i915#93] / [i915#95]) -> [DMESG-WARN][84] ([i915#93] / [i915#95])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl7/igt@[email protected]
- shard-apl: [DMESG-WARN][85] ([i915#180] / [i915#95]) -> [DMESG-WARN][86] ([i915#95])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl4/igt@[email protected]
[86]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl8/ig
t@[email protected]* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [DMESG-WARN][87] ([i915#1982]) -> [DMESG-FAIL][88] ([fdo#108145] / [i915#1982])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl2/igt@[email protected]
[88]:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl2/ig
t@[email protected]{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1149]: https://gitlab.freedesktop.org/drm/intel/issues/1149
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#128]: https://gitlab.freedesktop.org/drm/intel/issues/128
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1928]: https://gitlab.freedesktop.org/drm/intel/issues/1928
[i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#46]: https://gitlab.freedesktop.org/drm/intel/issues/46
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#588]: https://gitlab.freedesktop.org/drm/intel/issues/588
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95Participating hosts (11 -> 11)
------------------------------No changes in participating hosts
Build changes
-------------* Linux:
CI_DRM_8590->Patchwork_17882CI-20190529: 20190529
CI_DRM_8590:91c6f0274b54c89679cd23f6fc65e9fe5922971f@git://anongit.freedesktop.org/gfx-ci/linux
IGT_5695:53e8c878a6fb5708e63c99403691e8960b86ea9c@git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17882:23fe5e3ae83585e3d4ad9ecdfea368dd42ff6dfb@git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509:fdc5a4ca11124ab8413c7988896eec4c97336694@git://anongit.freedesktop.org/piglit
Quoted 4 lines
== Logs ==
For more details see:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/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
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [RESEND,v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev6)
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: series starting with [RESEND,v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev6)
URL : https://patchwork.freedesktop.org/series/77969/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8590_full -> Patchwork_17882_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_17882_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_whisper@basic-forked-all:
- shard-glk: [PASS][1] -> [DMESG-WARN][2] ([i915#118] / [i915#95])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk7/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk2/igt@[email protected]
* igt@gem_mmap_gtt@cpuset-big-copy-odd:
- shard-iclb: [PASS][3] -> [DMESG-WARN][4] ([i915#1982])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/igt@[email protected]
* igt@gem_workarounds@suspend-resume:
- shard-apl: [PASS][5] -> [DMESG-WARN][6] ([i915#180])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/igt@[email protected]
* igt@kms_big_fb@linear-32bpp-rotate-180:
- shard-skl: [PASS][7] -> [DMESG-WARN][8] ([i915#1982]) +9 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl5/igt@[email protected]
* igt@kms_big_fb@linear-64bpp-rotate-180:
- shard-glk: [PASS][9] -> [DMESG-FAIL][10] ([i915#118] / [i915#95]) +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk2/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk8/igt@[email protected]
* igt@kms_big_fb@x-tiled-16bpp-rotate-0:
- shard-glk: [PASS][11] -> [DMESG-WARN][12] ([i915#1982])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk5/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk4/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-256x85-offscreen:
- shard-apl: [PASS][13] -> [DMESG-WARN][14] ([i915#95]) +17 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl4/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl8/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [PASS][15] -> [DMESG-WARN][16] ([i915#180]) +4 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/igt@[email protected]
* igt@kms_draw_crc@draw-method-rgb565-mmap-gtt-xtiled:
- shard-snb: [PASS][17] -> [TIMEOUT][18] ([i915#1958])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move:
- shard-kbl: [PASS][19] -> [DMESG-WARN][20] ([i915#93] / [i915#95])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl1/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-cpu:
- shard-skl: [PASS][21] -> [FAIL][22] ([i915#49])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl9/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl9/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:
- shard-skl: [PASS][23] -> [FAIL][24] ([fdo#108145] / [i915#265]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl2/igt@[email protected]
* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-snb: [PASS][25] -> [SKIP][26] ([fdo#109271]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb2/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]
* igt@kms_psr@psr2_cursor_blt:
- shard-iclb: [PASS][27] -> [SKIP][28] ([fdo#109441]) +3 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb2/igt@kms_psr@psr2_cursor_blt.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb4/igt@kms_psr@psr2_cursor_blt.html
* igt@kms_universal_plane@universal-plane-gen9-features-pipe-c:
- shard-kbl: [PASS][29] -> [DMESG-WARN][30] ([i915#1982])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/igt@[email protected]
* igt@syncobj_wait@invalid-multi-wait-unsubmitted-submitted:
- shard-tglb: [PASS][31] -> [DMESG-WARN][32] ([i915#402])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-tglb6/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-tglb7/igt@[email protected]
#### Possible fixes ####
* {igt@gem_ctx_isolation@preservation-s3@rcs0}:
- shard-apl: [DMESG-WARN][33] ([i915#180]) -> [PASS][34] +2 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@gem_ctx_isolation@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/igt@gem_ctx_isolation@[email protected]
* igt@gem_exec_whisper@basic-queues-forked-all:
- shard-glk: [DMESG-WARN][35] ([i915#118] / [i915#95]) -> [PASS][36] +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk9/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk9/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-kbl: [DMESG-WARN][37] ([i915#1436] / [i915#716]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl1/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]
* igt@i915_suspend@debugfs-reader:
- shard-kbl: [INCOMPLETE][39] ([i915#155]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl6/igt@[email protected]
* igt@kms_color@pipe-c-ctm-red-to-blue:
- shard-kbl: [DMESG-WARN][41] ([i915#93] / [i915#95]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl7/igt@[email protected]
* igt@kms_color@pipe-d-ctm-0-5:
- shard-tglb: [DMESG-WARN][43] ([i915#1149] / [i915#402]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-tglb2/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-tglb1/igt@[email protected]
* igt@kms_cursor_legacy@all-pipes-torture-move:
- shard-skl: [DMESG-WARN][45] ([i915#128]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl10/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl3/igt@[email protected]
* {igt@kms_flip@2x-flip-vs-suspend@ab-hdmi-a1-hdmi-a2}:
- shard-glk: [DMESG-WARN][47] ([i915#1982]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk6/igt@kms_flip@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk8/igt@kms_flip@[email protected]
* igt@kms_flip_tiling@flip-x-tiled:
- shard-apl: [DMESG-WARN][49] ([i915#95]) -> [PASS][50] +26 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl7/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/igt@[email protected]
* igt@kms_hdr@bpc-switch-suspend:
- shard-skl: [FAIL][51] ([i915#1188]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl10/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl3/igt@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- shard-kbl: [DMESG-WARN][53] ([i915#180]) -> [PASS][54] +3 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]
* igt@kms_plane@plane-panning-bottom-right-pipe-c-planes:
- shard-skl: [DMESG-WARN][55] ([i915#1982]) -> [PASS][56] +2 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl5/igt@[email protected]
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [SKIP][57] ([fdo#109441]) -> [PASS][58] +2 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@kms_psr@psr2_primary_mmap_cpu.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_setmode@basic:
- shard-apl: [FAIL][59] ([i915#31]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl6/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/igt@[email protected]
- shard-kbl: [FAIL][61] ([i915#31]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl6/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]
* {igt@perf@polling-parameterized}:
- shard-hsw: [FAIL][63] ([i915#1542]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-hsw6/igt@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-hsw5/igt@[email protected]
#### Warnings ####
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-snb: [SKIP][65] ([fdo#109271]) -> [INCOMPLETE][66] ([i915#82]) +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb2/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb5/igt@[email protected]
- shard-iclb: [SKIP][67] ([i915#658]) -> [SKIP][68] ([i915#588])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/igt@[email protected]
* igt@kms_content_protection@atomic:
- shard-apl: [FAIL][69] ([fdo#110321] / [fdo#110336]) -> [TIMEOUT][70] ([i915#1319] / [i915#1635])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl6/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/igt@[email protected]
* igt@kms_content_protection@legacy:
- shard-kbl: [DMESG-FAIL][71] ([fdo#110321]) -> [TIMEOUT][72] ([i915#1319] / [i915#1958])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-apl: [DMESG-FAIL][73] ([fdo#110321] / [i915#95]) -> [TIMEOUT][74] ([i915#1319] / [i915#1635]) +1 similar issue
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/igt@[email protected]
* igt@kms_content_protection@srm:
- shard-kbl: [DMESG-FAIL][75] ([fdo#110321] / [i915#95]) -> [TIMEOUT][76] ([i915#1319])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [DMESG-WARN][77] ([i915#180] / [i915#93] / [i915#95]) -> [DMESG-WARN][78] ([i915#93] / [i915#95])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl7/igt@[email protected]
- shard-apl: [DMESG-WARN][79] ([i915#180] / [i915#95]) -> [DMESG-WARN][80] ([i915#95])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl4/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl8/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [DMESG-WARN][81] ([i915#1982]) -> [DMESG-FAIL][82] ([fdo#108145] / [i915#1982])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl2/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl2/igt@[email protected]
* igt@kms_plane_scaling@pipe-b-scaler-with-clipping-clamping:
- shard-snb: [SKIP][83] ([fdo#109271]) -> [TIMEOUT][84] ([i915#1958]) +1 similar issue
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1149]: https://gitlab.freedesktop.org/drm/intel/issues/1149
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#128]: https://gitlab.freedesktop.org/drm/intel/issues/128
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1928]: https://gitlab.freedesktop.org/drm/intel/issues/1928
[i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#46]: https://gitlab.freedesktop.org/drm/intel/issues/46
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#588]: https://gitlab.freedesktop.org/drm/intel/issues/588
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_8590 -> Patchwork_17882
CI-20190529: 20190529
CI_DRM_8590: 91c6f0274b54c89679cd23f6fc65e9fe5922971f @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5695: 53e8c878a6fb5708e63c99403691e8960b86ea9c @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17882: 23fe5e3ae83585e3d4ad9ecdfea368dd42ff6dfb @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: ✓ Fi.CI.IGT: success for series starting with [RESEND,v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev6)
Quoted 5 lines · Patchwork
== Series Details ==
Series: series starting with [RESEND,v3,1/3] drm/i915/dp_mst: Fix disabling MST on a port (rev6)
URL : https://patchwork.freedesktop.org/series/77969/
State : success
Thanks for the reviews, pushed patch 1 to -dinq and patches 2,3 to drm-misc-next.
Quoted 289 lines
== Summary ==
CI Bug Log - changes from
CI_DRM_8590_full->Patchwork_17882_full
====================================================Summary
-------**SUCCESS**
No regressions found.
Known issues
------------Here are the changes found in
Patchwork_17882_fullthat come from known issues:### IGT changes ###
#### Issues hit ####
* igt@gem_exec_whisper@basic-forked-all:
- shard-glk: [PASS][1] -> [DMESG-WARN][2] ([i915#118] / [i915#95])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk7/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk2/igt@[email protected]* igt@gem_mmap_gtt@cpuset-big-copy-odd:
- shard-iclb: [PASS][3] -> [DMESG-WARN][4] ([i915#1982])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/igt@[email protected]* igt@gem_workarounds@suspend-resume:
- shard-apl: [PASS][5] -> [DMESG-WARN][6] ([i915#180])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/igt@[email protected]* igt@kms_big_fb@linear-32bpp-rotate-180:
- shard-skl: [PASS][7] -> [DMESG-WARN][8] ([i915#1982]) +9 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl5/igt@[email protected]* igt@kms_big_fb@linear-64bpp-rotate-180:
- shard-glk: [PASS][9] -> [DMESG-FAIL][10] ([i915#118] / [i915#95]) +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk2/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk8/igt@[email protected]* igt@kms_big_fb@x-tiled-16bpp-rotate-0:
- shard-glk: [PASS][11] -> [DMESG-WARN][12] ([i915#1982])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk5/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk4/igt@[email protected]* igt@kms_cursor_crc@pipe-c-cursor-256x85-offscreen:
- shard-apl: [PASS][13] -> [DMESG-WARN][14] ([i915#95]) +17 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl4/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl8/igt@[email protected]* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [PASS][15] -> [DMESG-WARN][16] ([i915#180]) +4 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/igt@[email protected]* igt@kms_draw_crc@draw-method-rgb565-mmap-gtt-xtiled:
- shard-snb: [PASS][17] -> [TIMEOUT][18] ([i915#1958])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move:
- shard-kbl: [PASS][19] -> [DMESG-WARN][20] ([i915#93] / [i915#95])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl1/igt@[email protected]* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-cpu:
- shard-skl: [PASS][21] -> [FAIL][22] ([i915#49])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl9/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl9/igt@[email protected]* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min:
- shard-skl: [PASS][23] -> [FAIL][24] ([fdo#108145] / [i915#265]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl2/igt@[email protected]* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-snb: [PASS][25] -> [SKIP][26] ([fdo#109271]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb2/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]* igt@kms_psr@psr2_cursor_blt:
- shard-iclb: [PASS][27] -> [SKIP][28] ([fdo#109441]) +3 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb2/igt@kms_psr@psr2_cursor_blt.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb4/igt@kms_psr@psr2_cursor_blt.html* igt@kms_universal_plane@universal-plane-gen9-features-pipe-c:
- shard-kbl: [PASS][29] -> [DMESG-WARN][30] ([i915#1982])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/igt@[email protected]* igt@syncobj_wait@invalid-multi-wait-unsubmitted-submitted:
- shard-tglb: [PASS][31] -> [DMESG-WARN][32] ([i915#402])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-tglb6/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-tglb7/igt@[email protected]#### Possible fixes ####
* {igt@gem_ctx_isolation@preservation-s3@rcs0}:
- shard-apl: [DMESG-WARN][33] ([i915#180]) -> [PASS][34] +2 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@gem_ctx_isolation@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/igt@gem_ctx_isolation@[email protected]* igt@gem_exec_whisper@basic-queues-forked-all:
- shard-glk: [DMESG-WARN][35] ([i915#118] / [i915#95]) -> [PASS][36] +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk9/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk9/igt@[email protected]* igt@gen9_exec_parse@allowed-all:
- shard-kbl: [DMESG-WARN][37] ([i915#1436] / [i915#716]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl1/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]* igt@i915_suspend@debugfs-reader:
- shard-kbl: [INCOMPLETE][39] ([i915#155]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl6/igt@[email protected]* igt@kms_color@pipe-c-ctm-red-to-blue:
- shard-kbl: [DMESG-WARN][41] ([i915#93] / [i915#95]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl7/igt@[email protected]* igt@kms_color@pipe-d-ctm-0-5:
- shard-tglb: [DMESG-WARN][43] ([i915#1149] / [i915#402]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-tglb2/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-tglb1/igt@[email protected]* igt@kms_cursor_legacy@all-pipes-torture-move:
- shard-skl: [DMESG-WARN][45] ([i915#128]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl10/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl3/igt@[email protected]* {igt@kms_flip@2x-flip-vs-suspend@ab-hdmi-a1-hdmi-a2}:
- shard-glk: [DMESG-WARN][47] ([i915#1982]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-glk6/igt@kms_flip@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-glk8/igt@kms_flip@[email protected]* igt@kms_flip_tiling@flip-x-tiled:
- shard-apl: [DMESG-WARN][49] ([i915#95]) -> [PASS][50] +26 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl7/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/igt@[email protected]* igt@kms_hdr@bpc-switch-suspend:
- shard-skl: [FAIL][51] ([i915#1188]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl10/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl3/igt@[email protected]* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- shard-kbl: [DMESG-WARN][53] ([i915#180]) -> [PASS][54] +3 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]* igt@kms_plane@plane-panning-bottom-right-pipe-c-planes:
- shard-skl: [DMESG-WARN][55] ([i915#1982]) -> [PASS][56] +2 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl6/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl5/igt@[email protected]* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [SKIP][57] ([fdo#109441]) -> [PASS][58] +2 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@kms_psr@psr2_primary_mmap_cpu.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html* igt@kms_setmode@basic:
- shard-apl: [FAIL][59] ([i915#31]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl6/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/igt@[email protected]
- shard-kbl: [FAIL][61] ([i915#31]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl6/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]* {igt@perf@polling-parameterized}:
- shard-hsw: [FAIL][63] ([i915#1542]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-hsw6/igt@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-hsw5/igt@[email protected]#### Warnings ####
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-snb: [SKIP][65] ([fdo#109271]) -> [INCOMPLETE][66] ([i915#82]) +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb2/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb5/igt@[email protected]
- shard-iclb: [SKIP][67] ([i915#658]) -> [SKIP][68] ([i915#588])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-iclb6/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-iclb2/igt@[email protected]* igt@kms_content_protection@atomic:
- shard-apl: [FAIL][69] ([fdo#110321] / [fdo#110336]) -> [TIMEOUT][70] ([i915#1319] / [i915#1635])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl6/igt@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl3/igt@[email protected]* igt@kms_content_protection@legacy:
- shard-kbl: [DMESG-FAIL][71] ([fdo#110321]) -> [TIMEOUT][72] ([i915#1319] / [i915#1958])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl3/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl4/igt@[email protected]* igt@kms_content_protection@lic:
- shard-apl: [DMESG-FAIL][73] ([fdo#110321] / [i915#95]) -> [TIMEOUT][74] ([i915#1319] / [i915#1635]) +1 similar issue
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl2/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl1/igt@[email protected]* igt@kms_content_protection@srm:
- shard-kbl: [DMESG-FAIL][75] ([fdo#110321] / [i915#95]) -> [TIMEOUT][76] ([i915#1319])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl2/igt@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl3/igt@[email protected]* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [DMESG-WARN][77] ([i915#180] / [i915#93] / [i915#95]) -> [DMESG-WARN][78] ([i915#93] / [i915#95])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-kbl7/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-kbl7/igt@[email protected]
- shard-apl: [DMESG-WARN][79] ([i915#180] / [i915#95]) -> [DMESG-WARN][80] ([i915#95])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-apl4/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-apl8/igt@[email protected]* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [DMESG-WARN][81] ([i915#1982]) -> [DMESG-FAIL][82] ([fdo#108145] / [i915#1982])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-skl2/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-skl2/igt@[email protected]* igt@kms_plane_scaling@pipe-b-scaler-with-clipping-clamping:
- shard-snb: [SKIP][83] ([fdo#109271]) -> [TIMEOUT][84] ([i915#1958]) +1 similar issue
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8590/shard-snb6/igt@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/shard-snb1/igt@[email protected]{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1149]: https://gitlab.freedesktop.org/drm/intel/issues/1149
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#128]: https://gitlab.freedesktop.org/drm/intel/issues/128
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1635]: https://gitlab.freedesktop.org/drm/intel/issues/1635
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1928]: https://gitlab.freedesktop.org/drm/intel/issues/1928
[i915#1930]: https://gitlab.freedesktop.org/drm/intel/issues/1930
[i915#1958]: https://gitlab.freedesktop.org/drm/intel/issues/1958
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#46]: https://gitlab.freedesktop.org/drm/intel/issues/46
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#588]: https://gitlab.freedesktop.org/drm/intel/issues/588
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#82]: https://gitlab.freedesktop.org/drm/intel/issues/82
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95Participating hosts (11 -> 11)
------------------------------No changes in participating hosts
Build changes
-------------* Linux:
CI_DRM_8590->Patchwork_17882CI-20190529: 20190529
CI_DRM_8590:91c6f0274b54c89679cd23f6fc65e9fe5922971f@git://anongit.freedesktop.org/gfx-ci/linux
IGT_5695:53e8c878a6fb5708e63c99403691e8960b86ea9c@git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17882:23fe5e3ae83585e3d4ad9ecdfea368dd42ff6dfb@git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509:fdc5a4ca11124ab8413c7988896eec4c97336694@git://anongit.freedesktop.org/piglit
Quoted 3 lines
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17882/index.html
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel