* [Intel-gfx] [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
@ 2021-11-10 21:03 ` Kai Vehmanen
0 siblings, 0 replies; 26+ messages in thread
From: Kai Vehmanen @ 2021-11-10 21:03 UTC (permalink / raw)
To: alsa-devel, tiwai; +Cc: intel-gfx
Fix a corner case between PCI device driver remove callback and
runtime PM idle callback.
Following sequence of events can happen:
- at azx_create, context is allocated with devm_kzalloc() and
stored as pci_set_drvdata()
- user-space requests to unbind audio driver
- dd.c:__device_release_driver() calls PCI remove
- pci-driver.c:pci_device_remove() calls the audio
driver azx_remove() callback and this is completed
- pci-driver.c:pm_runtime_put_sync() leads to a call
to rpm_idle() which again calls azx_runtime_idle()
- the azx context object, as returned by dev_get_drvdata(),
is no longer valid
-> access fault in azx_runtime_idle when executing
struct snd_card *card = dev_get_drvdata(dev);
chip = card->private_data;
if (chip->disabled || hda->init_failed)
This was discovered by i915_module_load test with 5.15.0 based
linux-next tree.
Example log caught by i915_module_load test with linux-next
https://intel-gfx-ci.01.org/tree/linux-next/
<4> [264.038232] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b73f0: 0000 [#1] PREEMPT SMP NOPTI
<4> [264.038248] CPU: 0 PID: 5374 Comm: i915_module_loa Not tainted 5.15.0-next-20211109-gc8109c2ba35e-next-20211109 #1
[...]
<4> [264.038267] RIP: 0010:azx_runtime_idle+0x12/0x60 [snd_hda_intel]
[...]
<4> [264.038355] Call Trace:
<4> [264.038359] <TASK>
<4> [264.038362] __rpm_callback+0x3d/0x110
<4> [264.038371] rpm_idle+0x27f/0x380
<4> [264.038376] __pm_runtime_idle+0x3b/0x100
<4> [264.038382] pci_device_remove+0x6d/0xa0
<4> [264.038388] device_release_driver_internal+0xef/0x1e0
<4> [264.038395] unbind_store+0xeb/0x120
<4> [264.038400] kernfs_fop_write_iter+0x11a/0x1c0
Fix the issue by setting drvdata to NULL at end of azx_remove().
Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
---
sound/pci/hda/hda_intel.c | 1 +
1 file changed, 1 insertion(+)
Some non-persistent direct links showing the bug trigger on
different platforms with linux-next 20211109:
- https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-tgl-1115g4/igt@i915_module_load@reload.html
- https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-jsl-1/igt@i915_module_load@reload.html
Notably with 20211110 linux-next, the bug does not trigger:
- https://intel-gfx-ci.01.org/tree/linux-next/next-20211110/fi-tgl-1115g4/igt@i915_module_load@reload.html
diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
index 7762718cf429..b90c817e3f6f 100644
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -2364,6 +2364,7 @@ static void azx_remove(struct pci_dev *pci)
cancel_delayed_work_sync(&hda->probe_work);
device_lock(&pci->dev);
+ pci_set_drvdata(pci, NULL);
snd_card_free(card);
}
}
base-commit: 6322ec8d0de924cf9672b23c1b5052afafc2f03b
--
2.33.0
^ permalink raw reply related [flat|nested] 26+ messages in thread
* [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
@ 2021-11-10 21:03 ` Kai Vehmanen
0 siblings, 0 replies; 26+ messages in thread
From: Kai Vehmanen @ 2021-11-10 21:03 UTC (permalink / raw)
To: alsa-devel, tiwai; +Cc: intel-gfx, kai.vehmanen, mahesh.meena
Fix a corner case between PCI device driver remove callback and
runtime PM idle callback.
Following sequence of events can happen:
- at azx_create, context is allocated with devm_kzalloc() and
stored as pci_set_drvdata()
- user-space requests to unbind audio driver
- dd.c:__device_release_driver() calls PCI remove
- pci-driver.c:pci_device_remove() calls the audio
driver azx_remove() callback and this is completed
- pci-driver.c:pm_runtime_put_sync() leads to a call
to rpm_idle() which again calls azx_runtime_idle()
- the azx context object, as returned by dev_get_drvdata(),
is no longer valid
-> access fault in azx_runtime_idle when executing
struct snd_card *card = dev_get_drvdata(dev);
chip = card->private_data;
if (chip->disabled || hda->init_failed)
This was discovered by i915_module_load test with 5.15.0 based
linux-next tree.
Example log caught by i915_module_load test with linux-next
https://intel-gfx-ci.01.org/tree/linux-next/
<4> [264.038232] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b73f0: 0000 [#1] PREEMPT SMP NOPTI
<4> [264.038248] CPU: 0 PID: 5374 Comm: i915_module_loa Not tainted 5.15.0-next-20211109-gc8109c2ba35e-next-20211109 #1
[...]
<4> [264.038267] RIP: 0010:azx_runtime_idle+0x12/0x60 [snd_hda_intel]
[...]
<4> [264.038355] Call Trace:
<4> [264.038359] <TASK>
<4> [264.038362] __rpm_callback+0x3d/0x110
<4> [264.038371] rpm_idle+0x27f/0x380
<4> [264.038376] __pm_runtime_idle+0x3b/0x100
<4> [264.038382] pci_device_remove+0x6d/0xa0
<4> [264.038388] device_release_driver_internal+0xef/0x1e0
<4> [264.038395] unbind_store+0xeb/0x120
<4> [264.038400] kernfs_fop_write_iter+0x11a/0x1c0
Fix the issue by setting drvdata to NULL at end of azx_remove().
Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
---
sound/pci/hda/hda_intel.c | 1 +
1 file changed, 1 insertion(+)
Some non-persistent direct links showing the bug trigger on
different platforms with linux-next 20211109:
- https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-tgl-1115g4/igt@i915_module_load@reload.html
- https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-jsl-1/igt@i915_module_load@reload.html
Notably with 20211110 linux-next, the bug does not trigger:
- https://intel-gfx-ci.01.org/tree/linux-next/next-20211110/fi-tgl-1115g4/igt@i915_module_load@reload.html
diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
index 7762718cf429..b90c817e3f6f 100644
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -2364,6 +2364,7 @@ static void azx_remove(struct pci_dev *pci)
cancel_delayed_work_sync(&hda->probe_work);
device_lock(&pci->dev);
+ pci_set_drvdata(pci, NULL);
snd_card_free(card);
}
}
base-commit: 6322ec8d0de924cf9672b23c1b5052afafc2f03b
--
2.33.0
^ permalink raw reply related [flat|nested] 26+ messages in thread
* Re: [Intel-gfx] [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
2021-11-10 21:03 ` Kai Vehmanen
@ 2021-11-10 21:55 ` Takashi Iwai
-1 siblings, 0 replies; 26+ messages in thread
From: Takashi Iwai @ 2021-11-10 21:55 UTC (permalink / raw)
To: Kai Vehmanen; +Cc: alsa-devel, intel-gfx
On Wed, 10 Nov 2021 22:03:07 +0100,
Kai Vehmanen wrote:
>
> Fix a corner case between PCI device driver remove callback and
> runtime PM idle callback.
>
> Following sequence of events can happen:
> - at azx_create, context is allocated with devm_kzalloc() and
> stored as pci_set_drvdata()
> - user-space requests to unbind audio driver
> - dd.c:__device_release_driver() calls PCI remove
> - pci-driver.c:pci_device_remove() calls the audio
> driver azx_remove() callback and this is completed
> - pci-driver.c:pm_runtime_put_sync() leads to a call
> to rpm_idle() which again calls azx_runtime_idle()
> - the azx context object, as returned by dev_get_drvdata(),
> is no longer valid
> -> access fault in azx_runtime_idle when executing
> struct snd_card *card = dev_get_drvdata(dev);
> chip = card->private_data;
> if (chip->disabled || hda->init_failed)
>
> This was discovered by i915_module_load test with 5.15.0 based
> linux-next tree.
>
> Example log caught by i915_module_load test with linux-next
> https://intel-gfx-ci.01.org/tree/linux-next/
>
> <4> [264.038232] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b73f0: 0000 [#1] PREEMPT SMP NOPTI
> <4> [264.038248] CPU: 0 PID: 5374 Comm: i915_module_loa Not tainted 5.15.0-next-20211109-gc8109c2ba35e-next-20211109 #1
> [...]
> <4> [264.038267] RIP: 0010:azx_runtime_idle+0x12/0x60 [snd_hda_intel]
> [...]
> <4> [264.038355] Call Trace:
> <4> [264.038359] <TASK>
> <4> [264.038362] __rpm_callback+0x3d/0x110
> <4> [264.038371] rpm_idle+0x27f/0x380
> <4> [264.038376] __pm_runtime_idle+0x3b/0x100
> <4> [264.038382] pci_device_remove+0x6d/0xa0
> <4> [264.038388] device_release_driver_internal+0xef/0x1e0
> <4> [264.038395] unbind_store+0xeb/0x120
> <4> [264.038400] kernfs_fop_write_iter+0x11a/0x1c0
>
> Fix the issue by setting drvdata to NULL at end of azx_remove().
>
> Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> ---
> sound/pci/hda/hda_intel.c | 1 +
> 1 file changed, 1 insertion(+)
>
> Some non-persistent direct links showing the bug trigger on
> different platforms with linux-next 20211109:
> - https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-tgl-1115g4/igt@i915_module_load@reload.html
> - https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-jsl-1/igt@i915_module_load@reload.html
>
> Notably with 20211110 linux-next, the bug does not trigger:
> - https://intel-gfx-ci.01.org/tree/linux-next/next-20211110/fi-tgl-1115g4/igt@i915_module_load@reload.html
Is this the case with CONFIG_DEBUG_KOBJECT_RELEASE?
This would be the only logical explanation I can think of for now.
In anyway, the code change itself looks good, so I took the fix now.
thanks,
Takashi
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
@ 2021-11-10 21:55 ` Takashi Iwai
0 siblings, 0 replies; 26+ messages in thread
From: Takashi Iwai @ 2021-11-10 21:55 UTC (permalink / raw)
To: Kai Vehmanen; +Cc: alsa-devel, intel-gfx, mahesh.meena
On Wed, 10 Nov 2021 22:03:07 +0100,
Kai Vehmanen wrote:
>
> Fix a corner case between PCI device driver remove callback and
> runtime PM idle callback.
>
> Following sequence of events can happen:
> - at azx_create, context is allocated with devm_kzalloc() and
> stored as pci_set_drvdata()
> - user-space requests to unbind audio driver
> - dd.c:__device_release_driver() calls PCI remove
> - pci-driver.c:pci_device_remove() calls the audio
> driver azx_remove() callback and this is completed
> - pci-driver.c:pm_runtime_put_sync() leads to a call
> to rpm_idle() which again calls azx_runtime_idle()
> - the azx context object, as returned by dev_get_drvdata(),
> is no longer valid
> -> access fault in azx_runtime_idle when executing
> struct snd_card *card = dev_get_drvdata(dev);
> chip = card->private_data;
> if (chip->disabled || hda->init_failed)
>
> This was discovered by i915_module_load test with 5.15.0 based
> linux-next tree.
>
> Example log caught by i915_module_load test with linux-next
> https://intel-gfx-ci.01.org/tree/linux-next/
>
> <4> [264.038232] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b73f0: 0000 [#1] PREEMPT SMP NOPTI
> <4> [264.038248] CPU: 0 PID: 5374 Comm: i915_module_loa Not tainted 5.15.0-next-20211109-gc8109c2ba35e-next-20211109 #1
> [...]
> <4> [264.038267] RIP: 0010:azx_runtime_idle+0x12/0x60 [snd_hda_intel]
> [...]
> <4> [264.038355] Call Trace:
> <4> [264.038359] <TASK>
> <4> [264.038362] __rpm_callback+0x3d/0x110
> <4> [264.038371] rpm_idle+0x27f/0x380
> <4> [264.038376] __pm_runtime_idle+0x3b/0x100
> <4> [264.038382] pci_device_remove+0x6d/0xa0
> <4> [264.038388] device_release_driver_internal+0xef/0x1e0
> <4> [264.038395] unbind_store+0xeb/0x120
> <4> [264.038400] kernfs_fop_write_iter+0x11a/0x1c0
>
> Fix the issue by setting drvdata to NULL at end of azx_remove().
>
> Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> ---
> sound/pci/hda/hda_intel.c | 1 +
> 1 file changed, 1 insertion(+)
>
> Some non-persistent direct links showing the bug trigger on
> different platforms with linux-next 20211109:
> - https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-tgl-1115g4/igt@i915_module_load@reload.html
> - https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-jsl-1/igt@i915_module_load@reload.html
>
> Notably with 20211110 linux-next, the bug does not trigger:
> - https://intel-gfx-ci.01.org/tree/linux-next/next-20211110/fi-tgl-1115g4/igt@i915_module_load@reload.html
Is this the case with CONFIG_DEBUG_KOBJECT_RELEASE?
This would be the only logical explanation I can think of for now.
In anyway, the code change itself looks good, so I took the fix now.
thanks,
Takashi
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for ALSA: hda: fix general protection fault in azx_runtime_idle
2021-11-10 21:03 ` Kai Vehmanen
(?)
(?)
@ 2021-11-10 21:57 ` Patchwork
-1 siblings, 0 replies; 26+ messages in thread
From: Patchwork @ 2021-11-10 21:57 UTC (permalink / raw)
To: Kai Vehmanen; +Cc: intel-gfx
== Series Details ==
Series: ALSA: hda: fix general protection fault in azx_runtime_idle
URL : https://patchwork.freedesktop.org/series/96784/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
f81f77a16d9c ALSA: hda: fix general protection fault in azx_runtime_idle
-:31: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#31:
<4> [264.038232] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b73f0: 0000 [#1] PREEMPT SMP NOPTI
total: 0 errors, 1 warnings, 0 checks, 7 lines checked
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [Intel-gfx] [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
2021-11-10 21:55 ` Takashi Iwai
@ 2021-11-10 22:15 ` Kai Vehmanen
-1 siblings, 0 replies; 26+ messages in thread
From: Kai Vehmanen @ 2021-11-10 22:15 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel, intel-gfx
Hey,
On Wed, 10 Nov 2021, Takashi Iwai wrote:
> On Wed, 10 Nov 2021 22:03:07 +0100, Kai Vehmanen wrote:
> > Fix a corner case between PCI device driver remove callback and
> > runtime PM idle callback.
[...]
> > Some non-persistent direct links showing the bug trigger on
> > different platforms with linux-next 20211109:
> > - https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-tgl-1115g4/igt@i915_module_load@reload.html
> > - https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-jsl-1/igt@i915_module_load@reload.html
> >
> > Notably with 20211110 linux-next, the bug does not trigger:
> > - https://intel-gfx-ci.01.org/tree/linux-next/next-20211110/fi-tgl-1115g4/igt@i915_module_load@reload.html
>
> Is this the case with CONFIG_DEBUG_KOBJECT_RELEASE?
> This would be the only logical explanation I can think of for now.
hmm, that doesn't seem to be used. Here's a link to kconfig used in the
failing CI run:
https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/kconfig.txt
It's still a bit odd, especially given Scott just reported the other HDA
related regression in 5.15 today. The two issues don't seem to be related
though, although both are fixed by clearing drvdata (but in different
places of hda_intel.c).
I'll try to run some more tests tomorrow. The fix should be good in any
case, but it would be interesting to understand better what change made
this more (?) likely to hit than before. This is not a new test and the
problem happens on fairly old platforms, so something has changed.
Br, Kai
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
@ 2021-11-10 22:15 ` Kai Vehmanen
0 siblings, 0 replies; 26+ messages in thread
From: Kai Vehmanen @ 2021-11-10 22:15 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel, intel-gfx, Kai Vehmanen, mahesh.meena
Hey,
On Wed, 10 Nov 2021, Takashi Iwai wrote:
> On Wed, 10 Nov 2021 22:03:07 +0100, Kai Vehmanen wrote:
> > Fix a corner case between PCI device driver remove callback and
> > runtime PM idle callback.
[...]
> > Some non-persistent direct links showing the bug trigger on
> > different platforms with linux-next 20211109:
> > - https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-tgl-1115g4/igt@i915_module_load@reload.html
> > - https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-jsl-1/igt@i915_module_load@reload.html
> >
> > Notably with 20211110 linux-next, the bug does not trigger:
> > - https://intel-gfx-ci.01.org/tree/linux-next/next-20211110/fi-tgl-1115g4/igt@i915_module_load@reload.html
>
> Is this the case with CONFIG_DEBUG_KOBJECT_RELEASE?
> This would be the only logical explanation I can think of for now.
hmm, that doesn't seem to be used. Here's a link to kconfig used in the
failing CI run:
https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/kconfig.txt
It's still a bit odd, especially given Scott just reported the other HDA
related regression in 5.15 today. The two issues don't seem to be related
though, although both are fixed by clearing drvdata (but in different
places of hda_intel.c).
I'll try to run some more tests tomorrow. The fix should be good in any
case, but it would be interesting to understand better what change made
this more (?) likely to hit than before. This is not a new test and the
problem happens on fairly old platforms, so something has changed.
Br, Kai
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for ALSA: hda: fix general protection fault in azx_runtime_idle
2021-11-10 21:03 ` Kai Vehmanen
` (2 preceding siblings ...)
(?)
@ 2021-11-10 22:27 ` Patchwork
-1 siblings, 0 replies; 26+ messages in thread
From: Patchwork @ 2021-11-10 22:27 UTC (permalink / raw)
To: Kai Vehmanen; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 6043 bytes --]
== Series Details ==
Series: ALSA: hda: fix general protection fault in azx_runtime_idle
URL : https://patchwork.freedesktop.org/series/96784/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10863 -> Patchwork_21556
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/index.html
Participating hosts (39 -> 34)
------------------------------
Additional (2): fi-icl-u2 fi-tgl-u2
Missing (7): fi-kbl-soraka bat-dg1-5 fi-bsw-cyan bat-adlp-4 fi-pnv-d510 fi-icl-y fi-bdw-samus
Known issues
------------
Here are the changes found in Patchwork_21556 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_cs_nop@fork-gfx0:
- fi-icl-u2: NOTRUN -> [SKIP][1] ([fdo#109315]) +17 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-icl-u2/igt@amdgpu/amd_cs_nop@fork-gfx0.html
* igt@core_hotunplug@unbind-rebind:
- fi-tgl-u2: NOTRUN -> [INCOMPLETE][2] ([i915#4006])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-tgl-u2/igt@core_hotunplug@unbind-rebind.html
* igt@gem_huc_copy@huc-copy:
- fi-tgl-u2: NOTRUN -> [SKIP][3] ([i915#2190])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-tgl-u2/igt@gem_huc_copy@huc-copy.html
- fi-icl-u2: NOTRUN -> [SKIP][4] ([i915#2190])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-icl-u2/igt@gem_huc_copy@huc-copy.html
* igt@kms_chamelium@dp-hpd-fast:
- fi-tgl-u2: NOTRUN -> [SKIP][5] ([fdo#109284] / [fdo#111827]) +8 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-tgl-u2/igt@kms_chamelium@dp-hpd-fast.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-icl-u2: NOTRUN -> [SKIP][6] ([fdo#111827]) +8 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-icl-u2/igt@kms_chamelium@hdmi-hpd-fast.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-tgl-u2: NOTRUN -> [SKIP][7] ([i915#4103]) +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-tgl-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- fi-icl-u2: NOTRUN -> [SKIP][8] ([fdo#109278]) +2 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-icl-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html
* igt@kms_force_connector_basic@force-load-detect:
- fi-tgl-u2: NOTRUN -> [SKIP][9] ([fdo#109285])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-tgl-u2/igt@kms_force_connector_basic@force-load-detect.html
- fi-icl-u2: NOTRUN -> [SKIP][10] ([fdo#109285])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-icl-u2/igt@kms_force_connector_basic@force-load-detect.html
* igt@prime_vgem@basic-userptr:
- fi-icl-u2: NOTRUN -> [SKIP][11] ([i915#3301])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-icl-u2/igt@prime_vgem@basic-userptr.html
- fi-tgl-u2: NOTRUN -> [SKIP][12] ([i915#3301])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-tgl-u2/igt@prime_vgem@basic-userptr.html
* igt@runner@aborted:
- fi-tgl-u2: NOTRUN -> [FAIL][13] ([i915#1602] / [i915#2722] / [i915#4312])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-tgl-u2/igt@runner@aborted.html
#### Possible fixes ####
* igt@kms_frontbuffer_tracking@basic:
- fi-cml-u2: [DMESG-WARN][14] ([i915#4269]) -> [PASS][15]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
- {fi-hsw-gt1}: [DMESG-WARN][16] ([i915#4290]) -> [PASS][17]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/fi-hsw-gt1/igt@kms_frontbuffer_tracking@basic.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/fi-hsw-gt1/igt@kms_frontbuffer_tracking@basic.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2722]: https://gitlab.freedesktop.org/drm/intel/issues/2722
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#4006]: https://gitlab.freedesktop.org/drm/intel/issues/4006
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4269]: https://gitlab.freedesktop.org/drm/intel/issues/4269
[i915#4290]: https://gitlab.freedesktop.org/drm/intel/issues/4290
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
Build changes
-------------
* Linux: CI_DRM_10863 -> Patchwork_21556
CI-20190529: 20190529
CI_DRM_10863: de2d87964c398bd4de93d264192e7f69928cf9c8 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6276: 955e0652ed6b1c8697e7ea5c35f86b232b4d5c32 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_21556: f81f77a16d9cf045506fa3f5760bdc774a82c901 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
f81f77a16d9c ALSA: hda: fix general protection fault in azx_runtime_idle
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/index.html
[-- Attachment #2: Type: text/html, Size: 7276 bytes --]
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for ALSA: hda: fix general protection fault in azx_runtime_idle
2021-11-10 21:03 ` Kai Vehmanen
` (3 preceding siblings ...)
(?)
@ 2021-11-10 23:45 ` Patchwork
-1 siblings, 0 replies; 26+ messages in thread
From: Patchwork @ 2021-11-10 23:45 UTC (permalink / raw)
To: Kai Vehmanen; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 30282 bytes --]
== Series Details ==
Series: ALSA: hda: fix general protection fault in azx_runtime_idle
URL : https://patchwork.freedesktop.org/series/96784/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10863_full -> Patchwork_21556_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_21556_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_21556_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_21556_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-pwrite:
- shard-iclb: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-iclb4/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-pwrite.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-iclb6/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-pwrite.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@kms_cursor_crc@pipe-a-cursor-64x64-random:
- {shard-rkl}: [SKIP][3] ([fdo#112022] / [i915#4070]) -> [SKIP][4] +21 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-rkl-2/igt@kms_cursor_crc@pipe-a-cursor-64x64-random.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-rkl-4/igt@kms_cursor_crc@pipe-a-cursor-64x64-random.html
* igt@kms_cursor_edge_walk@pipe-a-256x256-right-edge:
- {shard-rkl}: [SKIP][5] ([i915#1849] / [i915#4070]) -> [SKIP][6] +4 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-rkl-1/igt@kms_cursor_edge_walk@pipe-a-256x256-right-edge.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-rkl-4/igt@kms_cursor_edge_walk@pipe-a-256x256-right-edge.html
* igt@kms_draw_crc@fill-fb:
- {shard-rkl}: [SKIP][7] ([fdo#111314]) -> [SKIP][8] +6 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-rkl-1/igt@kms_draw_crc@fill-fb.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-rkl-4/igt@kms_draw_crc@fill-fb.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-indfb-msflip-blt:
- {shard-rkl}: NOTRUN -> [SKIP][9] +94 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-rkl-4/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-indfb-msflip-blt.html
* igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-indfb-draw-mmap-gtt:
- {shard-rkl}: [SKIP][10] ([i915#1849]) -> [SKIP][11] +55 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-rkl-1/igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-indfb-draw-mmap-gtt.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-rkl-4/igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-indfb-draw-mmap-gtt.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-basic:
- {shard-rkl}: [SKIP][12] ([i915#4070]) -> [SKIP][13] +4 similar issues
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-rkl-2/igt@kms_plane_alpha_blend@pipe-c-alpha-basic.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-rkl-4/igt@kms_plane_alpha_blend@pipe-c-alpha-basic.html
Known issues
------------
Here are the changes found in Patchwork_21556_full that come from known issues:
### CI changes ###
#### Issues hit ####
* boot:
- shard-snb: ([PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19], [PASS][20], [PASS][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], [FAIL][53], [PASS][54], [PASS][55], [PASS][56], [PASS][57], [PASS][58], [PASS][59], [PASS][60], [PASS][61], [PASS][62], [PASS][63]) ([i915#4338])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb4/boot.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb4/boot.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb4/boot.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb4/boot.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb2/boot.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb2/boot.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb2/boot.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb2/boot.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb2/boot.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb7/boot.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb7/boot.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb7/boot.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb7/boot.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb7/boot.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb6/boot.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb6/boot.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb6/boot.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb6/boot.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb6/boot.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb5/boot.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb5/boot.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb5/boot.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb5/boot.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb5/boot.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-snb5/boot.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb4/boot.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb7/boot.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb7/boot.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb7/boot.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb7/boot.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb7/boot.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb6/boot.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb6/boot.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb6/boot.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb6/boot.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb6/boot.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb5/boot.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb5/boot.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb5/boot.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb5/boot.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb5/boot.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb4/boot.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb4/boot.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb4/boot.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb4/boot.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb4/boot.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb2/boot.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb2/boot.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb2/boot.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-snb2/boot.html
#### Possible fixes ####
* boot:
- shard-glk: ([PASS][64], [PASS][65], [PASS][66], [PASS][67], [PASS][68], [PASS][69], [PASS][70], [PASS][71], [PASS][72], [PASS][73], [FAIL][74], [PASS][75], [PASS][76], [PASS][77], [PASS][78], [PASS][79], [PASS][80], [PASS][81], [PASS][82], [PASS][83], [PASS][84], [PASS][85], [PASS][86], [PASS][87], [PASS][88]) ([i915#4392]) -> ([PASS][89], [PASS][90], [PASS][91], [PASS][92], [PASS][93], [PASS][94], [PASS][95], [PASS][96], [PASS][97], [PASS][98], [PASS][99], [PASS][100], [PASS][101], [PASS][102], [PASS][103], [PASS][104], [PASS][105], [PASS][106], [PASS][107], [PASS][108], [PASS][109], [PASS][110], [PASS][111], [PASS][112], [PASS][113])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk6/boot.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk5/boot.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk5/boot.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk5/boot.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk4/boot.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk4/boot.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk4/boot.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk4/boot.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk3/boot.html
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk3/boot.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk3/boot.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk2/boot.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk2/boot.html
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk2/boot.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk1/boot.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk1/boot.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk9/boot.html
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk9/boot.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk9/boot.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk8/boot.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk8/boot.html
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk7/boot.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk7/boot.html
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk6/boot.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk6/boot.html
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk9/boot.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk9/boot.html
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk9/boot.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk8/boot.html
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk8/boot.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk8/boot.html
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk7/boot.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk7/boot.html
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk6/boot.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk6/boot.html
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk6/boot.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk5/boot.html
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk5/boot.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk4/boot.html
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk4/boot.html
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk4/boot.html
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk3/boot.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk3/boot.html
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk3/boot.html
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk2/boot.html
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk2/boot.html
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk2/boot.html
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk1/boot.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk1/boot.html
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk1/boot.html
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@preservation-s3@bcs0:
- shard-tglb: [PASS][114] -> [INCOMPLETE][115] ([i915#456])
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-tglb3/igt@gem_ctx_isolation@preservation-s3@bcs0.html
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-tglb7/igt@gem_ctx_isolation@preservation-s3@bcs0.html
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: [PASS][116] -> [FAIL][117] ([i915#2846])
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-kbl6/igt@gem_exec_fair@basic-deadline.html
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-kbl2/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none@rcs0:
- shard-kbl: [PASS][118] -> [FAIL][119] ([i915#2842]) +2 similar issues
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-kbl7/igt@gem_exec_fair@basic-none@rcs0.html
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-kbl7/igt@gem_exec_fair@basic-none@rcs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [PASS][120] -> [FAIL][121] ([i915#2842])
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-tglb2/igt@gem_exec_fair@basic-pace-share@rcs0.html
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-tglb2/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-iclb: [PASS][122] -> [FAIL][123] ([i915#2842])
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-iclb2/igt@gem_exec_fair@basic-pace@vecs0.html
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-iclb3/igt@gem_exec_fair@basic-pace@vecs0.html
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [PASS][124] -> [FAIL][125] ([i915#2849])
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-iclb6/igt@gem_exec_fair@basic-throttle@rcs0.html
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-iclb8/igt@gem_exec_fair@basic-throttle@rcs0.html
* igt@gem_exec_suspend@basic-s3:
- shard-kbl: [PASS][126] -> [DMESG-WARN][127] ([i915#180]) +3 similar issues
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-kbl3/igt@gem_exec_suspend@basic-s3.html
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-kbl1/igt@gem_exec_suspend@basic-s3.html
* igt@gem_pread@exhaustion:
- shard-glk: NOTRUN -> [WARN][128] ([i915#2658])
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk5/igt@gem_pread@exhaustion.html
* igt@gem_pwrite@basic-exhaustion:
- shard-skl: NOTRUN -> [WARN][129] ([i915#2658])
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-skl6/igt@gem_pwrite@basic-exhaustion.html
* igt@gem_pxp@verify-pxp-stale-ctx-execution:
- shard-tglb: NOTRUN -> [SKIP][130] ([i915#4270])
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-tglb6/igt@gem_pxp@verify-pxp-stale-ctx-execution.html
* igt@gen9_exec_parse@unaligned-jump:
- shard-tglb: NOTRUN -> [SKIP][131] ([i915#2856]) +1 similar issue
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-tglb6/igt@gen9_exec_parse@unaligned-jump.html
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [PASS][132] -> [FAIL][133] ([i915#454])
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-iclb5/igt@i915_pm_dc@dc6-psr.html
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-iclb4/igt@i915_pm_dc@dc6-psr.html
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip:
- shard-kbl: NOTRUN -> [SKIP][134] ([fdo#109271] / [i915#3777]) +1 similar issue
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-kbl7/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip.html
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-hflip:
- shard-glk: NOTRUN -> [SKIP][135] ([fdo#109271] / [i915#3777])
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk5/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-hflip.html
* igt@kms_ccs@pipe-a-bad-rotation-90-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][136] ([fdo#109271] / [i915#3886]) +2 similar issues
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-apl8/igt@kms_ccs@pipe-a-bad-rotation-90-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc:
- shard-glk: NOTRUN -> [SKIP][137] ([fdo#109271] / [i915#3886]) +2 similar issues
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk5/igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][138] ([fdo#109271] / [i915#3886]) +6 similar issues
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-skl6/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-bad-pixel-format-y_tiled_gen12_rc_ccs_cc:
- shard-kbl: NOTRUN -> [SKIP][139] ([fdo#109271] / [i915#3886]) +5 similar issues
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-kbl1/igt@kms_ccs@pipe-c-bad-pixel-format-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-bad-rotation-90-yf_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][140] ([i915#3689]) +3 similar issues
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-tglb6/igt@kms_ccs@pipe-c-bad-rotation-90-yf_tiled_ccs.html
* igt@kms_cdclk@mode-transition:
- shard-apl: NOTRUN -> [SKIP][141] ([fdo#109271]) +84 similar issues
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-apl7/igt@kms_cdclk@mode-transition.html
* igt@kms_chamelium@common-hpd-after-suspend:
- shard-glk: NOTRUN -> [SKIP][142] ([fdo#109271] / [fdo#111827]) +5 similar issues
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk5/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_chamelium@hdmi-crc-nonplanar-formats:
- shard-kbl: NOTRUN -> [SKIP][143] ([fdo#109271] / [fdo#111827]) +8 similar issues
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-kbl1/igt@kms_chamelium@hdmi-crc-nonplanar-formats.html
* igt@kms_chamelium@vga-hpd:
- shard-apl: NOTRUN -> [SKIP][144] ([fdo#109271] / [fdo#111827]) +6 similar issues
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-apl8/igt@kms_chamelium@vga-hpd.html
* igt@kms_color_chamelium@pipe-c-ctm-0-25:
- shard-skl: NOTRUN -> [SKIP][145] ([fdo#109271] / [fdo#111827]) +7 similar issues
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-skl6/igt@kms_color_chamelium@pipe-c-ctm-0-25.html
* igt@kms_color_chamelium@pipe-c-ctm-red-to-blue:
- shard-tglb: NOTRUN -> [SKIP][146] ([fdo#109284] / [fdo#111827]) +1 similar issue
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-tglb5/igt@kms_color_chamelium@pipe-c-ctm-red-to-blue.html
* igt@kms_content_protection@lic:
- shard-kbl: NOTRUN -> [TIMEOUT][147] ([i915#1319])
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-kbl7/igt@kms_content_protection@lic.html
* igt@kms_content_protection@mei_interface:
- shard-tglb: NOTRUN -> [SKIP][148] ([fdo#111828])
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-tglb5/igt@kms_content_protection@mei_interface.html
* igt@kms_cursor_crc@pipe-c-cursor-32x10-rapid-movement:
- shard-tglb: NOTRUN -> [SKIP][149] ([i915#3359]) +1 similar issue
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-tglb5/igt@kms_cursor_crc@pipe-c-cursor-32x10-rapid-movement.html
* igt@kms_cursor_crc@pipe-d-cursor-256x256-random:
- shard-glk: NOTRUN -> [SKIP][150] ([fdo#109271]) +38 similar issues
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk5/igt@kms_cursor_crc@pipe-d-cursor-256x256-random.html
* igt@kms_cursor_crc@pipe-d-cursor-32x32-random:
- shard-tglb: NOTRUN -> [SKIP][151] ([i915#3319])
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-tglb5/igt@kms_cursor_crc@pipe-d-cursor-32x32-random.html
* igt@kms_cursor_edge_walk@pipe-d-64x64-left-edge:
- shard-kbl: NOTRUN -> [SKIP][152] ([fdo#109271]) +92 similar issues
[152]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-kbl7/igt@kms_cursor_edge_walk@pipe-d-64x64-left-edge.html
* igt@kms_cursor_legacy@pipe-d-single-bo:
- shard-apl: NOTRUN -> [SKIP][153] ([fdo#109271] / [i915#533]) +1 similar issue
[153]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-apl8/igt@kms_cursor_legacy@pipe-d-single-bo.html
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-apl: [PASS][154] -> [INCOMPLETE][155] ([i915#180] / [i915#1982])
[154]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-apl7/igt@kms_fbcon_fbt@fbc-suspend.html
[155]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-apl4/igt@kms_fbcon_fbt@fbc-suspend.html
* igt@kms_flip@2x-plain-flip-ts-check-interruptible@ab-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][156] -> [FAIL][157] ([i915#2122])
[156]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-glk9/igt@kms_flip@2x-plain-flip-ts-check-interruptible@ab-hdmi-a1-hdmi-a2.html
[157]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk3/igt@kms_flip@2x-plain-flip-ts-check-interruptible@ab-hdmi-a1-hdmi-a2.html
* igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1:
- shard-skl: [PASS][158] -> [FAIL][159] ([i915#2122])
[158]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-skl2/igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1.html
[159]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-skl9/igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile:
- shard-iclb: [PASS][160] -> [SKIP][161] ([i915#3701])
[160]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-iclb7/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile.html
[161]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs:
- shard-skl: NOTRUN -> [SKIP][162] ([fdo#109271] / [i915#2672])
[162]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-skl6/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs.html
* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-blt:
- shard-skl: NOTRUN -> [SKIP][163] ([fdo#109271]) +123 similar issues
[163]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-skl1/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@fbcpsr-suspend:
- shard-tglb: [PASS][164] -> [INCOMPLETE][165] ([i915#2411] / [i915#456])
[164]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-tglb8/igt@kms_frontbuffer_tracking@fbcpsr-suspend.html
[165]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-tglb7/igt@kms_frontbuffer_tracking@fbcpsr-suspend.html
* igt@kms_frontbuffer_tracking@psr-2p-primscrn-cur-indfb-move:
- shard-tglb: NOTRUN -> [SKIP][166] ([fdo#111825]) +7 similar issues
[166]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-tglb5/igt@kms_frontbuffer_tracking@psr-2p-primscrn-cur-indfb-move.html
* igt@kms_frontbuffer_tracking@psr-suspend:
- shard-skl: [PASS][167] -> [INCOMPLETE][168] ([i915#123])
[167]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-skl9/igt@kms_frontbuffer_tracking@psr-suspend.html
[168]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-skl9/igt@kms_frontbuffer_tracking@psr-suspend.html
* igt@kms_pipe_crc_basic@nonblocking-crc-pipe-d-frame-sequence:
- shard-kbl: NOTRUN -> [SKIP][169] ([fdo#109271] / [i915#533])
[169]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-kbl1/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-d-frame-sequence.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-basic:
- shard-glk: NOTRUN -> [FAIL][170] ([fdo#108145] / [i915#265])
[170]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk5/igt@kms_plane_alpha_blend@pipe-a-alpha-basic.html
* igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:
- shard-skl: NOTRUN -> [FAIL][171] ([fdo#108145] / [i915#265])
[171]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-skl6/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-basic:
- shard-kbl: NOTRUN -> [FAIL][172] ([fdo#108145] / [i915#265])
[172]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-kbl1/igt@kms_plane_alpha_blend@pipe-c-alpha-basic.html
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [PASS][173] -> [FAIL][174] ([fdo#108145] / [i915#265]) +3 similar issues
[173]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-skl9/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html
[174]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-skl8/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html
* igt@kms_prop_blob@blob-prop-lifetime:
- shard-skl: [PASS][175] -> [DMESG-WARN][176] ([i915#1982])
[175]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-skl6/igt@kms_prop_blob@blob-prop-lifetime.html
[176]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-skl1/igt@kms_prop_blob@blob-prop-lifetime.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-1:
- shard-apl: NOTRUN -> [SKIP][177] ([fdo#109271] / [i915#658]) +2 similar issues
[177]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-apl3/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-1.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4:
- shard-skl: NOTRUN -> [SKIP][178] ([fdo#109271] / [i915#658]) +2 similar issues
[178]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-skl6/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-5:
- shard-glk: NOTRUN -> [SKIP][179] ([fdo#109271] / [i915#658]) +1 similar issue
[179]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-glk5/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-5.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-4:
- shard-kbl: NOTRUN -> [SKIP][180] ([fdo#109271] / [i915#658]) +2 similar issues
[180]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-kbl1/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-4.html
* igt@kms_psr2_su@page_flip:
- shard-tglb: NOTRUN -> [SKIP][181] ([i915#1911])
[181]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-tglb5/igt@kms_psr2_su@page_flip.html
* igt@kms_psr@psr2_cursor_blt:
- shard-iclb: [PASS][182] -> [SKIP][183] ([fdo#109441]) +4 similar issues
[182]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10863/shard-iclb2/igt@kms_psr@psr2_cursor_blt.html
[183]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-iclb5/igt@kms_psr@psr2_cursor_blt.html
* igt@kms_vblank@pipe-d-wait-idle:
- shard-skl: NOTRUN -> [SKIP][184] ([fdo#109271] / [i915#533]) +1 similar issue
[184]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-skl6/igt@kms_vblank@pipe-d-wait-idle.html
* igt@prime_nv_api@i915_nv_import_twice_check_flink_name:
- shard-tglb: NOTRUN -> [SKIP][185] ([fdo#109291]) +1 similar issue
[185]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/shard-tglb6/igt@prim
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21556/index.html
[-- Attachment #2: Type: text/html, Size: 32845 bytes --]
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [Intel-gfx] [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
2021-11-10 22:15 ` Kai Vehmanen
@ 2021-11-11 13:29 ` Takashi Iwai
-1 siblings, 0 replies; 26+ messages in thread
From: Takashi Iwai @ 2021-11-11 13:29 UTC (permalink / raw)
To: Kai Vehmanen; +Cc: alsa-devel, intel-gfx
On Wed, 10 Nov 2021 23:15:40 +0100,
Kai Vehmanen wrote:
>
> Hey,
>
> On Wed, 10 Nov 2021, Takashi Iwai wrote:
>
> > On Wed, 10 Nov 2021 22:03:07 +0100, Kai Vehmanen wrote:
> > > Fix a corner case between PCI device driver remove callback and
> > > runtime PM idle callback.
> [...]
> > > Some non-persistent direct links showing the bug trigger on
> > > different platforms with linux-next 20211109:
> > > - https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-tgl-1115g4/igt@i915_module_load@reload.html
> > > - https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-jsl-1/igt@i915_module_load@reload.html
> > >
> > > Notably with 20211110 linux-next, the bug does not trigger:
> > > - https://intel-gfx-ci.01.org/tree/linux-next/next-20211110/fi-tgl-1115g4/igt@i915_module_load@reload.html
> >
> > Is this the case with CONFIG_DEBUG_KOBJECT_RELEASE?
> > This would be the only logical explanation I can think of for now.
>
> hmm, that doesn't seem to be used. Here's a link to kconfig used in the
> failing CI run:
> https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/kconfig.txt
OK, then it's not due to the delayed release, but the cause should be
the same, I suppose.
> It's still a bit odd, especially given Scott just reported the other HDA
> related regression in 5.15 today. The two issues don't seem to be related
> though, although both are fixed by clearing drvdata (but in different
> places of hda_intel.c).
I don't think it's the same issue, rather a coincidence of the
timing. There have been many changes in 5.15, after all :)
> I'll try to run some more tests tomorrow. The fix should be good in any
> case, but it would be interesting to understand better what change made
> this more (?) likely to hit than before. This is not a new test and the
> problem happens on fairly old platforms, so something has changed.
A potential problem with the current code is that it doesn't disable
the runtime PM at the release procedure. Could you try the patch
below? You can put WARN_ON(!chip) at azx_runtime_idle(), too, for
catching the invalid runtime call.
thanks,
Takashi
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -1347,8 +1347,13 @@ static void azx_free(struct azx *chip)
if (hda->freed)
return;
- if (azx_has_pm_runtime(chip) && chip->running)
+ if (azx_has_pm_runtime(chip) && chip->running) {
pm_runtime_get_noresume(&pci->dev);
+ pm_runtime_forbid(&pci->dev);
+ pm_runtime_dont_use_autosuspend(&pci->dev);
+ pm_runtime_disable(&pci->dev);
+ }
+
chip->running = 0;
azx_del_card_list(chip);
@@ -2320,6 +2325,7 @@ static int azx_probe_continue(struct azx *chip)
set_default_power_save(chip);
if (azx_has_pm_runtime(chip)) {
+ pm_runtime_enable(&pci->dev);
pm_runtime_use_autosuspend(&pci->dev);
pm_runtime_allow(&pci->dev);
pm_runtime_put_autosuspend(&pci->dev);
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
@ 2021-11-11 13:29 ` Takashi Iwai
0 siblings, 0 replies; 26+ messages in thread
From: Takashi Iwai @ 2021-11-11 13:29 UTC (permalink / raw)
To: Kai Vehmanen; +Cc: alsa-devel, intel-gfx, mahesh.meena
On Wed, 10 Nov 2021 23:15:40 +0100,
Kai Vehmanen wrote:
>
> Hey,
>
> On Wed, 10 Nov 2021, Takashi Iwai wrote:
>
> > On Wed, 10 Nov 2021 22:03:07 +0100, Kai Vehmanen wrote:
> > > Fix a corner case between PCI device driver remove callback and
> > > runtime PM idle callback.
> [...]
> > > Some non-persistent direct links showing the bug trigger on
> > > different platforms with linux-next 20211109:
> > > - https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-tgl-1115g4/igt@i915_module_load@reload.html
> > > - https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-jsl-1/igt@i915_module_load@reload.html
> > >
> > > Notably with 20211110 linux-next, the bug does not trigger:
> > > - https://intel-gfx-ci.01.org/tree/linux-next/next-20211110/fi-tgl-1115g4/igt@i915_module_load@reload.html
> >
> > Is this the case with CONFIG_DEBUG_KOBJECT_RELEASE?
> > This would be the only logical explanation I can think of for now.
>
> hmm, that doesn't seem to be used. Here's a link to kconfig used in the
> failing CI run:
> https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/kconfig.txt
OK, then it's not due to the delayed release, but the cause should be
the same, I suppose.
> It's still a bit odd, especially given Scott just reported the other HDA
> related regression in 5.15 today. The two issues don't seem to be related
> though, although both are fixed by clearing drvdata (but in different
> places of hda_intel.c).
I don't think it's the same issue, rather a coincidence of the
timing. There have been many changes in 5.15, after all :)
> I'll try to run some more tests tomorrow. The fix should be good in any
> case, but it would be interesting to understand better what change made
> this more (?) likely to hit than before. This is not a new test and the
> problem happens on fairly old platforms, so something has changed.
A potential problem with the current code is that it doesn't disable
the runtime PM at the release procedure. Could you try the patch
below? You can put WARN_ON(!chip) at azx_runtime_idle(), too, for
catching the invalid runtime call.
thanks,
Takashi
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -1347,8 +1347,13 @@ static void azx_free(struct azx *chip)
if (hda->freed)
return;
- if (azx_has_pm_runtime(chip) && chip->running)
+ if (azx_has_pm_runtime(chip) && chip->running) {
pm_runtime_get_noresume(&pci->dev);
+ pm_runtime_forbid(&pci->dev);
+ pm_runtime_dont_use_autosuspend(&pci->dev);
+ pm_runtime_disable(&pci->dev);
+ }
+
chip->running = 0;
azx_del_card_list(chip);
@@ -2320,6 +2325,7 @@ static int azx_probe_continue(struct azx *chip)
set_default_power_save(chip);
if (azx_has_pm_runtime(chip)) {
+ pm_runtime_enable(&pci->dev);
pm_runtime_use_autosuspend(&pci->dev);
pm_runtime_allow(&pci->dev);
pm_runtime_put_autosuspend(&pci->dev);
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for ALSA: hda: fix general protection fault in azx_runtime_idle (rev2)
2021-11-10 21:03 ` Kai Vehmanen
` (4 preceding siblings ...)
(?)
@ 2021-11-11 15:33 ` Patchwork
-1 siblings, 0 replies; 26+ messages in thread
From: Patchwork @ 2021-11-11 15:33 UTC (permalink / raw)
To: Takashi Iwai; +Cc: intel-gfx
== Series Details ==
Series: ALSA: hda: fix general protection fault in azx_runtime_idle (rev2)
URL : https://patchwork.freedesktop.org/series/96784/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
791aebc9d846 ALSA: hda: fix general protection fault in azx_runtime_idle
-:19: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#19:
> > > - https://intel-gfx-ci.01.org/tree/linux-next/next-20211109/fi-tgl-1115g4/igt@i915_module_load@reload.html
-:83: ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 1 errors, 1 warnings, 0 checks, 21 lines checked
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Intel-gfx] ✗ Fi.CI.DOCS: warning for ALSA: hda: fix general protection fault in azx_runtime_idle (rev2)
2021-11-10 21:03 ` Kai Vehmanen
` (5 preceding siblings ...)
(?)
@ 2021-11-11 15:37 ` Patchwork
-1 siblings, 0 replies; 26+ messages in thread
From: Patchwork @ 2021-11-11 15:37 UTC (permalink / raw)
To: Takashi Iwai; +Cc: intel-gfx
== Series Details ==
Series: ALSA: hda: fix general protection fault in azx_runtime_idle (rev2)
URL : https://patchwork.freedesktop.org/series/96784/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
./drivers/gpu/drm/i915/display/intel_fbc.c:635: warning: Excess function parameter 'i915' description in 'intel_fbc_is_active'
./drivers/gpu/drm/i915/display/intel_fbc.c:1638: warning: Excess function parameter 'i915' description in 'intel_fbc_handle_fifo_underrun_irq'
./drivers/gpu/drm/i915/display/intel_fbc.c:635: warning: Function parameter or member 'fbc' not described in 'intel_fbc_is_active'
./drivers/gpu/drm/i915/display/intel_fbc.c:635: warning: Excess function parameter 'i915' description in 'intel_fbc_is_active'
./drivers/gpu/drm/i915/display/intel_fbc.c:1638: warning: Function parameter or member 'fbc' not described in 'intel_fbc_handle_fifo_underrun_irq'
./drivers/gpu/drm/i915/display/intel_fbc.c:1638: warning: Excess function parameter 'i915' description in 'intel_fbc_handle_fifo_underrun_irq'
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Intel-gfx] ✗ Fi.CI.BAT: failure for ALSA: hda: fix general protection fault in azx_runtime_idle (rev2)
2021-11-10 21:03 ` Kai Vehmanen
` (6 preceding siblings ...)
(?)
@ 2021-11-11 16:01 ` Patchwork
-1 siblings, 0 replies; 26+ messages in thread
From: Patchwork @ 2021-11-11 16:01 UTC (permalink / raw)
To: Takashi Iwai; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 13658 bytes --]
== Series Details ==
Series: ALSA: hda: fix general protection fault in azx_runtime_idle (rev2)
URL : https://patchwork.freedesktop.org/series/96784/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10870 -> Patchwork_21563
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_21563 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_21563, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/index.html
Participating hosts (35 -> 32)
------------------------------
Additional (2): fi-blb-e6850 fi-apl-guc
Missing (5): bat-dg1-6 bat-dg1-5 fi-bsw-cyan fi-icl-u2 bat-adlp-4
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_21563:
### IGT changes ###
#### Possible regressions ####
* igt@core_hotunplug@unbind-rebind:
- fi-hsw-4770: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-hsw-4770/igt@core_hotunplug@unbind-rebind.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-hsw-4770/igt@core_hotunplug@unbind-rebind.html
- fi-bdw-5557u: [PASS][3] -> [DMESG-WARN][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-bdw-5557u/igt@core_hotunplug@unbind-rebind.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-bdw-5557u/igt@core_hotunplug@unbind-rebind.html
* igt@i915_module_load@reload:
- fi-cml-u2: [PASS][5] -> [DMESG-WARN][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-cml-u2/igt@i915_module_load@reload.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-cml-u2/igt@i915_module_load@reload.html
- fi-skl-6700k2: [PASS][7] -> [DMESG-WARN][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-skl-6700k2/igt@i915_module_load@reload.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-skl-6700k2/igt@i915_module_load@reload.html
- fi-bsw-kefka: [PASS][9] -> [DMESG-WARN][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-bsw-kefka/igt@i915_module_load@reload.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-bsw-kefka/igt@i915_module_load@reload.html
- fi-bsw-nick: [PASS][11] -> [DMESG-WARN][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-bsw-nick/igt@i915_module_load@reload.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-bsw-nick/igt@i915_module_load@reload.html
* igt@i915_pm_rpm@module-reload:
- fi-cfl-8109u: [PASS][13] -> [DMESG-WARN][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-cfl-8109u/igt@i915_pm_rpm@module-reload.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-cfl-8109u/igt@i915_pm_rpm@module-reload.html
- fi-cfl-8700k: [PASS][15] -> [DMESG-WARN][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-cfl-8700k/igt@i915_pm_rpm@module-reload.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-cfl-8700k/igt@i915_pm_rpm@module-reload.html
- fi-rkl-11600: [PASS][17] -> [DMESG-WARN][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-rkl-11600/igt@i915_pm_rpm@module-reload.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-rkl-11600/igt@i915_pm_rpm@module-reload.html
- fi-skl-guc: [PASS][19] -> [DMESG-WARN][20]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-skl-guc/igt@i915_pm_rpm@module-reload.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-skl-guc/igt@i915_pm_rpm@module-reload.html
- fi-kbl-7567u: [PASS][21] -> [DMESG-WARN][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-kbl-7567u/igt@i915_pm_rpm@module-reload.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-kbl-7567u/igt@i915_pm_rpm@module-reload.html
- fi-cfl-guc: [PASS][23] -> [DMESG-WARN][24]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-cfl-guc/igt@i915_pm_rpm@module-reload.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-cfl-guc/igt@i915_pm_rpm@module-reload.html
- fi-rkl-guc: [PASS][25] -> [DMESG-WARN][26]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-rkl-guc/igt@i915_pm_rpm@module-reload.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-rkl-guc/igt@i915_pm_rpm@module-reload.html
- fi-kbl-guc: [PASS][27] -> [FAIL][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-kbl-guc/igt@i915_pm_rpm@module-reload.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-kbl-guc/igt@i915_pm_rpm@module-reload.html
- fi-kbl-7500u: [PASS][29] -> [DMESG-WARN][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-kbl-7500u/igt@i915_pm_rpm@module-reload.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-kbl-7500u/igt@i915_pm_rpm@module-reload.html
- fi-glk-dsi: [PASS][31] -> [DMESG-WARN][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-glk-dsi/igt@i915_pm_rpm@module-reload.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-glk-dsi/igt@i915_pm_rpm@module-reload.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@core_hotunplug@unbind-rebind:
- {fi-hsw-gt1}: [PASS][33] -> [DMESG-WARN][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-hsw-gt1/igt@core_hotunplug@unbind-rebind.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-hsw-gt1/igt@core_hotunplug@unbind-rebind.html
* igt@i915_pm_rpm@module-reload:
- {fi-jsl-1}: [PASS][35] -> [FAIL][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-jsl-1/igt@i915_pm_rpm@module-reload.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-jsl-1/igt@i915_pm_rpm@module-reload.html
Known issues
------------
Here are the changes found in Patchwork_21563 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_fence@basic-busy@bcs0:
- fi-apl-guc: NOTRUN -> [SKIP][37] ([fdo#109271]) +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-apl-guc/igt@gem_exec_fence@basic-busy@bcs0.html
* igt@i915_hangman@error-state-basic:
- fi-apl-guc: NOTRUN -> [DMESG-WARN][38] ([i915#1610])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-apl-guc/igt@i915_hangman@error-state-basic.html
* igt@i915_pm_rpm@module-reload:
- fi-skl-6600u: [PASS][39] -> [INCOMPLETE][40] ([i915#151])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-skl-6600u/igt@i915_pm_rpm@module-reload.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-skl-6600u/igt@i915_pm_rpm@module-reload.html
- fi-kbl-8809g: [PASS][41] -> [INCOMPLETE][42] ([i915#151])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-kbl-8809g/igt@i915_pm_rpm@module-reload.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-kbl-8809g/igt@i915_pm_rpm@module-reload.html
* igt@kms_frontbuffer_tracking@basic:
- fi-cml-u2: [PASS][43] -> [DMESG-WARN][44] ([i915#4269])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10870/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-blb-e6850: NOTRUN -> [SKIP][45] ([fdo#109271]) +53 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-blb-e6850/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
* igt@runner@aborted:
- fi-rkl-11600: NOTRUN -> [FAIL][46] ([i915#4312])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-rkl-11600/igt@runner@aborted.html
- fi-bsw-kefka: NOTRUN -> [FAIL][47] ([i915#4312])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-bsw-kefka/igt@runner@aborted.html
- fi-cfl-8700k: NOTRUN -> [FAIL][48] ([fdo#109271] / [i915#1814] / [i915#3363] / [i915#4312])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-cfl-8700k/igt@runner@aborted.html
- fi-skl-6600u: NOTRUN -> [FAIL][49] ([i915#1814] / [i915#3363] / [i915#4312])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-skl-6600u/igt@runner@aborted.html
- fi-cfl-8109u: NOTRUN -> [FAIL][50] ([fdo#109271] / [i915#1814] / [i915#3363] / [i915#4312])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-cfl-8109u/igt@runner@aborted.html
- fi-glk-dsi: NOTRUN -> [FAIL][51] ([i915#1814] / [i915#3363] / [i915#4312] / [k.org#202321])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-glk-dsi/igt@runner@aborted.html
- fi-bsw-nick: NOTRUN -> [FAIL][52] ([i915#4312])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-bsw-nick/igt@runner@aborted.html
- fi-kbl-8809g: NOTRUN -> [FAIL][53] ([fdo#109271] / [i915#1814] / [i915#3363] / [i915#4312])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-kbl-8809g/igt@runner@aborted.html
- fi-apl-guc: NOTRUN -> [FAIL][54] ([i915#2426] / [i915#3363] / [i915#4312])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-apl-guc/igt@runner@aborted.html
- fi-bdw-5557u: NOTRUN -> [FAIL][55] ([i915#1602] / [i915#4312])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-bdw-5557u/igt@runner@aborted.html
- fi-kbl-soraka: NOTRUN -> [FAIL][56] ([i915#3363] / [i915#4312])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-kbl-soraka/igt@runner@aborted.html
- fi-hsw-4770: NOTRUN -> [FAIL][57] ([i915#2283] / [i915#4312])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-hsw-4770/igt@runner@aborted.html
- fi-kbl-7500u: NOTRUN -> [FAIL][58] ([fdo#109271] / [i915#1814] / [i915#3363] / [i915#4312])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-kbl-7500u/igt@runner@aborted.html
- fi-kbl-guc: NOTRUN -> [FAIL][59] ([fdo#109271] / [i915#1814] / [i915#3363] / [i915#4312])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-kbl-guc/igt@runner@aborted.html
- fi-cml-u2: NOTRUN -> [FAIL][60] ([i915#3363] / [i915#4312])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-cml-u2/igt@runner@aborted.html
- fi-rkl-guc: NOTRUN -> [FAIL][61] ([i915#4312])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-rkl-guc/igt@runner@aborted.html
- fi-cfl-guc: NOTRUN -> [FAIL][62] ([fdo#109271] / [i915#1814] / [i915#3363] / [i915#4312])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-cfl-guc/igt@runner@aborted.html
- fi-kbl-7567u: NOTRUN -> [FAIL][63] ([fdo#109271] / [i915#1814] / [i915#3363] / [i915#4312])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-kbl-7567u/igt@runner@aborted.html
- fi-skl-guc: NOTRUN -> [FAIL][64] ([i915#1814] / [i915#3363] / [i915#4312])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-skl-guc/igt@runner@aborted.html
- fi-skl-6700k2: NOTRUN -> [FAIL][65] ([i915#3363] / [i915#4312])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/fi-skl-6700k2/igt@runner@aborted.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#151]: https://gitlab.freedesktop.org/drm/intel/issues/151
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#1610]: https://gitlab.freedesktop.org/drm/intel/issues/1610
[i915#1814]: https://gitlab.freedesktop.org/drm/intel/issues/1814
[i915#2283]: https://gitlab.freedesktop.org/drm/intel/issues/2283
[i915#2426]: https://gitlab.freedesktop.org/drm/intel/issues/2426
[i915#3363]: https://gitlab.freedesktop.org/drm/intel/issues/3363
[i915#4269]: https://gitlab.freedesktop.org/drm/intel/issues/4269
[i915#4290]: https://gitlab.freedesktop.org/drm/intel/issues/4290
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[k.org#202321]: https://bugzilla.kernel.org/show_bug.cgi?id=202321
Build changes
-------------
* Linux: CI_DRM_10870 -> Patchwork_21563
CI-20190529: 20190529
CI_DRM_10870: 7916d1933c95f1bacacb6bcb33b81f5d643218c2 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6277: 7201d343fced07a1951feea119480d55bce787e4 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_21563: 791aebc9d8462ad2456276f71746b44b47db975a @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
791aebc9d846 ALSA: hda: fix general protection fault in azx_runtime_idle
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21563/index.html
[-- Attachment #2: Type: text/html, Size: 18241 bytes --]
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [Intel-gfx] [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
2021-11-11 13:29 ` Takashi Iwai
@ 2021-11-11 17:39 ` Kai Vehmanen
-1 siblings, 0 replies; 26+ messages in thread
From: Kai Vehmanen @ 2021-11-11 17:39 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel, intel-gfx
Hi,
On Thu, 11 Nov 2021, Takashi Iwai wrote:
> A potential problem with the current code is that it doesn't disable
> the runtime PM at the release procedure. Could you try the patch
> below? You can put WARN_ON(!chip) at azx_runtime_idle(), too, for
> catching the invalid runtime call.
[...]
> --- a/sound/pci/hda/hda_intel.c
> +++ b/sound/pci/hda/hda_intel.c
> @@ -1347,8 +1347,13 @@ static void azx_free(struct azx *chip)
> if (hda->freed)
> return;
>
> - if (azx_has_pm_runtime(chip) && chip->running)
> + if (azx_has_pm_runtime(chip) && chip->running) {
> pm_runtime_get_noresume(&pci->dev);
> + pm_runtime_forbid(&pci->dev);
> + pm_runtime_dont_use_autosuspend(&pci->dev);
> + pm_runtime_disable(&pci->dev);
> + }
> +
> chip->running = 0;
Tested with next-20211019 (first next tag where I've seen test failures)
and your patch, and this seems to do the trick. I didn't have my drvdata
patch included when I ran the test. No rpm_idle() calls
anymore after azx_remove(), so the bug is not hit.
> azx_del_card_list(chip);
> @@ -2320,6 +2325,7 @@ static int azx_probe_continue(struct azx *chip)
> set_default_power_save(chip);
>
> if (azx_has_pm_runtime(chip)) {
> + pm_runtime_enable(&pci->dev);
> pm_runtime_use_autosuspend(&pci->dev);
This does generate warnings
[ 13.495059] snd_hda_intel 0000:00:1f.3: Unbalanced pm_runtime_enable!
And later
[ 54.770701] Enabling runtime PM for inactive device (0000:00:1f.3) with active children
[ 54.770718] WARNING: CPU: 0 PID: 10 at drivers/base/power/runtime.c:1439 pm_runtime_enable+0x98/0xb0
Adding a "pm_runtime_set_active(&pci->dev)" to both azx_free() and
azx_probe_continue() seems to help and fix still works.
Br, Kai
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
@ 2021-11-11 17:39 ` Kai Vehmanen
0 siblings, 0 replies; 26+ messages in thread
From: Kai Vehmanen @ 2021-11-11 17:39 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel, intel-gfx, Kai Vehmanen, mahesh.meena
Hi,
On Thu, 11 Nov 2021, Takashi Iwai wrote:
> A potential problem with the current code is that it doesn't disable
> the runtime PM at the release procedure. Could you try the patch
> below? You can put WARN_ON(!chip) at azx_runtime_idle(), too, for
> catching the invalid runtime call.
[...]
> --- a/sound/pci/hda/hda_intel.c
> +++ b/sound/pci/hda/hda_intel.c
> @@ -1347,8 +1347,13 @@ static void azx_free(struct azx *chip)
> if (hda->freed)
> return;
>
> - if (azx_has_pm_runtime(chip) && chip->running)
> + if (azx_has_pm_runtime(chip) && chip->running) {
> pm_runtime_get_noresume(&pci->dev);
> + pm_runtime_forbid(&pci->dev);
> + pm_runtime_dont_use_autosuspend(&pci->dev);
> + pm_runtime_disable(&pci->dev);
> + }
> +
> chip->running = 0;
Tested with next-20211019 (first next tag where I've seen test failures)
and your patch, and this seems to do the trick. I didn't have my drvdata
patch included when I ran the test. No rpm_idle() calls
anymore after azx_remove(), so the bug is not hit.
> azx_del_card_list(chip);
> @@ -2320,6 +2325,7 @@ static int azx_probe_continue(struct azx *chip)
> set_default_power_save(chip);
>
> if (azx_has_pm_runtime(chip)) {
> + pm_runtime_enable(&pci->dev);
> pm_runtime_use_autosuspend(&pci->dev);
This does generate warnings
[ 13.495059] snd_hda_intel 0000:00:1f.3: Unbalanced pm_runtime_enable!
And later
[ 54.770701] Enabling runtime PM for inactive device (0000:00:1f.3) with active children
[ 54.770718] WARNING: CPU: 0 PID: 10 at drivers/base/power/runtime.c:1439 pm_runtime_enable+0x98/0xb0
Adding a "pm_runtime_set_active(&pci->dev)" to both azx_free() and
azx_probe_continue() seems to help and fix still works.
Br, Kai
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [Intel-gfx] [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
2021-11-11 17:39 ` Kai Vehmanen
@ 2021-11-12 10:02 ` Takashi Iwai
-1 siblings, 0 replies; 26+ messages in thread
From: Takashi Iwai @ 2021-11-12 10:02 UTC (permalink / raw)
To: Kai Vehmanen; +Cc: alsa-devel, intel-gfx
On Thu, 11 Nov 2021 18:39:36 +0100,
Kai Vehmanen wrote:
>
> Hi,
>
> On Thu, 11 Nov 2021, Takashi Iwai wrote:
>
> > A potential problem with the current code is that it doesn't disable
> > the runtime PM at the release procedure. Could you try the patch
> > below? You can put WARN_ON(!chip) at azx_runtime_idle(), too, for
> > catching the invalid runtime call.
> [...]
> > --- a/sound/pci/hda/hda_intel.c
> > +++ b/sound/pci/hda/hda_intel.c
> > @@ -1347,8 +1347,13 @@ static void azx_free(struct azx *chip)
> > if (hda->freed)
> > return;
> >
> > - if (azx_has_pm_runtime(chip) && chip->running)
> > + if (azx_has_pm_runtime(chip) && chip->running) {
> > pm_runtime_get_noresume(&pci->dev);
> > + pm_runtime_forbid(&pci->dev);
> > + pm_runtime_dont_use_autosuspend(&pci->dev);
> > + pm_runtime_disable(&pci->dev);
> > + }
> > +
> > chip->running = 0;
>
> Tested with next-20211019 (first next tag where I've seen test failures)
> and your patch, and this seems to do the trick. I didn't have my drvdata
> patch included when I ran the test. No rpm_idle() calls
> anymore after azx_remove(), so the bug is not hit.
So far, so good...
> > azx_del_card_list(chip);
> > @@ -2320,6 +2325,7 @@ static int azx_probe_continue(struct azx *chip)
> > set_default_power_save(chip);
> >
> > if (azx_has_pm_runtime(chip)) {
> > + pm_runtime_enable(&pci->dev);
> > pm_runtime_use_autosuspend(&pci->dev);
>
> This does generate warnings
> [ 13.495059] snd_hda_intel 0000:00:1f.3: Unbalanced pm_runtime_enable!
>
> And later
> [ 54.770701] Enabling runtime PM for inactive device (0000:00:1f.3) with active children
> [ 54.770718] WARNING: CPU: 0 PID: 10 at drivers/base/power/runtime.c:1439 pm_runtime_enable+0x98/0xb0
>
> Adding a "pm_runtime_set_active(&pci->dev)" to both azx_free() and
> azx_probe_continue() seems to help and fix still works.
Ah yes, I was confused as if it were already called in hdac_device.c,
but this was about the HD-audio bus controller, not the codec.
Below is the revised one.
Takashi
-- 8< --
From: Takashi Iwai <tiwai@suse.de>
Subject: [PATCH] ALSA: hda: intel: More comprehensive PM runtime setup for
controller driver
Currently we haven't explicitly enable and allow/forbid the runtime PM
at the probe and the remove phases of HD-audio controller driver, and
this was the reason of a GPF mentioned in the commit e81478bbe7a1
("ALSA: hda: fix general protection fault in azx_runtime_idle");
namely, even after the resources are released, the runtime PM might be
still invoked by the bound graphics driver during the remove of the
controller driver. Although we've fixed it by clearing the drvdata
reference, it'd be also better to cover the runtime PM issue more
properly.
This patch adds a few more pm_runtime_*() calls at the probe and the
remove time for setting and cleaning up the runtime PM. Particularly,
now more explicitly pm_runtime_enable() and _disable() get called as
well as pm_runtime_forbid() call at the remove callback, so that a
use-after-free should be avoided.
Reported-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
sound/pci/hda/hda_intel.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
index fe51163f2d82..45e85180048c 100644
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -1347,8 +1347,14 @@ static void azx_free(struct azx *chip)
if (hda->freed)
return;
- if (azx_has_pm_runtime(chip) && chip->running)
+ if (azx_has_pm_runtime(chip) && chip->running) {
pm_runtime_get_noresume(&pci->dev);
+ pm_runtime_disable(&pci->dev);
+ pm_runtime_set_suspended(&pci->dev);
+ pm_runtime_forbid(&pci->dev);
+ pm_runtime_dont_use_autosuspend(&pci->dev);
+ }
+
chip->running = 0;
azx_del_card_list(chip);
@@ -2322,6 +2328,8 @@ static int azx_probe_continue(struct azx *chip)
if (azx_has_pm_runtime(chip)) {
pm_runtime_use_autosuspend(&pci->dev);
pm_runtime_allow(&pci->dev);
+ pm_runtime_set_active(&pci->dev);
+ pm_runtime_enable(&pci->dev);
pm_runtime_put_autosuspend(&pci->dev);
}
--
2.31.1
^ permalink raw reply related [flat|nested] 26+ messages in thread
* Re: [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
@ 2021-11-12 10:02 ` Takashi Iwai
0 siblings, 0 replies; 26+ messages in thread
From: Takashi Iwai @ 2021-11-12 10:02 UTC (permalink / raw)
To: Kai Vehmanen; +Cc: alsa-devel, intel-gfx, mahesh.meena
On Thu, 11 Nov 2021 18:39:36 +0100,
Kai Vehmanen wrote:
>
> Hi,
>
> On Thu, 11 Nov 2021, Takashi Iwai wrote:
>
> > A potential problem with the current code is that it doesn't disable
> > the runtime PM at the release procedure. Could you try the patch
> > below? You can put WARN_ON(!chip) at azx_runtime_idle(), too, for
> > catching the invalid runtime call.
> [...]
> > --- a/sound/pci/hda/hda_intel.c
> > +++ b/sound/pci/hda/hda_intel.c
> > @@ -1347,8 +1347,13 @@ static void azx_free(struct azx *chip)
> > if (hda->freed)
> > return;
> >
> > - if (azx_has_pm_runtime(chip) && chip->running)
> > + if (azx_has_pm_runtime(chip) && chip->running) {
> > pm_runtime_get_noresume(&pci->dev);
> > + pm_runtime_forbid(&pci->dev);
> > + pm_runtime_dont_use_autosuspend(&pci->dev);
> > + pm_runtime_disable(&pci->dev);
> > + }
> > +
> > chip->running = 0;
>
> Tested with next-20211019 (first next tag where I've seen test failures)
> and your patch, and this seems to do the trick. I didn't have my drvdata
> patch included when I ran the test. No rpm_idle() calls
> anymore after azx_remove(), so the bug is not hit.
So far, so good...
> > azx_del_card_list(chip);
> > @@ -2320,6 +2325,7 @@ static int azx_probe_continue(struct azx *chip)
> > set_default_power_save(chip);
> >
> > if (azx_has_pm_runtime(chip)) {
> > + pm_runtime_enable(&pci->dev);
> > pm_runtime_use_autosuspend(&pci->dev);
>
> This does generate warnings
> [ 13.495059] snd_hda_intel 0000:00:1f.3: Unbalanced pm_runtime_enable!
>
> And later
> [ 54.770701] Enabling runtime PM for inactive device (0000:00:1f.3) with active children
> [ 54.770718] WARNING: CPU: 0 PID: 10 at drivers/base/power/runtime.c:1439 pm_runtime_enable+0x98/0xb0
>
> Adding a "pm_runtime_set_active(&pci->dev)" to both azx_free() and
> azx_probe_continue() seems to help and fix still works.
Ah yes, I was confused as if it were already called in hdac_device.c,
but this was about the HD-audio bus controller, not the codec.
Below is the revised one.
Takashi
-- 8< --
From: Takashi Iwai <tiwai@suse.de>
Subject: [PATCH] ALSA: hda: intel: More comprehensive PM runtime setup for
controller driver
Currently we haven't explicitly enable and allow/forbid the runtime PM
at the probe and the remove phases of HD-audio controller driver, and
this was the reason of a GPF mentioned in the commit e81478bbe7a1
("ALSA: hda: fix general protection fault in azx_runtime_idle");
namely, even after the resources are released, the runtime PM might be
still invoked by the bound graphics driver during the remove of the
controller driver. Although we've fixed it by clearing the drvdata
reference, it'd be also better to cover the runtime PM issue more
properly.
This patch adds a few more pm_runtime_*() calls at the probe and the
remove time for setting and cleaning up the runtime PM. Particularly,
now more explicitly pm_runtime_enable() and _disable() get called as
well as pm_runtime_forbid() call at the remove callback, so that a
use-after-free should be avoided.
Reported-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
sound/pci/hda/hda_intel.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
index fe51163f2d82..45e85180048c 100644
--- a/sound/pci/hda/hda_intel.c
+++ b/sound/pci/hda/hda_intel.c
@@ -1347,8 +1347,14 @@ static void azx_free(struct azx *chip)
if (hda->freed)
return;
- if (azx_has_pm_runtime(chip) && chip->running)
+ if (azx_has_pm_runtime(chip) && chip->running) {
pm_runtime_get_noresume(&pci->dev);
+ pm_runtime_disable(&pci->dev);
+ pm_runtime_set_suspended(&pci->dev);
+ pm_runtime_forbid(&pci->dev);
+ pm_runtime_dont_use_autosuspend(&pci->dev);
+ }
+
chip->running = 0;
azx_del_card_list(chip);
@@ -2322,6 +2328,8 @@ static int azx_probe_continue(struct azx *chip)
if (azx_has_pm_runtime(chip)) {
pm_runtime_use_autosuspend(&pci->dev);
pm_runtime_allow(&pci->dev);
+ pm_runtime_set_active(&pci->dev);
+ pm_runtime_enable(&pci->dev);
pm_runtime_put_autosuspend(&pci->dev);
}
--
2.31.1
^ permalink raw reply related [flat|nested] 26+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for ALSA: hda: fix general protection fault in azx_runtime_idle (rev3)
2021-11-10 21:03 ` Kai Vehmanen
` (7 preceding siblings ...)
(?)
@ 2021-11-12 10:28 ` Patchwork
-1 siblings, 0 replies; 26+ messages in thread
From: Patchwork @ 2021-11-12 10:28 UTC (permalink / raw)
To: Takashi Iwai; +Cc: intel-gfx
== Series Details ==
Series: ALSA: hda: fix general protection fault in azx_runtime_idle (rev3)
URL : https://patchwork.freedesktop.org/series/96784/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
3d6b0b3ff97c ALSA: hda: fix general protection fault in azx_runtime_idle
-:53: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#53:
> [ 54.770701] Enabling runtime PM for inactive device (0000:00:1f.3) with active children
-:73: WARNING:UNKNOWN_COMMIT_ID: Unknown commit id 'e81478bbe7a1', maybe rebased or not pulled?
#73:
this was the reason of a GPF mentioned in the commit e81478bbe7a1
total: 0 errors, 2 warnings, 0 checks, 23 lines checked
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Intel-gfx] ✗ Fi.CI.DOCS: warning for ALSA: hda: fix general protection fault in azx_runtime_idle (rev3)
2021-11-10 21:03 ` Kai Vehmanen
` (8 preceding siblings ...)
(?)
@ 2021-11-12 10:32 ` Patchwork
-1 siblings, 0 replies; 26+ messages in thread
From: Patchwork @ 2021-11-12 10:32 UTC (permalink / raw)
To: Takashi Iwai; +Cc: intel-gfx
== Series Details ==
Series: ALSA: hda: fix general protection fault in azx_runtime_idle (rev3)
URL : https://patchwork.freedesktop.org/series/96784/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
./drivers/gpu/drm/i915/display/intel_fbc.c:635: warning: Excess function parameter 'i915' description in 'intel_fbc_is_active'
./drivers/gpu/drm/i915/display/intel_fbc.c:1638: warning: Excess function parameter 'i915' description in 'intel_fbc_handle_fifo_underrun_irq'
./drivers/gpu/drm/i915/display/intel_fbc.c:635: warning: Function parameter or member 'fbc' not described in 'intel_fbc_is_active'
./drivers/gpu/drm/i915/display/intel_fbc.c:635: warning: Excess function parameter 'i915' description in 'intel_fbc_is_active'
./drivers/gpu/drm/i915/display/intel_fbc.c:1638: warning: Function parameter or member 'fbc' not described in 'intel_fbc_handle_fifo_underrun_irq'
./drivers/gpu/drm/i915/display/intel_fbc.c:1638: warning: Excess function parameter 'i915' description in 'intel_fbc_handle_fifo_underrun_irq'
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for ALSA: hda: fix general protection fault in azx_runtime_idle (rev3)
2021-11-10 21:03 ` Kai Vehmanen
` (9 preceding siblings ...)
(?)
@ 2021-11-12 10:57 ` Patchwork
-1 siblings, 0 replies; 26+ messages in thread
From: Patchwork @ 2021-11-12 10:57 UTC (permalink / raw)
To: Takashi Iwai; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 3596 bytes --]
== Series Details ==
Series: ALSA: hda: fix general protection fault in azx_runtime_idle (rev3)
URL : https://patchwork.freedesktop.org/series/96784/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10875 -> Patchwork_21571
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/index.html
Participating hosts (28 -> 25)
------------------------------
Additional (1): fi-tgl-dsi
Missing (4): fi-bsw-cyan fi-pnv-d510 bat-dg1-6 bat-dg1-5
Known issues
------------
Here are the changes found in Patchwork_21571 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live@execlists:
- fi-bsw-nick: [PASS][1] -> [INCOMPLETE][2] ([i915#2940])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/fi-bsw-nick/igt@i915_selftest@live@execlists.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/fi-bsw-nick/igt@i915_selftest@live@execlists.html
* igt@runner@aborted:
- fi-bsw-nick: NOTRUN -> [FAIL][3] ([fdo#109271] / [i915#1436] / [i915#3428] / [i915#4312])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/fi-bsw-nick/igt@runner@aborted.html
#### Possible fixes ####
* igt@kms_frontbuffer_tracking@basic:
- fi-cml-u2: [DMESG-WARN][4] ([i915#4269]) -> [PASS][5]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1759]: https://gitlab.freedesktop.org/drm/intel/issues/1759
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2373]: https://gitlab.freedesktop.org/drm/intel/issues/2373
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2940]: https://gitlab.freedesktop.org/drm/intel/issues/2940
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3428]: https://gitlab.freedesktop.org/drm/intel/issues/3428
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4269]: https://gitlab.freedesktop.org/drm/intel/issues/4269
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
Build changes
-------------
* Linux: CI_DRM_10875 -> Patchwork_21571
CI-20190529: 20190529
CI_DRM_10875: f73b8d83650f7b8278b0e166e1aba1024eed4e2e @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6280: 246bfd31dba6bf184b26b170d91d72c90a54be6b @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_21571: 3d6b0b3ff97c899765d050664162891d13e95183 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
3d6b0b3ff97c ALSA: hda: fix general protection fault in azx_runtime_idle
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/index.html
[-- Attachment #2: Type: text/html, Size: 3510 bytes --]
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [Intel-gfx] [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
2021-11-12 10:02 ` Takashi Iwai
@ 2021-11-12 12:27 ` Kai Vehmanen
-1 siblings, 0 replies; 26+ messages in thread
From: Kai Vehmanen @ 2021-11-12 12:27 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel, intel-gfx
Hi,
On Fri, 12 Nov 2021, Takashi Iwai wrote:
> On Thu, 11 Nov 2021 18:39:36 +0100, Kai Vehmanen wrote:
> > And later
> > [ 54.770701] Enabling runtime PM for inactive device (0000:00:1f.3) with active children
> > [ 54.770718] WARNING: CPU: 0 PID: 10 at drivers/base/power/runtime.c:1439 pm_runtime_enable+0x98/0xb0
> >
> > Adding a "pm_runtime_set_active(&pci->dev)" to both azx_free() and
> > azx_probe_continue() seems to help and fix still works.
>
> Ah yes, I was confused as if it were already called in hdac_device.c,
> but this was about the HD-audio bus controller, not the codec.
>
> Below is the revised one.
[...]
> Currently we haven't explicitly enable and allow/forbid the runtime PM
> at the probe and the remove phases of HD-audio controller driver, and
> this was the reason of a GPF mentioned in the commit e81478bbe7a1
> ("ALSA: hda: fix general protection fault in azx_runtime_idle");
> namely, even after the resources are released, the runtime PM might be
> still invoked by the bound graphics driver during the remove of the
> controller driver. Although we've fixed it by clearing the drvdata
> reference, it'd be also better to cover the runtime PM issue more
> properly.
>
> This patch adds a few more pm_runtime_*() calls at the probe and the
> remove time for setting and cleaning up the runtime PM. Particularly,
> now more explicitly pm_runtime_enable() and _disable() get called as
> well as pm_runtime_forbid() call at the remove callback, so that a
> use-after-free should be avoided.
>
> Reported-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
ack, tested this and no warnings anymore.
Reviewed-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Tested-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Br, Kai
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
@ 2021-11-12 12:27 ` Kai Vehmanen
0 siblings, 0 replies; 26+ messages in thread
From: Kai Vehmanen @ 2021-11-12 12:27 UTC (permalink / raw)
To: Takashi Iwai; +Cc: alsa-devel, intel-gfx, Kai Vehmanen, mahesh.meena
Hi,
On Fri, 12 Nov 2021, Takashi Iwai wrote:
> On Thu, 11 Nov 2021 18:39:36 +0100, Kai Vehmanen wrote:
> > And later
> > [ 54.770701] Enabling runtime PM for inactive device (0000:00:1f.3) with active children
> > [ 54.770718] WARNING: CPU: 0 PID: 10 at drivers/base/power/runtime.c:1439 pm_runtime_enable+0x98/0xb0
> >
> > Adding a "pm_runtime_set_active(&pci->dev)" to both azx_free() and
> > azx_probe_continue() seems to help and fix still works.
>
> Ah yes, I was confused as if it were already called in hdac_device.c,
> but this was about the HD-audio bus controller, not the codec.
>
> Below is the revised one.
[...]
> Currently we haven't explicitly enable and allow/forbid the runtime PM
> at the probe and the remove phases of HD-audio controller driver, and
> this was the reason of a GPF mentioned in the commit e81478bbe7a1
> ("ALSA: hda: fix general protection fault in azx_runtime_idle");
> namely, even after the resources are released, the runtime PM might be
> still invoked by the bound graphics driver during the remove of the
> controller driver. Although we've fixed it by clearing the drvdata
> reference, it'd be also better to cover the runtime PM issue more
> properly.
>
> This patch adds a few more pm_runtime_*() calls at the probe and the
> remove time for setting and cleaning up the runtime PM. Particularly,
> now more explicitly pm_runtime_enable() and _disable() get called as
> well as pm_runtime_forbid() call at the remove callback, so that a
> use-after-free should be avoided.
>
> Reported-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
ack, tested this and no warnings anymore.
Reviewed-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Tested-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Br, Kai
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for ALSA: hda: fix general protection fault in azx_runtime_idle (rev3)
2021-11-10 21:03 ` Kai Vehmanen
` (10 preceding siblings ...)
(?)
@ 2021-11-12 15:04 ` Patchwork
-1 siblings, 0 replies; 26+ messages in thread
From: Patchwork @ 2021-11-12 15:04 UTC (permalink / raw)
To: Takashi Iwai; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 30289 bytes --]
== Series Details ==
Series: ALSA: hda: fix general protection fault in azx_runtime_idle (rev3)
URL : https://patchwork.freedesktop.org/series/96784/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10875_full -> Patchwork_21571_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_21571_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_21571_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Participating hosts (11 -> 12)
------------------------------
Additional (1): pig-snb-2600
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_21571_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip:
- shard-tglb: NOTRUN -> [SKIP][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb6/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* {igt@gem_exec_balancer@parallel-out-fence}:
- {shard-rkl}: NOTRUN -> [SKIP][2]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-6/igt@gem_exec_balancer@parallel-out-fence.html
* igt@kms_big_fb@yf-tiled-32bpp-rotate-270:
- {shard-rkl}: ([SKIP][3], [SKIP][4]) ([i915#1845]) -> [SKIP][5]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-4/igt@kms_big_fb@yf-tiled-32bpp-rotate-270.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-2/igt@kms_big_fb@yf-tiled-32bpp-rotate-270.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-6/igt@kms_big_fb@yf-tiled-32bpp-rotate-270.html
* igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0:
- {shard-rkl}: [SKIP][6] ([i915#1845]) -> [SKIP][7] +1 similar issue
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-2/igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-6/igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0.html
Known issues
------------
Here are the changes found in Patchwork_21571_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-glk: [PASS][8] -> [FAIL][9] ([i915#2842])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-glk8/igt@gem_exec_fair@basic-none-share@rcs0.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-glk4/igt@gem_exec_fair@basic-none-share@rcs0.html
- shard-iclb: [PASS][10] -> [FAIL][11] ([i915#2842])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-iclb7/igt@gem_exec_fair@basic-none-share@rcs0.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-iclb4/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-tglb: NOTRUN -> [FAIL][12] ([i915#2842])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@gem_exec_fair@basic-pace-solo@rcs0.html
* igt@gem_exec_fair@basic-pace@vcs1:
- shard-kbl: [PASS][13] -> [SKIP][14] ([fdo#109271])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-kbl6/igt@gem_exec_fair@basic-pace@vcs1.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl3/igt@gem_exec_fair@basic-pace@vcs1.html
* igt@gem_exec_params@rsvd2-dirt:
- shard-tglb: NOTRUN -> [SKIP][15] ([fdo#109283])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@gem_exec_params@rsvd2-dirt.html
* igt@gem_huc_copy@huc-copy:
- shard-kbl: NOTRUN -> [SKIP][16] ([fdo#109271] / [i915#2190])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl2/igt@gem_huc_copy@huc-copy.html
* igt@gem_mmap_gtt@coherency:
- shard-tglb: NOTRUN -> [SKIP][17] ([fdo#111656])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@gem_mmap_gtt@coherency.html
* igt@gem_pxp@verify-pxp-stale-buf-execution:
- shard-tglb: NOTRUN -> [SKIP][18] ([i915#4270]) +1 similar issue
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@gem_pxp@verify-pxp-stale-buf-execution.html
* igt@gem_userptr_blits@dmabuf-sync:
- shard-skl: NOTRUN -> [SKIP][19] ([fdo#109271] / [i915#3323])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl6/igt@gem_userptr_blits@dmabuf-sync.html
* igt@gem_userptr_blits@input-checking:
- shard-kbl: NOTRUN -> [DMESG-WARN][20] ([i915#3002])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl1/igt@gem_userptr_blits@input-checking.html
* igt@gem_userptr_blits@vma-merge:
- shard-kbl: NOTRUN -> [FAIL][21] ([i915#3318])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl1/igt@gem_userptr_blits@vma-merge.html
* igt@gen9_exec_parse@bb-large:
- shard-tglb: NOTRUN -> [SKIP][22] ([i915#2856])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@gen9_exec_parse@bb-large.html
* igt@i915_pm_rc6_residency@media-rc6-accuracy:
- shard-tglb: NOTRUN -> [SKIP][23] ([fdo#109289] / [fdo#111719])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@i915_pm_rc6_residency@media-rc6-accuracy.html
* igt@i915_suspend@debugfs-reader:
- shard-tglb: [PASS][24] -> [INCOMPLETE][25] ([i915#456]) +1 similar issue
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-tglb3/igt@i915_suspend@debugfs-reader.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb7/igt@i915_suspend@debugfs-reader.html
* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-tglb: [PASS][26] -> [INCOMPLETE][27] ([i915#456] / [i915#750])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-tglb1/igt@i915_suspend@fence-restore-tiled2untiled.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb7/igt@i915_suspend@fence-restore-tiled2untiled.html
* igt@i915_suspend@forcewake:
- shard-kbl: NOTRUN -> [DMESG-WARN][28] ([i915#180])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl1/igt@i915_suspend@forcewake.html
* igt@kms_atomic_transition@plane-all-modeset-transition:
- shard-tglb: NOTRUN -> [SKIP][29] ([i915#1769])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_atomic_transition@plane-all-modeset-transition.html
* igt@kms_big_fb@x-tiled-64bpp-rotate-270:
- shard-tglb: NOTRUN -> [SKIP][30] ([fdo#111614])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_big_fb@x-tiled-64bpp-rotate-270.html
* igt@kms_big_fb@yf-tiled-16bpp-rotate-90:
- shard-tglb: NOTRUN -> [SKIP][31] ([fdo#111615]) +1 similar issue
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_big_fb@yf-tiled-16bpp-rotate-90.html
* igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][32] ([i915#3689]) +3 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_ccs.html
* igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_rc_ccs_cc:
- shard-apl: NOTRUN -> [SKIP][33] ([fdo#109271] / [i915#3886]) +1 similar issue
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-apl2/igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-ccs-on-another-bo-y_tiled_gen12_mc_ccs:
- shard-kbl: NOTRUN -> [SKIP][34] ([fdo#109271] / [i915#3886]) +11 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl2/igt@kms_ccs@pipe-c-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-c-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][35] ([fdo#109271] / [i915#3886]) +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl6/igt@kms_ccs@pipe-c-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_chamelium@vga-hpd-without-ddc:
- shard-kbl: NOTRUN -> [SKIP][36] ([fdo#109271] / [fdo#111827]) +17 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl1/igt@kms_chamelium@vga-hpd-without-ddc.html
* igt@kms_color@pipe-c-ctm-0-25:
- shard-skl: [PASS][37] -> [DMESG-WARN][38] ([i915#1982]) +3 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-skl4/igt@kms_color@pipe-c-ctm-0-25.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl9/igt@kms_color@pipe-c-ctm-0-25.html
* igt@kms_color_chamelium@pipe-c-degamma:
- shard-apl: NOTRUN -> [SKIP][39] ([fdo#109271] / [fdo#111827]) +6 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-apl2/igt@kms_color_chamelium@pipe-c-degamma.html
* igt@kms_color_chamelium@pipe-d-ctm-0-25:
- shard-skl: NOTRUN -> [SKIP][40] ([fdo#109271] / [fdo#111827]) +3 similar issues
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl6/igt@kms_color_chamelium@pipe-d-ctm-0-25.html
* igt@kms_color_chamelium@pipe-d-degamma:
- shard-tglb: NOTRUN -> [SKIP][41] ([fdo#109284] / [fdo#111827]) +7 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_color_chamelium@pipe-d-degamma.html
* igt@kms_content_protection@atomic:
- shard-kbl: NOTRUN -> [TIMEOUT][42] ([i915#1319]) +1 similar issue
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl1/igt@kms_content_protection@atomic.html
* igt@kms_content_protection@dp-mst-lic-type-1:
- shard-tglb: NOTRUN -> [SKIP][43] ([i915#3116])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_content_protection@dp-mst-lic-type-1.html
* igt@kms_content_protection@uevent:
- shard-kbl: NOTRUN -> [FAIL][44] ([i915#2105])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl1/igt@kms_content_protection@uevent.html
* igt@kms_cursor_crc@pipe-c-cursor-32x10-random:
- shard-tglb: NOTRUN -> [SKIP][45] ([i915#3359]) +4 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_cursor_crc@pipe-c-cursor-32x10-random.html
* igt@kms_cursor_crc@pipe-d-cursor-32x32-offscreen:
- shard-tglb: NOTRUN -> [SKIP][46] ([i915#3319])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_cursor_crc@pipe-d-cursor-32x32-offscreen.html
* igt@kms_cursor_crc@pipe-d-cursor-512x512-rapid-movement:
- shard-tglb: NOTRUN -> [SKIP][47] ([fdo#109279] / [i915#3359]) +1 similar issue
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_cursor_crc@pipe-d-cursor-512x512-rapid-movement.html
* igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
- shard-kbl: [PASS][48] -> [DMESG-WARN][49] ([i915#180]) +2 similar issues
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-kbl3/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl4/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html
* igt@kms_flip@flip-vs-suspend@b-edp1:
- shard-skl: [PASS][50] -> [INCOMPLETE][51] ([i915#198])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-skl10/igt@kms_flip@flip-vs-suspend@b-edp1.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl8/igt@kms_flip@flip-vs-suspend@b-edp1.html
* igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1:
- shard-skl: [PASS][52] -> [FAIL][53] ([i915#2122])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-skl8/igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl6/igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile:
- shard-iclb: [PASS][54] -> [SKIP][55] ([i915#3701])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-iclb3/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-tglb: [PASS][56] -> [INCOMPLETE][57] ([i915#2411] / [i915#2828] / [i915#456])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-tglb5/igt@kms_frontbuffer_tracking@fbc-suspend.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb7/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-draw-mmap-cpu:
- shard-skl: NOTRUN -> [SKIP][58] ([fdo#109271]) +43 similar issues
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl6/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-draw-mmap-cpu.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-draw-mmap-gtt:
- shard-tglb: NOTRUN -> [SKIP][59] ([fdo#111825]) +19 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-draw-mmap-gtt.html
* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-wc:
- shard-kbl: NOTRUN -> [SKIP][60] ([fdo#109271]) +169 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl2/igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-wc.html
* igt@kms_pipe_b_c_ivb@disable-pipe-b-enable-pipe-c:
- shard-apl: NOTRUN -> [SKIP][61] ([fdo#109271]) +41 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-apl2/igt@kms_pipe_b_c_ivb@disable-pipe-b-enable-pipe-c.html
* igt@kms_pipe_crc_basic@nonblocking-crc-pipe-d-frame-sequence:
- shard-kbl: NOTRUN -> [SKIP][62] ([fdo#109271] / [i915#533]) +2 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl1/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-d-frame-sequence.html
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
- shard-apl: [PASS][63] -> [DMESG-WARN][64] ([i915#180]) +1 similar issue
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-apl1/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-apl6/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-opaque-fb:
- shard-kbl: NOTRUN -> [FAIL][65] ([fdo#108145] / [i915#265]) +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl6/igt@kms_plane_alpha_blend@pipe-c-alpha-opaque-fb.html
- shard-apl: NOTRUN -> [FAIL][66] ([fdo#108145] / [i915#265])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-apl2/igt@kms_plane_alpha_blend@pipe-c-alpha-opaque-fb.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb:
- shard-skl: NOTRUN -> [FAIL][67] ([i915#265])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl6/igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb.html
* igt@kms_plane_lowres@pipe-a-tiling-none:
- shard-tglb: NOTRUN -> [SKIP][68] ([i915#3536]) +1 similar issue
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_plane_lowres@pipe-a-tiling-none.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-1:
- shard-skl: NOTRUN -> [SKIP][69] ([fdo#109271] / [i915#658])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl6/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-1.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3:
- shard-kbl: NOTRUN -> [SKIP][70] ([fdo#109271] / [i915#658]) +4 similar issues
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl6/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3.html
* igt@kms_psr2_sf@plane-move-sf-dmg-area-3:
- shard-tglb: NOTRUN -> [SKIP][71] ([i915#2920])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_psr2_sf@plane-move-sf-dmg-area-3.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1:
- shard-apl: NOTRUN -> [SKIP][72] ([fdo#109271] / [i915#658])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-apl2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1.html
* igt@kms_psr@psr2_cursor_blt:
- shard-tglb: NOTRUN -> [FAIL][73] ([i915#132] / [i915#3467])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_psr@psr2_cursor_blt.html
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [PASS][74] -> [SKIP][75] ([fdo#109441]) +2 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-iclb4/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_setmode@basic:
- shard-glk: [PASS][76] -> [FAIL][77] ([i915#31])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-glk7/igt@kms_setmode@basic.html
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-glk1/igt@kms_setmode@basic.html
* igt@kms_vrr@flip-suspend:
- shard-tglb: NOTRUN -> [SKIP][78] ([fdo#109502])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@kms_vrr@flip-suspend.html
* igt@kms_writeback@writeback-check-output:
- shard-kbl: NOTRUN -> [SKIP][79] ([fdo#109271] / [i915#2437])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl1/igt@kms_writeback@writeback-check-output.html
* igt@kms_writeback@writeback-fb-id:
- shard-skl: NOTRUN -> [SKIP][80] ([fdo#109271] / [i915#2437])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl6/igt@kms_writeback@writeback-fb-id.html
* igt@nouveau_crc@pipe-d-source-outp-inactive:
- shard-tglb: NOTRUN -> [SKIP][81] ([i915#2530])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@nouveau_crc@pipe-d-source-outp-inactive.html
* igt@perf@polling-parameterized:
- shard-skl: [PASS][82] -> [FAIL][83] ([i915#1542])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-skl1/igt@perf@polling-parameterized.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl5/igt@perf@polling-parameterized.html
* igt@perf@unprivileged-single-ctx-counters:
- shard-tglb: NOTRUN -> [SKIP][84] ([fdo#109289]) +1 similar issue
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@perf@unprivileged-single-ctx-counters.html
* igt@prime_nv_api@i915_nv_reimport_twice_check_flink_name:
- shard-tglb: NOTRUN -> [SKIP][85] ([fdo#109291]) +2 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@prime_nv_api@i915_nv_reimport_twice_check_flink_name.html
* igt@prime_vgem@fence-write-hang:
- shard-tglb: NOTRUN -> [SKIP][86] ([fdo#109295])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@prime_vgem@fence-write-hang.html
* igt@sysfs_clients@pidname:
- shard-apl: NOTRUN -> [SKIP][87] ([fdo#109271] / [i915#2994])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-apl2/igt@sysfs_clients@pidname.html
* igt@sysfs_clients@recycle:
- shard-kbl: NOTRUN -> [SKIP][88] ([fdo#109271] / [i915#2994]) +3 similar issues
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl1/igt@sysfs_clients@recycle.html
* igt@sysfs_clients@sema-10:
- shard-tglb: NOTRUN -> [SKIP][89] ([i915#2994]) +1 similar issue
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb6/igt@sysfs_clients@sema-10.html
* igt@tools_test@sysfs_l3_parity:
- shard-tglb: NOTRUN -> [SKIP][90] ([fdo#109307])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb3/igt@tools_test@sysfs_l3_parity.html
#### Possible fixes ####
* igt@fbdev@eof:
- {shard-rkl}: [SKIP][91] ([i915#2582]) -> [PASS][92]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-4/igt@fbdev@eof.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-6/igt@fbdev@eof.html
* igt@gem_ctx_isolation@preservation-s3@vecs0:
- shard-skl: [INCOMPLETE][93] ([i915#198]) -> [PASS][94]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-skl4/igt@gem_ctx_isolation@preservation-s3@vecs0.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl9/igt@gem_ctx_isolation@preservation-s3@vecs0.html
* igt@gem_eio@in-flight-1us:
- shard-skl: [TIMEOUT][95] ([i915#3063]) -> [PASS][96]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-skl8/igt@gem_eio@in-flight-1us.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl6/igt@gem_eio@in-flight-1us.html
* igt@gem_eio@unwedge-stress:
- shard-iclb: [TIMEOUT][97] ([i915#2369] / [i915#2481] / [i915#3070]) -> [PASS][98]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-iclb3/igt@gem_eio@unwedge-stress.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-iclb5/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_endless@dispatch@rcs0:
- shard-tglb: [INCOMPLETE][99] ([i915#3778]) -> [PASS][100]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-tglb2/igt@gem_exec_endless@dispatch@rcs0.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb6/igt@gem_exec_endless@dispatch@rcs0.html
* igt@gem_exec_fair@basic-none-solo@rcs0:
- {shard-rkl}: [FAIL][101] ([i915#2849]) -> ([PASS][102], [PASS][103])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-6/igt@gem_exec_fair@basic-none-solo@rcs0.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-2/igt@gem_exec_fair@basic-none-solo@rcs0.html
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-4/igt@gem_exec_fair@basic-none-solo@rcs0.html
* igt@gem_exec_fair@basic-none@vecs0:
- shard-kbl: [FAIL][104] ([i915#2842]) -> [PASS][105] +1 similar issue
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-kbl7/igt@gem_exec_fair@basic-none@vecs0.html
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl7/igt@gem_exec_fair@basic-none@vecs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [FAIL][106] ([i915#2842]) -> [PASS][107]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-tglb6/igt@gem_exec_fair@basic-pace-share@rcs0.html
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-tglb1/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-kbl: [SKIP][108] ([fdo#109271]) -> [PASS][109]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-kbl6/igt@gem_exec_fair@basic-pace@rcs0.html
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl3/igt@gem_exec_fair@basic-pace@rcs0.html
- shard-glk: [FAIL][110] ([i915#2842]) -> [PASS][111]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-glk2/igt@gem_exec_fair@basic-pace@rcs0.html
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-glk8/igt@gem_exec_fair@basic-pace@rcs0.html
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [FAIL][112] ([i915#2849]) -> [PASS][113]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-iclb4/igt@gem_exec_fair@basic-throttle@rcs0.html
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-iclb2/igt@gem_exec_fair@basic-throttle@rcs0.html
* igt@gem_exec_whisper@basic-contexts:
- shard-glk: [DMESG-WARN][114] ([i915#118]) -> [PASS][115]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-glk2/igt@gem_exec_whisper@basic-contexts.html
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-glk8/igt@gem_exec_whisper@basic-contexts.html
* igt@i915_module_load@reload:
- shard-skl: [DMESG-WARN][116] ([i915#1982]) -> [PASS][117] +1 similar issue
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-skl5/igt@i915_module_load@reload.html
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-skl10/igt@i915_module_load@reload.html
* igt@i915_pm_rpm@dpms-mode-unset-lpsp:
- {shard-rkl}: [SKIP][118] ([i915#1397]) -> [PASS][119]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-2/igt@i915_pm_rpm@dpms-mode-unset-lpsp.html
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-6/igt@i915_pm_rpm@dpms-mode-unset-lpsp.html
* igt@i915_pm_rpm@system-suspend-modeset:
- {shard-rkl}: [SKIP][120] ([fdo#109308]) -> [PASS][121] +1 similar issue
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-2/igt@i915_pm_rpm@system-suspend-modeset.html
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-6/igt@i915_pm_rpm@system-suspend-modeset.html
* igt@i915_selftest@live@gt_pm:
- {shard-rkl}: [DMESG-FAIL][122] -> [PASS][123]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-6/igt@i915_selftest@live@gt_pm.html
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-1/igt@i915_selftest@live@gt_pm.html
* igt@kms_async_flips@async-flip-with-page-flip-events:
- {shard-rkl}: ([PASS][124], [SKIP][125]) ([i915#1845]) -> [PASS][126]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-6/igt@kms_async_flips@async-flip-with-page-flip-events.html
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-4/igt@kms_async_flips@async-flip-with-page-flip-events.html
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-6/igt@kms_async_flips@async-flip-with-page-flip-events.html
* igt@kms_atomic@atomic-invalid-params:
- shard-kbl: [INCOMPLETE][127] -> [PASS][128]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-kbl6/igt@kms_atomic@atomic-invalid-params.html
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-kbl1/igt@kms_atomic@atomic-invalid-params.html
* igt@kms_atomic_transition@plane-primary-toggle-with-vblank-wait:
- {shard-rkl}: ([SKIP][129], [SKIP][130]) ([i915#1845]) -> [PASS][131] +2 similar issues
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-2/igt@kms_atomic_transition@plane-primary-toggle-with-vblank-wait.html
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-4/igt@kms_atomic_transition@plane-primary-toggle-with-vblank-wait.html
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-6/igt@kms_atomic_transition@plane-primary-toggle-with-vblank-wait.html
* igt@kms_ccs@pipe-a-bad-rotation-90-y_tiled_gen12_rc_ccs:
- {shard-rkl}: [SKIP][132] ([i915#1845]) -> [PASS][133] +16 similar issues
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-4/igt@kms_ccs@pipe-a-bad-rotation-90-y_tiled_gen12_rc_ccs.html
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-6/igt@kms_ccs@pipe-a-bad-rotation-90-y_tiled_gen12_rc_ccs.html
* igt@kms_color@pipe-a-ctm-0-75:
- {shard-rkl}: [SKIP][134] ([i915#1149] / [i915#4098]) -> [PASS][135] +1 similar issue
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-4/igt@kms_color@pipe-a-ctm-0-75.html
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-6/igt@kms_color@pipe-a-ctm-0-75.html
* igt@kms_color@pipe-b-ctm-0-75:
- {shard-rkl}: [SKIP][136] ([i915#1149] / [i915#1849] / [i915#4070]) -> [PASS][137] +2 similar issues
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-2/igt@kms_color@pipe-b-ctm-0-75.html
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-6/igt@kms_color@pipe-b-ctm-0-75.html
* igt@kms_color@pipe-c-invalid-gamma-lut-sizes:
- {shard-rkl}: [SKIP][138] ([i915#4070]) -> [PASS][139]
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-1/igt@kms_color@pipe-c-invalid-gamma-lut-sizes.html
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/shard-rkl-4/igt@kms_color@pipe-c-invalid-gamma-lut-sizes.html
* igt@kms_cursor_crc@pipe-b-cursor-256x85-sliding:
- {shard-rkl}: [SKIP][140] ([fdo#112022] / [i915#4070]) -> [PASS][141] +3 similar issues
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10875/shard-rkl-2/igt@kms_cursor_crc@pipe-b-cursor-256x85-sliding.html
[141]: https://intel-gfx-ci.01.org/tree/drm-
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21571/index.html
[-- Attachment #2: Type: text/html, Size: 33500 bytes --]
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [Intel-gfx] [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
2021-11-12 12:27 ` Kai Vehmanen
@ 2021-11-15 7:57 ` Takashi Iwai
-1 siblings, 0 replies; 26+ messages in thread
From: Takashi Iwai @ 2021-11-15 7:57 UTC (permalink / raw)
To: Kai Vehmanen; +Cc: alsa-devel, intel-gfx
On Fri, 12 Nov 2021 13:27:34 +0100,
Kai Vehmanen wrote:
>
> Hi,
>
> On Fri, 12 Nov 2021, Takashi Iwai wrote:
>
> > On Thu, 11 Nov 2021 18:39:36 +0100, Kai Vehmanen wrote:
> > > And later
> > > [ 54.770701] Enabling runtime PM for inactive device (0000:00:1f.3) with active children
> > > [ 54.770718] WARNING: CPU: 0 PID: 10 at drivers/base/power/runtime.c:1439 pm_runtime_enable+0x98/0xb0
> > >
> > > Adding a "pm_runtime_set_active(&pci->dev)" to both azx_free() and
> > > azx_probe_continue() seems to help and fix still works.
> >
> > Ah yes, I was confused as if it were already called in hdac_device.c,
> > but this was about the HD-audio bus controller, not the codec.
> >
> > Below is the revised one.
> [...]
> > Currently we haven't explicitly enable and allow/forbid the runtime PM
> > at the probe and the remove phases of HD-audio controller driver, and
> > this was the reason of a GPF mentioned in the commit e81478bbe7a1
> > ("ALSA: hda: fix general protection fault in azx_runtime_idle");
> > namely, even after the resources are released, the runtime PM might be
> > still invoked by the bound graphics driver during the remove of the
> > controller driver. Although we've fixed it by clearing the drvdata
> > reference, it'd be also better to cover the runtime PM issue more
> > properly.
> >
> > This patch adds a few more pm_runtime_*() calls at the probe and the
> > remove time for setting and cleaning up the runtime PM. Particularly,
> > now more explicitly pm_runtime_enable() and _disable() get called as
> > well as pm_runtime_forbid() call at the remove callback, so that a
> > use-after-free should be avoided.
> >
> > Reported-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
>
> ack, tested this and no warnings anymore.
>
> Reviewed-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> Tested-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
OK, I'll submit and merge the patch.
As the original problem was fixed by NULL checks, I'd push this for
5.16, though.
thanks,
Takashi
^ permalink raw reply [flat|nested] 26+ messages in thread
* Re: [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle
@ 2021-11-15 7:57 ` Takashi Iwai
0 siblings, 0 replies; 26+ messages in thread
From: Takashi Iwai @ 2021-11-15 7:57 UTC (permalink / raw)
To: Kai Vehmanen; +Cc: alsa-devel, intel-gfx, mahesh.meena
On Fri, 12 Nov 2021 13:27:34 +0100,
Kai Vehmanen wrote:
>
> Hi,
>
> On Fri, 12 Nov 2021, Takashi Iwai wrote:
>
> > On Thu, 11 Nov 2021 18:39:36 +0100, Kai Vehmanen wrote:
> > > And later
> > > [ 54.770701] Enabling runtime PM for inactive device (0000:00:1f.3) with active children
> > > [ 54.770718] WARNING: CPU: 0 PID: 10 at drivers/base/power/runtime.c:1439 pm_runtime_enable+0x98/0xb0
> > >
> > > Adding a "pm_runtime_set_active(&pci->dev)" to both azx_free() and
> > > azx_probe_continue() seems to help and fix still works.
> >
> > Ah yes, I was confused as if it were already called in hdac_device.c,
> > but this was about the HD-audio bus controller, not the codec.
> >
> > Below is the revised one.
> [...]
> > Currently we haven't explicitly enable and allow/forbid the runtime PM
> > at the probe and the remove phases of HD-audio controller driver, and
> > this was the reason of a GPF mentioned in the commit e81478bbe7a1
> > ("ALSA: hda: fix general protection fault in azx_runtime_idle");
> > namely, even after the resources are released, the runtime PM might be
> > still invoked by the bound graphics driver during the remove of the
> > controller driver. Although we've fixed it by clearing the drvdata
> > reference, it'd be also better to cover the runtime PM issue more
> > properly.
> >
> > This patch adds a few more pm_runtime_*() calls at the probe and the
> > remove time for setting and cleaning up the runtime PM. Particularly,
> > now more explicitly pm_runtime_enable() and _disable() get called as
> > well as pm_runtime_forbid() call at the remove callback, so that a
> > use-after-free should be avoided.
> >
> > Reported-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
>
> ack, tested this and no warnings anymore.
>
> Reviewed-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> Tested-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
OK, I'll submit and merge the patch.
As the original problem was fixed by NULL checks, I'd push this for
5.16, though.
thanks,
Takashi
^ permalink raw reply [flat|nested] 26+ messages in thread
end of thread, other threads:[~2021-11-15 7:59 UTC | newest]
Thread overview: 26+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-10 21:03 [Intel-gfx] [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle Kai Vehmanen
2021-11-10 21:03 ` Kai Vehmanen
2021-11-10 21:55 ` [Intel-gfx] " Takashi Iwai
2021-11-10 21:55 ` Takashi Iwai
2021-11-10 22:15 ` [Intel-gfx] " Kai Vehmanen
2021-11-10 22:15 ` Kai Vehmanen
2021-11-11 13:29 ` [Intel-gfx] " Takashi Iwai
2021-11-11 13:29 ` Takashi Iwai
2021-11-11 17:39 ` [Intel-gfx] " Kai Vehmanen
2021-11-11 17:39 ` Kai Vehmanen
2021-11-12 10:02 ` [Intel-gfx] " Takashi Iwai
2021-11-12 10:02 ` Takashi Iwai
2021-11-12 12:27 ` [Intel-gfx] " Kai Vehmanen
2021-11-12 12:27 ` Kai Vehmanen
2021-11-15 7:57 ` [Intel-gfx] " Takashi Iwai
2021-11-15 7:57 ` Takashi Iwai
2021-11-10 21:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-11-10 22:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-10 23:45 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-11 15:33 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for ALSA: hda: fix general protection fault in azx_runtime_idle (rev2) Patchwork
2021-11-11 15:37 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2021-11-11 16:01 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-11-12 10:28 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for ALSA: hda: fix general protection fault in azx_runtime_idle (rev3) Patchwork
2021-11-12 10:32 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2021-11-12 10:57 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-12 15:04 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.