Introduce DRM device wedged event
Subsystems (5)
v7 cover Introduce DRM device wedged event
This series introduces device wedged event in DRM subsystem and uses it in xe and i915 drivers. Detailed description in commit message.
This was earlier attempted as xe specific uevent in v1 and v2.
https://patchwork.freedesktop.org/series/136909/
v2: Change authorship to Himal (Aravind)
Add uevent for all device wedged cases (Aravind)
v3: Generic re-implementation in DRM subsystem (Lucas)
v4: s/drm_dev_wedged/drm_dev_wedged_event
Use drm_info() (Jani)
Kernel doc adjustment (Aravind)
Change authorship to Raag (Aravind)
v5: Send recovery method with uevent (Lina)
Expose supported recovery methods via sysfs (Lucas)
v6: Access wedge_recovery_opts[] using helper function (Jani)
Use snprintf() (Jani)
v7: Convert recovery helpers into regular functions (Andy, Jani)
Aesthetic adjustments (Andy)
Handle invalid method cases
Add documentation to drm-uapi.rst (Sima)
Raag Jadav (5):
drm: Introduce device wedged event
drm: Expose wedge recovery methods
drm/doc: Document device wedged event
drm/xe: Use device wedged event
drm/i915: Use device wedged event
Documentation/gpu/drm-uapi.rst | 42 +++++++++++++++ drivers/gpu/drm/drm_drv.c | 77 +++++++++++++++++++++++++++ drivers/gpu/drm/drm_sysfs.c | 22 ++++++++ drivers/gpu/drm/i915/gt/intel_reset.c | 2 + drivers/gpu/drm/i915/i915_driver.c | 10 ++++ drivers/gpu/drm/xe/xe_device.c | 17 +++++- drivers/gpu/drm/xe/xe_device.h | 1 + drivers/gpu/drm/xe/xe_pci.c | 2 + include/drm/drm_device.h | 23 ++++++++ include/drm/drm_drv.h | 3 ++ 10 files changed, 197 insertions(+), 2 deletions(-)
Signature · 1 line
2.34.1
PATCH v7 1/5 drm: Introduce device wedged event
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================
v4: s/drm_dev_wedged/drm_dev_wedged_event
Use drm_info() (Jani)
Kernel doc adjustment (Aravind)
v5: Send recovery method with uevent (Lina)
v6: Access wedge_recovery_opts[] using helper function (Jani)
Use snprintf() (Jani)
v7: Convert recovery helpers into regular functions (Andy, Jani)
Aesthetic adjustments (Andy)
Handle invalid method cases
--- drivers/gpu/drm/drm_drv.c | 77 +++++++++++++++++++++++++++++++++++++++ include/drm/drm_device.h | 23 ++++++++++++ include/drm/drm_drv.h | 3 ++ 3 files changed, 103 insertions(+)
drivers/gpu/drm/drm_drv.c +77 -0
@@ -26,6 +26,8 @@* DEALINGS IN THE SOFTWARE. */ +#include <linux/array_size.h> +#include <linux/build_bug.h> #include <linux/debugfs.h> #include <linux/fs.h> #include <linux/module.h>
@@ -33,6 +35,7 @@#include <linux/mount.h> #include <linux/pseudo_fs.h> #include <linux/slab.h> +#include <linux/sprintf.h> #include <linux/srcu.h> #include <linux/xarray.h>
@@ -70,6 +73,42 @@ static struct dentry *drm_debugfs_root;DEFINE_STATIC_SRCU (drm_unplug_srcu); +/* +* Available recovery methods for wedged device. To be sent along with device +* wedged uevent. +*/ +static const char *const drm_wedge_recovery_opts[] = { + [DRM_WEDGE_RECOVERY_REBIND ] ="rebind" , + [DRM_WEDGE_RECOVERY_BUS_RESET ] ="bus-reset" , + [DRM_WEDGE_RECOVERY_REBOOT ] ="reboot" , +}; + +static bool drm_wedge_recovery_is_valid (enum drm_wedge_recovery method) +{ +static_assert (ARRAY_SIZE (drm_wedge_recovery_opts) ==DRM_WEDGE_RECOVERY_MAX ); + +return method >=DRM_WEDGE_RECOVERY_REBIND && method <DRM_WEDGE_RECOVERY_MAX ; +} + +/** +* drm_wedge_recovery_name - provide wedge recovery name +* @method: method to be used for recovery +* +* This validates wedge recovery @method against the available ones in +* drm_wedge_recovery_opts[] and provides respective recovery name in string +* format if found valid. +* +* Returns: pointer to const recovery string on success, NULL otherwise. +*/ +const char *drm_wedge_recovery_name (enum drm_wedge_recovery method) +{ +if (drm_wedge_recovery_is_valid (method)) +return drm_wedge_recovery_opts[method]; + +return NULL ; +} +EXPORT_SYMBOL (drm_wedge_recovery_name); +/* * DRM Minors * A DRM device can provide several char-dev interfaces on the DRM-Major. Each
@@ -497,6 +536,44 @@ void drm_dev_unplug(struct drm_device *dev) }EXPORT_SYMBOL (drm_dev_unplug); +/** +* drm_dev_wedged_event - generate a device wedged uevent +* @dev: DRM device +* @method: method to be used for recovery +* +* This generates a device wedged uevent for the DRM device specified by @dev. +* Recovery @method from drm_wedge_recovery_opts[] (if supprted by the device) +* is sent in the uevent environment as WEDGED=<method>, on the basis of which, +* userspace may take respective action to recover the device. +* +* Returns: 0 on success, or negative error code otherwise. +*/ +int drm_dev_wedged_event (struct drm_device *dev,enum drm_wedge_recovery method) +{ +/* Event string length up to 16+ characters with available methods */ +char event_string[32 ] = {}; +char *envp[] = { event_string,NULL }; +const char *recovery; + + recovery =drm_wedge_recovery_name (method); +if (!recovery) { +drm_err (dev,"device wedged, invalid recovery method %d\n" , method); +return -EINVAL ; + } + +if (!test_bit (method, &dev->wedge_recovery)) { +drm_err (dev,"device wedged, %s based recovery not supported\n" , +drm_wedge_recovery_name (method)); +return -EOPNOTSUPP ; + } + +snprintf (event_string,sizeof (event_string),"WEDGED=%s" , recovery); + +drm_info (dev,"device wedged, generating uevent for %s based recovery\n" , recovery); +return kobject_uevent_env (&dev->primary->kdev->kobj,KOBJ_CHANGE , envp); +} +EXPORT_SYMBOL (drm_dev_wedged_event); +/* * DRM internal mount * We want to be able to allocate our own "struct address_space" to control
include/drm/drm_device.h +23 -0
@@ -40,6 +40,26 @@ enum switch_power_state { DRM_SWITCH_POWER_DYNAMIC_OFF = 3, }; +/** +* enum drm_wedge_recovery - Recovery method for wedged device in order of +* severity. To be set as bit fields in drm_device.wedge_recovery variable. +* Drivers can choose to support any one or multiple of them depending on +* their needs. +*/ +enum drm_wedge_recovery { +/** @DRM_WEDGE_RECOVERY_REBIND: unbind + rebind driver */ +DRM_WEDGE_RECOVERY_REBIND , + +/** @DRM_WEDGE_RECOVERY_BUS_RESET: unbind + reset bus device + rebind */ +DRM_WEDGE_RECOVERY_BUS_RESET , + +/** @DRM_WEDGE_RECOVERY_REBOOT: reboot system */ +DRM_WEDGE_RECOVERY_REBOOT , + +/** @DRM_WEDGE_RECOVERY_MAX: for bounds checking, do not use */ +DRM_WEDGE_RECOVERY_MAX +}; +/** * struct drm_device - DRM device structure *
@@ -317,6 +337,9 @@ struct drm_device {* Root directory for debugfs files. */ struct dentry *debugfs_root; + +/** @wedge_recovery: Supported recovery methods for wedged device */ + unsigned long wedge_recovery; };#endif
include/drm/drm_drv.h +3 -0
@@ -462,6 +462,9 @@ bool drm_dev_enter(struct drm_device *dev, int *idx);void drm_dev_exit (int idx);void drm_dev_unplug (struct drm_device *dev); +const char *drm_wedge_recovery_name (enum drm_wedge_recovery method); +int drm_dev_wedged_event (struct drm_device *dev,enum drm_wedge_recovery method); +/** * drm_dev_is_unplugged - is a DRM device unplugged * @dev: DRM device
Signature · 1 line
2.34.1
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 26 lines · Raag Jadav
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================
...
drivers/gpu/drm/drm_drv.c static struct dentry *drm_debugfs_root; · line 84
Quoted 9 lines
drivers/gpu/drm/drm_drv.c +9
-0+/* +* Available recovery methods for wedged device. To be sent along with device +* wedged uevent. +*/ +static const char *const drm_wedge_recovery_opts[] = { + [DRM_WEDGE_RECOVERY_REBIND ] ="rebind" , + [DRM_WEDGE_RECOVERY_BUS_RESET ] ="bus-reset" , + [DRM_WEDGE_RECOVERY_REBOOT ] ="reboot" , +};
Place for static_assert() is here, as it closer to the actual data we test...
drivers/gpu/drm/drm_drv.c static struct dentry *drm_debugfs_root; · line 88
Quoted 3 lines
drivers/gpu/drm/drm_drv.c +3
-0+static bool drm_wedge_recovery_is_valid (enum drm_wedge_recovery method) +{ +static_assert (ARRAY_SIZE (drm_wedge_recovery_opts) ==DRM_WEDGE_RECOVERY_MAX );
...it doesn't fully belong to this function (or only to this function).
Review
Quoted 2 lines
(quoted diff) +2
-0+ return method >= DRM_WEDGE_RECOVERY_REBIND && method < DRM_WEDGE_RECOVERY_MAX; +}
Why do we need this one-liner (after above comment being addressed) as a separate function?
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 30 lines · Andy Shevchenko
Quoted 26 lines · Raag Jadav
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================...
Quoted 11 lines
drivers/gpu/drm/drm_drv.c static struct dentry *drm_debugfs_root; · line 84
Quoted 9 lines
drivers/gpu/drm/drm_drv.c +9
-0+/* +* Available recovery methods for wedged device. To be sent along with device +* wedged uevent. +*/ +static const char *const drm_wedge_recovery_opts[] = { + [DRM_WEDGE_RECOVERY_REBIND ] ="rebind" , + [DRM_WEDGE_RECOVERY_BUS_RESET ] ="bus-reset" , + [DRM_WEDGE_RECOVERY_REBOOT ] ="reboot" , +};Place for
static_assert()is here, as it closer to the actual data we test...
Shouldn't it be at the point of access?
If no, why do we care about the data when it's not being used?
Quoted 5 lines
drivers/gpu/drm/drm_drv.c static struct dentry *drm_debugfs_root; · line 88
Quoted 3 lines
drivers/gpu/drm/drm_drv.c +3
-0+static bool drm_wedge_recovery_is_valid (enum drm_wedge_recovery method) +{ +static_assert (ARRAY_SIZE (drm_wedge_recovery_opts) ==DRM_WEDGE_RECOVERY_MAX );...it doesn't fully belong to this function (or only to this function).
The purpose of having a helper is to have a single point of access, no?
Side note: It also goes well with is_valid() semantic IMHO.
Quoted 5 lines
Review
Quoted 2 lines
(quoted diff) +2
-0+ return method >= DRM_WEDGE_RECOVERY_REBIND && method < DRM_WEDGE_RECOVERY_MAX; +}Why do we need this one-liner (after above comment being addressed) as a separate function?
I'm not sure if I'm following you. Method is not a constant here, we'll get it on the stack.
Raag
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 2 lines · Raag Jadav
Quoted 1 line · Andy Shevchenko
On Mon, Sep 30, 2024 at 01:08:41PM +0530, Raag Jadav wrote:
...
Quoted 9 lines
Quoted 7 lines
drivers/gpu/drm/drm_drv.c static struct dentry *drm_debugfs_root; · line 84
Quoted 5 lines
drivers/gpu/drm/drm_drv.c +5
-0+static const char *const drm_wedge_recovery_opts[] = { + [DRM_WEDGE_RECOVERY_REBIND ] ="rebind" , + [DRM_WEDGE_RECOVERY_BUS_RESET ] ="bus-reset" , + [DRM_WEDGE_RECOVERY_REBOOT ] ="reboot" , +};Place for
static_assert()is here, as it closer to the actual data we test...Shouldn't it be at the point of access?
No, the idea of static_assert() is in word 'static', meaning it's allowed to be used in the global space.
Quoted 1 line
If no, why do we care about the data when it's not being used?
What does this suppose to mean? The assertion is for enforcing the boundaries that are defined by different means (constant of the size and real size of an array).
...
Quoted 7 lines
Quoted 5 lines
drivers/gpu/drm/drm_drv.c static struct dentry *drm_debugfs_root; · line 88
Quoted 3 lines
drivers/gpu/drm/drm_drv.c +3
-0+static bool drm_wedge_recovery_is_valid (enum drm_wedge_recovery method) +{ +static_assert (ARRAY_SIZE (drm_wedge_recovery_opts) ==DRM_WEDGE_RECOVERY_MAX );...it doesn't fully belong to this function (or only to this function).
The purpose of having a helper is to have a single point of access, no?
What single access you are talking about? It seems you are trying to solve non-existing issue. There is a function that is being used exactly once and it's a one-liner. There is no point to have it being separated (at least right now).
Quoted 1 line
Side note: It also goes well with
is_valid()semantic IMHO.
It doesn't matter at all, it's unrelated to the point.
Quoted 8 lines
Quoted 5 lines
Review
Quoted 2 lines
(quoted diff) +2
-0+ return method >= DRM_WEDGE_RECOVERY_REBIND && method < DRM_WEDGE_RECOVERY_MAX; +}Why do we need this one-liner (after above comment being addressed) as a separate function?
I'm not sure if I'm following you. Method is not a constant here, we'll get it on the stack.
I elaborated above.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 16 lines · Andy Shevchenko
Quoted 2 lines · Raag Jadav
Quoted 1 line · Andy Shevchenko
On Mon, Sep 30, 2024 at 01:08:41PM +0530, Raag Jadav wrote:
...
Quoted 9 lines
Quoted 7 lines
drivers/gpu/drm/drm_drv.c static struct dentry *drm_debugfs_root; · line 84
Quoted 5 lines
drivers/gpu/drm/drm_drv.c +5
-0+static const char *const drm_wedge_recovery_opts[] = { + [DRM_WEDGE_RECOVERY_REBIND ] ="rebind" , + [DRM_WEDGE_RECOVERY_BUS_RESET ] ="bus-reset" , + [DRM_WEDGE_RECOVERY_REBOOT ] ="reboot" , +};Place for
static_assert()is here, as it closer to the actual data we test...Shouldn't it be at the point of access?
Quoted 8 lines
No, the idea of
static_assert()is in word 'static', meaning it's allowed to be used in the global space.Quoted 1 line
If no, why do we care about the data when it's not being used?
What does this suppose to mean? The assertion is for enforcing the boundaries that are defined by different means (constant of the size and real size of an array).
The point was to simply not assert without an active user of the array, which is not the case now but may be possible with growing functionality in the future.
Raag
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 4 lines · Raag Jadav
Quoted 3 lines · Andy Shevchenko
Quoted 2 lines · Raag Jadav
Quoted 1 line · Andy Shevchenko
On Mon, Sep 30, 2024 at 01:08:41PM +0530, Raag Jadav wrote:
...
Quoted 13 lines
Quoted 13 lines
Quoted 9 lines
Quoted 7 lines
drivers/gpu/drm/drm_drv.c static struct dentry *drm_debugfs_root; · line 84
Quoted 5 lines
drivers/gpu/drm/drm_drv.c +5
-0+static const char *const drm_wedge_recovery_opts[] = { + [DRM_WEDGE_RECOVERY_REBIND ] ="rebind" , + [DRM_WEDGE_RECOVERY_BUS_RESET ] ="bus-reset" , + [DRM_WEDGE_RECOVERY_REBOOT ] ="reboot" , +};Place for
static_assert()is here, as it closer to the actual data we test...Shouldn't it be at the point of access?
No, the idea of
static_assert()is in word 'static', meaning it's allowed to be used in the global space.
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
If no, why do we care about the data when it's not being used?
What does this suppose to mean? The assertion is for enforcing the boundaries that are defined by different means (constant of the size and real size of an array).
The point was to simply not assert without an active user of the array, which is not the case now but may be possible with growing functionality in the future.
static_assert() is a compile-time check. How is it even related to this? So, i.o.w., you are contradicting yourself in this code: on one hand you want compile-time static checker, on the other you do not want it and rely on the usage of the function.
Possible solutions:
1) remove static_assert() completely;
2) move it as I said.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 23 lines · Andy Shevchenko
Quoted 4 lines · Raag Jadav
Quoted 3 lines · Andy Shevchenko
Quoted 2 lines · Raag Jadav
Quoted 1 line · Andy Shevchenko
On Mon, Sep 30, 2024 at 01:08:41PM +0530, Raag Jadav wrote:
...
Quoted 15 lines
Quoted 15 lines
Quoted 9 lines
Quoted 7 lines
drivers/gpu/drm/drm_drv.c static struct dentry *drm_debugfs_root; · line 84
Quoted 5 lines
drivers/gpu/drm/drm_drv.c +5
-0+static const char *const drm_wedge_recovery_opts[] = { + [DRM_WEDGE_RECOVERY_REBIND ] ="rebind" , + [DRM_WEDGE_RECOVERY_BUS_RESET ] ="bus-reset" , + [DRM_WEDGE_RECOVERY_REBOOT ] ="reboot" , +};Place for
static_assert()is here, as it closer to the actual data we test...Shouldn't it be at the point of access?
No, the idea of
static_assert()is in word 'static', meaning it's allowed to be used in the global space.Quoted 1 line
If no, why do we care about the data when it's not being used?
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
What does this suppose to mean? The assertion is for enforcing the boundaries that are defined by different means (constant of the size and real size of an array).
The point was to simply not assert without an active user of the array, which is not the case now but may be possible with growing functionality in the future.
static_assert()is a compile-time check. How is it even related to this?
Yes, I understand. Semantically it made more sense to me is all, since core helpers can always end up in config based ifdeffery.
Anyway, I'll update.
Raag
Re: [PATCH v7 1/5] drm: Introduce device wedged event
In reply to Raag JadavHi,
sorry for late comments,
Quoted 6 lines · Raag Jadav
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Quoted 6 lines
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
what about when driver just wants to tell that it is in unusable state, but recovery method is unknown or not possible?
Quoted 4 lines
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>.
could this be something like below instead:
WEDGED=<reason> RECOVERY=<method>[,<method>]
then driver will have a chance to tell what happen _and_ additionally provide a hint(s) how to recover from that situation
Quoted 9 lines
Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
btw, what if driver detects a really broken HW, or has no clue what will help here, shouldn't we have a "none" method?
Quoted 56 lines
=============== ==================================v4: s/drm_dev_wedged/drm_dev_wedged_event
Usedrm_info()(Jani)
Kernel doc adjustment (Aravind)
v5: Send recovery method with uevent (Lina)
v6: Access wedge_recovery_opts[] using helper function (Jani)
Usesnprintf()(Jani)
v7: Convert recovery helpers into regular functions (Andy, Jani)
Aesthetic adjustments (Andy)
Handle invalid method casesSigned-off-by Raag Jadav <[email protected]>--- drivers/gpu/drm/drm_drv.c | 77 +++++++++++++++++++++++++++++++++++++++ include/drm/drm_device.h | 23 ++++++++++++ include/drm/drm_drv.h | 3 ++ 3 files changed, 103 insertions(+)drivers/gpu/drm/drm_drv.c +15
-0@@ -26,6 +26,8 @@* DEALINGS IN THE SOFTWARE. */ +#include <linux/array_size.h> +#include <linux/build_bug.h> #include <linux/debugfs.h> #include <linux/fs.h> #include <linux/module.h> @@ -33,6 +35,7 @@#include <linux/mount.h> #include <linux/pseudo_fs.h> #include <linux/slab.h> +#include <linux/sprintf.h> #include <linux/srcu.h> #include <linux/xarray.h> @@ -70,6 +73,42 @@ static struct dentry *drm_debugfs_root;DEFINE_STATIC_SRCU (drm_unplug_srcu); +/* +* Available recovery methods for wedged device. To be sent along with device +* wedged uevent. +*/ +static const char *const drm_wedge_recovery_opts[] = { + [DRM_WEDGE_RECOVERY_REBIND ] ="rebind" , + [DRM_WEDGE_RECOVERY_BUS_RESET ] ="bus-reset" , + [DRM_WEDGE_RECOVERY_REBOOT ] ="reboot" , +}; + +static bool drm_wedge_recovery_is_valid (enum drm_wedge_recovery method) +{
drivers/gpu/drm/drm_drv.c static struct dentry *drm_debugfs_root; · line 97
Quoted 10 lines
drivers/gpu/drm/drm_drv.c +10
-0+static_assert (ARRAY_SIZE (drm_wedge_recovery_opts) ==DRM_WEDGE_RECOVERY_MAX ); + +return method >=DRM_WEDGE_RECOVERY_REBIND && method <DRM_WEDGE_RECOVERY_MAX ; +} + +/** +* drm_wedge_recovery_name - provide wedge recovery name +* @method: method to be used for recovery +* +* This validates wedge recovery @method against the available ones in
do we really need to validate an enum? maybe the problem is that there is MAX enumerator that just shouldn't be there?
drivers/gpu/drm/drm_drv.c static struct dentry *drm_debugfs_root; · line 106
Quoted 9 lines
drivers/gpu/drm/drm_drv.c +9
-0+* drm_wedge_recovery_opts[] and provides respective recovery name in string +* format if found valid. +* +* Returns: pointer to const recovery string on success, NULL otherwise. +*/ +const char *drm_wedge_recovery_name (enum drm_wedge_recovery method) +{ +if (drm_wedge_recovery_is_valid (method)) +return drm_wedge_recovery_opts[method];
as we only have 3 methods, maybe simple switch() will do the work?
Quoted 9 lines
drivers/gpu/drm/drm_drv.c +5
-0+ +return NULL ; +} +EXPORT_SYMBOL (drm_wedge_recovery_name); +/* * DRM Minors * A DRM device can provide several char-dev interfaces on the DRM-Major. Each
drivers/gpu/drm/drm_drv.c void drm_dev_unplug(struct drm_device *dev) · line 545
Quoted 10 lines
drivers/gpu/drm/drm_drv.c +7
-0@@ -497,6 +536,44 @@ void drm_dev_unplug(struct drm_device *dev) }EXPORT_SYMBOL (drm_dev_unplug); +/** +* drm_dev_wedged_event - generate a device wedged uevent +* @dev: DRM device +* @method: method to be used for recovery +* +* This generates a device wedged uevent for the DRM device specified by @dev. +* Recovery @method from drm_wedge_recovery_opts[] (if supprted by the device)
typo
drivers/gpu/drm/drm_drv.c void drm_dev_unplug(struct drm_device *dev) · line 554
Quoted 9 lines
drivers/gpu/drm/drm_drv.c +9
-0+* is sent in the uevent environment as WEDGED=<method>, on the basis of which, +* userspace may take respective action to recover the device. +* +* Returns: 0 on success, or negative error code otherwise. +*/ +int drm_dev_wedged_event (struct drm_device *dev,enum drm_wedge_recovery method) +{ +/* Event string length up to 16+ characters with available methods */ +char event_string[32 ] = {};
magic 32 here and likely don't need to be initialized with { }
drivers/gpu/drm/drm_drv.c void drm_dev_unplug(struct drm_device *dev) · line 560
Quoted 6 lines
drivers/gpu/drm/drm_drv.c +6
-0+char *envp[] = { event_string,NULL }; +const char *recovery; + + recovery =drm_wedge_recovery_name (method); +if (!recovery) { +drm_err (dev,"device wedged, invalid recovery method %d\n" , method);
maybe use drm_WARN() to see who is abusing the API ?
drivers/gpu/drm/drm_drv.c void drm_dev_unplug(struct drm_device *dev) · line 561
Quoted 1 line
drivers/gpu/drm/drm_drv.c +1
-0+return -EINVAL ;
but shouldn't we still trigger an event with "none" recovery?
drivers/gpu/drm/drm_drv.c void drm_dev_unplug(struct drm_device *dev) · line 566
Quoted 5 lines
drivers/gpu/drm/drm_drv.c +5
-0+ } + +if (!test_bit (method, &dev->wedge_recovery)) { +drm_err (dev,"device wedged, %s based recovery not supported\n" , +drm_wedge_recovery_name (method));
do we really need this kind of guard? it will be a driver code that will call this function, so likely it knows better what will work to recover
drivers/gpu/drm/drm_drv.c void drm_dev_unplug(struct drm_device *dev) · line 572
Quoted 6 lines
drivers/gpu/drm/drm_drv.c +6
-0+return -EOPNOTSUPP ; + } + +snprintf (event_string,sizeof (event_string),"WEDGED=%s" , recovery); + +drm_info (dev,"device wedged, generating uevent for %s based recovery\n" , recovery);
nit:
drm_info(dev, "device wedged, needs %s to recover\n", recovery);
Quoted 39 lines
drivers/gpu/drm/drm_drv.c +4
-0+return kobject_uevent_env (&dev->primary->kdev->kobj,KOBJ_CHANGE , envp); +} +EXPORT_SYMBOL (drm_dev_wedged_event); +/* * DRM internal mount * We want to be able to allocate our own "struct address_space" to control include/drm/drm_device.h +20
-0@@ -40,6 +40,26 @@ enum switch_power_state { DRM_SWITCH_POWER_DYNAMIC_OFF = 3, }; +/** +* enum drm_wedge_recovery - Recovery method for wedged device in order of +* severity. To be set as bit fields in drm_device.wedge_recovery variable. +* Drivers can choose to support any one or multiple of them depending on +* their needs. +*/ +enum drm_wedge_recovery { +/** @DRM_WEDGE_RECOVERY_REBIND: unbind + rebind driver */ +DRM_WEDGE_RECOVERY_REBIND , + +/** @DRM_WEDGE_RECOVERY_BUS_RESET: unbind + reset bus device + rebind */ +DRM_WEDGE_RECOVERY_BUS_RESET , + +/** @DRM_WEDGE_RECOVERY_REBOOT: reboot system */ +DRM_WEDGE_RECOVERY_REBOOT , + +/** @DRM_WEDGE_RECOVERY_MAX: for bounds checking, do not use */ +DRM_WEDGE_RECOVERY_MAX +}; +/** * struct drm_device - DRM device structure *
include/drm/drm_device.h struct drm_device { · line 342
Quoted 6 lines
include/drm/drm_device.h +3
-0@@ -317,6 +337,9 @@ struct drm_device {* Root directory for debugfs files. */ struct dentry *debugfs_root; + +/** @wedge_recovery: Supported recovery methods for wedged device */ +unsigned long wedge_recovery;
hmm, so before the driver can ask for a reboot as a recovery method from wedge it has to somehow add 'reboot' as available method? why it that?
and if you insist that this is useful then at least document how this should be initialized (to not forcing developers to look at drm_dev_wedged_event code where it's used)
Quoted 17 lines
include/drm/drm_device.h +0
-0};#endif include/drm/drm_drv.h +3
-0@@ -462,6 +462,9 @@ bool drm_dev_enter(struct drm_device *dev, int *idx);void drm_dev_exit (int idx);void drm_dev_unplug (struct drm_device *dev); +const char *drm_wedge_recovery_name (enum drm_wedge_recovery method); +int drm_dev_wedged_event (struct drm_device *dev,enum drm_wedge_recovery method); +/** * drm_dev_is_unplugged - is a DRM device unplugged * @dev: DRM device
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 3 lines · Michal Wajdeczko
Hi,
sorry for late comments,
Sure, no problem.
Quoted 14 lines · Raag Jadav
Quoted 6 lines
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Quoted 6 lines
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Quoted 2 lines
what about when driver just wants to tell that it is in unusable state, but recovery method is unknown or not possible?
Interesting... However, what would be the consumer expectation for it? If the expectation is to not recover, why send an event at all?
Quoted 5 lines
Quoted 4 lines
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>.
Quoted 7 lines
could this be something like below instead:
WEDGED=<reason> RECOVERY=<method>[,<method>]then driver will have a chance to tell what happen _and_ additionally provide a hint(s) how to recover from that situation
Documentation/gpu/drm-uapi.rst +337
UMD can issue an ioctl to the KMD to check the reset status
...or <reason> for wedging, which KMD will signify with an error code...
UMD will then proceed to report it to the application using the appropriate API error code
(should've explicitly added, sorry)
Quoted 10 lines
Quoted 9 lines
Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
Quoted 2 lines
btw, what if driver detects a really broken HW, or has no clue what will help here, shouldn't we have a "none" method?
Sure. But same as above, we have to define expectations.
Quoted 60 lines
Quoted 60 lines
=============== ==================================v4: s/drm_dev_wedged/drm_dev_wedged_event
Usedrm_info()(Jani)
Kernel doc adjustment (Aravind)
v5: Send recovery method with uevent (Lina)
v6: Access wedge_recovery_opts[] using helper function (Jani)
Usesnprintf()(Jani)
v7: Convert recovery helpers into regular functions (Andy, Jani)
Aesthetic adjustments (Andy)
Handle invalid method casesSigned-off-by Raag Jadav <[email protected]>--- drivers/gpu/drm/drm_drv.c | 77 +++++++++++++++++++++++++++++++++++++++ include/drm/drm_device.h | 23 ++++++++++++ include/drm/drm_drv.h | 3 ++ 3 files changed, 103 insertions(+)drivers/gpu/drm/drm_drv.c +19
-0@@ -26,6 +26,8 @@* DEALINGS IN THE SOFTWARE. */ +#include <linux/array_size.h> +#include <linux/build_bug.h> #include <linux/debugfs.h> #include <linux/fs.h> #include <linux/module.h> @@ -33,6 +35,7 @@#include <linux/mount.h> #include <linux/pseudo_fs.h> #include <linux/slab.h> +#include <linux/sprintf.h> #include <linux/srcu.h> #include <linux/xarray.h> @@ -70,6 +73,42 @@ static struct dentry *drm_debugfs_root;DEFINE_STATIC_SRCU (drm_unplug_srcu); +/* +* Available recovery methods for wedged device. To be sent along with device +* wedged uevent. +*/ +static const char *const drm_wedge_recovery_opts[] = { + [DRM_WEDGE_RECOVERY_REBIND ] ="rebind" , + [DRM_WEDGE_RECOVERY_BUS_RESET ] ="bus-reset" , + [DRM_WEDGE_RECOVERY_REBOOT ] ="reboot" , +}; + +static bool drm_wedge_recovery_is_valid (enum drm_wedge_recovery method) +{ +static_assert (ARRAY_SIZE (drm_wedge_recovery_opts) ==DRM_WEDGE_RECOVERY_MAX ); + +return method >=DRM_WEDGE_RECOVERY_REBIND && method <DRM_WEDGE_RECOVERY_MAX ; +}
Quoted 8 lines
drivers/gpu/drm/drm_drv.c static struct dentry *drm_debugfs_root; · line 97
Quoted 6 lines
drivers/gpu/drm/drm_drv.c +6
-0+ +/** +* drm_wedge_recovery_name - provide wedge recovery name +* @method: method to be used for recovery +* +* This validates wedge recovery @method against the available ones in do we really need to validate an enum?
I'm all for trusting the drivers explicitly, but since this is a core feature I thought we'd have some guard rails (for abusers).
Quoted 1 line
maybe the problem is that there is MAX enumerator that just shouldn't be there?
With MAX in place we won't need to adjust the helpers to match with enum modifications in the future (if any).
Quoted 11 lines
drivers/gpu/drm/drm_drv.c static struct dentry *drm_debugfs_root; · line 106
Quoted 9 lines
drivers/gpu/drm/drm_drv.c +9
-0+* drm_wedge_recovery_opts[] and provides respective recovery name in string +* format if found valid. +* +* Returns: pointer to const recovery string on success, NULL otherwise. +*/ +const char *drm_wedge_recovery_name (enum drm_wedge_recovery method) +{ +if (drm_wedge_recovery_is_valid (method)) +return drm_wedge_recovery_opts[method];as we only have 3 methods, maybe simple
switch()will do the work?
Sure.
Quoted 12 lines
Quoted 12 lines
drivers/gpu/drm/drm_drv.c +5
-0+ +return NULL ; +} +EXPORT_SYMBOL (drm_wedge_recovery_name); +/* * DRM Minors * A DRM device can provide several char-dev interfaces on the DRM-Major. Each @@ -497,6 +536,44 @@ void drm_dev_unplug(struct drm_device *dev) }EXPORT_SYMBOL (drm_dev_unplug);
Quoted 9 lines
drivers/gpu/drm/drm_drv.c void drm_dev_unplug(struct drm_device *dev) · line 545
Quoted 7 lines
drivers/gpu/drm/drm_drv.c +7
-0+/** +* drm_dev_wedged_event - generate a device wedged uevent +* @dev: DRM device +* @method: method to be used for recovery +* +* This generates a device wedged uevent for the DRM device specified by @dev. +* Recovery @method from drm_wedge_recovery_opts[] (if supprted by the device) typo
Good catch.
Quoted 11 lines
drivers/gpu/drm/drm_drv.c void drm_dev_unplug(struct drm_device *dev) · line 554
Quoted 9 lines
drivers/gpu/drm/drm_drv.c +9
-0+* is sent in the uevent environment as WEDGED=<method>, on the basis of which, +* userspace may take respective action to recover the device. +* +* Returns: 0 on success, or negative error code otherwise. +*/ +int drm_dev_wedged_event (struct drm_device *dev,enum drm_wedge_recovery method) +{ +/* Event string length up to 16+ characters with available methods */ +char event_string[32 ] = {};magic 32 here
Anything to add to the event string length comment above?
Quoted 8 lines
drivers/gpu/drm/drm_drv.c void drm_dev_unplug(struct drm_device *dev) · line 560
Quoted 6 lines
drivers/gpu/drm/drm_drv.c +6
-0+char *envp[] = { event_string,NULL }; +const char *recovery; + + recovery =drm_wedge_recovery_name (method); +if (!recovery) { +drm_err (dev,"device wedged, invalid recovery method %d\n" , method);maybe use
drm_WARN()to see who is abusing the API ?
Sure.
Quoted 3 lines
drivers/gpu/drm/drm_drv.c void drm_dev_unplug(struct drm_device *dev) · line 561
Quoted 1 line
drivers/gpu/drm/drm_drv.c +1
-0+return -EINVAL ;but shouldn't we still trigger an event with "none" recovery?
Explained above.
Quoted 8 lines
drivers/gpu/drm/drm_drv.c void drm_dev_unplug(struct drm_device *dev) · line 566
Quoted 5 lines
drivers/gpu/drm/drm_drv.c +5
-0+ } + +if (!test_bit (method, &dev->wedge_recovery)) { +drm_err (dev,"device wedged, %s based recovery not supported\n" , +drm_wedge_recovery_name (method));do we really need this kind of guard? it will be a driver code that will call this function, so likely it knows better what will work to recover
Agree, although unsupported method could cause undefined behaviour.
Quoted 9 lines
drivers/gpu/drm/drm_drv.c void drm_dev_unplug(struct drm_device *dev) · line 572
Quoted 6 lines
drivers/gpu/drm/drm_drv.c +6
-0+return -EOPNOTSUPP ; + } + +snprintf (event_string,sizeof (event_string),"WEDGED=%s" , recovery); + +drm_info (dev,"device wedged, generating uevent for %s based recovery\n" , recovery);nit:
drm_info(dev, "device wedged, needs %s to recover\n", recovery);
Sure.
Quoted 40 lines
Quoted 40 lines
drivers/gpu/drm/drm_drv.c +4
-0+return kobject_uevent_env (&dev->primary->kdev->kobj,KOBJ_CHANGE , envp); +} +EXPORT_SYMBOL (drm_dev_wedged_event); +/* * DRM internal mount * We want to be able to allocate our own "struct address_space" to control include/drm/drm_device.h +20
-0@@ -40,6 +40,26 @@ enum switch_power_state { DRM_SWITCH_POWER_DYNAMIC_OFF = 3, }; +/** +* enum drm_wedge_recovery - Recovery method for wedged device in order of +* severity. To be set as bit fields in drm_device.wedge_recovery variable. +* Drivers can choose to support any one or multiple of them depending on +* their needs. +*/ +enum drm_wedge_recovery { +/** @DRM_WEDGE_RECOVERY_REBIND: unbind + rebind driver */ +DRM_WEDGE_RECOVERY_REBIND , + +/** @DRM_WEDGE_RECOVERY_BUS_RESET: unbind + reset bus device + rebind */ +DRM_WEDGE_RECOVERY_BUS_RESET , + +/** @DRM_WEDGE_RECOVERY_REBOOT: reboot system */ +DRM_WEDGE_RECOVERY_REBOOT , + +/** @DRM_WEDGE_RECOVERY_MAX: for bounds checking, do not use */ +DRM_WEDGE_RECOVERY_MAX +}; +/** * struct drm_device - DRM device structure * @@ -317,6 +337,9 @@ struct drm_device {* Root directory for debugfs files.
Quoted 8 lines
include/drm/drm_device.h struct drm_device { · line 342
Quoted 5 lines
include/drm/drm_device.h +3
-0*/ struct dentry *debugfs_root; + +/** @wedge_recovery: Supported recovery methods for wedged device */ +unsigned long wedge_recovery;hmm, so before the driver can ask for a reboot as a recovery method from wedge it has to somehow add 'reboot' as available method? why it that?
It's for consumers to use as fallbacks in case the preferred recovery method (sent along with uevent) don't workout. (patch 2/5)
Quoted 3 lines
and if you insist that this is useful then at least document how this should be initialized (to not forcing developers to look at
drm_dev_wedged_eventcode where it's used)
Sure.
Raag
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 37 lines · Raag Jadav
Quoted 27 lines · Michal Wajdeczko
Quoted 26 lines · Raag Jadav
include/drm/drm_device.h +20
-0+/** +* enum drm_wedge_recovery - Recovery method for wedged device in order of +* severity. To be set as bit fields in drm_device.wedge_recovery variable. +* Drivers can choose to support any one or multiple of them depending on +* their needs. +*/ +enum drm_wedge_recovery { +/** @DRM_WEDGE_RECOVERY_REBIND: unbind + rebind driver */ +DRM_WEDGE_RECOVERY_REBIND , + +/** @DRM_WEDGE_RECOVERY_BUS_RESET: unbind + reset bus device + rebind */ +DRM_WEDGE_RECOVERY_BUS_RESET , + +/** @DRM_WEDGE_RECOVERY_REBOOT: reboot system */ +DRM_WEDGE_RECOVERY_REBOOT , + +/** @DRM_WEDGE_RECOVERY_MAX: for bounds checking, do not use */ +DRM_WEDGE_RECOVERY_MAX +}; +/** * struct drm_device - DRM device structure * @@ -317,6 +337,9 @@ struct drm_device {* Root directory for debugfs files. Quoted 8 lines
include/drm/drm_device.h struct drm_device { · line 342
Quoted 5 lines
include/drm/drm_device.h +3
-0*/ struct dentry *debugfs_root; + +/** @wedge_recovery: Supported recovery methods for wedged device */ +unsigned long wedge_recovery;hmm, so before the driver can ask for a reboot as a recovery method from wedge it has to somehow add 'reboot' as available method? why it that?
Quoted 2 lines
It's for consumers to use as fallbacks in case the preferred recovery method (sent along with uevent) don't workout. (patch 2/5)
On second thought...
Lucas, do we have a convincing enough usecase for fallback recovery? If <method> were to fail, I would expect there to be even bigger problems like kernel crash or unrecoverable hardware failure.
At that point is it worth retrying?
Raag
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 41 lines · Raag Jadav
Quoted 37 lines · Raag Jadav
Quoted 27 lines · Michal Wajdeczko
Quoted 26 lines · Raag Jadav
include/drm/drm_device.h +20
-0+/** +* enum drm_wedge_recovery - Recovery method for wedged device in order of +* severity. To be set as bit fields in drm_device.wedge_recovery variable. +* Drivers can choose to support any one or multiple of them depending on +* their needs. +*/ +enum drm_wedge_recovery { +/** @DRM_WEDGE_RECOVERY_REBIND: unbind + rebind driver */ +DRM_WEDGE_RECOVERY_REBIND , + +/** @DRM_WEDGE_RECOVERY_BUS_RESET: unbind + reset bus device + rebind */ +DRM_WEDGE_RECOVERY_BUS_RESET , + +/** @DRM_WEDGE_RECOVERY_REBOOT: reboot system */ +DRM_WEDGE_RECOVERY_REBOOT , + +/** @DRM_WEDGE_RECOVERY_MAX: for bounds checking, do not use */ +DRM_WEDGE_RECOVERY_MAX +}; +/** * struct drm_device - DRM device structure * @@ -317,6 +337,9 @@ struct drm_device {* Root directory for debugfs files. Quoted 8 lines
include/drm/drm_device.h struct drm_device { · line 342
Quoted 5 lines
include/drm/drm_device.h +3
-0*/ struct dentry *debugfs_root; + +/** @wedge_recovery: Supported recovery methods for wedged device */ +unsigned long wedge_recovery;hmm, so before the driver can ask for a reboot as a recovery method from wedge it has to somehow add 'reboot' as available method? why it that?
Quoted 2 lines
It's for consumers to use as fallbacks in case the preferred recovery method (sent along with uevent) don't workout. (patch 2/5)
Quoted 7 lines
On second thought...
Lucas, do we have a convincing enough usecase for fallback recovery? If <method> were to fail, I would expect there to be even bigger problems like kernel crash or unrecoverable hardware failure.
At that point is it worth retrying?
when we were talking about this, I brought it up about allowing the driver to inform what was the supported wedge recovery mechanisms when the notification is sent. Not to be intended as fallback mechanism.
So if the driver sends a notification with:
DRM_WEDGE_RECOVERY_REBIND | DRM_WEDGE_RECOVERY_BUS_RESET | DRM_WEDGE_RECOVERY_REBOOT
it means any of these would be suitable, with the first being the option with less side-effect. I don't think we are advising userspace to use fallback, just informing what the driver/device supports. Depending on the error, the driver may leave only
DRM_WEDGE_RECOVERY_REBOOT
That name could actually be DRM_WEDGE_RECOVERY_NONE. Because at that state the driver doesn't really know what can be done to recover. With that we can drop _MAX and use _NONE for bounding check. I think we can also omit it in the notification as it's clear:
WEDGED
DRM_WEDGE_RECOVERY_REBIND | DRM_WEDGE_RECOVERY_BUS_RESET
This means the driver can use any of these options to recover
WEDGED
DRM_WEDGE_RECOVERY_BUS_RESET
only bus reset would fix it
WEDGED
driver doesn't know anything that could fix it. It may be a soft-reboot, hard-reboot, firmware flashing etc... We just don't know.
Lucas De Marchi
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 78 lines · Lucas De Marchi
Quoted 41 lines · Raag Jadav
Quoted 37 lines · Raag Jadav
Quoted 27 lines · Michal Wajdeczko
Quoted 26 lines · Raag Jadav
include/drm/drm_device.h +20
-0+/** +* enum drm_wedge_recovery - Recovery method for wedged device in order of +* severity. To be set as bit fields in drm_device.wedge_recovery variable. +* Drivers can choose to support any one or multiple of them depending on +* their needs. +*/ +enum drm_wedge_recovery { +/** @DRM_WEDGE_RECOVERY_REBIND: unbind + rebind driver */ +DRM_WEDGE_RECOVERY_REBIND , + +/** @DRM_WEDGE_RECOVERY_BUS_RESET: unbind + reset bus device + rebind */ +DRM_WEDGE_RECOVERY_BUS_RESET , + +/** @DRM_WEDGE_RECOVERY_REBOOT: reboot system */ +DRM_WEDGE_RECOVERY_REBOOT , + +/** @DRM_WEDGE_RECOVERY_MAX: for bounds checking, do not use */ +DRM_WEDGE_RECOVERY_MAX +}; +/** * struct drm_device - DRM device structure * @@ -317,6 +337,9 @@ struct drm_device {* Root directory for debugfs files. Quoted 8 lines
include/drm/drm_device.h struct drm_device { · line 342
Quoted 5 lines
include/drm/drm_device.h +3
-0*/ struct dentry *debugfs_root; + +/** @wedge_recovery: Supported recovery methods for wedged device */ +unsigned long wedge_recovery;hmm, so before the driver can ask for a reboot as a recovery method from wedge it has to somehow add 'reboot' as available method? why it that?
Quoted 2 lines
It's for consumers to use as fallbacks in case the preferred recovery method (sent along with uevent) don't workout. (patch 2/5)
Quoted 7 lines
On second thought...
Lucas, do we have a convincing enough usecase for fallback recovery? If <method> were to fail, I would expect there to be even bigger problems like kernel crash or unrecoverable hardware failure.
At that point is it worth retrying?
when we were talking about this, I brought it up about allowing the driver to inform what was the supported wedge recovery mechanisms when the notification is sent. Not to be intended as fallback mechanism.
So if the driver sends a notification with:
DRM_WEDGE_RECOVERY_REBIND|DRM_WEDGE_RECOVERY_BUS_RESET|DRM_WEDGE_RECOVERY_REBOOTit means any of these would be suitable, with the first being the option with less side-effect. I don't think we are advising userspace to use fallback, just informing what the driver/device supports. Depending on the error, the driver may leave only
DRM_WEDGE_RECOVERY_REBOOTThat name could actually be
DRM_WEDGE_RECOVERY_NONE. Because at that state the driver doesn't really know what can be done to recover. With that we can drop_MAXand use_NONEfor bounding check. I think we can also omit it in the notification as it's clear:WEDGED
DRM_WEDGE_RECOVERY_REBIND|DRM_WEDGE_RECOVERY_BUS_RESETThis means the driver can use any of these options to recover
WEDGED
DRM_WEDGE_RECOVERY_BUS_RESET
Quoted 6 lines
only bus reset would fix it
WEDGED
driver doesn't know anything that could fix it. It may be a soft-reboot, hard-reboot, firmware flashing etc... We just don't know.
With this I think we can drop sysfs.
(Already too many ABIs to deal with)
Raag
Re: [PATCH v7 1/5] drm: Introduce device wedged event
In reply to Raag JadavQuoted 37 lines · Raag Jadav
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================v4: s/drm_dev_wedged/drm_dev_wedged_event
Usedrm_info()(Jani)
Kernel doc adjustment (Aravind)
v5: Send recovery method with uevent (Lina)
v6: Access wedge_recovery_opts[] using helper function (Jani)
Usesnprintf()(Jani)
v7: Convert recovery helpers into regular functions (Andy, Jani)
Aesthetic adjustments (Andy)
Handle invalid method cases
Quoted 2 lines
Signed-off-by Raag Jadav <[email protected]>---
Cc'ing amd, collabora and others as I found semi-related work at
https://lore.kernel.org/dri-devel/[email protected]/
https://lore.kernel.org/amd-gfx/[email protected]/
https://lore.kernel.org/dri-devel/[email protected]/
https://lore.kernel.org/amd-gfx/CAAxE2A5v_RkZ9ex4=7jiBSKVb22_1FAj0AANBcmKtETt5c3gVA@mail.gmail.com/
Please share feedback about usefulness and adoption of this. Improvements are welcome.
Raag
Quoted 172 lines
drivers/gpu/drm/drm_drv.c | 77 +++++++++++++++++++++++++++++++++++++++ include/drm/drm_device.h | 23 ++++++++++++ include/drm/drm_drv.h | 3 ++ 3 files changed, 103 insertions(+)drivers/gpu/drm/drm_drv.c +77
-0@@ -26,6 +26,8 @@* DEALINGS IN THE SOFTWARE. */ +#include <linux/array_size.h> +#include <linux/build_bug.h> #include <linux/debugfs.h> #include <linux/fs.h> #include <linux/module.h> @@ -33,6 +35,7 @@#include <linux/mount.h> #include <linux/pseudo_fs.h> #include <linux/slab.h> +#include <linux/sprintf.h> #include <linux/srcu.h> #include <linux/xarray.h> @@ -70,6 +73,42 @@ static struct dentry *drm_debugfs_root;DEFINE_STATIC_SRCU (drm_unplug_srcu); +/* +* Available recovery methods for wedged device. To be sent along with device +* wedged uevent. +*/ +static const char *const drm_wedge_recovery_opts[] = { + [DRM_WEDGE_RECOVERY_REBIND ] ="rebind" , + [DRM_WEDGE_RECOVERY_BUS_RESET ] ="bus-reset" , + [DRM_WEDGE_RECOVERY_REBOOT ] ="reboot" , +}; + +static bool drm_wedge_recovery_is_valid (enum drm_wedge_recovery method) +{ +static_assert (ARRAY_SIZE (drm_wedge_recovery_opts) ==DRM_WEDGE_RECOVERY_MAX ); + +return method >=DRM_WEDGE_RECOVERY_REBIND && method <DRM_WEDGE_RECOVERY_MAX ; +} + +/** +* drm_wedge_recovery_name - provide wedge recovery name +* @method: method to be used for recovery +* +* This validates wedge recovery @method against the available ones in +* drm_wedge_recovery_opts[] and provides respective recovery name in string +* format if found valid. +* +* Returns: pointer to const recovery string on success, NULL otherwise. +*/ +const char *drm_wedge_recovery_name (enum drm_wedge_recovery method) +{ +if (drm_wedge_recovery_is_valid (method)) +return drm_wedge_recovery_opts[method]; + +return NULL ; +} +EXPORT_SYMBOL (drm_wedge_recovery_name); +/* * DRM Minors * A DRM device can provide several char-dev interfaces on the DRM-Major. Each @@ -497,6 +536,44 @@ void drm_dev_unplug(struct drm_device *dev) }EXPORT_SYMBOL (drm_dev_unplug); +/** +* drm_dev_wedged_event - generate a device wedged uevent +* @dev: DRM device +* @method: method to be used for recovery +* +* This generates a device wedged uevent for the DRM device specified by @dev. +* Recovery @method from drm_wedge_recovery_opts[] (if supprted by the device) +* is sent in the uevent environment as WEDGED=<method>, on the basis of which, +* userspace may take respective action to recover the device. +* +* Returns: 0 on success, or negative error code otherwise. +*/ +int drm_dev_wedged_event (struct drm_device *dev,enum drm_wedge_recovery method) +{ +/* Event string length up to 16+ characters with available methods */ +char event_string[32 ] = {}; +char *envp[] = { event_string,NULL }; +const char *recovery; + + recovery =drm_wedge_recovery_name (method); +if (!recovery) { +drm_err (dev,"device wedged, invalid recovery method %d\n" , method); +return -EINVAL ; + } + +if (!test_bit (method, &dev->wedge_recovery)) { +drm_err (dev,"device wedged, %s based recovery not supported\n" , +drm_wedge_recovery_name (method)); +return -EOPNOTSUPP ; + } + +snprintf (event_string,sizeof (event_string),"WEDGED=%s" , recovery); + +drm_info (dev,"device wedged, generating uevent for %s based recovery\n" , recovery); +return kobject_uevent_env (&dev->primary->kdev->kobj,KOBJ_CHANGE , envp); +} +EXPORT_SYMBOL (drm_dev_wedged_event); +/* * DRM internal mount * We want to be able to allocate our own "struct address_space" to control include/drm/drm_device.h +23
-0@@ -40,6 +40,26 @@ enum switch_power_state { DRM_SWITCH_POWER_DYNAMIC_OFF = 3, }; +/** +* enum drm_wedge_recovery - Recovery method for wedged device in order of +* severity. To be set as bit fields in drm_device.wedge_recovery variable. +* Drivers can choose to support any one or multiple of them depending on +* their needs. +*/ +enum drm_wedge_recovery { +/** @DRM_WEDGE_RECOVERY_REBIND: unbind + rebind driver */ +DRM_WEDGE_RECOVERY_REBIND , + +/** @DRM_WEDGE_RECOVERY_BUS_RESET: unbind + reset bus device + rebind */ +DRM_WEDGE_RECOVERY_BUS_RESET , + +/** @DRM_WEDGE_RECOVERY_REBOOT: reboot system */ +DRM_WEDGE_RECOVERY_REBOOT , + +/** @DRM_WEDGE_RECOVERY_MAX: for bounds checking, do not use */ +DRM_WEDGE_RECOVERY_MAX +}; +/** * struct drm_device - DRM device structure * @@ -317,6 +337,9 @@ struct drm_device {* Root directory for debugfs files. */ struct dentry *debugfs_root; + +/** @wedge_recovery: Supported recovery methods for wedged device */ + unsigned long wedge_recovery; };#endif include/drm/drm_drv.h +3
-0@@ -462,6 +462,9 @@ bool drm_dev_enter(struct drm_device *dev, int *idx);void drm_dev_exit (int idx);void drm_dev_unplug (struct drm_device *dev); +const char *drm_wedge_recovery_name (enum drm_wedge_recovery method); +int drm_dev_wedged_event (struct drm_device *dev,enum drm_wedge_recovery method); +/** * drm_dev_is_unplugged - is a DRM device unplugged * @dev: DRM device Signature · 1 line
2.34.1
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Am 17.10.24 um 04:47 schrieb Raag Jadav:
Quoted 6 lines · Raag Jadav
Quoted 5 lines
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Well introduce is probably the wrong wording since i915 already has that and amdgpu looked into it but never upstreamed the support.
I would rather say standardize.
Quoted 14 lines
Quoted 14 lines
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
Quoted 7 lines
Quoted 7 lines
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================
Well that sounds like userspace would need to be involved in recovery.
That in turn is a complete no-go since we at least need to signal all dma_fences to unblock the kernel. In other words things like bus reset needs to happen inside the kernel and *not* in userspace.
What we can do is to signal to userspace: Hey a bus reset of device X happened, maybe restart container, daemon, whatever service which was using this device.
Regards,
Christian.
Quoted 198 lines
Quoted 11 lines
v4: s/drm_dev_wedged/drm_dev_wedged_event
Usedrm_info()(Jani)
Kernel doc adjustment (Aravind)
v5: Send recovery method with uevent (Lina)
v6: Access wedge_recovery_opts[] using helper function (Jani)
Usesnprintf()(Jani)
v7: Convert recovery helpers into regular functions (Andy, Jani)
Aesthetic adjustments (Andy)
Handle invalid method casesQuoted 2 lines
Signed-off-by Raag Jadav <[email protected]>---
Cc'ing amd, collabora and others as I found semi-related work at
https://lore.kernel.org/dri-devel/[email protected]/
https://lore.kernel.org/amd-gfx/[email protected]/
https://lore.kernel.org/dri-devel/[email protected]/
https://lore.kernel.org/amd-gfx/CAAxE2A5v_RkZ9ex4=7jiBSKVb22_1FAj0AANBcmKtETt5c3gVA@mail.gmail.com/Please share feedback about usefulness and adoption of this. Improvements are welcome.
Raag
Quoted 172 lines
drivers/gpu/drm/drm_drv.c | 77 +++++++++++++++++++++++++++++++++++++++ include/drm/drm_device.h | 23 ++++++++++++ include/drm/drm_drv.h | 3 ++ 3 files changed, 103 insertions(+)drivers/gpu/drm/drm_drv.c +77
-0@@ -26,6 +26,8 @@* DEALINGS IN THE SOFTWARE. */ +#include <linux/array_size.h> +#include <linux/build_bug.h> #include <linux/debugfs.h> #include <linux/fs.h> #include <linux/module.h> @@ -33,6 +35,7 @@#include <linux/mount.h> #include <linux/pseudo_fs.h> #include <linux/slab.h> +#include <linux/sprintf.h> #include <linux/srcu.h> #include <linux/xarray.h> @@ -70,6 +73,42 @@ static struct dentry *drm_debugfs_root;DEFINE_STATIC_SRCU (drm_unplug_srcu); +/* +* Available recovery methods for wedged device. To be sent along with device +* wedged uevent. +*/ +static const char *const drm_wedge_recovery_opts[] = { + [DRM_WEDGE_RECOVERY_REBIND ] ="rebind" , + [DRM_WEDGE_RECOVERY_BUS_RESET ] ="bus-reset" , + [DRM_WEDGE_RECOVERY_REBOOT ] ="reboot" , +}; + +static bool drm_wedge_recovery_is_valid (enum drm_wedge_recovery method) +{ +static_assert (ARRAY_SIZE (drm_wedge_recovery_opts) ==DRM_WEDGE_RECOVERY_MAX ); + +return method >=DRM_WEDGE_RECOVERY_REBIND && method <DRM_WEDGE_RECOVERY_MAX ; +} + +/** +* drm_wedge_recovery_name - provide wedge recovery name +* @method: method to be used for recovery +* +* This validates wedge recovery @method against the available ones in +* drm_wedge_recovery_opts[] and provides respective recovery name in string +* format if found valid. +* +* Returns: pointer to const recovery string on success, NULL otherwise. +*/ +const char *drm_wedge_recovery_name (enum drm_wedge_recovery method) +{ +if (drm_wedge_recovery_is_valid (method)) +return drm_wedge_recovery_opts[method]; + +return NULL ; +} +EXPORT_SYMBOL (drm_wedge_recovery_name); +/* * DRM Minors * A DRM device can provide several char-dev interfaces on the DRM-Major. Each @@ -497,6 +536,44 @@ void drm_dev_unplug(struct drm_device *dev) }EXPORT_SYMBOL (drm_dev_unplug); +/** +* drm_dev_wedged_event - generate a device wedged uevent +* @dev: DRM device +* @method: method to be used for recovery +* +* This generates a device wedged uevent for the DRM device specified by @dev. +* Recovery @method from drm_wedge_recovery_opts[] (if supprted by the device) +* is sent in the uevent environment as WEDGED=<method>, on the basis of which, +* userspace may take respective action to recover the device. +* +* Returns: 0 on success, or negative error code otherwise. +*/ +int drm_dev_wedged_event (struct drm_device *dev,enum drm_wedge_recovery method) +{ +/* Event string length up to 16+ characters with available methods */ +char event_string[32 ] = {}; +char *envp[] = { event_string,NULL }; +const char *recovery; + + recovery =drm_wedge_recovery_name (method); +if (!recovery) { +drm_err (dev,"device wedged, invalid recovery method %d\n" , method); +return -EINVAL ; + } + +if (!test_bit (method, &dev->wedge_recovery)) { +drm_err (dev,"device wedged, %s based recovery not supported\n" , +drm_wedge_recovery_name (method)); +return -EOPNOTSUPP ; + } + +snprintf (event_string,sizeof (event_string),"WEDGED=%s" , recovery); + +drm_info (dev,"device wedged, generating uevent for %s based recovery\n" , recovery); +return kobject_uevent_env (&dev->primary->kdev->kobj,KOBJ_CHANGE , envp); +} +EXPORT_SYMBOL (drm_dev_wedged_event); +/* * DRM internal mount * We want to be able to allocate our own "struct address_space" to control include/drm/drm_device.h +23
-0@@ -40,6 +40,26 @@ enum switch_power_state { DRM_SWITCH_POWER_DYNAMIC_OFF = 3, }; +/** +* enum drm_wedge_recovery - Recovery method for wedged device in order of +* severity. To be set as bit fields in drm_device.wedge_recovery variable. +* Drivers can choose to support any one or multiple of them depending on +* their needs. +*/ +enum drm_wedge_recovery { +/** @DRM_WEDGE_RECOVERY_REBIND: unbind + rebind driver */ +DRM_WEDGE_RECOVERY_REBIND , + +/** @DRM_WEDGE_RECOVERY_BUS_RESET: unbind + reset bus device + rebind */ +DRM_WEDGE_RECOVERY_BUS_RESET , + +/** @DRM_WEDGE_RECOVERY_REBOOT: reboot system */ +DRM_WEDGE_RECOVERY_REBOOT , + +/** @DRM_WEDGE_RECOVERY_MAX: for bounds checking, do not use */ +DRM_WEDGE_RECOVERY_MAX +}; +/** * struct drm_device - DRM device structure * @@ -317,6 +337,9 @@ struct drm_device {* Root directory for debugfs files. */ struct dentry *debugfs_root; + +/** @wedge_recovery: Supported recovery methods for wedged device */ + unsigned long wedge_recovery; };#endif include/drm/drm_drv.h +3
-0@@ -462,6 +462,9 @@ bool drm_dev_enter(struct drm_device *dev, int *idx);void drm_dev_exit (int idx);void drm_dev_unplug (struct drm_device *dev); +const char *drm_wedge_recovery_name (enum drm_wedge_recovery method); +int drm_dev_wedged_event (struct drm_device *dev,enum drm_wedge_recovery method); +/** * drm_dev_is_unplugged - is a DRM device unplugged * @dev: DRM device Signature · 1 line
2.34.1
Rodrigo Vivi
maintainerRe: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 10 lines · Christian König
Am 17.10.24 um 04:47 schrieb Raag Jadav:
Quoted 6 lines · Raag Jadav
Quoted 5 lines
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Well introduce is probably the wrong wording since i915 already has that and amdgpu looked into it but never upstreamed the support.
in i915 we have the reset and error uevents, but not one specific for 'wedge'. This would indeed be a new one.
Quoted 27 lines
I would rather say standardize.
Quoted 14 lines
Quoted 14 lines
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
Quoted 7 lines
Quoted 7 lines
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================Well that sounds like userspace would need to be involved in recovery.
Quoted 7 lines
That in turn is a complete no-go since we at least need to signal all
dma_fencesto unblock the kernel. In other words things like bus reset needs to happen inside the kernel and *not* in userspace.What we can do is to signal to userspace: Hey a bus reset of device X happened, maybe restart container, daemon, whatever service which was using this device.
Well, when we declare device 'wedged' it is because we don't want to take any drastic measures inside the kernel and want to leave it in a protected and unusable state. In a way that users wouldn't lose display for instance, or at least the device is in a debugable state.
Then, the instructions here is to tell what could possibly be attempted from userspace to get the device to an usable state.
The 'wedge' mode (the one emiting this uevent) needs to be responsible for signaling all the fences and everything needed for a clean unbind and whatever next step might be indicated to userspace.
That should already be part of any wedged mode, regardless the uevent to inform the userspace here.
Quoted 195 lines
Regards,
Christian.Quoted 190 lines
Quoted 11 lines
v4: s/drm_dev_wedged/drm_dev_wedged_event
Usedrm_info()(Jani)
Kernel doc adjustment (Aravind)
v5: Send recovery method with uevent (Lina)
v6: Access wedge_recovery_opts[] using helper function (Jani)
Usesnprintf()(Jani)
v7: Convert recovery helpers into regular functions (Andy, Jani)
Aesthetic adjustments (Andy)
Handle invalid method casesQuoted 2 lines
Signed-off-by Raag Jadav <[email protected]>---
Cc'ing amd, collabora and others as I found semi-related work at
https://lore.kernel.org/dri-devel/[email protected]/
https://lore.kernel.org/amd-gfx/[email protected]/
https://lore.kernel.org/dri-devel/[email protected]/
https://lore.kernel.org/amd-gfx/CAAxE2A5v_RkZ9ex4=7jiBSKVb22_1FAj0AANBcmKtETt5c3gVA@mail.gmail.com/Please share feedback about usefulness and adoption of this. Improvements are welcome.
Raag
Quoted 164 lines
drivers/gpu/drm/drm_drv.c | 77 +++++++++++++++++++++++++++++++++++++++ include/drm/drm_device.h | 23 ++++++++++++ include/drm/drm_drv.h | 3 ++ 3 files changed, 103 insertions(+)drivers/gpu/drm/drm_drv.c +77
-0@@ -26,6 +26,8 @@* DEALINGS IN THE SOFTWARE. */ +#include <linux/array_size.h> +#include <linux/build_bug.h> #include <linux/debugfs.h> #include <linux/fs.h> #include <linux/module.h> @@ -33,6 +35,7 @@#include <linux/mount.h> #include <linux/pseudo_fs.h> #include <linux/slab.h> +#include <linux/sprintf.h> #include <linux/srcu.h> #include <linux/xarray.h> @@ -70,6 +73,42 @@ static struct dentry *drm_debugfs_root;DEFINE_STATIC_SRCU (drm_unplug_srcu); +/* +* Available recovery methods for wedged device. To be sent along with device +* wedged uevent. +*/ +static const char *const drm_wedge_recovery_opts[] = { + [DRM_WEDGE_RECOVERY_REBIND ] ="rebind" , + [DRM_WEDGE_RECOVERY_BUS_RESET ] ="bus-reset" , + [DRM_WEDGE_RECOVERY_REBOOT ] ="reboot" , +}; + +static bool drm_wedge_recovery_is_valid (enum drm_wedge_recovery method) +{ +static_assert (ARRAY_SIZE (drm_wedge_recovery_opts) ==DRM_WEDGE_RECOVERY_MAX ); + +return method >=DRM_WEDGE_RECOVERY_REBIND && method <DRM_WEDGE_RECOVERY_MAX ; +} + +/** +* drm_wedge_recovery_name - provide wedge recovery name +* @method: method to be used for recovery +* +* This validates wedge recovery @method against the available ones in +* drm_wedge_recovery_opts[] and provides respective recovery name in string +* format if found valid. +* +* Returns: pointer to const recovery string on success, NULL otherwise. +*/ +const char *drm_wedge_recovery_name (enum drm_wedge_recovery method) +{ +if (drm_wedge_recovery_is_valid (method)) +return drm_wedge_recovery_opts[method]; + +return NULL ; +} +EXPORT_SYMBOL (drm_wedge_recovery_name); +/* * DRM Minors * A DRM device can provide several char-dev interfaces on the DRM-Major. Each @@ -497,6 +536,44 @@ void drm_dev_unplug(struct drm_device *dev) }EXPORT_SYMBOL (drm_dev_unplug); +/** +* drm_dev_wedged_event - generate a device wedged uevent +* @dev: DRM device +* @method: method to be used for recovery +* +* This generates a device wedged uevent for the DRM device specified by @dev. +* Recovery @method from drm_wedge_recovery_opts[] (if supprted by the device) +* is sent in the uevent environment as WEDGED=<method>, on the basis of which, +* userspace may take respective action to recover the device. +* +* Returns: 0 on success, or negative error code otherwise. +*/ +int drm_dev_wedged_event (struct drm_device *dev,enum drm_wedge_recovery method) +{ +/* Event string length up to 16+ characters with available methods */ +char event_string[32 ] = {}; +char *envp[] = { event_string,NULL }; +const char *recovery; + + recovery =drm_wedge_recovery_name (method); +if (!recovery) { +drm_err (dev,"device wedged, invalid recovery method %d\n" , method); +return -EINVAL ; + } + +if (!test_bit (method, &dev->wedge_recovery)) { +drm_err (dev,"device wedged, %s based recovery not supported\n" , +drm_wedge_recovery_name (method)); +return -EOPNOTSUPP ; + } + +snprintf (event_string,sizeof (event_string),"WEDGED=%s" , recovery); + +drm_info (dev,"device wedged, generating uevent for %s based recovery\n" , recovery); +return kobject_uevent_env (&dev->primary->kdev->kobj,KOBJ_CHANGE , envp); +} +EXPORT_SYMBOL (drm_dev_wedged_event); +/* * DRM internal mount * We want to be able to allocate our own "struct address_space" to control include/drm/drm_device.h +23
-0@@ -40,6 +40,26 @@ enum switch_power_state { DRM_SWITCH_POWER_DYNAMIC_OFF = 3, }; +/** +* enum drm_wedge_recovery - Recovery method for wedged device in order of +* severity. To be set as bit fields in drm_device.wedge_recovery variable. +* Drivers can choose to support any one or multiple of them depending on +* their needs. +*/ +enum drm_wedge_recovery { +/** @DRM_WEDGE_RECOVERY_REBIND: unbind + rebind driver */ +DRM_WEDGE_RECOVERY_REBIND , + +/** @DRM_WEDGE_RECOVERY_BUS_RESET: unbind + reset bus device + rebind */ +DRM_WEDGE_RECOVERY_BUS_RESET , + +/** @DRM_WEDGE_RECOVERY_REBOOT: reboot system */ +DRM_WEDGE_RECOVERY_REBOOT , + +/** @DRM_WEDGE_RECOVERY_MAX: for bounds checking, do not use */ +DRM_WEDGE_RECOVERY_MAX +}; +/** * struct drm_device - DRM device structure * @@ -317,6 +337,9 @@ struct drm_device {* Root directory for debugfs files. */ struct dentry *debugfs_root; + +/** @wedge_recovery: Supported recovery methods for wedged device */ + unsigned long wedge_recovery; };#endif include/drm/drm_drv.h +3
-0@@ -462,6 +462,9 @@ bool drm_dev_enter(struct drm_device *dev, int *idx);void drm_dev_exit (int idx);void drm_dev_unplug (struct drm_device *dev); +const char *drm_wedge_recovery_name (enum drm_wedge_recovery method); +int drm_dev_wedged_event (struct drm_device *dev,enum drm_wedge_recovery method); +/** * drm_dev_is_unplugged - is a DRM device unplugged * @dev: DRM device Signature · 1 line
2.34.1
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Am 17.10.24 um 18:43 schrieb Rodrigo Vivi:
Quoted 27 lines · Christian König
Quoted 26 lines
Quoted 13 lines
Quoted 13 lines
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
Quoted 7 lines
Quoted 7 lines
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================Well that sounds like userspace would need to be involved in recovery.
That in turn is a complete no-go since we at least need to signal all
dma_fencesto unblock the kernel. In other words things like bus reset needs to happen inside the kernel and *not* in userspace.
Quoted 7 lines
Quoted 3 lines
What we can do is to signal to userspace: Hey a bus reset of device X happened, maybe restart container, daemon, whatever service which was using this device.
Well, when we declare device 'wedged' it is because we don't want to take any drastic measures inside the kernel and want to leave it in a protected and unusable state. In a way that users wouldn't lose display for instance, or at least the device is in a debugable state.
Uff, that needs to be very very well documented or otherwise the whole approach is an absolutely clear NAK from my side as DMA-buf maintainer.
Quoted 10 lines
Then, the instructions here is to tell what could possibly be attempted from userspace to get the device to an usable state.
The 'wedge' mode (the one emiting this uevent) needs to be responsible for signaling all the fences and everything needed for a clean unbind and whatever next step might be indicated to userspace.
That should already be part of any wedged mode, regardless the uevent to inform the userspace here.
You need to approach that from a different side. With the current patch set you are ignoring documented mandatory driver behavior as far as I can see.
So first of all describe in the documentation what the wedged mode is and what requirements a driver has to fulfill to enter it: https://docs.kernel.org/gpu/drm-uapi.html#device-reset
Especially document that all system memory accesses of the device needs to be blocked by (for example) disabling DMA accesses in the PCI config space.
When it is guaranteed that the device can't access any system memory any more the device driver should signal all pending fences of this device.
And only after all of that is done the driver can send an uevent to inform userspace that it can debug the hanged state.
As far as I can see this makes the enum how to recover the device superfluous because you will most likely always need a bus reset to get out of this again.
Regards,
Christian.
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 57 lines · Christian König
Am 17.10.24 um 18:43 schrieb Rodrigo Vivi:
Quoted 27 lines · Christian König
Quoted 26 lines
Quoted 13 lines
Quoted 13 lines
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
Quoted 7 lines
Quoted 7 lines
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================Well that sounds like userspace would need to be involved in recovery.
That in turn is a complete no-go since we at least need to signal all
dma_fencesto unblock the kernel. In other words things like bus reset needs to happen inside the kernel and *not* in userspace.Quoted 7 lines
Quoted 3 lines
What we can do is to signal to userspace: Hey a bus reset of device X happened, maybe restart container, daemon, whatever service which was using this device.
Well, when we declare device 'wedged' it is because we don't want to take any drastic measures inside the kernel and want to leave it in a protected and unusable state. In a way that users wouldn't lose display for instance, or at least the device is in a debugable state.
Uff, that needs to be very very well documented or otherwise the whole approach is an absolutely clear NAK from my side as DMA-buf maintainer.
Quoted 10 lines
Then, the instructions here is to tell what could possibly be attempted from userspace to get the device to an usable state.
The 'wedge' mode (the one emiting this uevent) needs to be responsible for signaling all the fences and everything needed for a clean unbind and whatever next step might be indicated to userspace.
That should already be part of any wedged mode, regardless the uevent to inform the userspace here.
You need to approach that from a different side. With the current patch set you are ignoring documented mandatory driver behavior as far as I can see.
So first of all describe in the documentation what the wedged mode is and what requirements a driver has to fulfill to enter it:
https://docs.kernel.org/gpu/drm-uapi.html#device-reset
Quoted 8 lines
Especially document that all system memory accesses of the device needs to be blocked by (for example) disabling DMA accesses in the PCI config space.
When it is guaranteed that the device can't access any system memory any more the device driver should signal all pending fences of this device.
And only after all of that is done the driver can send an uevent to inform userspace that it can debug the hanged state.
Sure, will do.
Quoted 3 lines
As far as I can see this makes the enum how to recover the device superfluous because you will most likely always need a bus reset to get out of this again.
That depends on the kind of fault the device has encountered and the bus it is sitting on. There could be buses that don't support reset.
Raag
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Am 18.10.24 um 14:46 schrieb Raag Jadav:
Quoted 5 lines
Quoted 3 lines
As far as I can see this makes the enum how to recover the device superfluous because you will most likely always need a bus reset to get out of this again.
That depends on the kind of fault the device has encountered and the bus it is sitting on. There could be buses that don't support reset.
That is even more an argument to not expose this in the uevent.
Getting the device working again is strongly device dependent and can't be handled in a generic way.
Regards,
Christian.
Quoted 2 lines
Raag
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 11 lines · Christian König
Am 18.10.24 um 14:46 schrieb Raag Jadav:
Quoted 5 lines
Quoted 3 lines
As far as I can see this makes the enum how to recover the device superfluous because you will most likely always need a bus reset to get out of this again.
That depends on the kind of fault the device has encountered and the bus it is sitting on. There could be buses that don't support reset.
That is even more an argument to not expose this in the uevent.
Getting the device working again is strongly device dependent and can't be handled in a generic way.
My understanding is that the proposed methods can be handled in a generic way and are useful for the devices that do support it. This way the userspace can atleast have a hint about recovery.
For others we can have something like WEDGED=none (as proposed by Michal and Lucas in other threads) and let admin/user decide how to deal with it.
Raag
Re: [PATCH v7 1/5] drm: Introduce device wedged event
In reply to Raag JadavHi Raag,
Em 30/09/2024 04:38, Raag Jadav escreveu:
Quoted 19 lines
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
Quoted 9 lines
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================
I proposed something similar in the past: https://lore.kernel.org/dri-devel/[email protected]/
The motivation was that amdgpu was getting stuck after every GPU reset, and there was just a black screen. The uevent would then trigger a daemon to reset the compositor and getting things back together. As you can see in my thread, the feature was blocked in favor of getting better overall GPU reset from the kernel side.
Which kind of scenarios are making i915/xe the need to have userspace involvement? I tested a bunch of resets in i915 but never managed to get the driver stuck.
For the bus-reset, amdgpu does that too, but it doesn't require userspace intervention.
Rodrigo Vivi
maintainerRe: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 40 lines · André Almeida
Hi Raag,
Em 30/09/2024 04:38, Raag Jadav escreveu:
Quoted 19 lines
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
Quoted 9 lines
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================I proposed something similar in the past: https://lore.kernel.org/dri-devel/[email protected]/
The motivation was that amdgpu was getting stuck after every GPU reset, and there was just a black screen. The uevent would then trigger a daemon to reset the compositor and getting things back together. As you can see in my thread, the feature was blocked in favor of getting better overall GPU reset from the kernel side.
Quoted 3 lines
Which kind of scenarios are making i915/xe the need to have userspace involvement? I tested a bunch of resets in i915 but never managed to get the driver stuck.
2 scenarios:
1. Multiple levels of reset has failed and device was declared wedged. This is rare indeed as the resets improved a lot.
2. Debug case. We can boot the driver with option to declare device wedged at any timeout, so the device can be debugged.
Quoted 3 lines
For the bus-reset, amdgpu does that too, but it doesn't require userspace intervention.
How do you trigger that?
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 54 lines · Rodrigo Vivi
Quoted 40 lines · André Almeida
Hi Raag,
Em 30/09/2024 04:38, Raag Jadav escreveu:
Quoted 19 lines
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
Quoted 9 lines
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================I proposed something similar in the past: https://lore.kernel.org/dri-devel/[email protected]/
The motivation was that amdgpu was getting stuck after every GPU reset, and there was just a black screen. The uevent would then trigger a daemon to reset the compositor and getting things back together. As you can see in my thread, the feature was blocked in favor of getting better overall GPU reset from the kernel side.
Quoted 3 lines
Which kind of scenarios are making i915/xe the need to have userspace involvement? I tested a bunch of resets in i915 but never managed to get the driver stuck.
2 scenarios:
1. Multiple levels of reset has failed and device was declared wedged. This is rare indeed as the resets improved a lot.
2. Debug case. We can boot the driver with option to declare device wedged at any timeout, so the device can be debugged.Quoted 1 line
Quoted 4 lines
Quoted 2 lines
For the bus-reset, amdgpu does that too, but it doesn't require userspace intervention.
How do you trigger that?
What do you mean by bus reset? I think Chrisitian is just referring to a full adapter reset (as opposed to a queue reset or something more fine grained). Driver can reset the device via MMIO or firmware, depending on the device. I think there are also PCI helpers for things like PCI FLR.
Alex
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Em 18/10/2024 12:31, Alex Deucher escreveu:
Quoted 58 lines · Rodrigo Vivi
Quoted 57 lines · André Almeida
Quoted 40 lines
Hi Raag,
Em 30/09/2024 04:38, Raag Jadav escreveu:
Quoted 19 lines
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
Quoted 9 lines
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================I proposed something similar in the past: https://lore.kernel.org/dri-devel/[email protected]/
The motivation was that amdgpu was getting stuck after every GPU reset, and there was just a black screen. The uevent would then trigger a daemon to reset the compositor and getting things back together. As you can see in my thread, the feature was blocked in favor of getting better overall GPU reset from the kernel side.
Quoted 3 lines
Which kind of scenarios are making i915/xe the need to have userspace involvement? I tested a bunch of resets in i915 but never managed to get the driver stuck.
2 scenarios:
1. Multiple levels of reset has failed and device was declared wedged. This is rare indeed as the resets improved a lot.
2. Debug case. We can boot the driver with option to declare device wedged at any timeout, so the device can be debugged.Quoted 3 lines
For the bus-reset, amdgpu does that too, but it doesn't require userspace intervention.
Quoted 8 lines
Quoted 1 line
How do you trigger that?
What do you mean by bus reset? I think Chrisitian is just referring to a full adapter reset (as opposed to a queue reset or something more fine grained). Driver can reset the device via MMIO or firmware, depending on the device. I think there are also PCI helpers for things like PCI FLR.
I was referring to AMD_RESET_PCI:
"Does a full bus reset using core Linux subsystem PCI reset and does a secondary bus reset or FLR, depending on what the underlying hardware supports."
And that can be triggered by using amdgpu_reset_method=5 as the module option.
Re: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 69 lines · André Almeida
Em 18/10/2024 12:31, Alex Deucher escreveu:
Quoted 58 lines · Rodrigo Vivi
Quoted 57 lines · André Almeida
Quoted 40 lines
Hi Raag,
Em 30/09/2024 04:38, Raag Jadav escreveu:
Quoted 19 lines
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
Quoted 9 lines
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================I proposed something similar in the past: https://lore.kernel.org/dri-devel/[email protected]/
The motivation was that amdgpu was getting stuck after every GPU reset, and there was just a black screen. The uevent would then trigger a daemon to reset the compositor and getting things back together. As you can see in my thread, the feature was blocked in favor of getting better overall GPU reset from the kernel side.
Quoted 3 lines
Which kind of scenarios are making i915/xe the need to have userspace involvement? I tested a bunch of resets in i915 but never managed to get the driver stuck.
2 scenarios:
1. Multiple levels of reset has failed and device was declared wedged. This is rare indeed as the resets improved a lot.
2. Debug case. We can boot the driver with option to declare device wedged at any timeout, so the device can be debugged.Quoted 3 lines
For the bus-reset, amdgpu does that too, but it doesn't require userspace intervention.
Quoted 8 lines
Quoted 1 line
How do you trigger that?
What do you mean by bus reset? I think Chrisitian is just referring to a full adapter reset (as opposed to a queue reset or something more fine grained). Driver can reset the device via MMIO or firmware, depending on the device. I think there are also PCI helpers for things like PCI FLR.
Quoted 9 lines
I was referring to
AMD_RESET_PCI:"Does a full bus reset using core Linux subsystem PCI reset and does a secondary bus reset or FLR, depending on what the underlying hardware supports."
And that can be triggered by using
amdgpu_reset_method=5as the module option.
That option doesn't actually do anything useful on most AMD GPUs. We don't support FLR on most boards and SBR doesn't work once the driver has been loaded except for really old chips. That said, internally these all end up being mode1 or mode2 resets which the driver can trigger directly and which are the defaults.
Alex
Rodrigo Vivi
maintainerRe: [PATCH v7 1/5] drm: Introduce device wedged event
Quoted 80 lines · Alex Deucher
Quoted 69 lines · André Almeida
Em 18/10/2024 12:31, Alex Deucher escreveu:
Quoted 58 lines · Rodrigo Vivi
Quoted 57 lines · André Almeida
Quoted 40 lines
Hi Raag,
Em 30/09/2024 04:38, Raag Jadav escreveu:
Quoted 19 lines
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
Quoted 9 lines
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================I proposed something similar in the past: https://lore.kernel.org/dri-devel/[email protected]/
The motivation was that amdgpu was getting stuck after every GPU reset, and there was just a black screen. The uevent would then trigger a daemon to reset the compositor and getting things back together. As you can see in my thread, the feature was blocked in favor of getting better overall GPU reset from the kernel side.
Quoted 3 lines
Which kind of scenarios are making i915/xe the need to have userspace involvement? I tested a bunch of resets in i915 but never managed to get the driver stuck.
2 scenarios:
1. Multiple levels of reset has failed and device was declared wedged. This is rare indeed as the resets improved a lot.
2. Debug case. We can boot the driver with option to declare device wedged at any timeout, so the device can be debugged.Quoted 3 lines
For the bus-reset, amdgpu does that too, but it doesn't require userspace intervention.
Quoted 8 lines
Quoted 1 line
How do you trigger that?
What do you mean by bus reset? I think Chrisitian is just referring to a full adapter reset (as opposed to a queue reset or something more fine grained). Driver can reset the device via MMIO or firmware, depending on the device. I think there are also PCI helpers for things like PCI FLR.
Quoted 9 lines
I was referring to
AMD_RESET_PCI:"Does a full bus reset using core Linux subsystem PCI reset and does a secondary bus reset or FLR, depending on what the underlying hardware supports."
And that can be triggered by using
amdgpu_reset_method=5as the module option.
Quoted 5 lines
That option doesn't actually do anything useful on most AMD GPUs. We don't support FLR on most boards and SBR doesn't work once the driver has been loaded except for really old chips. That said, internally these all end up being mode1 or mode2 resets which the driver can trigger directly and which are the defaults.
okay, this is the same for us then.
And this is the main reason that we have this option:
- unbind + reset bus device + rebind
unbind by itself needs to be a supported and working case regardless the reset state. Then this sequence should be fine.
Afaik there's no way that the driver itself could call for the bus reset.
Quoted 2 lines
Alex
Re: [PATCH v7 1/5] drm: Introduce device wedged event
In reply to André AlmeidaQuoted 32 lines · André Almeida
Hi Raag,
Em 30/09/2024 04:38, Raag Jadav escreveu:
Quoted 19 lines
Introduce device wedged event, which will notify userspace of wedged (hanged/unusable) state of the DRM device through a uevent. This is useful especially in cases where the device is no longer operating as expected even after a hardware reset and has become unrecoverable from driver context.
Purpose of this implementation is to provide drivers a generic way to recover with the help of userspace intervention. Different drivers may have different ideas of a "wedged device" depending on their hardware implementation, and hence the vendor agnostic nature of the event. It is up to the drivers to decide when they see the need for recovery and how they want to recover from the available methods.
Current implementation defines three recovery methods, out of which, drivers can choose to support any one or multiple of them. Preferred recovery method will be sent in the uevent environment as WEDGED=<method>. Userspace consumers (sysadmin) can define udev rules to parse this event and take respective action to recover the device.
Quoted 9 lines
=============== ================================== Recovery method Consumer expectations =============== ==================================
rebind unbind + rebind driver
bus-reset unbind + reset bus device + rebind
reboot reboot system
=============== ==================================
Quoted 2 lines
I proposed something similar in the past:
https://lore.kernel.org/dri-devel/[email protected]/
Thanks for sharing. I went through it and I think we can use some of the ideas with generic adaption.
While we can always execute scripts on uevent, it'd be good to have a userspace daemon applying automated policies for wedge cases based on admin/user needs. This way we can also manage repeat offenders.
Xe has devcoredump so telemetry would also be a nice addition.
Great opportunity to collaborate here.
Quoted 5 lines
The motivation was that amdgpu was getting stuck after every GPU reset, and there was just a black screen. The uevent would then trigger a daemon to reset the compositor and getting things back together. As you can see in my thread, the feature was blocked in favor of getting better overall GPU reset from the kernel side.
We have hardware level resets but (although rare) they're also prone to failure. We do what we can to recover from driver context but it adds on to the complexity overtime. Something like wedging, if done right, would be much more robust IMHO.
Raag
PATCH v7 2/5 drm: Expose wedge recovery methods
In reply to Raag JadavNow that we have device wedged event in place, add wedge_recovery sysfs attribute which will expose recovery methods supported by the DRM device. This is useful for userspace consumers in cases where the device supports multiple recovery methods which can be used as fallbacks.
$ cat /sys/class/drm/card<N>/wedge_recovery rebind bus-reset reboot
--- drivers/gpu/drm/drm_sysfs.c | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+)
drivers/gpu/drm/drm_sysfs.c +22 -0
@@ -24,6 +24,7 @@#include <drm/drm_accel.h> #include <drm/drm_connector.h> #include <drm/drm_device.h> +#include <drm/drm_drv.h> #include <drm/drm_file.h> #include <drm/drm_modes.h> #include <drm/drm_print.h>
@@ -508,6 +509,26 @@ void drm_sysfs_connector_property_event(struct drm_connector *connector, }EXPORT_SYMBOL (drm_sysfs_connector_property_event); +static ssize_t wedge_recovery_show (struct device *device, +struct device_attribute *attr,char *buf) +{ +struct drm_minor *minor =to_drm_minor (device); +struct drm_device *dev = minor->dev; +unsigned int method, count =DRM_WEDGE_RECOVERY_REBIND ; + +for_each_set_bit (method, &dev->wedge_recovery,DRM_WEDGE_RECOVERY_MAX ) + count +=sysfs_emit_at (buf, count,"%s\n" ,drm_wedge_recovery_name (method)); + +return count; +} +static DEVICE_ATTR_RO (wedge_recovery); + +static struct attribute *minor_dev_attrs[] = { + &dev_attr_wedge_recovery.attr, +NULL +}; +ATTRIBUTE_GROUPS (minor_dev); +struct device *drm_sysfs_minor_alloc (struct drm_minor *minor) {const char *minor_str;
@@ -532,6 +553,7 @@ struct device *drm_sysfs_minor_alloc(struct drm_minor *minor) kdev->devt =MKDEV (DRM_MAJOR , minor->index); kdev->class = drm_class; kdev->type = &drm_sysfs_device_minor; + kdev->groups = minor_dev_groups; } kdev->parent = minor->dev->dev;
Signature · 1 line
2.34.1
Re: [PATCH v7 2/5] drm: Expose wedge recovery methods
Quoted 9 lines · Raag Jadav
Now that we have device wedged event in place, add
wedge_recoverysysfs attribute which will expose recovery methods supported by the DRM device. This is useful for userspace consumers in cases where the device supports multiple recovery methods which can be used as fallbacks.$ cat /sys/class/drm/card<N>/wedge_recovery rebind bus-reset reboot
...
drivers/gpu/drm/drm_sysfs.c void drm_sysfs_connector_property_event(struct drm_connector *connector, · line 513
Quoted 2 lines
drivers/gpu/drm/drm_sysfs.c +2
-0+static ssize_t wedge_recovery_show (struct device *device, +struct device_attribute *attr,char *buf)
Looking at the below line it seems you are fine with 100 limit, so, why two lines above if they perfectly fit 100?
Quoted 10 lines
drivers/gpu/drm/drm_sysfs.c +10
-0+{ +struct drm_minor *minor =to_drm_minor (device); +struct drm_device *dev = minor->dev; +unsigned int method, count =DRM_WEDGE_RECOVERY_REBIND ; + +for_each_set_bit (method, &dev->wedge_recovery,DRM_WEDGE_RECOVERY_MAX ) + count +=sysfs_emit_at (buf, count,"%s\n" ,drm_wedge_recovery_name (method)); + +return count; +}
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v7 2/5] drm: Expose wedge recovery methods
Quoted 11 lines · Andy Shevchenko
Quoted 9 lines · Raag Jadav
Now that we have device wedged event in place, add
wedge_recoverysysfs attribute which will expose recovery methods supported by the DRM device. This is useful for userspace consumers in cases where the device supports multiple recovery methods which can be used as fallbacks.$ cat /sys/class/drm/card<N>/wedge_recovery rebind bus-reset reboot
Quoted 7 lines
...
drivers/gpu/drm/drm_sysfs.c void drm_sysfs_connector_property_event(struct drm_connector *connector, · line 513
Quoted 2 lines
drivers/gpu/drm/drm_sysfs.c +2
-0+static ssize_t wedge_recovery_show (struct device *device, +struct device_attribute *attr,char *buf)Looking at the below line it seems you are fine with 100 limit, so, why two lines above if they perfectly fit 100?
Just trying to avoid another bikeshed about conventions ;)
Raag
PATCH v7 3/5 drm/doc: Document device wedged event
In reply to Raag JadavAdd documentation for device wedged event along with its consumer expectations. For now it is amended to 'Device reset' chapter, but with extended functionality in the future it can be refactored into its own chapter.
--- Documentation/gpu/drm-uapi.rst | 42 ++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+)
Documentation/gpu/drm-uapi.rst +42 -0
@@ -313,6 +313,22 @@ driver separately, with no common DRM interface. Ideally this should be properly integrated at DRM scheduler to provide a common ground for all drivers. After a reset, KMD should reject new command submissions for affected contexts. +Drivers can optionally make use of device wedged event (implemented as +drm_dev_wedged_event() in DRM subsystem) which notifies userspace of wedged +(hanged/unusable) state of the DRM device through a uevent. This is useful +especially in cases where the device is no longer operating as expected even +after a hardware reset and has become unrecoverable from driver context. +Purpose of this implementation is to provide drivers a generic way to recover +with the help of userspace intervention, and hence the vendor agnostic nature +of the event. + +Different drivers may have different ideas of a "wedged device" depending on +their hardware implementation. It is up to the drivers to decide when they see +the need for recovery and how they want to recover from the available methods. +Current implementation defines three recovery methods, out of which, drivers +can choose to support any one or multiple of them. Preferred recovery method +will be sent in the uevent environment as WEDGED=<method>. + User Mode Driver ----------------
@@ -323,6 +339,32 @@ if the UMD requires it. After detecting a reset, UMD will then proceed to report it to the application using the appropriate API error code, as explained in the section below about robustness. +On device wedged scenario, userspace will receive a uevent from KMD with +its preferred recovery method in the uevent environment as WEDGED=<method>. +Userspace consumers (sysadmin) can define udev rules to parse this event +and take respective action to recover the device. + +.. table:: Wedged Device Recovery + + =============== ================================== + Recovery method Consumer expectations + =============== ================================== + rebind unbind + rebind driver + bus-reset unbind + reset bus device + rebind + reboot reboot system + =============== ================================== + +Userspace consumers can optionally read the recovery methods supported by the +device via ``wedge_recovery`` sysfs attribute:: + + $ cat /sys/class/drm/card<N>/wedge_recovery + rebind + bus-reset + reboot + +This is useful in cases where the device supports multiple recovery methods +which can be used as fallbacks. + Robustness ----------
Signature · 1 line
2.34.1
PATCH v7 4/5 drm/xe: Use device wedged event
In reply to Raag JadavThis was previously attempted as xe specific reset uevent but dropped in commit 77a0d4d1cea2 ("drm/xe/uapi: Remove reset uevent for now") as part of refactoring.
Now that we have device wedged event provided by DRM core, make use of it and support both driver rebind and bus-reset based recovery. With this in place userspace will be notified of wedged device, on the basis of which, userspace may take respective action to recover the device.
$ udevadm monitor --property --kernel monitor will print the received events for: KERNEL - the kernel uevent
KERNEL[265.802982] change /devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:01.0/0000:03:00.0/drm/card0 (drm)
ACTION=change DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:01.0/0000:03:00.0/drm/card0 SUBSYSTEM=drm
WEDGED=bus-reset
DEVNAME=/dev/dri/card0
DEVTYPE=drm_minor
SEQNUM=5208
MAJOR=226
MINOR=0
v2: Change authorship to Himal (Aravind)
Add uevent for all device wedged cases (Aravind)
v3: Generic re-implementation in DRM subsystem (Lucas)
v4: Change authorship to Raag (Aravind)
--- drivers/gpu/drm/xe/xe_device.c | 17 +++++++++++++++-- drivers/gpu/drm/xe/xe_device.h | 1 + drivers/gpu/drm/xe/xe_pci.c | 2 ++ 3 files changed, 18 insertions(+), 2 deletions(-)
drivers/gpu/drm/xe/xe_device.c +15 -2
@@ -785,6 +785,15 @@ int xe_device_probe(struct xe_device *xe)return err; } +void xe_setup_wedge_recovery (struct xe_device *xe) +{ +struct drm_device *dev = &xe->drm; + +/* Support both driver rebind and bus-reset based recovery. */ +set_bit (DRM_WEDGE_RECOVERY_REBIND , &dev->wedge_recovery); +set_bit (DRM_WEDGE_RECOVERY_BUS_RESET , &dev->wedge_recovery); +} +static void xe_device_remove_display (struct xe_device *xe) {xe_display_unregister (xe);
@@ -991,11 +1000,12 @@ static void xe_device_wedged_fini(struct drm_device *drm, void *arg)* xe_device_declare_wedged - Declare device wedged * @xe: xe device instance * -* This is a final state that can only be cleared with a mudule +* This is a final state that can only be cleared with a module * re-probe (unbind + bind). * In this state every IOCTL will be blocked so the GT cannot be used. * In general it will be called upon any critical error such as gt reset -* failure or guc loading failure. +* failure or guc loading failure. Userspace will be notified of this state +* by a DRM uevent. * If xe.wedged module parameter is set to 2, this function will be called * on every single execution timeout (a.k.a. GPU hang) right after devcoredump * snapshot capture. In this mode, GT reset won't be attempted so the state of
@@ -1025,6 +1035,9 @@ void xe_device_declare_wedged(struct xe_device *xe)"IOCTLs and executions are blocked. Only a rebind may clear the failure\n" "Please file a _new_ bug report at https://gitlab.freedesktop.org/drm/xe/kernel/issues/new\n" , dev_name(xe->drm.dev)); + +/* Notify userspace of wedged device */ +drm_dev_wedged_event (&xe->drm,DRM_WEDGE_RECOVERY_BUS_RESET ); }for_each_gt (gt, xe, id)
drivers/gpu/drm/xe/xe_device.h +1 -0
@@ -186,6 +186,7 @@ static inline bool xe_device_wedged(struct xe_device *xe)return atomic_read (&xe->wedged.flag); } +void xe_setup_wedge_recovery (struct xe_device *xe);void xe_device_declare_wedged (struct xe_device *xe);struct xe_file *xe_file_get (struct xe_file *xef);
drivers/gpu/drm/xe/xe_pci.c +2 -0
@@ -860,6 +860,8 @@ static int xe_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent)if (err) goto err_driver_cleanup; +xe_setup_wedge_recovery (xe); +drm_dbg (&xe->drm,"d3cold: capable=%s\n" ,str_yes_no (xe->d3cold.capable));
Signature · 1 line
2.34.1
PATCH v7 5/5 drm/i915: Use device wedged event
In reply to Raag JadavNow that we have device wedged event provided by DRM core, make use of it and support both driver rebind and bus-reset based recovery. With this in place, userspace will be notified of wedged device on gt reset failure.
--- drivers/gpu/drm/i915/gt/intel_reset.c | 2 ++ drivers/gpu/drm/i915/i915_driver.c | 10 ++++++++++ 2 files changed, 12 insertions(+)
drivers/gpu/drm/i915/gt/intel_reset.c +2 -0
@@ -1418,6 +1418,8 @@ static void intel_gt_reset_global(struct intel_gt *gt,if (!test_bit (I915_WEDGED , >->reset.flags))kobject_uevent_env (kobj,KOBJ_CHANGE , reset_done_event); +else +drm_dev_wedged_event (>->i915->drm,DRM_WEDGE_RECOVERY_BUS_RESET ); }/**
drivers/gpu/drm/i915/i915_driver.c +10 -0
@@ -711,6 +711,15 @@ static void i915_welcome_messages(struct drm_i915_private *dev_priv) "DRM_I915_DEBUG_RUNTIME_PM enabled\n"); } +static void i915_setup_wedge_recovery (struct drm_i915_private *i915) +{ +struct drm_device *dev = &i915->drm; + +/* Support both driver rebind and bus-reset based recovery. */ +set_bit (DRM_WEDGE_RECOVERY_REBIND , &dev->wedge_recovery); +set_bit (DRM_WEDGE_RECOVERY_BUS_RESET , &dev->wedge_recovery); +} +static struct drm_i915_private *i915_driver_create (struct pci_dev *pdev,const struct pci_device_id *ent) {
@@ -812,6 +821,7 @@ int i915_driver_probe(struct pci_dev *pdev, const struct pci_device_id *ent)enable_rpm_wakeref_asserts (&i915->runtime_pm); +i915_setup_wedge_recovery (i915);i915_welcome_messages (i915); i915->do_release = true;
Signature · 1 line
2.34.1
Patchwork
CI✗ CI.Patch_applied: failure for Introduce DRM device wedged event (rev5)
In reply to Raag Jadav== Series Details ==
== Series Details ==
Series: Introduce DRM device wedged event (rev5)
URL : https://patchwork.freedesktop.org/series/138070/
State : failure
== Summary ==
=== Applying kernel patches on branch 'drm-tip' with base: ===
Base commit: cd8c80767801 drm-tip: 2024y-09m-30d-06h-48m-45s UTC integration manifest === git am output follows ===
error: patch failed: Documentation/gpu/drm-uapi.rst:313
error: Documentation/gpu/drm-uapi.rst: patch does not apply
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Applying: drm: Introduce device wedged event
Applying: drm: Expose wedge recovery methods
Applying: drm/doc: Document device wedged event
Patch failed at 0003 drm/doc: Document device wedged event
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".
Patchwork
CI✗ Fi.CI.CHECKPATCH: warning for Introduce DRM device wedged event (rev5)
In reply to Raag Jadav== Series Details ==
== Series Details ==
Series: Introduce DRM device wedged event (rev5)
URL : https://patchwork.freedesktop.org/series/138069/
State : warning
== Summary ==
Error: patch https://patchwork.freedesktop.org/api/1.0/series/138069/revisions/5/mbox/ not found
Patchwork
CI✗ Fi.CI.SPARSE: warning for Introduce DRM device wedged event (rev5)
In reply to Raag Jadav== Series Details ==
== Series Details ==
Series: Introduce DRM device wedged event (rev5)
URL : https://patchwork.freedesktop.org/series/138069/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Patchwork
CI✓ Fi.CI.BAT: success for Introduce DRM device wedged event (rev5)
In reply to Raag Jadav== Series Details ==
== Series Details ==
Series: Introduce DRM device wedged event (rev5)
URL : https://patchwork.freedesktop.org/series/138069/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_15461 -> Patchwork_138069v5
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/index.html
Participating hosts (42 -> 43)
------------------------------
Additional (2): bat-dg2-13 bat-rpls-4
Missing (1): fi-snb-2520m
Known issues
------------
Here are the changes found in Patchwork_138069v5 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@debugfs_test@basic-hwmon:
- bat-rpls-4: NOTRUN -> [SKIP][1] ([i915#9318])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-rpls-4/igt@[email protected]
* igt@gem_lmem_swapping@parallel-random-engines:
- bat-rpls-4: NOTRUN -> [SKIP][2] ([i915#4613]) +3 other tests skip
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-rpls-4/igt@[email protected]
* igt@gem_tiled_pread_basic:
- bat-rpls-4: NOTRUN -> [SKIP][3] ([i915#3282])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-rpls-4/igt@gem_tiled_pread_basic.html
* igt@i915_selftest@live:
- bat-mtlp-8: [PASS][4] -> [ABORT][5] ([i915#12216]) +1 other test abort
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/bat-mtlp-8/igt@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-mtlp-8/igt@[email protected]
- bat-arlh-2: [PASS][6] -> [ABORT][7] ([i915#12133])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/bat-arlh-2/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-arlh-2/igt@[email protected]
* igt@i915_selftest@live@gt_heartbeat:
- bat-arls-5: NOTRUN -> [DMESG-WARN][8] ([i915#11637] / [i915#12133]) +8 other tests dmesg-warn
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-arls-5/igt@i915_selftest@live@gt_heartbeat.html
* igt@i915_selftest@live@gt_tlb:
- bat-arls-5: NOTRUN -> [DMESG-WARN][9] ([i915#11637]) +21 other tests dmesg-warn
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-arls-5/igt@i915_selftest@live@gt_tlb.html
* igt@i915_selftest@live@objects:
- bat-arls-5: NOTRUN -> [DMESG-WARN][10] ([i915#10341] / [i915#11637]) +2 other tests dmesg-warn
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-arls-5/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@workarounds:
- bat-arlh-2: [PASS][11] -> [ABORT][12] ([i915#12061])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/bat-arlh-2/igt@i915_selftest@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-arlh-2/igt@i915_selftest@[email protected]
* igt@kms_chamelium_hpd@dp-hpd-fast:
- bat-dg2-13: NOTRUN -> [SKIP][13] ([i915#7828]) +8 other tests skip
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-dg2-13/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- bat-rpls-4: NOTRUN -> [SKIP][14] ([i915#4103]) +1 other test skip
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-rpls-4/igt@[email protected]
* igt@kms_dsc@dsc-basic:
- bat-rpls-4: NOTRUN -> [SKIP][15] ([i915#3555] / [i915#3840] / [i915#9886])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-rpls-4/igt@[email protected]
* igt@kms_force_connector_basic@force-load-detect:
- bat-rpls-4: NOTRUN -> [SKIP][16]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-rpls-4/igt@[email protected]
* igt@kms_pm_backlight@basic-brightness:
- bat-rpls-4: NOTRUN -> [SKIP][17] ([i915#5354])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-rpls-4/igt@[email protected]
* igt@kms_psr@psr-primary-page-flip:
- bat-rpls-4: NOTRUN -> [SKIP][18] ([i915#1072] / [i915#9732]) +3 other tests skip
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-rpls-4/igt@[email protected]
* igt@kms_setmode@basic-clone-single-crtc:
- bat-rpls-4: NOTRUN -> [SKIP][19] ([i915#3555])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-rpls-4/igt@[email protected]
* igt@prime_vgem@basic-read:
- bat-rpls-4: NOTRUN -> [SKIP][20] ([i915#3708]) +2 other tests skip
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-rpls-4/igt@[email protected]
#### Warnings ####
* igt@i915_module_load@reload:
- bat-arls-5: [DMESG-WARN][21] ([i915#11637] / [i915#1982]) -> [DMESG-WARN][22] ([i915#11637])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/bat-arls-5/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-arls-5/igt@[email protected]
* igt@i915_selftest@live:
- bat-arls-5: [ABORT][23] ([i915#12061] / [i915#12133]) -> [DMESG-WARN][24] ([i915#10341] / [i915#12133])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/bat-arls-5/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-arls-5/igt@[email protected]
* igt@i915_selftest@live@workarounds:
- bat-arls-5: [ABORT][25] ([i915#12061]) -> [DMESG-WARN][26] ([i915#10341] / [i915#11637])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/bat-arls-5/igt@i915_selftest@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/bat-arls-5/igt@i915_selftest@[email protected]
* igt@kms_pm_rpm@basic-pci-d3-state:
- fi-kbl-7567u: [DMESG-WARN][27] ([i915#11621] / [i915#180]) -> [DMESG-WARN][28] ([i915#11621] / [i915#180] / [i915#1982]) +1 other test dmesg-warn
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/fi-kbl-7567u/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/fi-kbl-7567u/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#10341]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10341
[i915#1072]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/1072
[i915#11621]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11621
[i915#11637]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11637
[i915#12061]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12061
[i915#12133]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12133
[i915#12216]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12216
[i915#180]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/180
[i915#1982]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/1982
[i915#3282]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3282
[i915#3555]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3555
[i915#3708]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3708
[i915#3840]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/3840
[i915#4103]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4103
[i915#4613]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4613
[i915#5354]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/5354
[i915#7828]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7828
[i915#9318]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9318
[i915#9732]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9732
[i915#9886]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9886
Build changes
-------------
* Linux: CI_DRM_15461 -> Patchwork_138069v5
CI-20190529: 20190529
CI_DRM_15461: 4e4d7873ac763aa0bd9207ea9ec2b89bb52a6fe1 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_8043: 8043
Patchwork_138069v5: 4e4d7873ac763aa0bd9207ea9ec2b89bb52a6fe1 @ git://anongit.freedesktop.org/gfx-ci/linux
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/index.html
Patchwork
CI✗ Fi.CI.IGT: failure for Introduce DRM device wedged event (rev5)
In reply to Raag Jadav== Series Details ==
== Series Details ==
Series: Introduce DRM device wedged event (rev5)
URL : https://patchwork.freedesktop.org/series/138069/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_15461_full -> Patchwork_138069v5_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_138069v5_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_138069v5_full, please notify your bug team ([email protected]) to allow them to document this new failure mode, which will reduce false positives in CI.
Participating hosts (9 -> 8)
------------------------------
Missing (1): shard-glk-0
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_138069v5_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_ctx_isolation@preservation-s3@vcs0:
- shard-dg1: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-16/igt@gem_ctx_isolation@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-19/igt@gem_ctx_isolation@[email protected]
* igt@kms_cursor_crc@cursor-sliding-512x512:
- shard-mtlp: NOTRUN -> [SKIP][3]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@[email protected]
* igt@kms_cursor_crc@cursor-suspend@pipe-d-hdmi-a-3:
- shard-dg1: NOTRUN -> [INCOMPLETE][4] +1 other test incomplete
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@kms_cursor_crc@[email protected]
* igt@kms_flip@2x-flip-vs-wf_vblank-interruptible@bc-hdmi-a1-hdmi-a2:
- shard-glk: ([PASS][5], [PASS][6]) -> [FAIL][7] +1 other test fail
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk3/igt@kms_flip@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk1/igt@kms_flip@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk7/igt@kms_flip@[email protected]
* igt@kms_joiner@invalid-modeset-force-ultra-joiner:
- shard-tglu: NOTRUN -> [SKIP][8]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_pm_backlight@brightness-with-dpms:
- shard-rkl: NOTRUN -> [SKIP][9] +2 other tests skip
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-5/igt@[email protected]
* igt@perf_pmu@busy-accuracy-98@rcs0:
- shard-tglu: [PASS][10] -> [FAIL][11] +2 other tests fail
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-tglu-5/igt@perf_pmu@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-10/igt@perf_pmu@[email protected]
Known issues
------------
Here are the changes found in Patchwork_138069v5_full that come from known issues:
### CI changes ###
#### Possible fixes ####
* boot:
- shard-dg1: ([PASS][12], [PASS][13], [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19], [PASS][20], [FAIL][21], [PASS][22], [PASS][23], [PASS][24], [PASS][25], [PASS][26], [PASS][27], [PASS][28], [PASS][29], [PASS][30], [PASS][31], [PASS][32], [PASS][33], [PASS][34], [PASS][35]) -> ([PASS][36], [PASS][37], [PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], [PASS][43], [PASS][44], [PASS][45], [PASS][46], [PASS][47], [PASS][48], [PASS][49], [PASS][50], [PASS][51], [PASS][52], [PASS][53], [PASS][54], [PASS][55], [PASS][56], [PASS][57], [PASS][58], [PASS][59], [PASS][60])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-15/boot.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-12/boot.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-12/boot.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-12/boot.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-13/boot.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-13/boot.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-14/boot.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-14/boot.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-14/boot.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-15/boot.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-15/boot.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-16/boot.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-16/boot.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-16/boot.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-16/boot.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-17/boot.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-17/boot.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-17/boot.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-18/boot.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-18/boot.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-18/boot.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-19/boot.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-19/boot.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-19/boot.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/boot.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/boot.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/boot.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-14/boot.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-14/boot.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-15/boot.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-15/boot.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-15/boot.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-15/boot.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-16/boot.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-16/boot.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-16/boot.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-16/boot.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/boot.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/boot.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/boot.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/boot.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-18/boot.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-18/boot.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-18/boot.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-18/boot.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-19/boot.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-19/boot.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-19/boot.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/boot.html
### IGT changes ###
#### Issues hit ####
* igt@debugfs_test@basic-hwmon:
- shard-tglu: NOTRUN -> [SKIP][61] ([i915#9318])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@device_reset@cold-reset-bound:
- shard-tglu: NOTRUN -> [SKIP][62] ([i915#11078])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-2/igt@[email protected]
* igt@drm_fdinfo@busy@vcs1:
- shard-dg1: NOTRUN -> [SKIP][63] ([i915#8414]) +11 other tests skip
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@drm_fdinfo@[email protected]
* igt@gem_ccs@block-multicopy-compressed:
- shard-tglu: NOTRUN -> [SKIP][64] ([i915#9323])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@gem_ccs@ctrl-surf-copy:
- shard-dg1: NOTRUN -> [SKIP][65] ([i915#3555] / [i915#9323])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@gem_ccs@suspend-resume:
- shard-rkl: NOTRUN -> [SKIP][66] ([i915#9323]) +1 other test skip
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-5/igt@[email protected]
* igt@gem_close_race@multigpu-basic-process:
- shard-tglu: NOTRUN -> [SKIP][67] ([i915#7697])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-2/igt@[email protected]
* igt@gem_close_race@multigpu-basic-threads:
- shard-rkl: NOTRUN -> [SKIP][68] ([i915#7697])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@gem_create@create-ext-cpu-access-sanity-check:
- shard-tglu: NOTRUN -> [SKIP][69] ([i915#6335]) +1 other test skip
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-6/igt@[email protected]
* igt@gem_ctx_engines@invalid-engines:
- shard-tglu: NOTRUN -> [FAIL][70] ([i915#12027])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@gem_ctx_persistence@hang:
- shard-snb: NOTRUN -> [SKIP][71] ([i915#1099])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-snb4/igt@[email protected]
* igt@gem_ctx_sseu@invalid-args:
- shard-rkl: NOTRUN -> [SKIP][72] ([i915#280])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-5/igt@[email protected]
* igt@gem_exec_balancer@parallel-contexts:
- shard-rkl: NOTRUN -> [SKIP][73] ([i915#4525]) +2 other tests skip
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@[email protected]
* igt@gem_exec_capture@capture-recoverable:
- shard-rkl: NOTRUN -> [SKIP][74] ([i915#6344])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@[email protected]
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-tglu: NOTRUN -> [FAIL][75] ([i915#2842]) +9 other tests fail
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none@bcs0:
- shard-rkl: NOTRUN -> [FAIL][76] ([i915#2842]) +3 other tests fail
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace-solo:
- shard-glk: NOTRUN -> [FAIL][77] ([i915#2842]) +1 other test fail
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk3/igt@[email protected]
* igt@gem_exec_flush@basic-uc-pro-default:
- shard-dg1: NOTRUN -> [SKIP][78] ([i915#3539] / [i915#4852]) +2 other tests skip
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@gem_exec_flush@basic-uc-ro-default:
- shard-dg2: NOTRUN -> [SKIP][79] ([i915#3539] / [i915#4852])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@gem_exec_reloc@basic-cpu-gtt:
- shard-dg2: NOTRUN -> [SKIP][80] ([i915#3281])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-8/igt@[email protected]
- shard-dg1: NOTRUN -> [SKIP][81] ([i915#3281]) +4 other tests skip
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@[email protected]
- shard-mtlp: NOTRUN -> [SKIP][82] ([i915#3281])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@[email protected]
* igt@gem_exec_reloc@basic-gtt-wc-noreloc:
- shard-rkl: NOTRUN -> [SKIP][83] ([i915#3281]) +12 other tests skip
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@gem_exec_schedule@smoketest-all:
- shard-snb: NOTRUN -> [SKIP][84] +27 other tests skip
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-snb5/igt@[email protected]
* igt@gem_exec_suspend@basic-s0:
- shard-dg2: [PASS][85] -> [INCOMPLETE][86] ([i915#11441]) +1 other test incomplete
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-8/igt@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-1/igt@[email protected]
* igt@gem_fence_thrash@bo-copy:
- shard-dg1: NOTRUN -> [SKIP][87] ([i915#4860])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@gem_fence_thrash@bo-write-verify-none:
- shard-dg2: NOTRUN -> [SKIP][88] ([i915#4860])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@gem_lmem_evict@dontneed-evict-race:
- shard-tglu: NOTRUN -> [SKIP][89] ([i915#4613] / [i915#7582])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-2/igt@[email protected]
* igt@gem_lmem_swapping@heavy-verify-random-ccs:
- shard-tglu: NOTRUN -> [SKIP][90] ([i915#4613]) +4 other tests skip
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-6/igt@[email protected]
* igt@gem_lmem_swapping@parallel-random-verify:
- shard-rkl: NOTRUN -> [SKIP][91] ([i915#4613]) +1 other test skip
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@gem_lmem_swapping@verify-random-ccs:
- shard-dg1: NOTRUN -> [SKIP][92] ([i915#12193])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@[email protected]
* igt@gem_lmem_swapping@verify-random-ccs@lmem0:
- shard-dg1: NOTRUN -> [SKIP][93] ([i915#4565])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@gem_lmem_swapping@[email protected]
* igt@gem_media_fill@media-fill:
- shard-mtlp: NOTRUN -> [SKIP][94] ([i915#8289])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-8/igt@[email protected]
- shard-dg2: NOTRUN -> [SKIP][95] ([i915#8289])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@gem_mmap_gtt@basic-small-copy-odd:
- shard-dg1: NOTRUN -> [SKIP][96] ([i915#4077]) +2 other tests skip
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@[email protected]
* igt@gem_mmap_wc@set-cache-level:
- shard-dg1: NOTRUN -> [SKIP][97] ([i915#4083])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@gem_partial_pwrite_pread@writes-after-reads-snoop:
- shard-dg1: NOTRUN -> [SKIP][98] ([i915#3282]) +3 other tests skip
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@gem_pxp@protected-raw-src-copy-not-readible:
- shard-rkl: NOTRUN -> [SKIP][99] ([i915#4270]) +3 other tests skip
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-5/igt@[email protected]
- shard-mtlp: NOTRUN -> [SKIP][100] ([i915#4270])
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-1/igt@[email protected]
* igt@gem_pxp@verify-pxp-stale-ctx-execution:
- shard-tglu: NOTRUN -> [SKIP][101] ([i915#4270]) +1 other test skip
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@gem_readwrite@beyond-eob:
- shard-rkl: NOTRUN -> [SKIP][102] ([i915#3282]) +6 other tests skip
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@[email protected]
* igt@gem_set_tiling_vs_blt@tiled-to-untiled:
- shard-rkl: NOTRUN -> [SKIP][103] ([i915#8411])
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-5/igt@[email protected]
- shard-mtlp: NOTRUN -> [SKIP][104] ([i915#4079])
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-1/igt@[email protected]
* igt@gem_userptr_blits@coherency-unsync:
- shard-tglu: NOTRUN -> [SKIP][105] ([i915#3297]) +3 other tests skip
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-2/igt@[email protected]
* igt@gem_userptr_blits@map-fixed-invalidate-overlap:
- shard-dg1: NOTRUN -> [SKIP][106] ([i915#3297] / [i915#4880])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@[email protected]
* igt@gem_userptr_blits@relocations:
- shard-dg1: NOTRUN -> [SKIP][107] ([i915#3281] / [i915#3297])
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@gen9_exec_parse@basic-rejected:
- shard-tglu: NOTRUN -> [SKIP][108] ([i915#2527] / [i915#2856]) +3 other tests skip
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@gen9_exec_parse@shadow-peek:
- shard-rkl: NOTRUN -> [SKIP][109] ([i915#2527]) +4 other tests skip
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@gen9_exec_parse@unaligned-jump:
- shard-mtlp: NOTRUN -> [SKIP][110] ([i915#2856])
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@[email protected]
- shard-dg2: NOTRUN -> [SKIP][111] ([i915#2856])
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-8/igt@[email protected]
* igt@i915_module_load@reload-with-fault-injection:
- shard-rkl: [PASS][112] -> [ABORT][113] ([i915#9820])
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-rkl-2/igt@[email protected]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-1/igt@[email protected]
- shard-dg1: [PASS][114] -> [ABORT][115] ([i915#9820])
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-14/igt@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-14/igt@[email protected]
- shard-mtlp: [PASS][116] -> [ABORT][117] ([i915#10131] / [i915#9820])
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-mtlp-6/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-8/igt@[email protected]
* igt@i915_pm_freq_api@freq-reset-multiple:
- shard-tglu: NOTRUN -> [SKIP][118] ([i915#8399])
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-6/igt@[email protected]
* igt@i915_pm_sseu@full-enable:
- shard-tglu: NOTRUN -> [SKIP][119] ([i915#4387])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-2/igt@[email protected]
* igt@i915_selftest@mock:
- shard-dg1: NOTRUN -> [DMESG-WARN][120] ([i915#1982] / [i915#9311])
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@[email protected]
* igt@i915_selftest@mock@memory_region:
- shard-dg1: NOTRUN -> [DMESG-WARN][121] ([i915#9311])
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@i915_selftest@mock@memory_region.html
* igt@i915_suspend@basic-s3-without-i915:
- shard-dg2: [PASS][122] -> [INCOMPLETE][123] ([i915#4817])
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-4/igt@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-10/igt@[email protected]
* igt@intel_hwmon@hwmon-read:
- shard-rkl: NOTRUN -> [SKIP][124] ([i915#7707])
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@intel_hwmon@hwmon-write:
- shard-tglu: NOTRUN -> [SKIP][125] ([i915#7707])
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_atomic_transition@plane-all-modeset-transition-fencing-internal-panels:
- shard-glk: NOTRUN -> [SKIP][126] ([i915#1769])
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk3/igt@kms_atomic_transition@plane-all-modeset-transition-fencing-internal-panels.html
* igt@kms_atomic_transition@plane-all-modeset-transition@pipe-a-hdmi-a-1:
- shard-tglu: [PASS][127] -> [FAIL][128] ([i915#11808]) +1 other test fail
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-tglu-6/igt@kms_atomic_transition@[email protected]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-10/igt@kms_atomic_transition@[email protected]
* igt@kms_big_fb@4-tiled-max-hw-stride-32bpp-rotate-0-async-flip:
- shard-tglu: NOTRUN -> [SKIP][129] ([i915#5286]) +4 other tests skip
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_big_fb@4-tiled-max-hw-stride-32bpp-rotate-0-hflip:
- shard-rkl: NOTRUN -> [SKIP][130] ([i915#5286]) +4 other tests skip
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@[email protected]
* igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-dg1: NOTRUN -> [SKIP][131] ([i915#4538] / [i915#5286]) +4 other tests skip
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@[email protected]
* igt@kms_big_fb@linear-64bpp-rotate-270:
- shard-dg1: NOTRUN -> [SKIP][132] ([i915#3638] / [i915#4423])
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@kms_big_fb@y-tiled-8bpp-rotate-270:
- shard-dg2: NOTRUN -> [SKIP][133] ([i915#4538] / [i915#5190])
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-10/igt@[email protected]
- shard-dg1: NOTRUN -> [SKIP][134] ([i915#3638]) +1 other test skip
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
- shard-mtlp: NOTRUN -> [SKIP][135] +1 other test skip
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@[email protected]
* igt@kms_big_fb@y-tiled-8bpp-rotate-90:
- shard-rkl: NOTRUN -> [SKIP][136] ([i915#3638]) +3 other tests skip
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_big_fb@yf-tiled-16bpp-rotate-180:
- shard-dg1: NOTRUN -> [SKIP][137] ([i915#4538]) +2 other tests skip
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@kms_ccs@bad-rotation-90-4-tiled-bmg-ccs:
- shard-tglu: NOTRUN -> [SKIP][138] ([i915#12313]) +4 other tests skip
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_ccs@crc-primary-rotation-180-4-tiled-lnl-ccs:
- shard-rkl: NOTRUN -> [SKIP][139] ([i915#12313])
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_ccs@crc-primary-rotation-180-4-tiled-mtl-rc-ccs@pipe-b-hdmi-a-2:
- shard-rkl: NOTRUN -> [SKIP][140] ([i915#6095]) +70 other tests skip
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-1/igt@kms_ccs@[email protected]
* igt@kms_ccs@crc-primary-rotation-180-y-tiled-ccs@pipe-a-hdmi-a-3:
- shard-dg1: NOTRUN -> [SKIP][141] ([i915#6095]) +75 other tests skip
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@kms_ccs@[email protected]
* igt@kms_ccs@crc-primary-rotation-180-y-tiled-gen12-rc-ccs@pipe-a-edp-1:
- shard-mtlp: NOTRUN -> [SKIP][142] ([i915#6095]) +4 other tests skip
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-3/igt@kms_ccs@[email protected]
* igt@kms_ccs@crc-sprite-planes-basic-4-tiled-mtl-rc-ccs-cc@pipe-b-hdmi-a-1:
- shard-tglu: NOTRUN -> [SKIP][143] ([i915#6095]) +54 other tests skip
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-6/igt@kms_ccs@crc-sprite-planes-basic-4-tiled-mtl-rc-ccs-cc@pipe-b-hdmi-a-1.html
* igt@kms_ccs@missing-ccs-buffer-4-tiled-mtl-mc-ccs@pipe-b-hdmi-a-1:
- shard-dg2: NOTRUN -> [SKIP][144] ([i915#10307] / [i915#6095]) +130 other tests skip
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-4/igt@kms_ccs@[email protected]
* igt@kms_ccs@random-ccs-data-4-tiled-bmg-ccs:
- shard-dg2: NOTRUN -> [SKIP][145] ([i915#12313])
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-10/igt@[email protected]
- shard-dg1: NOTRUN -> [SKIP][146] ([i915#12313])
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
- shard-mtlp: NOTRUN -> [SKIP][147] ([i915#12313])
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@[email protected]
* igt@kms_ccs@random-ccs-data-4-tiled-mtl-rc-ccs:
- shard-dg2: NOTRUN -> [SKIP][148] ([i915#9197]) +6 other tests skip
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_ccs@random-ccs-data-yf-tiled-ccs@pipe-d-hdmi-a-1:
- shard-dg2: NOTRUN -> [SKIP][149] ([i915#10307] / [i915#10434] / [i915#6095]) +4 other tests skip
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-4/igt@kms_ccs@[email protected]
* igt@kms_cdclk@mode-transition-all-outputs:
- shard-rkl: NOTRUN -> [SKIP][150] ([i915#3742])
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-5/igt@[email protected]
* igt@kms_chamelium_audio@hdmi-audio-edid:
- shard-tglu: NOTRUN -> [SKIP][151] ([i915#7828]) +8 other tests skip
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-6/igt@[email protected]
* igt@kms_chamelium_frames@hdmi-crc-nonplanar-formats:
- shard-dg1: NOTRUN -> [SKIP][152] ([i915#7828]) +4 other tests skip
[152]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@kms_chamelium_hpd@hdmi-hpd-after-suspend:
- shard-dg2: NOTRUN -> [SKIP][153] ([i915#7828]) +1 other test skip
[153]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_chamelium_hpd@vga-hpd:
- shard-mtlp: NOTRUN -> [SKIP][154] ([i915#7828])
[154]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@[email protected]
* igt@kms_chamelium_hpd@vga-hpd-fast:
- shard-rkl: NOTRUN -> [SKIP][155] ([i915#7828]) +6 other tests skip
[155]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-5/igt@[email protected]
* igt@kms_content_protection@atomic:
- shard-tglu: NOTRUN -> [SKIP][156] ([i915#6944] / [i915#7116] / [i915#7118] / [i915#9424]) +1 other test skip
[156]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_content_protection@dp-mst-type-0:
- shard-rkl: NOTRUN -> [SKIP][157] ([i915#3116])
[157]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-5/igt@[email protected]
* igt@kms_content_protection@dp-mst-type-1:
- shard-dg1: NOTRUN -> [SKIP][158] ([i915#3299]) +1 other test skip
[158]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@[email protected]
* igt@kms_content_protection@mei-interface:
- shard-rkl: NOTRUN -> [SKIP][159] ([i915#9424]) +1 other test skip
[159]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_content_protection@type1:
- shard-rkl: NOTRUN -> [SKIP][160] ([i915#7118] / [i915#9424])
[160]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@[email protected]
* igt@kms_cursor_crc@cursor-offscreen-32x32:
- shard-dg1: NOTRUN -> [SKIP][161] ([i915#3555] / [i915#4423])
[161]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@kms_cursor_crc@cursor-onscreen-32x32:
- shard-dg1: NOTRUN -> [SKIP][162] ([i915#3555])
[162]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@kms_cursor_crc@cursor-random-512x170:
- shard-rkl: NOTRUN -> [SKIP][163] ([i915#11453])
[163]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-5/igt@[email protected]
* igt@kms_cursor_crc@cursor-random-512x512:
- shard-tglu: NOTRUN -> [SKIP][164] ([i915#11453])
[164]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_cursor_crc@cursor-rapid-movement-32x10:
- shard-rkl: NOTRUN -> [SKIP][165] ([i915#3555]) +6 other tests skip
[165]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@[email protected]
* igt@kms_cursor_crc@cursor-sliding-32x10:
- shard-tglu: NOTRUN -> [SKIP][166] ([i915#3555]) +7 other tests skip
[166]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_cursor_crc@cursor-sliding-512x512:
- shard-dg2: NOTRUN -> [SKIP][167] ([i915#11453])
[167]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-10/igt@[email protected]
- shard-dg1: NOTRUN -> [SKIP][168] ([i915#11453]) +1 other test skip
[168]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- shard-rkl: NOTRUN -> [SKIP][169] ([i915#4103]) +1 other test skip
[169]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-5/igt@[email protected]
* igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions:
- shard-tglu: NOTRUN -> [SKIP][170] ([i915#4103])
[170]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions.html
* igt@kms_display_modes@mst-extended-mode-negative:
- shard-rkl: NOTRUN -> [SKIP][171] ([i915#8588])
[171]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_dither@fb-8bpc-vs-panel-6bpc:
- shard-rkl: NOTRUN -> [SKIP][172] ([i915#3555] / [i915#3804])
[172]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_dither@fb-8bpc-vs-panel-6bpc@pipe-a-hdmi-a-2:
- shard-rkl: NOTRUN -> [SKIP][173] ([i915#3804])
[173]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@kms_dither@[email protected]
* igt@kms_dp_aux_dev:
- shard-dg1: NOTRUN -> [SKIP][174] ([i915#1257])
[174]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@kms_dp_aux_dev.html
* igt@kms_dsc@dsc-basic:
- shard-rkl: NOTRUN -> [SKIP][175] ([i915#3555] / [i915#3840])
[175]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@[email protected]
* igt@kms_dsc@dsc-fractional-bpp:
- shard-mtlp: NOTRUN -> [SKIP][176] ([i915#3840] / [i915#9688])
[176]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@[email protected]
* igt@kms_fbcon_fbt@psr-suspend:
- shard-rkl: NOTRUN -> [SKIP][177] ([i915#3955])
[177]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_feature_discovery@chamelium:
- shard-tglu: NOTRUN -> [SKIP][178] ([i915#2065] / [i915#4854])
[178]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_feature_discovery@display-2x:
- shard-dg1: NOTRUN -> [SKIP][179] ([i915#1839])
[179]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@kms_feature_discovery@display-3x:
- shard-rkl: NOTRUN -> [SKIP][180] ([i915#1839]) +1 other test skip
[180]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_feature_discovery@dp-mst:
- shard-tglu: NOTRUN -> [SKIP][181] ([i915#9337])
[181]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_flip@2x-blocking-absolute-wf_vblank:
- shard-tglu: NOTRUN -> [SKIP][182] ([i915#3637]) +6 other tests skip
[182]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-6/igt@kms_flip@2x-blocking-absolute-wf_vblank.html
* igt@kms_flip@2x-flip-vs-panning-vs-hang:
- shard-dg2: NOTRUN -> [SKIP][183]
[183]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-10/igt@[email protected]
- shard-mtlp: NOTRUN -> [SKIP][184] ([i915#3637])
[184]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@[email protected]
* igt@kms_flip@2x-modeset-vs-vblank-race@ab-vga1-hdmi-a1:
- shard-snb: [PASS][185] -> [FAIL][186] ([i915#10826]) +1 other test fail
[185]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-snb7/igt@kms_flip@[email protected]
[186]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-snb6/igt@kms_flip@[email protected]
* igt@kms_flip@2x-plain-flip:
- shard-rkl: NOTRUN -> [SKIP][187] +22 other tests skip
[187]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@[email protected]
* igt@kms_flip@2x-wf_vblank-ts-check-interruptible:
- shard-glk: NOTRUN -> [FAIL][188] ([i915#2122]) +1 other test fail
[188]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk3/igt@kms_flip@2x-wf_vblank-ts-check-interruptible.html
* igt@kms_flip@blocking-wf_vblank@a-hdmi-a2:
- shard-rkl: NOTRUN -> [FAIL][189] ([i915#11961])
[189]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-1/igt@kms_flip@[email protected]
* igt@kms_flip@blocking-wf_vblank@b-hdmi-a1:
- shard-dg2: NOTRUN -> [FAIL][190] ([i915#2122]) +1 other test fail
[190]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-8/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible:
- shard-mtlp: [PASS][191] -> [FAIL][192] ([i915#2122]) +3 other tests fail
[191]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-mtlp-6/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible.html
[192]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-6/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible.html
* igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@c-hdmi-a1:
- shard-tglu: [PASS][193] -> [FAIL][194] ([i915#2122])
[193]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-tglu-3/igt@kms_flip@[email protected]
[194]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-9/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible@a-hdmi-a2:
- shard-glk: [PASS][195] -> [INCOMPLETE][196] ([i915#4839])
[195]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk6/igt@kms_flip@[email protected]
[196]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk4/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-fb-recreate-interruptible:
- shard-tglu: NOTRUN -> [FAIL][197] ([i915#2122]) +2 other tests fail
[197]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_flip@plain-flip-fb-recreate-interruptible@b-hdmi-a1:
- shard-rkl: NOTRUN -> [FAIL][198] ([i915#2122]) +1 other test fail
[198]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-4/igt@kms_flip@[email protected]
- shard-snb: [PASS][199] -> [FAIL][200] ([i915#2122]) +6 other tests fail
[199]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-snb1/igt@kms_flip@[email protected]
[200]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-snb7/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-32bpp-4tiledg2rcccs-downscaling:
- shard-dg1: NOTRUN -> [SKIP][201] ([i915#2672] / [i915#3555]) +2 other tests skip
[201]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-32bpp-4tiledg2rcccs-downscaling.html
* igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-upscaling:
- shard-dg2: [PASS][202] -> [SKIP][203] ([i915#3555]) +3 other tests skip
[202]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-3/igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-upscaling.html
[203]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-upscaling.html
* igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-downscaling:
- shard-mtlp: NOTRUN -> [SKIP][204] ([i915#2672] / [i915#3555] / [i915#8813])
[204]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-downscaling.html
- shard-dg2: NOTRUN -> [SKIP][205] ([i915#2672] / [i915#3555])
[205]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-10/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-downscaling.html
* igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-downscaling@pipe-a-default-mode:
- shard-mtlp: NOTRUN -> [SKIP][206] ([i915#2672])
[206]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-downscaling@pipe-a-default-mode.html
* igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-downscaling@pipe-a-valid-mode:
- shard-dg2: NOTRUN -> [SKIP][207] ([i915#2672]) +4 other tests skip
[207]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-10/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-downscaling@pipe-a-valid-mode.html
- shard-dg1: NOTRUN -> [SKIP][208] ([i915#2587] / [i915#2672]) +2 other tests skip
[208]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-downscaling@pipe-a-valid-mode.html
* igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-64bpp-yftile-upscaling:
- shard-tglu: NOTRUN -> [SKIP][209] ([i915#2672] / [i915#3555]) +3 other tests skip
[209]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-64bpp-yftile-upscaling.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling:
- shard-tglu: NOTRUN -> [SKIP][210] ([i915#2587] / [i915#2672] / [i915#3555])
[210]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-6/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling@pipe-a-valid-mode:
- shard-tglu: NOTRUN -> [SKIP][211] ([i915#2587] / [i915#2672]) +4 other tests skip
[211]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-6/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling@pipe-a-valid-mode.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-upscaling@pipe-a-valid-mode:
- shard-rkl: NOTRUN -> [SKIP][212] ([i915#2672]) +3 other tests skip
[212]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-upscaling@pipe-a-valid-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tiledg2rcccs-upscaling:
- shard-rkl: NOTRUN -> [SKIP][213] ([i915#2672] / [i915#3555]) +3 other tests skip
[213]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tiledg2rcccs-upscaling.html
* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-pwrite:
- shard-dg1: NOTRUN -> [SKIP][214] +16 other tests skip
[214]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-pwrite.html
- shard-mtlp: NOTRUN -> [SKIP][215] ([i915#1825])
[215]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-pwrite.html
- shard-dg2: NOTRUN -> [SKIP][216] ([i915#5354])
[216]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-10/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@fbc-rgb565-draw-mmap-gtt:
- shard-dg1: NOTRUN -> [SKIP][217] ([i915#8708]) +10 other tests skip
[217]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-rgb565-draw-render:
- shard-dg2: [PASS][218] -> [SKIP][219] ([i915#5354]) +9 other tests skip
[218]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-3/igt@[email protected]
[219]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-spr-indfb-fullscreen:
- shard-tglu: NOTRUN -> [SKIP][220] +83 other tests skip
[220]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-6/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-spr-indfb-fullscreen.html
* igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-blt:
- shard-dg1: NOTRUN -> [SKIP][221] ([i915#3458]) +5 other tests skip
[221]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-mmap-wc:
- shard-rkl: NOTRUN -> [SKIP][222] ([i915#3023]) +22 other tests skip
[222]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-tiling-4:
- shard-rkl: NOTRUN -> [SKIP][223] ([i915#5439])
[223]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-tiling-y:
- shard-mtlp: NOTRUN -> [SKIP][224] ([i915#10055])
[224]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-1/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-2p-primscrn-spr-indfb-draw-mmap-wc:
- shard-rkl: NOTRUN -> [SKIP][225] ([i915#1825]) +33 other tests skip
[225]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@kms_frontbuffer_tracking@psr-2p-primscrn-spr-indfb-draw-mmap-wc.html
* igt@kms_hdr@bpc-switch-dpms:
- shard-dg2: [PASS][226] -> [SKIP][227] ([i915#3555] / [i915#8228])
[226]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-10/igt@[email protected]
[227]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-7/igt@[email protected]
* igt@kms_hdr@bpc-switch-suspend:
- shard-tglu: NOTRUN -> [SKIP][228] ([i915#3555] / [i915#8228]) +2 other tests skip
[228]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_hdr@invalid-hdr:
- shard-dg1: NOTRUN -> [SKIP][229] ([i915#3555] / [i915#8228])
[229]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@kms_panel_fitting@atomic-fastset:
- shard-rkl: NOTRUN -> [SKIP][230] ([i915#6301])
[230]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_plane@plane-position-covered:
- shard-dg2: [PASS][231] -> [SKIP][232] ([i915#8825]) +1 other test skip
[231]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@[email protected]
[232]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_plane_alpha_blend@alpha-basic:
- shard-glk: NOTRUN -> [FAIL][233] ([i915#12178])
[233]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk3/igt@[email protected]
* igt@kms_plane_alpha_blend@alpha-basic@pipe-a-hdmi-a-1:
- shard-glk: NOTRUN -> [FAIL][234] ([i915#7862]) +1 other test fail
[234]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk3/igt@kms_plane_alpha_blend@[email protected]
* igt@kms_plane_alpha_blend@coverage-vs-premult-vs-constant:
- shard-dg2: [PASS][235] -> [SKIP][236] ([i915#7294])
[235]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@[email protected]
[236]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_plane_scaling@intel-max-src-size@pipe-a-dp-3:
- shard-dg2: NOTRUN -> [FAIL][237] ([i915#8292])
[237]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-10/igt@kms_plane_scaling@[email protected]
* igt@kms_plane_scaling@intel-max-src-size@pipe-a-hdmi-a-2:
- shard-rkl: NOTRUN -> [FAIL][238] ([i915#8292]) +1 other test fail
[238]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@kms_plane_scaling@[email protected]
* igt@kms_plane_scaling@plane-downscale-factor-0-25-with-rotation:
- shard-rkl: NOTRUN -> [SKIP][239] ([i915#12247]) +8 other tests skip
[239]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@[email protected]
* igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-pixel-formats@pipe-b:
- shard-mtlp: NOTRUN -> [SKIP][240] ([i915#12247]) +1 other test skip
[240]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@kms_plane_scaling@[email protected]
* igt@kms_plane_scaling@planes-downscale-factor-0-5-unity-scaling:
- shard-dg2: [PASS][241] -> [SKIP][242] ([i915#12247] / [i915#8152] / [i915#9423])
[241]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@[email protected]
[242]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_plane_scaling@planes-scaler-unity-scaling:
- shard-dg2: [PASS][243] -> [SKIP][244] ([i915#3555] / [i915#8152] / [i915#9423])
[243]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@[email protected]
[244]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_plane_scaling@planes-scaler-unity-scaling@pipe-a:
- shard-dg2: [PASS][245] -> [SKIP][246] ([i915#12247]) +8 other tests skip
[245]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@kms_plane_scaling@[email protected]
[246]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@kms_plane_scaling@[email protected]
* igt@kms_plane_scaling@planes-scaler-unity-scaling@pipe-d:
- shard-dg2: [PASS][247] -> [SKIP][248] ([i915#12247] / [i915#8152]) +2 other tests skip
[247]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@kms_plane_scaling@[email protected]
[248]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@kms_plane_scaling@[email protected]
* igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-25:
- shard-tglu: NOTRUN -> [SKIP][249] ([i915#12247] / [i915#3555])
[249]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-7/igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-25.html
* igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5:
- shard-tglu: NOTRUN -> [SKIP][250] ([i915#12247] / [i915#3555] / [i915#6953])
[250]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-b:
- shard-tglu: NOTRUN -> [SKIP][251] ([i915#12247]) +17 other tests skip
[251]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@kms_plane_scaling@[email protected]
* igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-75:
- shard-dg2: [PASS][252] -> [SKIP][253] ([i915#12247] / [i915#6953] / [i915#8152] / [i915#9423])
[252]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-3/igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-75.html
[253]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-75.html
* igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25:
- shard-dg1: NOTRUN -> [SKIP][254] ([i915#12247] / [i915#6953])
[254]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25.html
* igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-25@pipe-b:
- shard-dg1: NOTRUN -> [SKIP][255] ([i915#12247]) +3 other tests skip
[255]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@kms_plane_scaling@[email protected]
* igt@kms_pm_backlight@basic-brightness:
- shard-tglu: NOTRUN -> [SKIP][256] ([i915#9812])
[256]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_pm_backlight@fade-with-suspend:
- shard-rkl: NOTRUN -> [SKIP][257] ([i915#5354])
[257]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_pm_dc@dc5-dpms-negative:
- shard-dg2: [PASS][258] -> [SKIP][259] ([i915#9293])
[258]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-3/igt@[email protected]
[259]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_pm_dc@dc5-psr:
- shard-tglu: NOTRUN -> [SKIP][260] ([i915#9685]) +1 other test skip
[260]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_pm_dc@dc6-psr:
- shard-rkl: NOTRUN -> [SKIP][261] ([i915#9685]) +1 other test skip
[261]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_pm_lpsp@screens-disabled:
- shard-tglu: NOTRUN -> [SKIP][262] ([i915#8430])
[262]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-2/igt@[email protected]
* igt@kms_pm_rpm@dpms-lpsp:
- shard-dg2: [PASS][263] -> [SKIP][264] ([i915#9519]) +2 other tests skip
[263]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-8/igt@[email protected]
[264]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-1/igt@[email protected]
- shard-rkl: [PASS][265] -> [SKIP][266] ([i915#9519]) +1 other test skip
[265]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-rkl-7/igt@[email protected]
[266]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-1/igt@[email protected]
* igt@kms_pm_rpm@modeset-lpsp:
- shard-dg1: NOTRUN -> [SKIP][267] ([i915#9519])
[267]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@kms_pm_rpm@modeset-non-lpsp-stress-no-wait:
- shard-mtlp: NOTRUN -> [SKIP][268] ([i915#9519])
[268]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@[email protected]
* igt@kms_pm_rpm@system-suspend-modeset:
- shard-dg1: NOTRUN -> [DMESG-WARN][269] ([i915#4423]) +1 other test dmesg-warn
[269]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@kms_prime@basic-crc-hybrid:
- shard-tglu: NOTRUN -> [SKIP][270] ([i915#6524])
[270]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_prime@d3hot:
- shard-rkl: NOTRUN -> [SKIP][271] ([i915#6524])
[271]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_psr2_sf@fbc-psr2-cursor-plane-move-continuous-exceed-fully-sf:
- shard-dg2: NOTRUN -> [SKIP][272] ([i915#11520])
[272]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@kms_psr2_sf@fbc-psr2-cursor-plane-move-continuous-exceed-fully-sf.html
* igt@kms_psr2_sf@fbc-psr2-cursor-plane-move-continuous-exceed-sf:
- shard-dg1: NOTRUN -> [SKIP][273] ([i915#11520]) +1 other test skip
[273]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@[email protected]
* igt@kms_psr2_sf@fbc-psr2-overlay-plane-move-continuous-exceed-fully-sf:
- shard-glk: NOTRUN -> [SKIP][274] ([i915#11520]) +1 other test skip
[274]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk3/igt@kms_psr2_sf@fbc-psr2-overlay-plane-move-continuous-exceed-fully-sf.html
* igt@kms_psr2_sf@psr2-overlay-plane-move-continuous-sf:
- shard-tglu: NOTRUN -> [SKIP][275] ([i915#11520]) +5 other tests skip
[275]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-6/igt@[email protected]
* igt@kms_psr2_sf@psr2-overlay-plane-update-continuous-sf:
- shard-rkl: NOTRUN -> [SKIP][276] ([i915#11520]) +8 other tests skip
[276]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_psr2_sf@psr2-overlay-plane-update-sf-dmg-area:
- shard-dg1: NOTRUN -> [SKIP][277] ([i915#11520] / [i915#4423])
[277]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@kms_psr2_su@page_flip-nv12:
- shard-dg1: NOTRUN -> [SKIP][278] ([i915#9683])
[278]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@kms_psr2_su@page_flip-nv12.html
* igt@kms_psr2_su@page_flip-xrgb8888:
- shard-tglu: NOTRUN -> [SKIP][279] ([i915#9683]) +2 other tests skip
[279]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-6/igt@kms_psr2_su@page_flip-xrgb8888.html
* igt@kms_psr@fbc-psr-no-drrs:
- shard-tglu: NOTRUN -> [SKIP][280] ([i915#9732]) +19 other tests skip
[280]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-2/igt@[email protected]
* igt@kms_psr@psr-cursor-plane-onoff:
- shard-dg1: NOTRUN -> [SKIP][281] ([i915#1072] / [i915#9732]) +7 other tests skip
[281]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@[email protected]
* igt@kms_psr@psr-no-drrs:
- shard-glk: NOTRUN -> [SKIP][282] +40 other tests skip
[282]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk3/igt@[email protected]
* igt@kms_psr@psr-sprite-plane-move:
- shard-rkl: NOTRUN -> [SKIP][283] ([i915#1072] / [i915#9732]) +20 other tests skip
[283]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@[email protected]
* igt@kms_psr@psr2-dpms:
- shard-dg2: NOTRUN -> [SKIP][284] ([i915#1072] / [i915#9732])
[284]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-10/igt@[email protected]
* igt@kms_selftest@drm_framebuffer:
- shard-rkl: NOTRUN -> [ABORT][285] ([i915#12231]) +1 other test abort
[285]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-5/igt@kms_selftest@drm_framebuffer.html
* igt@kms_setmode@basic:
- shard-dg2: NOTRUN -> [SKIP][286] ([i915#3555])
[286]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_sysfs_edid_timing:
- shard-dg2: [PASS][287] -> [FAIL][288] ([IGT#2])
[287]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@kms_sysfs_edid_timing.html
[288]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@kms_sysfs_edid_timing.html
* igt@kms_tiled_display@basic-test-pattern:
- shard-tglu: NOTRUN -> [SKIP][289] ([i915#8623])
[289]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_vblank@wait-idle-hang:
- shard-dg2: [PASS][290] -> [SKIP][291] ([i915#9197]) +18 other tests skip
[290]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-3/igt@[email protected]
[291]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_vrr@flip-basic-fastset:
- shard-tglu: NOTRUN -> [SKIP][292] ([i915#9906])
[292]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@kms_vrr@negative-basic:
- shard-dg1: NOTRUN -> [SKIP][293] ([i915#3555] / [i915#9906])
[293]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@kms_writeback@writeback-check-output-xrgb2101010:
- shard-rkl: NOTRUN -> [SKIP][294] ([i915#2437] / [i915#9412])
[294]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@kms_writeback@writeback-fb-id:
- shard-dg1: NOTRUN -> [SKIP][295] ([i915#2437])
[295]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-17/igt@[email protected]
* igt@kms_writeback@writeback-pixel-formats:
- shard-dg1: NOTRUN -> [SKIP][296] ([i915#2437] / [i915#9412])
[296]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@perf@per-context-mode-unprivileged:
- shard-dg1: NOTRUN -> [SKIP][297] ([i915#2433])
[297]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-12/igt@[email protected]
* igt@perf@unprivileged-single-ctx-counters:
- shard-rkl: NOTRUN -> [SKIP][298] ([i915#2433])
[298]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@perf_pmu@busy-double-start@vecs1:
- shard-dg2: [PASS][299] -> [FAIL][300] ([i915#4349]) +4 other tests fail
[299]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-11/igt@perf_pmu@[email protected]
[300]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-4/igt@perf_pmu@[email protected]
* igt@perf_pmu@cpu-hotplug:
- shard-tglu: NOTRUN -> [SKIP][301] ([i915#8850])
[301]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@perf_pmu@rc6@other-idle-gt0:
- shard-tglu: NOTRUN -> [SKIP][302] ([i915#8516])
[302]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@perf_pmu@[email protected]
* igt@prime_vgem@basic-write:
- shard-rkl: NOTRUN -> [SKIP][303] ([i915#3291] / [i915#3708])
[303]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@prime_vgem@fence-flip-hang:
- shard-rkl: NOTRUN -> [SKIP][304] ([i915#3708])
[304]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
* igt@sriov_basic@enable-vfs-autoprobe-off:
- shard-tglu: NOTRUN -> [SKIP][305] ([i915#9917])
[305]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-6/igt@[email protected]
* igt@sriov_basic@enable-vfs-bind-unbind-each-numvfs-all:
- shard-rkl: NOTRUN -> [SKIP][306] ([i915#9917])
[306]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-3/igt@[email protected]
#### Possible fixes ####
* igt@fbdev@pan:
- shard-dg2: [SKIP][307] ([i915#2582]) -> [PASS][308]
[307]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[308]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@[email protected]
* igt@gem_ctx_engines@invalid-engines:
- shard-glk: ([PASS][309], [FAIL][310]) ([i915#12027]) -> [PASS][311]
[309]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk5/igt@[email protected]
[310]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk4/igt@[email protected]
[311]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk1/igt@[email protected]
* igt@gem_ctx_isolation@preservation-s3:
- shard-dg2: [INCOMPLETE][312] -> [PASS][313] +1 other test pass
[312]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-3/igt@[email protected]
[313]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@gem_ctx_persistence@hostile:
- shard-rkl: [FAIL][314] ([i915#11980]) -> [PASS][315]
[314]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-rkl-4/igt@[email protected]
[315]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-7/igt@[email protected]
* igt@gem_exec_big@single:
- shard-tglu: [ABORT][316] ([i915#11713]) -> [PASS][317]
[316]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-tglu-4/igt@[email protected]
[317]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-7/igt@[email protected]
* igt@gem_exec_fair@basic-deadline:
- shard-glk: [FAIL][318] ([i915#2846]) -> [PASS][319]
[318]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk2/igt@[email protected]
[319]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk3/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-glk: ([PASS][320], [ABORT][321]) ([i915#5566]) -> [PASS][322]
[320]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk1/igt@[email protected]
[321]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk4/igt@[email protected]
[322]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk1/igt@[email protected]
* igt@gen9_exec_parse@allowed-single:
- shard-glk: [ABORT][323] ([i915#5566]) -> [PASS][324]
[323]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk8/igt@[email protected]
[324]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk3/igt@[email protected]
* igt@i915_module_load@reload-with-fault-injection:
- shard-tglu: [ABORT][325] ([i915#9820]) -> [PASS][326]
[325]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-tglu-7/igt@[email protected]
[326]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@[email protected]
* igt@i915_pm_rc6_residency@rc6-accuracy:
- shard-mtlp: [INCOMPLETE][327] -> [PASS][328] +1 other test pass
[327]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-mtlp-1/igt@[email protected]
[328]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-7/igt@[email protected]
* igt@i915_pm_rpm@system-suspend-execbuf:
- shard-dg1: [DMESG-WARN][329] ([i915#4423]) -> [PASS][330]
[329]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-13/igt@[email protected]
[330]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-16/igt@[email protected]
* igt@kms_atomic_interruptible@atomic-setmode:
- shard-dg2: [SKIP][331] ([i915#9197]) -> [PASS][332] +21 other tests pass
[331]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[332]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@[email protected]
* igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-180-hflip:
- shard-mtlp: [FAIL][333] ([i915#5138]) -> [PASS][334] +2 other tests pass
[333]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-mtlp-6/igt@[email protected]
[334]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-6/igt@[email protected]
* igt@kms_big_fb@linear-max-hw-stride-32bpp-rotate-180:
- shard-dg1: [FAIL][335] ([i915#5138]) -> [PASS][336]
[335]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-12/igt@[email protected]
[336]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-15/igt@[email protected]
* igt@kms_cursor_crc@cursor-suspend@pipe-c-hdmi-a-1:
- shard-glk: ([INCOMPLETE][337], [INCOMPLETE][338]) ([i915#7882]) -> [PASS][339] +1 other test pass
[337]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk3/igt@kms_cursor_crc@[email protected]
[338]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk1/igt@kms_cursor_crc@[email protected]
[339]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk8/igt@kms_cursor_crc@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions:
- shard-glk: ([FAIL][340], [PASS][341]) ([i915#2346]) -> [PASS][342]
[340]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk4/igt@[email protected]
[341]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk3/igt@[email protected]
[342]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk1/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-snb: [FAIL][343] -> [PASS][344]
[343]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-snb6/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[344]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-snb7/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_fb_coherency@memset-crc:
- shard-dg2: [SKIP][345] -> [PASS][346]
[345]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[346]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-3/igt@[email protected]
* igt@kms_flip@2x-flip-vs-wf_vblank@ab-hdmi-a1-hdmi-a2:
- shard-glk: ([FAIL][347], [PASS][348]) -> [PASS][349] +4 other tests pass
[347]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk3/igt@kms_flip@[email protected]
[348]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk4/igt@kms_flip@[email protected]
[349]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk1/igt@kms_flip@[email protected]
* igt@kms_flip@2x-plain-flip-ts-check@ac-hdmi-a1-hdmi-a2:
- shard-glk: ([PASS][350], [FAIL][351]) ([i915#2122]) -> [PASS][352] +5 other tests pass
[350]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk6/igt@kms_flip@[email protected]
[351]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk9/igt@kms_flip@[email protected]
[352]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk8/igt@kms_flip@[email protected]
* igt@kms_flip@blocking-wf_vblank@c-hdmi-a1:
- shard-tglu: [FAIL][353] ([i915#2122]) -> [PASS][354] +4 other tests pass
[353]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-tglu-7/igt@kms_flip@[email protected]
[354]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-3/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@a-vga1:
- shard-snb: [FAIL][355] ([i915#2122]) -> [PASS][356] +5 other tests pass
[355]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-snb7/igt@kms_flip@[email protected]
[356]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-snb2/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-fb-recreate-interruptible:
- shard-dg2: [FAIL][357] ([i915#2122]) -> [PASS][358]
[357]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-10/igt@[email protected]
[358]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-7/igt@[email protected]
* igt@kms_flip@plain-flip-fb-recreate-interruptible@c-hdmi-a4:
- shard-dg1: [FAIL][359] ([i915#2122]) -> [PASS][360] +3 other tests pass
[359]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg1-14/igt@kms_flip@[email protected]
[360]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg1-16/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move:
- shard-dg2: [SKIP][361] ([i915#5354]) -> [PASS][362] +5 other tests pass
[361]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[362]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-7/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-blt:
- shard-dg2: [FAIL][363] ([i915#6880]) -> [PASS][364] +1 other test pass
[363]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-6/igt@[email protected]
[364]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-10/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-indfb-plflip-blt:
- shard-snb: [SKIP][365] -> [PASS][366] +16 other tests pass
[365]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-snb1/igt@[email protected]
[366]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-snb7/igt@[email protected]
* igt@kms_invalid_mode@bad-vtotal:
- shard-dg2: [SKIP][367] ([i915#3555]) -> [PASS][368]
[367]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[368]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@[email protected]
* igt@kms_plane_alpha_blend@alpha-transparent-fb:
- shard-dg2: [SKIP][369] ([i915#7294]) -> [PASS][370]
[369]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[370]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@[email protected]
* igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation:
- shard-dg2: [SKIP][371] ([i915#3555] / [i915#8152] / [i915#9423]) -> [PASS][372]
[371]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation.html
[372]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-3/igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation.html
* igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-75:
- shard-dg2: [SKIP][373] ([i915#3555] / [i915#6953] / [i915#8152] / [i915#9423]) -> [PASS][374]
[373]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-75.html
[374]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-75.html
* igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-75@pipe-c:
- shard-dg2: [SKIP][375] ([i915#12247]) -> [PASS][376] +5 other tests pass
[375]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@kms_plane_scaling@[email protected]
[376]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@kms_plane_scaling@[email protected]
* igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-75@pipe-d:
- shard-dg2: [SKIP][377] ([i915#12247] / [i915#8152]) -> [PASS][378] +1 other test pass
[377]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@kms_plane_scaling@[email protected]
[378]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@kms_plane_scaling@[email protected]
* igt@kms_pm_dc@dc9-dpms:
- shard-dg2: [FAIL][379] ([i915#7330]) -> [PASS][380]
[379]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[380]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@[email protected]
* igt@kms_pm_rpm@modeset-non-lpsp-stress:
- shard-dg2: [SKIP][381] ([i915#9519]) -> [PASS][382] +1 other test pass
[381]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[382]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-3/igt@[email protected]
* igt@kms_properties@plane-properties-legacy:
- shard-dg2: [SKIP][383] ([i915#11521]) -> [PASS][384]
[383]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[384]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@[email protected]
* igt@kms_setmode@basic:
- shard-tglu: [FAIL][385] -> [PASS][386] +2 other tests pass
[385]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-tglu-5/igt@[email protected]
[386]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-tglu-10/igt@[email protected]
* igt@kms_vrr@negative-basic:
- shard-mtlp: [FAIL][387] ([i915#10393]) -> [PASS][388] +1 other test pass
[387]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-mtlp-8/igt@[email protected]
[388]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-2/igt@[email protected]
#### Warnings ####
* igt@i915_pipe_stress@stress-xrgb8888-ytiled:
- shard-dg2: [SKIP][389] ([i915#7091]) -> [SKIP][390] ([i915#9197])
[389]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-3/igt@[email protected]
[390]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_big_fb@x-tiled-32bpp-rotate-270:
- shard-dg2: [SKIP][391] ([i915#9197]) -> [SKIP][392] +1 other test skip
[391]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[392]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@[email protected]
* igt@kms_big_fb@x-tiled-8bpp-rotate-90:
- shard-dg2: [SKIP][393] -> [SKIP][394] ([i915#9197])
[393]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@[email protected]
[394]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_big_fb@y-tiled-8bpp-rotate-90:
- shard-dg2: [SKIP][395] ([i915#4538] / [i915#5190]) -> [SKIP][396] ([i915#5190] / [i915#9197]) +4 other tests skip
[395]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@[email protected]
[396]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-async-flip:
- shard-dg2: [SKIP][397] ([i915#5190] / [i915#9197]) -> [SKIP][398] ([i915#4538] / [i915#5190]) +4 other tests skip
[397]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[398]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@[email protected]
* igt@kms_ccs@bad-rotation-90-yf-tiled-ccs:
- shard-dg2: [SKIP][399] ([i915#9197]) -> [SKIP][400] ([i915#10307] / [i915#6095]) +4 other tests skip
[399]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[400]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@[email protected]
* igt@kms_ccs@ccs-on-another-bo-y-tiled-gen12-mc-ccs:
- shard-dg2: [SKIP][401] ([i915#10307] / [i915#6095]) -> [SKIP][402] ([i915#9197]) +4 other tests skip
[401]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@[email protected]
[402]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_ccs@crc-primary-rotation-180-4-tiled-lnl-ccs:
- shard-dg2: [SKIP][403] ([i915#12313]) -> [SKIP][404] ([i915#9197])
[403]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@[email protected]
[404]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_chamelium_hpd@hdmi-hpd-after-suspend:
- shard-mtlp: [INCOMPLETE][405] ([i915#2295]) -> [SKIP][406] ([i915#7828])
[405]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-mtlp-2/igt@[email protected]
[406]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-mtlp-8/igt@[email protected]
* igt@kms_content_protection@lic-type-1:
- shard-dg2: [SKIP][407] ([i915#9424]) -> [SKIP][408] ([i915#9197])
[407]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@[email protected]
[408]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_content_protection@uevent:
- shard-dg2: [FAIL][409] ([i915#1339] / [i915#7173]) -> [SKIP][410] ([i915#7118] / [i915#9424])
[409]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-10/igt@[email protected]
[410]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-7/igt@[email protected]
- shard-snb: [SKIP][411] -> [INCOMPLETE][412] ([i915#8816])
[411]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-snb1/igt@[email protected]
[412]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-snb7/igt@[email protected]
* igt@kms_cursor_crc@cursor-offscreen-512x170:
- shard-dg2: [SKIP][413] ([i915#11453]) -> [SKIP][414] ([i915#9197]) +1 other test skip
[413]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-3/igt@[email protected]
[414]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_cursor_crc@cursor-rapid-movement-512x512:
- shard-dg2: [SKIP][415] ([i915#9197]) -> [SKIP][416] ([i915#11453])
[415]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[416]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@[email protected]
* igt@kms_cursor_crc@cursor-sliding-max-size:
- shard-dg2: [SKIP][417] ([i915#3555]) -> [SKIP][418] ([i915#9197]) +1 other test skip
[417]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@[email protected]
[418]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_cursor_legacy@cursora-vs-flipb-atomic:
- shard-dg2: [SKIP][419] ([i915#9197]) -> [SKIP][420] ([i915#5354]) +1 other test skip
[419]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[420]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-3/igt@[email protected]
* igt@kms_cursor_legacy@cursora-vs-flipb-toggle:
- shard-dg2: [SKIP][421] ([i915#5354]) -> [SKIP][422] ([i915#9197]) +2 other tests skip
[421]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-3/igt@[email protected]
[422]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_dsc@dsc-with-formats:
- shard-dg2: [SKIP][423] ([i915#9197]) -> [SKIP][424] ([i915#3555] / [i915#3840])
[423]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[424]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@[email protected]
* igt@kms_flip@blocking-wf_vblank:
- shard-rkl: [FAIL][425] ([i915#10826]) -> [FAIL][426] ([i915#11961] / [i915#2122])
[425]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-rkl-2/igt@kms_flip@blocking-wf_vblank.html
[426]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-rkl-1/igt@kms_flip@blocking-wf_vblank.html
- shard-snb: [FAIL][427] ([i915#10826] / [i915#2122]) -> [FAIL][428] ([i915#2122])
[427]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-snb2/igt@kms_flip@blocking-wf_vblank.html
[428]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-snb1/igt@kms_flip@blocking-wf_vblank.html
* igt@kms_flip@blocking-wf_vblank@a-vga1:
- shard-snb: [FAIL][429] ([i915#10826]) -> [FAIL][430] ([i915#2122])
[429]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-snb2/igt@kms_flip@[email protected]
[430]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-snb1/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible:
- shard-glk: ([FAIL][431], [PASS][432]) ([i915#2122]) -> [FAIL][433] ([i915#2122]) +1 other test fail
[431]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk4/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible.html
[432]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-glk3/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible.html
[433]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-glk1/igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible.html
* igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-downscaling:
- shard-dg2: [SKIP][434] ([i915#3555]) -> [SKIP][435] ([i915#2672] / [i915#3555]) +1 other test skip
[434]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-downscaling.html
[435]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-3/igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-downscaling.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling:
- shard-dg2: [SKIP][436] ([i915#3555] / [i915#5190]) -> [SKIP][437] ([i915#2672] / [i915#3555] / [i915#5190]) +1 other test skip
[436]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling.html
[437]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-upscaling:
- shard-dg2: [SKIP][438] ([i915#2672] / [i915#3555] / [i915#5190]) -> [SKIP][439] ([i915#3555] / [i915#5190])
[438]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-upscaling.html
[439]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-upscaling.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-pwrite:
- shard-dg2: [SKIP][440] ([i915#5354]) -> [SKIP][441] ([i915#3458]) +9 other tests skip
[440]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-pwrite.html
[441]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-draw-pwrite.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-mmap-gtt:
- shard-dg2: [SKIP][442] ([i915#8708]) -> [SKIP][443] ([i915#5354]) +5 other tests skip
[442]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-3/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-mmap-gtt.html
[443]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-shrfb-draw-mmap-gtt.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-shrfb-draw-mmap-wc:
- shard-dg2: [SKIP][444] ([i915#5354]) -> [SKIP][445] ([i915#8708]) +7 other tests skip
[444]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-shrfb-draw-mmap-wc.html
[445]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-shrfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-pwrite:
- shard-dg2: [SKIP][446] ([i915#10433] / [i915#3458]) -> [SKIP][447] ([i915#3458])
[446]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-4/igt@[email protected]
[447]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-3/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-cpu:
- shard-dg2: [SKIP][448] ([i915#3458]) -> [SKIP][449] ([i915#5354]) +6 other tests skip
[448]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-cpu.html
[449]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-mmap-cpu.html
* igt@kms_frontbuffer_tracking@psr-rgb565-draw-mmap-cpu:
- shard-dg2: [SKIP][450] ([i915#3458]) -> [SKIP][451] ([i915#10433] / [i915#3458])
[450]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-11/igt@[email protected]
[451]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-4/igt@[email protected]
* igt@kms_hdr@invalid-metadata-sizes:
- shard-dg2: [SKIP][452] ([i915#9197]) -> [SKIP][453] ([i915#3555] / [i915#8228])
[452]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[453]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-7/igt@[email protected]
* igt@kms_panel_fitting@atomic-fastset:
- shard-dg2: [SKIP][454] ([i915#6301]) -> [SKIP][455] ([i915#9197])
[454]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-1/igt@[email protected]
[455]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_plane_lowres@tiling-yf:
- shard-dg2: [SKIP][456] ([i915#9197]) -> [SKIP][457] ([i915#3555] / [i915#8821])
[456]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[457]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@[email protected]
* igt@kms_plane_multiple@tiling-y:
- shard-dg2: [SKIP][458] ([i915#9197]) -> [SKIP][459] ([i915#8806])
[458]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[459]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-7/igt@[email protected]
* igt@kms_plane_multiple@tiling-yf:
- shard-dg2: [SKIP][460] ([i915#9197]) -> [SKIP][461] ([i915#3555] / [i915#8806])
[460]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@[email protected]
[461]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-3/igt@[email protected]
* igt@kms_plane_scaling@intel-max-src-size:
- shard-dg2: [SKIP][462] ([i915#6953] / [i915#9423]) -> [FAIL][463] ([i915#8292])
[462]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-6/igt@[email protected]
[463]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-10/igt@[email protected]
* igt@kms_plane_scaling@planes-downscale-factor-0-25:
- shard-dg2: [SKIP][464] ([i915#12247] / [i915#6953] / [i915#9423]) -> [SKIP][465] ([i915#12247] / [i915#6953] / [i915#8152] / [i915#9423])
[464]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-3/igt@[email protected]
[465]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-2/igt@[email protected]
* igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-factor-0-25:
- shard-dg2: [SKIP][466] ([i915#12247] / [i915#6953] / [i915#8152] / [i915#9423]) -> [SKIP][467] ([i915#12247] / [i915#6953] / [i915#9423])
[466]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-factor-0-25.html
[467]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-factor-0-25.html
* igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-factor-0-25@pipe-d:
- shard-dg2: [SKIP][468] ([i915#12247] / [i915#8152]) -> [SKIP][469] ([i915#12247])
[468]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15461/shard-dg2-2/igt@kms_plane_scaling@[email protected]
[469]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/shard-dg2-11/igt@kms_plane_scaling@planes-downscale-factor-0-25-upscale-factor-0-25@pipe-d.
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_138069v5/index.html