ALSA: hda: Release display power reference during shutdown/reboot
PATCH 1/1 ALSA: hda: Release display power reference during shutdown/reboot
Make sure the HDA driver's display power reference is released during shutdown/reboot.
During the shutdown/reboot sequence the pci device core calls the pm_runtime_resume handler for all devices before calling the driver's shutdown callback and so the HDA driver's runtime resume callback will acquire a display power reference (on HSW/BDW). This triggers a power reference held WARN on HSW/BDW in the i915 driver's subsequent shutdown handler, which expects all display power references to be released by that time.
Since the HDA controller is stopped in the shutdown handler in any case, let's follow here the same sequence as the one during runtime suspend. This will also reset the HDA link and drop the display power reference, getting rid of the above WARN.
Tested on HSW.
--- sound/pci/hda/hda_intel.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/pci/hda/hda_intel.c +1 -1
@@ -2383,7 +2383,7 @@ static void azx_shutdown(struct pci_dev *pci)return ; chip = card->private_data;if (chip && chip->running) -azx_stop_chip (chip); +__azx_runtime_suspend (chip); }/* PCI IDs */
Signature · 6 lines
2.27.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for ALSA: hda: Release display power reference during shutdown/reboot
== Series Details ==
== Series Details ==
Series: ALSA: hda: Release display power reference during shutdown/reboot
URL : https://patchwork.freedesktop.org/series/91742/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10255 -> Patchwork_20420
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/index.html
Known issues
------------
Here are the changes found in Patchwork_20420 that come from known issues:
### IGT changes ###
#### Warnings ####
* igt@debugfs_test@read_all_entries:
- fi-cml-s: [DMESG-WARN][1] -> [DMESG-WARN][2] ([i915#1982])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10255/fi-cml-s/igt@debugfs_test@read_all_entries.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/fi-cml-s/igt@debugfs_test@read_all_entries.html
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
Participating hosts (44 -> 38)
------------------------------
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-apl-guc fi-ctg-p8600 fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_10255 -> Patchwork_20420
CI-20190529: 20190529
CI_DRM_10255: 33910d77746495afd054c12d50f158be8039bac0 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6115: 4ef420186b82f1a6d9c9b69d2f8de4fd100a2af3 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_20420: 386f0f4fbaa72ac03e89304ca7550568d6061f59 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
386f0f4fbaa7 ALSA: hda: Release display power reference during shutdown/reboot
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for ALSA: hda: Release display power reference during shutdown/reboot
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: ALSA: hda: Release display power reference during shutdown/reboot
URL : https://patchwork.freedesktop.org/series/91742/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10255_full -> Patchwork_20420_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_20420_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_20420_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_20420_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_big_fb@y-tiled-16bpp-rotate-180:
- shard-iclb: NOTRUN -> [DMESG-WARN][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/shard-iclb1/igt@[email protected]
- shard-tglb: NOTRUN -> [DMESG-WARN][2]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/shard-tglb5/igt@[email protected]
* igt@kms_cursor_legacy@cursora-vs-flipa-legacy:
- shard-snb: NOTRUN -> [DMESG-WARN][3] +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/shard-snb7/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_20420_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_big_fb@y-tiled-16bpp-rotate-180:
- shard-glk: NOTRUN -> [DMESG-WARN][4] ([i915#1610])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/shard-glk1/igt@[email protected]
- shard-kbl: NOTRUN -> [DMESG-WARN][5] ([i915#1610])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/shard-kbl7/igt@[email protected]
- shard-skl: NOTRUN -> [DMESG-WARN][6] ([i915#1610])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/shard-skl9/igt@[email protected]
* igt@kms_concurrent@pipe-a:
- shard-apl: NOTRUN -> [DMESG-WARN][7] ([i915#1610])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/shard-apl3/igt@[email protected]
* igt@kms_cursor_crc@pipe-d-cursor-suspend:
- shard-snb: NOTRUN -> [SKIP][8] ([fdo#109271]) +2 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/shard-snb6/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-2p-primscrn-cur-indfb-onoff:
- shard-apl: NOTRUN -> [SKIP][9] ([fdo#109271])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/shard-apl1/igt@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
- shard-apl: NOTRUN -> [DMESG-WARN][10] ([i915#1610] / [i915#180])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/shard-apl7/igt@[email protected]
#### Warnings ####
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
- shard-kbl: [DMESG-WARN][11] ([i915#1610]) -> [DMESG-WARN][12] ([i915#1610] / [i915#180])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10255/shard-kbl7/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/shard-kbl2/igt@[email protected]
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#1610]: https://gitlab.freedesktop.org/drm/intel/issues/1610
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_10255 -> Patchwork_20420
CI-20190529: 20190529
CI_DRM_10255: 33910d77746495afd054c12d50f158be8039bac0 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6115: 4ef420186b82f1a6d9c9b69d2f8de4fd100a2af3 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_20420: 386f0f4fbaa72ac03e89304ca7550568d6061f59 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20420/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
kernel test robot
build botThank you for the patch! Yet something to improve:
Hi Imre,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on sound/for-next]
[also build test ERROR on v5.13-rc7 next-20210621]
[If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Imre-Deak/ALSA-hda-Release-display-power-reference-during-shutdown-reboot/20210622-014628 base: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next config: alpha-allyesconfig (attached as .config) compiler: alpha-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/69033b3b4fd0f59ad73279ee931c5f28e37e6f61
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Imre-Deak/ALSA-hda-Release-display-power-reference-during-shutdown-reboot/20210622-014628 git checkout 69033b3b4fd0f59ad73279ee931c5f28e37e6f61
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=alpha
If you fix the issue, kindly add following tag as appropriate
All errors (new ones prefixed by >>):
sound/pci/hda/hda_intel.c: In function 'azx_shutdown':
>> sound/pci/hda/hda_intel.c:2388:3: error: implicit declaration of function '__azx_runtime_suspend'; did you mean '__pm_runtime_suspend'? [-Werror=implicit-function-declaration]
2388 | __azx_runtime_suspend(chip);
| ^~~~~~~~~~~~~~~~~~~~~
| __pm_runtime_suspendcc1: some warnings being treated as errors
vim +2388 sound/pci/hda/hda_intel.c
2378
2379 static void azx_shutdown(struct pci_dev *pci)
2380 {
2381 struct snd_card *card = pci_get_drvdata(pci);
2382 struct azx *chip;
2383
2384 if (!card)
2385 return;
2386 chip = card->private_data;
2387 if (chip && chip->running)
> 2388 __azx_runtime_suspend(chip);
2389 }
2390
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
Quoted 12 lines · Imre Deak
Make sure the HDA driver's display power reference is released during shutdown/reboot.
During the shutdown/reboot sequence the pci device core calls the
pm_runtime_resumehandler for all devices before calling the driver's shutdown callback and so the HDA driver's runtime resume callback will acquire a display power reference (on HSW/BDW). This triggers a power reference held WARN on HSW/BDW in the i915 driver's subsequent shutdown handler, which expects all display power references to be released by that time.
Quoted 4 lines
Since the HDA controller is stopped in the shutdown handler in any case, let's follow here the same sequence as the one during runtime suspend. This will also reset the HDA link and drop the display power reference, getting rid of the above WARN.
As kbuild bot suggested, __azx_runtime_suspend() is defined only with CONFIG_PM. We need either moving the function out of ifdef CONFIG_PM block, or having CONFIG_PM conditional call there.
I myself have no much preference, but maybe the latter can be easier to be cherry-picked to stable kernels.
thanks,
Takashi
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 14 lines · Takashi Iwai
Quoted 12 lines · Imre Deak
Make sure the HDA driver's display power reference is released during shutdown/reboot.
During the shutdown/reboot sequence the pci device core calls the
pm_runtime_resumehandler for all devices before calling the driver's shutdown callback and so the HDA driver's runtime resume callback will acquire a display power reference (on HSW/BDW). This triggers a power reference held WARN on HSW/BDW in the i915 driver's subsequent shutdown handler, which expects all display power references to be released by that time.
Quoted 8 lines
Quoted 4 lines
Since the HDA controller is stopped in the shutdown handler in any case, let's follow here the same sequence as the one during runtime suspend. This will also reset the HDA link and drop the display power reference, getting rid of the above WARN.
As kbuild bot suggested,
__azx_runtime_suspend()is defined only withCONFIG_PM. We need either moving the function out of ifdefCONFIG_PMblock, or havingCONFIG_PMconditional call there.
Thanks, missed that. I think we need to drop the power ref in the !CONFIG_PM case as well (since AFAICS then the ref is held after the device is probed), so I'd move __azx_runtime_suspend() out of the CONFIG_PM block (and perhaps rename it to azx_shutdown_chip).
Quoted 2 lines
I myself have no much preference, but maybe the latter can be easier to be cherry-picked to stable kernels.
To my knowledge this only fixes the book-keeping in the i915 driver, so not sure if it's a stable material.
Trying things now with !CONFIG_PM, I noticed that the HDA codec would still keep a separate power reference (which was dropped for me with CONFIG_PM, as the codec was runtime suspended). To fix that we'd need something like the following (on top of the above changes in a separate patch), any comments on it?:
include/sound/core.h +2 -0
@@ -61,6 +61,7 @@ struct snd_device_ops {int (*dev_free)(struct snd_device *dev);int (*dev_register)(struct snd_device *dev);int (*dev_disconnect)(struct snd_device *dev); +void (*dev_shutdown)(struct snd_device *dev); };struct snd_device {
@@ -314,6 +315,7 @@ void snd_device_disconnect(struct snd_card *card, void *device_data);void snd_device_disconnect_all (struct snd_card *card);void snd_device_free (struct snd_card *card,void *device_data);void snd_device_free_all (struct snd_card *card); +void snd_device_shutdown_all (struct snd_card *card);int snd_device_get_state (struct snd_card *card,void *device_data);/* isadma.c */
sound/core/device.c +11 -0
@@ -238,6 +238,17 @@ void snd_device_free_all(struct snd_card *card)__snd_device_free (dev); } +void snd_device_shutdown_all (struct snd_card *card) +{ +struct snd_device *dev; + +list_for_each_entry_reverse (dev, &card->devices, list) { +if (dev->ops->dev_shutdown) + dev->ops->dev_shutdown (dev); + } +} +EXPORT_SYMBOL_GPL (snd_device_shutdown_all); +/** * snd_device_get_state - Get the current state of the given device * @card: the card instance
sound/pci/hda/hda_codec.c +8 -0
@@ -866,6 +866,13 @@ static void snd_hda_codec_dev_release(struct device *dev)kfree (codec); } +static void snd_hda_codec_dev_shutdown (struct snd_device *device) +{ +struct hda_codec *codec = device->device_data; + +codec_display_power (codec, false); +} +#define DEV_NAME_LEN 31 static int snd_hda_codec_device_init(struct hda_bus *bus, struct snd_card *card,
@@ -930,6 +937,7 @@ int snd_hda_codec_device_new(struct hda_bus *bus, struct snd_card *card,static const struct snd_device_ops dev_ops = { .dev_register = snd_hda_codec_dev_register, .dev_free = snd_hda_codec_dev_free, + .dev_shutdown = snd_hda_codec_dev_shutdown, };dev_dbg (card->dev,"%s: entry\n" , __func__);
sound/pci/hda/hda_intel.c +3 -1
@@ -2382,8 +2382,10 @@ static void azx_shutdown(struct pci_dev *pci)if (!card)return ; chip = card->private_data; -if (chip && chip->running) +if (chip && chip->running) { +snd_device_shutdown_all (card);azx_shutdown_chip (chip); + } }/* PCI IDs */
Quoted 3 lines
thanks,
Takashi
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 33 lines · Imre Deak
Quoted 14 lines · Takashi Iwai
Quoted 12 lines · Imre Deak
Make sure the HDA driver's display power reference is released during shutdown/reboot.
During the shutdown/reboot sequence the pci device core calls the
pm_runtime_resumehandler for all devices before calling the driver's shutdown callback and so the HDA driver's runtime resume callback will acquire a display power reference (on HSW/BDW). This triggers a power reference held WARN on HSW/BDW in the i915 driver's subsequent shutdown handler, which expects all display power references to be released by that time.Quoted 8 lines
Quoted 4 lines
Since the HDA controller is stopped in the shutdown handler in any case, let's follow here the same sequence as the one during runtime suspend. This will also reset the HDA link and drop the display power reference, getting rid of the above WARN.
As kbuild bot suggested,
__azx_runtime_suspend()is defined only withCONFIG_PM. We need either moving the function out of ifdefCONFIG_PMblock, or havingCONFIG_PMconditional call there.Thanks, missed that. I think we need to drop the power ref in the !CONFIG_PM case as well (since AFAICS then the ref is held after the device is probed), so I'd move
__azx_runtime_suspend()out of theCONFIG_PMblock (and perhaps rename it toazx_shutdown_chip).Quoted 2 lines
I myself have no much preference, but maybe the latter can be easier to be cherry-picked to stable kernels.
Quoted 8 lines
To my knowledge this only fixes the book-keeping in the i915 driver, so not sure if it's a stable material.
Trying things now with !CONFIG_PM, I noticed that the HDA codec would still keep a separate power reference (which was dropped for me with
CONFIG_PM, as the codec was runtime suspended). To fix that we'd need something like the following (on top of the above changes in a separate patch), any comments on it?:
Adding the common dev_shutdown sounds a bit like overkill. Since it's just a missing shutdown handling in the hd-audio codec side, does the patch like below work instead?
If this works, feel free to fold into your patch.
thanks,
Takashi
---
sound/pci/hda/hda_bind.c +5 -2
@@ -167,8 +167,11 @@ static void hda_codec_driver_shutdown(struct device *dev) {struct hda_codec *codec =dev_to_hda_codec (dev); -if (!pm_runtime_suspended (dev) && codec->patch_ops.reboot_notify) - codec->patch_ops.reboot_notify (codec); +if (!pm_runtime_suspended (dev)) { +if (codec->patch_ops.reboot_notify) + codec->patch_ops.reboot_notify (codec); +snd_hda_codec_display_power (codec, false); + } } int __hda_codec_driver_register(struct hda_codec_driver *drv, const char *name,
sound/pci/hda/hda_codec.c +5 -5
@@ -798,7 +798,7 @@ static unsigned int hda_set_power_state(struct hda_codec *codec, unsigned int power_state);/* enable/disable display power per codec */ -static void codec_display_power (struct hda_codec *codec,bool enable) +void snd_hda_codec_display_power (struct hda_codec *codec,bool enable) {if (codec->display_power_control)snd_hdac_display_power (&codec->bus->core, codec->addr, enable);
@@ -810,7 +810,7 @@ void snd_hda_codec_register(struct hda_codec *codec)if (codec->registered)return ;if (device_is_registered (hda_codec_dev (codec))) { -codec_display_power (codec, true); +snd_hda_codec_display_power (codec, true);pm_runtime_enable (hda_codec_dev (codec));/* it was powered up in snd_hda_codec_new(), now all done */ snd_hda_power_down (codec);
@@ -836,7 +836,7 @@ static int snd_hda_codec_dev_free(struct snd_device *device)*/ if (codec->core.type ==HDA_DEV_LEGACY )snd_hdac_device_unregister (&codec->core); -codec_display_power (codec, false); +snd_hda_codec_display_power (codec, false);/* * In the case of ASoC HD-audio bus, the device refcount is released in
@@ -2893,7 +2893,7 @@ static int hda_codec_runtime_suspend(struct device *dev) (codec_has_clkstop(codec) && codec_has_epss(codec) && (state & AC_PWRST_CLK_STOP_OK)))snd_hdac_codec_link_down (&codec->core); -codec_display_power (codec, false); +snd_hda_codec_display_power (codec, false);return 0 ; }
@@ -2905,7 +2905,7 @@ static int hda_codec_runtime_resume(struct device *dev)if (!codec->card)return 0 ; -codec_display_power (codec, true); +snd_hda_codec_display_power (codec, true);snd_hdac_codec_link_up (&codec->core);hda_call_codec_resume (codec);pm_runtime_mark_last_busy (dev);
sound/pci/hda/hda_local.h +2 -0
@@ -709,6 +709,8 @@ void snd_hdmi_write_eld_info(struct hdmi_eld *eld,#define SND_PRINT_CHANNEL_ALLOCATION_ADVISED_BUFSIZE 80void snd_print_channel_allocation (int spk_alloc,char *buf,int buflen); +void snd_hda_codec_display_power (struct hda_codec *codec,bool enable); +/* */ #define codec_err(codec, fmt, args...) \
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 44 lines · Takashi Iwai
Quoted 33 lines · Imre Deak
Quoted 14 lines · Takashi Iwai
Quoted 12 lines · Imre Deak
Make sure the HDA driver's display power reference is released during shutdown/reboot.
During the shutdown/reboot sequence the pci device core calls the
pm_runtime_resumehandler for all devices before calling the driver's shutdown callback and so the HDA driver's runtime resume callback will acquire a display power reference (on HSW/BDW). This triggers a power reference held WARN on HSW/BDW in the i915 driver's subsequent shutdown handler, which expects all display power references to be released by that time.Quoted 8 lines
Quoted 4 lines
Since the HDA controller is stopped in the shutdown handler in any case, let's follow here the same sequence as the one during runtime suspend. This will also reset the HDA link and drop the display power reference, getting rid of the above WARN.
As kbuild bot suggested,
__azx_runtime_suspend()is defined only withCONFIG_PM. We need either moving the function out of ifdefCONFIG_PMblock, or havingCONFIG_PMconditional call there.Thanks, missed that. I think we need to drop the power ref in the !CONFIG_PM case as well (since AFAICS then the ref is held after the device is probed), so I'd move
__azx_runtime_suspend()out of theCONFIG_PMblock (and perhaps rename it toazx_shutdown_chip).Quoted 2 lines
I myself have no much preference, but maybe the latter can be easier to be cherry-picked to stable kernels.
Quoted 8 lines
To my knowledge this only fixes the book-keeping in the i915 driver, so not sure if it's a stable material.
Trying things now with !CONFIG_PM, I noticed that the HDA codec would still keep a separate power reference (which was dropped for me with
CONFIG_PM, as the codec was runtime suspended). To fix that we'd need something like the following (on top of the above changes in a separate patch), any comments on it?:
Quoted 3 lines
Adding the common
dev_shutdownsounds a bit like overkill. Since it's just a missing shutdown handling in the hd-audio codec side, does the patch like below work instead?
Yes, makes sense, I missed that the codec driver has a shutdown hook already:/ It also fixes the problem.
I wondered about the the 1. codec -> 2. i915 shutdown hook ordering guarantee, but I think that's given by the device_link we add between i915 and the HDA controller dev and the codec dev being located on the HDA controller's bus.
Quoted 1 line
If this works, feel free to fold into your patch.
Ok, will send them as separate patches, if they look ok, could you merge them via the audio tree?
Thanks for the review,
Imre
Quoted 77 lines
thanks,
Takashi
---
sound/pci/hda/hda_bind.c +5
-2@@ -167,8 +167,11 @@ static void hda_codec_driver_shutdown(struct device *dev) {struct hda_codec *codec =dev_to_hda_codec (dev); -if (!pm_runtime_suspended (dev) && codec->patch_ops.reboot_notify) - codec->patch_ops.reboot_notify (codec); +if (!pm_runtime_suspended (dev)) { +if (codec->patch_ops.reboot_notify) + codec->patch_ops.reboot_notify (codec); +snd_hda_codec_display_power (codec, false); + } } int __hda_codec_driver_register(struct hda_codec_driver *drv, const char *name,sound/pci/hda/hda_codec.c +5
-5@@ -798,7 +798,7 @@ static unsigned int hda_set_power_state(struct hda_codec *codec, unsigned int power_state);/* enable/disable display power per codec */ -static void codec_display_power (struct hda_codec *codec,bool enable) +void snd_hda_codec_display_power (struct hda_codec *codec,bool enable) {if (codec->display_power_control)snd_hdac_display_power (&codec->bus->core, codec->addr, enable);@@ -810,7 +810,7 @@ void snd_hda_codec_register(struct hda_codec *codec)if (codec->registered)return ;if (device_is_registered (hda_codec_dev (codec))) { -codec_display_power (codec, true); +snd_hda_codec_display_power (codec, true);pm_runtime_enable (hda_codec_dev (codec));/* it was powered up in snd_hda_codec_new(), now all done */ snd_hda_power_down (codec);@@ -836,7 +836,7 @@ static int snd_hda_codec_dev_free(struct snd_device *device)*/ if (codec->core.type ==HDA_DEV_LEGACY )snd_hdac_device_unregister (&codec->core); -codec_display_power (codec, false); +snd_hda_codec_display_power (codec, false);/* * In the case of ASoC HD-audio bus, the device refcount is released in @@ -2893,7 +2893,7 @@ static int hda_codec_runtime_suspend(struct device *dev) (codec_has_clkstop(codec) && codec_has_epss(codec) && (state & AC_PWRST_CLK_STOP_OK)))snd_hdac_codec_link_down (&codec->core); -codec_display_power (codec, false); +snd_hda_codec_display_power (codec, false);return 0 ; }@@ -2905,7 +2905,7 @@ static int hda_codec_runtime_resume(struct device *dev)if (!codec->card)return 0 ; -codec_display_power (codec, true); +snd_hda_codec_display_power (codec, true);snd_hdac_codec_link_up (&codec->core);hda_call_codec_resume (codec);pm_runtime_mark_last_busy (dev);sound/pci/hda/hda_local.h +0
-0
sound/pci/hda/hda_local.h void snd_hdmi_write_eld_info(struct hdmi_eld *eld, · line 716
Quoted 8 lines
sound/pci/hda/hda_local.h +2
-0@@ -709,6 +709,8 @@ void snd_hdmi_write_eld_info(struct hdmi_eld *eld,#define SND_PRINT_CHANNEL_ALLOCATION_ADVISED_BUFSIZE 80void snd_print_channel_allocation (int spk_alloc,char *buf,int buflen); +void snd_hda_codec_display_power (struct hda_codec *codec,bool enable); +/* */ #define codec_err(codec, fmt, args...) \
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BUILD: failure for ALSA: hda: Release display power reference during shutdown/reboot (rev2)
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: ALSA: hda: Release display power reference during shutdown/reboot (rev2)
URL : https://patchwork.freedesktop.org/series/91742/
State : failure
== Summary ==
Applying: ALSA: hda: Release display power reference during shutdown/reboot
error: sha1 information is lacking or useless (sound/pci/hda/hda_intel.c).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch Patch failed at 0001 ALSA: hda: Release display power reference during shutdown/reboot When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for ALSA: hda: Release display power reference during shutdown/reboot (rev3)
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: ALSA: hda: Release display power reference during shutdown/reboot (rev3)
URL : https://patchwork.freedesktop.org/series/91742/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip bf84d7730b88 ALSA: hda: Release display power reference during shutdown/reboot -:19: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line) #19:
Quoted 1 line
Quoted 1 line
Quoted 1 line
shutdown callback and so the HDA driver's runtime resume callback will
-:140: ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 1 errors, 1 warnings, 0 checks, 61 lines checked
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for ALSA: hda: Release display power reference during shutdown/reboot (rev3)
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: ALSA: hda: Release display power reference during shutdown/reboot (rev3)
URL : https://patchwork.freedesktop.org/series/91742/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10266 -> Patchwork_20436
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/index.html
Known issues
------------
Here are the changes found in Patchwork_20436 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_cs_nop@sync-fork-compute0:
- fi-kbl-soraka: NOTRUN -> [SKIP][1] ([fdo#109271]) +4 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/fi-kbl-soraka/igt@amdgpu/[email protected]
#### Possible fixes ####
* igt@i915_module_load@reload:
- fi-kbl-soraka: [DMESG-WARN][2] ([i915#1982]) -> [PASS][3]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/fi-kbl-soraka/igt@[email protected]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/fi-kbl-soraka/igt@[email protected]
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
Participating hosts (42 -> 38)
------------------------------
Missing (4): fi-ilk-m540 fi-bsw-cyan fi-bdw-samus fi-hsw-4200u
Build changes
-------------
* Linux: CI_DRM_10266 -> Patchwork_20436
CI-20190529: 20190529
CI_DRM_10266: 186513ad0e0c815f0afeda3ffe748dca3e4a5be7 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6117: 3ba0a02404f243d6d8f232c6215163cc4b0fd699 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_20436: bf84d7730b887e10914ff66fb428d494bb38e4bf @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
bf84d7730b88 ALSA: hda: Release display power reference during shutdown/reboot
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for ALSA: hda: Release display power reference during shutdown/reboot (rev3)
In reply to Imre Deak== Series Details ==
== Series Details ==
Series: ALSA: hda: Release display power reference during shutdown/reboot (rev3)
URL : https://patchwork.freedesktop.org/series/91742/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10266_full -> Patchwork_20436_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_20436_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_20436_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_20436_full:
### IGT changes ###
#### Possible regressions ####
* igt@sysfs_timeslice_duration@timeout@vecs0:
- shard-skl: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl8/igt@sysfs_timeslice_duration@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl8/igt@sysfs_timeslice_duration@[email protected]
Known issues
------------
Here are the changes found in Patchwork_20436_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@preservation-s3@bcs0:
- shard-kbl: NOTRUN -> [DMESG-WARN][3] ([i915#180])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-kbl7/igt@gem_ctx_isolation@[email protected]
* igt@gem_ctx_persistence@legacy-engines-hostile-preempt:
- shard-snb: NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#1099]) +3 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-snb6/igt@[email protected]
* igt@gem_eio@unwedge-stress:
- shard-snb: NOTRUN -> [FAIL][5] ([i915#3354])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-snb2/igt@[email protected]
* igt@gem_exec_fair@basic-deadline:
- shard-apl: NOTRUN -> [FAIL][6] ([i915#2846])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-apl8/igt@[email protected]
* igt@gem_exec_fair@basic-pace@vcs1:
- shard-iclb: NOTRUN -> [FAIL][7] ([i915#2842])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb2/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-glk: [PASS][8] -> [FAIL][9] ([i915#2842]) +2 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-glk3/igt@gem_exec_fair@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-glk4/igt@gem_exec_fair@[email protected]
- shard-iclb: [PASS][10] -> [FAIL][11] ([i915#2849])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-iclb5/igt@gem_exec_fair@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_reloc@basic-wide-active@vcs1:
- shard-iclb: NOTRUN -> [FAIL][12] ([i915#3633])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb4/igt@gem_exec_reloc@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-apl: NOTRUN -> [SKIP][13] ([fdo#109271] / [i915#2190])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-apl8/igt@[email protected]
* igt@gem_pwrite@basic-exhaustion:
- shard-skl: NOTRUN -> [WARN][14] ([i915#2658])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl3/igt@[email protected]
- shard-snb: NOTRUN -> [WARN][15] ([i915#2658]) +1 similar issue
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-snb2/igt@[email protected]
* igt@gem_userptr_blits@vma-merge:
- shard-snb: NOTRUN -> [FAIL][16] ([i915#2724])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-snb6/igt@[email protected]
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: NOTRUN -> [WARN][17] ([i915#1804] / [i915#2684])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb7/igt@[email protected]
* igt@i915_pm_rpm@modeset-lpsp-stress:
- shard-apl: NOTRUN -> [SKIP][18] ([fdo#109271]) +158 similar issues
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-apl3/igt@[email protected]
* igt@i915_selftest@live@gt_pm:
- shard-skl: NOTRUN -> [DMESG-FAIL][19] ([i915#1886] / [i915#2291])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl1/igt@i915_selftest@live@gt_pm.html
* igt@kms_chamelium@dp-crc-fast:
- shard-iclb: NOTRUN -> [SKIP][20] ([fdo#109284] / [fdo#111827]) +1 similar issue
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb7/igt@[email protected]
* igt@kms_chamelium@hdmi-hpd-storm-disable:
- shard-skl: NOTRUN -> [SKIP][21] ([fdo#109271] / [fdo#111827]) +11 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl1/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-ctm-blue-to-red:
- shard-snb: NOTRUN -> [SKIP][22] ([fdo#109271] / [fdo#111827]) +16 similar issues
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-snb6/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-ctm-limited-range:
- shard-apl: NOTRUN -> [SKIP][23] ([fdo#109271] / [fdo#111827]) +18 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-apl3/igt@[email protected]
* igt@kms_content_protection@atomic-dpms:
- shard-iclb: NOTRUN -> [SKIP][24] ([fdo#109300] / [fdo#111066])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb7/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-apl: NOTRUN -> [TIMEOUT][25] ([i915#1319]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-apl3/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-512x170-sliding:
- shard-iclb: NOTRUN -> [SKIP][26] ([fdo#109278] / [fdo#109279])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb7/igt@[email protected]
* igt@kms_cursor_legacy@cursorb-vs-flipb-atomic-transitions-varying-size:
- shard-iclb: NOTRUN -> [SKIP][27] ([fdo#109274] / [fdo#109278]) +1 similar issue
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb7/igt@kms_cursor_legacy@cursorb-vs-flipb-atomic-transitions-varying-size.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-skl: [PASS][28] -> [FAIL][29] ([i915#2346] / [i915#533])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl1/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl10/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_cursor_legacy@pipe-d-torture-move:
- shard-skl: NOTRUN -> [SKIP][30] ([fdo#109271]) +102 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl9/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1:
- shard-skl: [PASS][31] -> [FAIL][32] ([i915#79])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl3/igt@kms_flip@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl5/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@b-hdmi-a1:
- shard-glk: [PASS][33] -> [FAIL][34] ([i915#79])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-glk1/igt@kms_flip@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-glk2/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible@c-dp1:
- shard-kbl: [PASS][35] -> [DMESG-WARN][36] ([i915#180])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-kbl7/igt@kms_flip@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-kbl2/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible@c-edp1:
- shard-skl: [PASS][37] -> [INCOMPLETE][38] ([i915#198])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl5/igt@kms_flip@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl8/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-ts-check@c-hdmi-a1:
- shard-glk: [PASS][39] -> [FAIL][40] ([i915#2122])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-glk1/igt@kms_flip@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-glk2/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs:
- shard-skl: NOTRUN -> [SKIP][41] ([fdo#109271] / [i915#2672])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl3/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-shrfb-fliptrack-mmap-gtt:
- shard-iclb: NOTRUN -> [SKIP][42] ([fdo#109280]) +5 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb7/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-blt:
- shard-snb: NOTRUN -> [SKIP][43] ([fdo#109271]) +330 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-snb6/igt@[email protected]
* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [PASS][44] -> [FAIL][45] ([i915#1188])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl8/igt@[email protected]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl4/igt@[email protected]
* igt@kms_invalid_dotclock:
- shard-iclb: NOTRUN -> [SKIP][46] ([fdo#109310])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb7/igt@kms_invalid_dotclock.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- shard-apl: NOTRUN -> [SKIP][47] ([fdo#109271] / [i915#533]) +3 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-apl6/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb:
- shard-skl: NOTRUN -> [FAIL][48] ([i915#265])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl3/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-alpha-basic:
- shard-apl: NOTRUN -> [FAIL][49] ([fdo#108145] / [i915#265]) +3 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-apl6/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max:
- shard-skl: NOTRUN -> [FAIL][50] ([fdo#108145] / [i915#265]) +1 similar issue
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl1/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [PASS][51] -> [FAIL][52] ([fdo#108145] / [i915#265])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl8/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl9/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-d-coverage-vs-premult-vs-constant:
- shard-iclb: NOTRUN -> [SKIP][53] ([fdo#109278]) +3 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb7/igt@kms_plane_alpha_blend@pipe-d-coverage-vs-premult-vs-constant.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2:
- shard-apl: NOTRUN -> [SKIP][54] ([fdo#109271] / [i915#658]) +2 similar issues
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-apl3/igt@[email protected]
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1:
- shard-skl: NOTRUN -> [SKIP][55] ([fdo#109271] / [i915#658]) +1 similar issue
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl1/igt@[email protected]
* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [PASS][56] -> [SKIP][57] ([fdo#109441]) +1 similar issue
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb5/igt@kms_psr@psr2_sprite_plane_move.html
* igt@kms_setmode@basic:
- shard-snb: NOTRUN -> [FAIL][58] ([i915#31])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-snb2/igt@[email protected]
* igt@kms_sysfs_edid_timing:
- shard-skl: NOTRUN -> [FAIL][59] ([IGT#2])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl1/igt@kms_sysfs_edid_timing.html
* igt@kms_writeback@writeback-invalid-parameters:
- shard-apl: NOTRUN -> [SKIP][60] ([fdo#109271] / [i915#2437])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-apl7/igt@[email protected]
* igt@perf@polling-parameterized:
- shard-skl: [PASS][61] -> [FAIL][62] ([i915#1542])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl1/igt@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl6/igt@[email protected]
* igt@sysfs_clients@fair-1:
- shard-skl: NOTRUN -> [SKIP][63] ([fdo#109271] / [i915#2994])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl3/igt@[email protected]
* igt@sysfs_clients@fair-7:
- shard-apl: NOTRUN -> [SKIP][64] ([fdo#109271] / [i915#2994]) +1 similar issue
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-apl8/igt@[email protected]
#### Possible fixes ####
* igt@gem_ctx_isolation@preservation-s3@rcs0:
- shard-kbl: [INCOMPLETE][65] ([i915#794]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-kbl2/igt@gem_ctx_isolation@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-kbl7/igt@gem_ctx_isolation@[email protected]
* igt@gem_eio@unwedge-stress:
- shard-tglb: [TIMEOUT][67] ([i915#2369] / [i915#3063]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-tglb2/igt@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-tglb5/igt@[email protected]
* igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [FAIL][69] ([i915#2842]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-tglb2/igt@gem_exec_fair@[email protected]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-tglb7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-apl: [SKIP][71] ([fdo#109271]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-apl1/igt@gem_exec_fair@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-apl3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none@rcs0:
- shard-glk: [FAIL][73] ([i915#2842]) -> [PASS][74] +1 similar issue
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-glk3/igt@gem_exec_fair@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-glk4/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none@vcs0:
- shard-kbl: [FAIL][75] ([i915#2842]) -> [PASS][76] +2 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-kbl7/igt@gem_exec_fair@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-kbl6/igt@gem_exec_fair@[email protected]
* igt@gem_mmap_gtt@big-copy-odd:
- shard-skl: [FAIL][77] ([i915#307]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl7/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl7/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-skl: [DMESG-WARN][79] ([i915#1436] / [i915#716]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl6/igt@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl9/igt@[email protected]
* igt@kms_big_fb@linear-32bpp-rotate-180:
- shard-glk: [DMESG-WARN][81] ([i915#118] / [i915#95]) -> [PASS][82] +2 similar issues
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-glk1/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-glk2/igt@[email protected]
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@bc-hdmi-a1-hdmi-a2:
- shard-glk: [FAIL][83] ([i915#79]) -> [PASS][84]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-glk7/igt@kms_flip@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-glk5/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend@c-edp1:
- shard-skl: [INCOMPLETE][85] ([i915#146] / [i915#198]) -> [PASS][86]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl8/igt@kms_flip@[email protected]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl4/igt@kms_flip@[email protected]
* igt@kms_psr@psr2_cursor_blt:
- shard-iclb: [SKIP][87] ([fdo#109441]) -> [PASS][88] +2 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-iclb5/igt@kms_psr@psr2_cursor_blt.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb2/igt@kms_psr@psr2_cursor_blt.html
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-apl: [DMESG-WARN][89] ([i915#180] / [i915#295]) -> [PASS][90]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-apl1/igt@[email protected]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-apl3/igt@[email protected]
* igt@perf@polling-small-buf:
- shard-skl: [FAIL][91] ([i915#1722]) -> [PASS][92]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl6/igt@[email protected]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl6/igt@[email protected]
#### Warnings ####
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: [WARN][93] ([i915#1804] / [i915#2684]) -> [WARN][94] ([i915#2684])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-iclb7/igt@[email protected]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb2/igt@[email protected]
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-3:
- shard-iclb: [SKIP][95] ([i915#2920]) -> [SKIP][96] ([i915#658]) +2 similar issues
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-iclb2/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb5/igt@[email protected]
* igt@kms_psr2_sf@plane-move-sf-dmg-area-0:
- shard-iclb: [SKIP][97] ([i915#658]) -> [SKIP][98] ([i915#2920]) +3 similar issues
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-iclb5/igt@[email protected]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb2/igt@[email protected]
* igt@runner@aborted:
- shard-kbl: ([FAIL][99], [FAIL][100], [FAIL][101]) ([i915#180] / [i915#3002] / [i915#3363]) -> ([FAIL][102], [FAIL][103], [FAIL][104], [FAIL][105]) ([i915#1436] / [i915#180] / [i915#3002] / [i915#3363])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-kbl4/igt@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-kbl7/igt@[email protected]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-kbl3/igt@[email protected]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-kbl2/igt@[email protected]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-kbl4/igt@[email protected]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-kbl7/igt@[email protected]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-kbl7/igt@[email protected]
- shard-iclb: ([FAIL][106], [FAIL][107], [FAIL][108]) ([i915#1814] / [i915#3002]) -> ([FAIL][109], [FAIL][110]) ([i915#3002])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-iclb7/igt@[email protected]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-iclb4/igt@[email protected]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-iclb2/igt@[email protected]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb5/igt@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-iclb4/igt@[email protected]
- shard-apl: ([FAIL][111], [FAIL][112], [FAIL][113], [FAIL][114], [FAIL][115]) ([i915#180] / [i915#1814] / [i915#3002] / [i915#3363]) -> [FAIL][116] ([i915#3002] / [i915#3363])
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-apl7/igt@[email protected]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-apl7/igt@[email protected]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-apl3/igt@[email protected]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-apl1/igt@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-apl3/igt@[email protected]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-apl2/igt@[email protected]
- shard-skl: ([FAIL][117], [FAIL][118], [FAIL][119]) ([i915#1436] / [i915#3002] / [i915#3363]) -> ([FAIL][120], [FAIL][121]) ([i915#3002] / [i915#3363])
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl2/igt@[email protected]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl6/igt@[email protected]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10266/shard-skl6/igt@[email protected]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl10/igt@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/shard-skl6/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[IGT#2]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/2
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109279]: https://bugs.freedesktop.org/show_bug.cgi?id=109279
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109300]: https://bugs.freedesktop.org/show_bug.cgi?id=109300
[fdo#109310]: https://bugs.freedesktop.org/show_bug.cgi?id=109310
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#111066]: https://bugs.freedesktop.org/show_bug.cgi?id=111066
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1099]: https://gitlab.freedesktop.org/drm/intel/issues/1099
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#146]: https://gitlab.freedesktop.org/drm/intel/issues/146
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#1722]: https://gitlab.freedesktop.org/drm/intel/issues/1722
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1804]: https://gitlab.freedesktop.org/drm/intel/issues/1804
[i915#1814]: https://gitlab.freedesktop.org/drm/intel/issues/1814
[i915#1886]: https://gitlab.freedesktop.org/drm/intel/issues/1886
[i915#198]: https://gitlab.freedesktop.org/drm/intel/issues/198
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2291]: https://gitlab.freedesktop.org/drm/intel/issues/2291
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2369]: https://gitlab.freedesktop.org/drm/intel/issues/2369
[i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2684]: https://gitlab.freedesktop.org/drm/intel/issues/2684
[i915#2724]: https://gitlab.freedesktop.org/drm/intel/issues/2724
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2846]: https://gitlab.freedesktop.org/drm/intel/issues/2846
[i915#2849]: https://gitlab.freedesktop.org/drm/intel/issues/2849
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#295]: https://gitlab.freedesktop.org/drm/intel/issues/295
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[i915#3002]: https://gitlab.freedesktop.org/drm/intel/issues/3002
[i915#3063]: https://gitlab.freedesktop.org/drm/intel/issues/3063
[i915#307]: https://gitlab.freedesktop.org/drm/intel/issues/307
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#3354]: https://gitlab.freedesktop.org/drm/intel/issues/3354
[i915#3363]: https://gitlab.freedesktop.org/drm/intel/issues/3363
[i915#3633]: https://gitlab.freedesktop.org/drm/intel/issues/3633
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#794]: https://gitlab.freedesktop.org/drm/intel/issues/794
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_10266 -> Patchwork_20436
CI-20190529: 20190529
CI_DRM_10266: 186513ad0e0c815f0afeda3ffe748dca3e4a5be7 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6117: 3ba0a02404f243d6d8f232c6215163cc4b0fd699 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_20436: bf84d7730b887e10914ff66fb428d494bb38e4bf @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20436/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx