iommu_intel or i915 regression in 4.18, 4.19.12 and drm-tip
I just got a used Thinkpad X201 (Core i5 M 520, Intel QM57 chipset) and hit some kernel panics while trying to view image/animation-intensive stuff in Firefox (X11) unless I use "iommu_intel=igfx_off".
With Debian stable backport kernels, "linux-image-4.17.0-0.bpo.3-amd64" (4.17.17-1~bpo9+1) has no problems. But "linux-image-4.18.0-0.bpo.3-amd64" (4.18.20-2~bpo9+1) gives a blank screen before I can login via agetty and run startx.
Building 4.19.12 myself got me into X11 and able to start Firefox to panic the kernel. I also updated to the latest BIOS (1.40), but it's an EOL laptop (but it's still the most powerful laptop I use). I intend to replace the BIOS with Coreboot soon...
Initially, I thought I was hitting another GPU hang from 4.18+:
https://bugs.freedesktop.org/show_bug.cgi?id=107945
But building drm-tip @ commit 28bb1fc015cedadf3b099b8bd0bb27609849f362 ("drm-tip: 2018y-12m-25d-08h-12m-37s UTC integration manifest") I was still able to reproduce the panic unless I use iommu_intel=igfx_off "i915.reset=1" did not help matters, either.
Below is what I got from netconsole while on drm-tip:
Kernel panic - not syncing: DMAR hardware is malfunctioning Shutting down cpus with NMI Kernel Offset: disabled ---[ end Kernel panic - not syncing: DMAR hardware is malfunctioning ]--- ------------[ cut here ]------------ sched: Unexpected reschedule of offline CPU#3! WARNING: CPU: 0 PID: 105 at native_smp_send_reschedule+0x34/0x40 Modules linked in: netconsole ccm snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic intel_powerclamp coretemp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel ghash_clmulni_intel arc4 iwldvm aesni_intel aes_x86_64 crypto_simd cryptd mac80211 glue_helper intel_cstate iwlwifi intel_uncore i915 intel_gtt i2c_algo_bit iosf_mbi drm_kms_helper cfbfillrect syscopyarea intel_ips cfbimgblt sysfillrect sysimgblt fb_sys_fops cfbcopyarea thinkpad_acpi prime_numbers cfg80211 ledtrig_audio i2c_i801 sg snd_hda_intel led_class snd_hda_codec drm ac drm_panel_orientation_quirks snd_hwdep battery e1000e agpgart snd_hda_core snd_pcm snd_timer ptp snd soundcore pps_core ehci_pci ehci_hcd lpc_ich video mfd_core button acpi_cpufreq ecryptfs ip_tables x_tables ipv6 evdev thermal [last unloaded: net console] CPU: 0 PID: 105 Comm: kworker/u8:3 Not tainted 4.20.0-rc7b1+ #1 Hardware name: LENOVO 3680FBU/3680FBU, BIOS 6QET70WW (1.40 ) 10/11/2012 Workqueue: i915 __i915_gem_free_work [i915] RIP: 0010:native_smp_send_reschedule+0x34/0x40 Code: 05 69 c6 c9 00 73 15 48 8b 05 18 2d b3 00 be fd 00 00 00 48 8b 40 30 e9 9a 58 7d 00 89 fe 48 c7 c7 78 73 af 81 e8 dc c2 01 00 <0f> 0b c3 66 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 05 0d 7d df RSP: 0018:ffff888075003d98 EFLAGS: 00010092 RAX: 000000000000002e RBX: ffff8880751a0740 RCX: 0000000000000006 RDX: 0000000000000007 RSI: 0000000000000082 RDI: ffff888075015440 RBP: ffff88806e823700 R08: 0000000000000000 R09: ffff888072fc07c0 R10: ffff888075003d60 R11: 00000000fff5c002 R12: ffff8880751a0740 R13: ffff8880751a0740 R14: 0000000000000000 R15: 0000000000000003 FS: 0000000000000000(0000) GS:ffff888075000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fdb1f53f000 CR3: 0000000001c0a004 CR4: 00000000000206f0 Call Trace: <IRQ> ? check_preempt_curr+0x4e/0x90 ? ttwu_do_wakeup.isra.19+0x14/0xf0 ? try_to_wake_up+0x323/0x410 ? autoremove_wake_function+0xe/0x30 ? __wake_up_common+0x8d/0x140 ? __wake_up_common_lock+0x6c/0x90 ? irq_work_run_list+0x49/0x80 ? tick_sched_handle.isra.6+0x50/0x50 ? update_process_times+0x3b/0x50 ? tick_sched_handle.isra.6+0x30/0x50 ? tick_sched_timer+0x3b/0x80 ? __hrtimer_run_queues+0xea/0x270 ? hrtimer_interrupt+0x101/0x240 ? smp_apic_timer_interrupt+0x6a/0x150 ? apic_timer_interrupt+0xf/0x20 </IRQ> ? panic+0x1ca/0x212 ? panic+0x1c7/0x212 ? __iommu_flush_iotlb+0x19e/0x1c0 ? iommu_flush_iotlb_psi+0x96/0xf0 ? intel_unmap+0xbf/0xf0 ? i915_gem_object_put_pages_gtt+0x36/0x220 [i915] ? drm_ht_remove+0x20/0x20 [drm] ? drm_mm_remove_node+0x1ad/0x310 [drm] ? __pm_runtime_resume+0x54/0x70 ? __i915_gem_object_unset_pages+0x129/0x170 [i915] ? __i915_gem_object_put_pages+0x70/0xa0 [i915] ? __i915_gem_free_objects+0x245/0x4e0 [i915] ? __switch_to_asm+0x24/0x60 ? __i915_gem_free_work+0x65/0xa0 [i915] ? process_one_work+0x1fd/0x410 ? worker_thread+0x49/0x3f0 ? kthread+0xf8/0x130 ? process_one_work+0x410/0x410 ? kthread_park+0x90/0x90 ? ret_from_fork+0x35/0x40 WARNING: CPU: 0 PID: 105 at native_smp_send_reschedule+0x34/0x40 ---[ end trace 7dd2184d8c86cef5 ]--- ------------[ cut here ]------------ sched: Unexpected reschedule of offline CPU#2! WARNING: CPU: 0 PID: 105 at native_smp_send_reschedule+0x34/0x40 Modules linked in: netconsole ccm snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic intel_powerclamp coretemp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel ghash_clmulni_intel arc4 iwldvm aesni_intel aes_x86_64 crypto_simd cryptd mac80211 glue_helper intel_cstate iwlwifi intel_uncore i915 intel_gtt i2c_algo_bit iosf_mbi drm_kms_helper cfbfillrect syscopyarea intel_ips cfbimgblt sysfillrect sysimgblt fb_sys_fops cfbcopyarea thinkpad_acpi prime_numbers cfg80211 ledtrig_audio i2c_i801 sg snd_hda_intel led_class snd_hda_codec drm ac drm_panel_orientation_quirks snd_hwdep battery e1000e agpgart snd_hda_core snd_pcm snd_timer ptp snd soundcore pps_core ehci_pci ehci_hcd lpc_ich video mfd_core button acpi_cpufreq ecryptfs ip_tables x_tables ipv6 evdev thermal [last unloaded: net console] CPU: 0 PID: 105 Comm: kworker/u8:3 Tainted: G W 4.20.0-rc7b1+ #1 Hardware name: LENOVO 3680FBU/3680FBU, BIOS 6QET70WW (1.40 ) 10/11/2012 Workqueue: i915 __i915_gem_free_work [i915] RIP: 0010:native_smp_send_reschedule+0x34/0x40 Code: 05 69 c6 c9 00 73 15 48 8b 05 18 2d b3 00 be fd 00 00 00 48 8b 40 30 e9 9a 58 7d 00 89 fe 48 c7 c7 78 73 af 81 e8 dc c2 01 00 <0f> 0b c3 66 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 05 0d 7d df RSP: 0018:ffff888075003d10 EFLAGS: 00010086 RAX: 000000000000002e RBX: ffff888075120740 RCX: 0000000000000006 RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff888075015440 RBP: ffff88807378b700 R08: 0000000000000000 R09: ffff888072fc07c0 R10: ffff888075003cd8 R11: 00000000ffeb4a02 R12: ffff888075120740 R13: ffff888075120740 R14: 0000000000000004 R15: 0000000000000002 FS: 0000000000000000(0000) GS:ffff888075000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fdb1f53f000 CR3: 0000000001c0a004 CR4: 00000000000206f0 Call Trace: <IRQ> ? check_preempt_curr+0x4e/0x90 ? ttwu_do_wakeup.isra.19+0x14/0xf0 ? try_to_wake_up+0x323/0x410 ? __wake_up_common+0x8d/0x140 ? ep_poll_callback+0xbd/0x2a0 ? __wake_up_common+0x8d/0x140 ? __wake_up_common_lock+0x6c/0x90 ? irq_work_run_list+0x49/0x80 ? tick_sched_handle.isra.6+0x50/0x50 ? update_process_times+0x3b/0x50 ? tick_sched_handle.isra.6+0x30/0x50 ? tick_sched_timer+0x3b/0x80 ? __hrtimer_run_queues+0xea/0x270 ? hrtimer_interrupt+0x101/0x240 ? smp_apic_timer_interrupt+0x6a/0x150 ? apic_timer_interrupt+0xf/0x20 </IRQ> ? panic+0x1ca/0x212 ? panic+0x1c7/0x212 ? __iommu_flush_iotlb+0x19e/0x1c0 ? iommu_flush_iotlb_psi+0x96/0xf0 ? intel_unmap+0xbf/0xf0 ? i915_gem_object_put_pages_gtt+0x36/0x220 [i915] ? drm_ht_remove+0x20/0x20 [drm] ---[ end trace 7dd2184d8c86cef6 ]---
Thanks. I barely use graphics and certainly not with KVM; so I don't think I'll be missing anything igfx_off. But maybe this bugreport can help other X201 users.
Quoting Eric Wong (2018-12-27 13:49:48)
Quoted 9 lines
I just got a used Thinkpad X201 (Core i5 M 520, Intel QM57 chipset) and hit some kernel panics while trying to view image/animation-intensive stuff in Firefox (X11) unless I use "iommu_intel=igfx_off".
With Debian stable backport kernels, "linux-image-4.17.0-0.bpo.3-amd64" (4.17.17-1~bpo9+1) has no problems. But "linux-image-4.18.0-0.bpo.3-amd64" (4.18.20-2~bpo9+1) gives a blank screen before I can login via agetty and run startx.
Could you open a new bug at (and attach relevant information there):
https://01.org/linuxgraphics/documentation/how-report-bugs
Most confusing about this is that 4.17 would have worked to begin with, without intel_iommu=igfx_off (unless it was the default for older kernel?)
Did you maybe update other parts of the system while updating the kernel?
If you could attach full boot dmesg from working and non-working kernel + have config file of both kernel's in Bugzilla. That'd be a good start!
Regards, Joonas
Quoted 16 lines
Building 4.19.12 myself got me into X11 and able to start Firefox to panic the kernel. I also updated to the latest BIOS (1.40), but it's an EOL laptop (but it's still the most powerful laptop I use). I intend to replace the BIOS with Coreboot soon...
Initially, I thought I was hitting another GPU hang from 4.18+:
https://bugs.freedesktop.org/show_bug.cgi?id=107945But building drm-tip @ commit
28bb1fc015cedadf3b099b8bd0bb27609849f362("drm-tip: 2018y-12m-25d-08h-12m-37s UTC integration manifest") I was still able to reproduce the panic unless I use iommu_intel=igfx_off "i915.reset=1" did not help matters, either.Below is what I got from netconsole while on drm-tip:
Quoted 8 lines
Kernel panic - not syncing: DMAR hardware is malfunctioning Shutting down cpus with NMI Kernel Offset: disabled ---[ end Kernel panic - not syncing: DMAR hardware is malfunctioning ]--- ------------[ cut here ]------------ sched: Unexpected reschedule of offline CPU#3! WARNING: CPU: 0 PID: 105 at native_smp_send_reschedule+0x34/0x40 Modules linked in: netconsole ccm snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic intel_powerclamp coretemp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel ghash_clmulni_intel arc4 iwldvm aesni_intel aes_x86_64 crypto_simd cryptd mac80211 glue_helper intel_cstate iwlwifi intel_uncore i915 intel_gtt i2c_algo_bit iosf_mbi drm_kms_helper cfbfillrect syscopyarea intel_ips cfbimgblt sysfillrect sysimgblt fb_sys_fops cfbcopyarea thinkpad_acpi prime_numbers cfg80211 ledtrig_audio i2c_i801 sg snd_hda_intel led_class snd_hda_codec drm ac drm_panel_orientation_quirks snd_hwdep battery e1000e agpgart snd_hda_core snd_pcm snd_timer ptp snd soundcore pps_core ehci_pci ehci_hcd lpc_ich video mfd_core button acpi_cpufreq ecryptfs ip_tables x_tables ipv6 evdev thermal [last unloaded: n
etconsole]
Quoted 50 lines
CPU: 0 PID: 105 Comm: kworker/u8:3 Not tainted 4.20.0-rc7b1+ #1 Hardware name: LENOVO 3680FBU/3680FBU, BIOS 6QET70WW (1.40 ) 10/11/2012 Workqueue: i915 __i915_gem_free_work [i915] RIP: 0010:native_smp_send_reschedule+0x34/0x40 Code: 05 69 c6 c9 00 73 15 48 8b 05 18 2d b3 00 be fd 00 00 00 48 8b 40 30 e9 9a 58 7d 00 89 fe 48 c7 c7 78 73 af 81 e8 dc c2 01 00 <0f> 0b c3 66 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 05 0d 7d df RSP: 0018:ffff888075003d98 EFLAGS: 00010092 RAX: 000000000000002e RBX: ffff8880751a0740 RCX: 0000000000000006 RDX: 0000000000000007 RSI: 0000000000000082 RDI: ffff888075015440 RBP: ffff88806e823700 R08: 0000000000000000 R09: ffff888072fc07c0 R10: ffff888075003d60 R11: 00000000fff5c002 R12: ffff8880751a0740 R13: ffff8880751a0740 R14: 0000000000000000 R15: 0000000000000003 FS: 0000000000000000(0000) GS:ffff888075000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fdb1f53f000 CR3: 0000000001c0a004 CR4: 00000000000206f0 Call Trace: <IRQ> ? check_preempt_curr+0x4e/0x90 ? ttwu_do_wakeup.isra.19+0x14/0xf0 ? try_to_wake_up+0x323/0x410 ? autoremove_wake_function+0xe/0x30 ? __wake_up_common+0x8d/0x140 ? __wake_up_common_lock+0x6c/0x90 ? irq_work_run_list+0x49/0x80 ? tick_sched_handle.isra.6+0x50/0x50 ? update_process_times+0x3b/0x50 ? tick_sched_handle.isra.6+0x30/0x50 ? tick_sched_timer+0x3b/0x80 ? __hrtimer_run_queues+0xea/0x270 ? hrtimer_interrupt+0x101/0x240 ? smp_apic_timer_interrupt+0x6a/0x150 ? apic_timer_interrupt+0xf/0x20 </IRQ> ? panic+0x1ca/0x212 ? panic+0x1c7/0x212 ? __iommu_flush_iotlb+0x19e/0x1c0 ? iommu_flush_iotlb_psi+0x96/0xf0 ? intel_unmap+0xbf/0xf0 ? i915_gem_object_put_pages_gtt+0x36/0x220 [i915] ? drm_ht_remove+0x20/0x20 [drm] ? drm_mm_remove_node+0x1ad/0x310 [drm] ? __pm_runtime_resume+0x54/0x70 ? __i915_gem_object_unset_pages+0x129/0x170 [i915] ? __i915_gem_object_put_pages+0x70/0xa0 [i915] ? __i915_gem_free_objects+0x245/0x4e0 [i915] ? __switch_to_asm+0x24/0x60 ? __i915_gem_free_work+0x65/0xa0 [i915] ? process_one_work+0x1fd/0x410 ? worker_thread+0x49/0x3f0 ? kthread+0xf8/0x130 ? process_one_work+0x410/0x410
Quoted 8 lines
? kthread_park+0x90/0x90 ? ret_from_fork+0x35/0x40 WARNING: CPU: 0 PID: 105 at native_smp_send_reschedule+0x34/0x40 ---[ end trace 7dd2184d8c86cef5 ]--- ------------[ cut here ]------------ sched: Unexpected reschedule of offline CPU#2! WARNING: CPU: 0 PID: 105 at native_smp_send_reschedule+0x34/0x40 Modules linked in: netconsole ccm snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic intel_powerclamp coretemp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel ghash_clmulni_intel arc4 iwldvm aesni_intel aes_x86_64 crypto_simd cryptd mac80211 glue_helper intel_cstate iwlwifi intel_uncore i915 intel_gtt i2c_algo_bit iosf_mbi drm_kms_helper cfbfillrect syscopyarea intel_ips cfbimgblt sysfillrect sysimgblt fb_sys_fops cfbcopyarea thinkpad_acpi prime_numbers cfg80211 ledtrig_audio i2c_i801 sg snd_hda_intel led_class snd_hda_codec drm ac drm_panel_orientation_quirks snd_hwdep battery e1000e agpgart snd_hda_core snd_pcm snd_timer ptp snd soundcore pps_core ehci_pci ehci_hcd lpc_ich video mfd_core button acpi_cpufreq ecryptfs ip_tables x_tables ipv6 evdev thermal [last unloaded: n
etconsole]
Quoted 46 lines
CPU: 0 PID: 105 Comm: kworker/u8:3 Tainted: G W 4.20.0-rc7b1+ #1 Hardware name: LENOVO 3680FBU/3680FBU, BIOS 6QET70WW (1.40 ) 10/11/2012 Workqueue: i915 __i915_gem_free_work [i915] RIP: 0010:native_smp_send_reschedule+0x34/0x40 Code: 05 69 c6 c9 00 73 15 48 8b 05 18 2d b3 00 be fd 00 00 00 48 8b 40 30 e9 9a 58 7d 00 89 fe 48 c7 c7 78 73 af 81 e8 dc c2 01 00 <0f> 0b c3 66 0f 1f 84 00 00 00 00 00 66 66 66 66 90 8b 05 0d 7d df RSP: 0018:ffff888075003d10 EFLAGS: 00010086 RAX: 000000000000002e RBX: ffff888075120740 RCX: 0000000000000006 RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff888075015440 RBP: ffff88807378b700 R08: 0000000000000000 R09: ffff888072fc07c0 R10: ffff888075003cd8 R11: 00000000ffeb4a02 R12: ffff888075120740 R13: ffff888075120740 R14: 0000000000000004 R15: 0000000000000002 FS: 0000000000000000(0000) GS:ffff888075000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fdb1f53f000 CR3: 0000000001c0a004 CR4: 00000000000206f0 Call Trace: <IRQ> ? check_preempt_curr+0x4e/0x90 ? ttwu_do_wakeup.isra.19+0x14/0xf0 ? try_to_wake_up+0x323/0x410 ? __wake_up_common+0x8d/0x140 ? ep_poll_callback+0xbd/0x2a0 ? __wake_up_common+0x8d/0x140 ? __wake_up_common_lock+0x6c/0x90 ? irq_work_run_list+0x49/0x80 ? tick_sched_handle.isra.6+0x50/0x50 ? update_process_times+0x3b/0x50 ? tick_sched_handle.isra.6+0x30/0x50 ? tick_sched_timer+0x3b/0x80 ? __hrtimer_run_queues+0xea/0x270 ? hrtimer_interrupt+0x101/0x240 ? smp_apic_timer_interrupt+0x6a/0x150 ? apic_timer_interrupt+0xf/0x20 </IRQ> ? panic+0x1ca/0x212 ? panic+0x1c7/0x212 ? __iommu_flush_iotlb+0x19e/0x1c0 ? iommu_flush_iotlb_psi+0x96/0xf0 ? intel_unmap+0xbf/0xf0 ? i915_gem_object_put_pages_gtt+0x36/0x220 [i915] ? drm_ht_remove+0x20/0x20 [drm] ---[ end trace 7dd2184d8c86cef6 ]---Thanks. I barely use graphics and certainly not with KVM; so I don't think I'll be missing anything
igfx_off. But maybe this bugreport can help other X201 users.
Quoted 6 lines · Joonas Lahtinen
Quoting Eric Wong (2018-12-27 13:49:48)
Quoted 5 lines
I just got a used Thinkpad X201 (Core i5 M 520, Intel QM57 chipset) and hit some kernel panics while trying to view image/animation-intensive stuff in Firefox (X11) unless I use "iommu_intel=igfx_off".
Quoted 8 lines
Quoted 4 lines
With Debian stable backport kernels, "linux-image-4.17.0-0.bpo.3-amd64" (4.17.17-1~bpo9+1) has no problems. But "linux-image-4.18.0-0.bpo.3-amd64" (4.18.20-2~bpo9+1) gives a blank screen before I can login via agetty and run startx.
Most confusing about this is that 4.17 would have worked to begin with, without intel_iommu=igfx_off (unless it was the default for older kernel?)
Yeah, so the Debian bpo 4.17(.17) kernel did not set CONFIG_INTEL_IOMMU_DEFAULT_ON, so I didn't encounter problems. My self-built kernels all set CONFIG_INTEL_IOMMU_DEFAULT_ON.
Booting the Debian 4.17 kernel with "intel_iommu=on" gives the same hanging problem I hit with self-built 4.19.{12,13} kernels.
I'm not sure how far back the problem goes (maybe forever), since I only got this hardware. Not sure what's the problem with Debian 4.18, either; but (self-built) 4.19.13 is fine w/o CONFIG_INTEL_IOMMU_DEFAULT_ON.
Debian backports doesn't have kernels for 4.19 or 4.20, yet.
Quoted 2 lines
Did you maybe update other parts of the system while updating the kernel?
Definitely not; just the kernel + headers ("make bindeb-pkg)".
Quoted 2 lines
If you could attach full boot dmesg from working and non-working kernel + have config file of both kernel's in Bugzilla. That'd be a good start!
Sorry, I get anxiety attacks when it comes to logins and forms. Anyways, I managed to get the Debian kernel dmesg output uploaded with and without iommu_intel=on:
https://bugs.freedesktop.org/attachment.cgi?bugid=109219
Quoting Eric Wong (2019-01-04 03:06:26)
Quoted 12 lines
Quoted 10 lines · Joonas Lahtinen
Quoting Eric Wong (2018-12-27 13:49:48)
Quoted 9 lines
I just got a used Thinkpad X201 (Core i5 M 520, Intel QM57 chipset) and hit some kernel panics while trying to view image/animation-intensive stuff in Firefox (X11) unless I use "iommu_intel=igfx_off".
With Debian stable backport kernels, "linux-image-4.17.0-0.bpo.3-amd64" (4.17.17-1~bpo9+1) has no problems. But "linux-image-4.18.0-0.bpo.3-amd64" (4.18.20-2~bpo9+1) gives a blank screen before I can login via agetty and run startx.
Quoted 7 lines
Quoted 3 lines
Most confusing about this is that 4.17 would have worked to begin with, without intel_iommu=igfx_off (unless it was the default for older kernel?)
Yeah, so the Debian bpo 4.17(.17) kernel did not set
CONFIG_INTEL_IOMMU_DEFAULT_ON, so I didn't encounter problems. My self-built kernels all setCONFIG_INTEL_IOMMU_DEFAULT_ON.
So it's the case that IOMMU never worked on your machine.
My recommendation would be to simply use intel_iommu=igfx_off if you need IOMMU.
Old hardware is known to have issues with IOMMU, and retroactively enabling IOMMU on those machines just brings them up :/
Regards, Joonas
Quoted 15 lines
Booting the Debian 4.17 kernel with "intel_iommu=on" gives the same hanging problem I hit with self-built 4.19.{12,13} kernels.
I'm not sure how far back the problem goes (maybe forever), since I only got this hardware. Not sure what's the problem with Debian 4.18, either; but (self-built) 4.19.13 is fine w/o
CONFIG_INTEL_IOMMU_DEFAULT_ON.Debian backports doesn't have kernels for 4.19 or 4.20, yet.
Quoted 2 lines
Did you maybe update other parts of the system while updating the kernel?
Definitely not; just the kernel + headers ("make bindeb-pkg)".
Quoted 7 lines
Quoted 2 lines
If you could attach full boot dmesg from working and non-working kernel + have config file of both kernel's in Bugzilla. That'd be a good start!
Sorry, I get anxiety attacks when it comes to logins and forms. Anyways, I managed to get the Debian kernel dmesg output uploaded with and without iommu_intel=on:
https://bugs.freedesktop.org/attachment.cgi?bugid=109219
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
PATCH 1/1 iommu/intel: quirk to disable DMAR for QM57 igfx
Quoted 5 lines · Joonas Lahtinen
Quoting Eric Wong (2019-01-04 03:06:26)
Quoted 3 lines
Yeah, so the Debian bpo 4.17(.17) kernel did not set
CONFIG_INTEL_IOMMU_DEFAULT_ON, so I didn't encounter problems. My self-built kernels all setCONFIG_INTEL_IOMMU_DEFAULT_ON.
Quoted 7 lines
So it's the case that IOMMU never worked on your machine.
My recommendation would be to simply use intel_iommu=igfx_off if you need IOMMU.
Old hardware is known to have issues with IOMMU, and retroactively enabling IOMMU on those machines just brings them up :/
How about we use a quirk in case distros make IOMMU the default one day?
--------8<--------
Subject: [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx
Like the GM45, it seems the integrated graphics on QM57 seems broken and hanging graphics with "intel_iommu=on". So allow future users to unconditionally enable DMAR support and not have to remember or know to specify "intel_iommu=igfx_off"
cf. https://lore.kernel.org/lkml/20181227114948.ev4b3jte3ubsc5us@dcvr/
cf. https://lore.kernel.org/lkml/154659116310.4596.13613897418163029789@jlahtine-desk.ger.corp.intel.com/
--- drivers/iommu/intel-iommu.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/iommu/intel-iommu.c +2 -2
@@ -5399,7 +5399,7 @@ const struct iommu_ops intel_iommu_ops = {static void quirk_iommu_g4x_gfx (struct pci_dev *dev) { -/* G4x/GM45 integrated gfx dmar support is totally busted. */ +/* G4x/GM45/QM57 integrated gfx dmar support is totally busted. */ pr_info ("Disabling IOMMU for graphics on this chipset\n" ); dmar_map_gfx =0 ; }
@@ -5411,6 +5411,7 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2e20, quirk_iommu_g4x_gfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x2e30 , quirk_iommu_g4x_gfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x2e40 , quirk_iommu_g4x_gfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x2e90 , quirk_iommu_g4x_gfx); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0044 , quirk_iommu_g4x_gfx);static void quirk_iommu_rwbf (struct pci_dev *dev) {
@@ -5457,7 +5458,6 @@ static void quirk_calpella_no_shadow_gtt(struct pci_dev *dev) } }DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0040 , quirk_calpella_no_shadow_gtt); -DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0044 , quirk_calpella_no_shadow_gtt);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0062 , quirk_calpella_no_shadow_gtt);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x006a , quirk_calpella_no_shadow_gtt);
Signature · 1 line
EW
Joerg Roedel
maintainerRe: [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx
Quoted 9 lines · Eric Wong
drivers/iommu/intel-iommu.c +1
-0@@ -5411,6 +5411,7 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2e20, quirk_iommu_g4x_gfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x2e30 , quirk_iommu_g4x_gfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x2e40 , quirk_iommu_g4x_gfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x2e90 , quirk_iommu_g4x_gfx); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0044 , quirk_iommu_g4x_gfx);static void quirk_iommu_rwbf (struct pci_dev *dev) {
drivers/iommu/intel-iommu.c static void quirk_calpella_no_shadow_gtt(struct pci_dev *dev) · line 5462
Quoted 6 lines
drivers/iommu/intel-iommu.c +0
-1@@ -5457,7 +5458,6 @@ static void quirk_calpella_no_shadow_gtt(struct pci_dev *dev) } }DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0040 , quirk_calpella_no_shadow_gtt); -DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0044 , quirk_calpella_no_shadow_gtt);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0062 , quirk_calpella_no_shadow_gtt);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x006a , quirk_calpella_no_shadow_gtt);
This seems to make sense to me. Joonas, any comments or objections?
Regards,
Joerg
Re: [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx
Quoted 8 lines · Joerg Roedel
Quoted 6 lines · Eric Wong
drivers/iommu/intel-iommu.c +1
-0@@ -5411,6 +5411,7 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2e20, quirk_iommu_g4x_gfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x2e30 , quirk_iommu_g4x_gfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x2e40 , quirk_iommu_g4x_gfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x2e90 , quirk_iommu_g4x_gfx); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0044 , quirk_iommu_g4x_gfx);
Quoted 11 lines
drivers/iommu/intel-iommu.c static void quirk_calpella_no_shadow_gtt(struct pci_dev *dev) · line 5462
Quoted 9 lines
drivers/iommu/intel-iommu.c +0
-1static void quirk_iommu_rwbf (struct pci_dev *dev) {@@ -5457,7 +5458,6 @@ static void quirk_calpella_no_shadow_gtt(struct pci_dev *dev) } }DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0040 , quirk_calpella_no_shadow_gtt); -DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0044 , quirk_calpella_no_shadow_gtt);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0062 , quirk_calpella_no_shadow_gtt);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x006a , quirk_calpella_no_shadow_gtt);This seems to make sense to me. Joonas, any comments or objections?
This is ironlake, which has a huge iommu hack in the gpu driver to work around hard hangs, which:
- causes massive stalls and kills performance
- isn't well tested (it's the only one that needs this), so tends to break
So if we do this then imo we should:
- probably nuke that w/a too (check for needs_idle_maps and all the related stuff in i915_gem_gtt.c)
- roll it out for all affected chips (i.e. need to include 0x0040).
Note that the string of platforms which have various issues with iommu and igfx is very long, thus far we only disabled it where there's no workaround to stop it from hanging the box, but otherwise left it enabled. So if we make a policy change to also disable it anywhere where it doesn't work well (instead of not at all), there's a pile more platforms to switch.
-Daniel
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Joerg Roedel
maintainerRe: [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx
Hi Daniel,
Quoted 6 lines · Daniel Vetter
Note that the string of platforms which have various issues with iommu and igfx is very long, thus far we only disabled it where there's no workaround to stop it from hanging the box, but otherwise left it enabled. So if we make a policy change to also disable it anywhere where it doesn't work well (instead of not at all), there's a pile more platforms to switch.
I think its best to just disable iommu for the igfx devices on these platforms. Can you pick up Eric's patch and extend it with the list of affected platforms?
Thanks,
Joerg
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx
Quoting Joerg Roedel (2019-01-22 13:01:09)
Quoted 10 lines
Hi Daniel,
Quoted 6 lines · Daniel Vetter
Note that the string of platforms which have various issues with iommu and igfx is very long, thus far we only disabled it where there's no workaround to stop it from hanging the box, but otherwise left it enabled. So if we make a policy change to also disable it anywhere where it doesn't work well (instead of not at all), there's a pile more platforms to switch.
Quoted 3 lines
I think its best to just disable iommu for the igfx devices on these platforms. Can you pick up Eric's patch and extend it with the list of affected platforms?
We've been discussing this again more actively since a few months ago, and the discussion is still ongoing internally.
According to our IOMMU folks there exists some desire to be able to assign the iGFX device aka have intel_iommu=on instead of intel_iommu=igfx_off due to how the devices might be grouped in IOMMU groups. Even when you would not be using the iGFX device.
So for some uses, the fact that the device (group) is assignable seems to be more important than the iGFX device to be working. I'm afraid that retroactively disabling the assignment for such an old platform might break those usage scenarios. By my quick reading of the code, there's no way for user to turn the iGFX DMAR on once the quirk disables it.
I guess one solution would be to default to intel_iommu=igfx_off for platforms that are older than certain threshold. But still allow user to enable. But that then requires duplicating the PCI ID database into iommu code.
I don't really have winning moves to present, but I'm open to hearing how we can avoid more damage than starting to default to intel_iommu=on did already.
Regards, Joonas
Quoted 4 lines
Thanks,
Joerg
Joerg Roedel
maintainerRe: [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx
Quoted 4 lines · Joonas Lahtinen
According to our IOMMU folks there exists some desire to be able to assign the iGFX device aka have intel_iommu=on instead of intel_iommu=igfx_off due to how the devices might be grouped in IOMMU groups. Even when you would not be using the iGFX device.
You can force the igfx device into a SI domain, or does that also trigger the iommu issues on the chipset?
In any case, if iommu=on breaks these systems I want to make them work again with opt-out, even at the cost of breaking assignability.
Regards,
Joerg
Re: [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx
Quoting Joerg Roedel (2019-01-22 18:51:35)
Quoted 8 lines · Joonas Lahtinen
Quoted 4 lines
According to our IOMMU folks there exists some desire to be able to assign the iGFX device aka have intel_iommu=on instead of intel_iommu=igfx_off due to how the devices might be grouped in IOMMU groups. Even when you would not be using the iGFX device.
You can force the igfx device into a SI domain, or does that also trigger the iommu issues on the chipset?
To be honest, we've had a mixture different issues on different SKUs that have not been hit in the past when intel_iommu was just disabled by default.
I know that in one group of the problems, the issue has been debugged into the GPU having its own set of virtualization mapping translation hardware with caching and it fails to track changes to the mapping. So if a identity mapping was established and never changed, I'd assume that to fix at least that class of problems.
Would just passing intel_iommu=on already cause a non-identity mapping to possibly be used for the integrated GPU? If it did, then it would explain quite few of the issues.
We have many reports where just having intel_iommu=on (and using the system normally, without any virtualization stuff going on) will cause unexplained GPU hangs. For those users, simply switching to intel_iommu=igfx_off solves the problems, and the debug often ends there.
Regards, Joonas
Quoted 6 lines
In any case, if iommu=on breaks these systems I want to make them work again with opt-out, even at the cost of breaking assignability.
Regards,
Joerg
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Joerg Roedel
maintainerRe: [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx
Quoted 5 lines · Joonas Lahtinen
We have many reports where just having intel_iommu=on (and using the system normally, without any virtualization stuff going on) will cause unexplained GPU hangs. For those users, simply switching to intel_iommu=igfx_off solves the problems, and the debug often ends there.
If you can reproduce problems on your side, then you can try to enable CONFIG_INTEL_IOMMU_BROKEN_GFX_WA to force the GFX devices into the identity mapping. We can also add a boot-parameter and workarounds if it turns out that this is sufficient to make the GFX devices work with IOMMU enabled.
Regards,
Joerg
Patchwork
CI✗ Fi.CI.CHECKPATCH: warning for iommu/intel: quirk to disable DMAR for QM57 igfx
In reply to Eric Wong== Series Details ==
== Series Details ==
Series: iommu/intel: quirk to disable DMAR for QM57 igfx
URL : https://patchwork.freedesktop.org/series/55481/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip 1620746a0d85 iommu/intel: quirk to disable DMAR for QM57 igfx -:32: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line) #32: cf. https://lore.kernel.org/lkml/154659116310.4596.13613897418163029789@jlahtine-desk.ger.corp.intel.com/
total: 0 errors, 1 warnings, 0 checks, 22 lines checked
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✓ Fi.CI.BAT: success for iommu/intel: quirk to disable DMAR for QM57 igfx
In reply to Eric Wong== Series Details ==
== Series Details ==
Series: iommu/intel: quirk to disable DMAR for QM57 igfx
URL : https://patchwork.freedesktop.org/series/55481/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5453 -> Patchwork_11991
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/55481/revisions/1/mbox/
Known issues
------------
Here are the changes found in Patchwork_11991 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_module_load@reload-with-fault-injection:
- fi-kbl-7567u: PASS -> DMESG-WARN [fdo#103558] / [fdo#105602] +1
* igt@kms_busy@basic-flip-a:
- fi-gdg-551: PASS -> FAIL [fdo#103182]
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s3:
- fi-skl-6700k2: INCOMPLETE [fdo#104108] / [fdo#107773] -> PASS
* igt@i915_module_load@reload:
- fi-blb-e6850: INCOMPLETE [fdo#107718] -> PASS
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: FAIL [fdo#108767] -> PASS
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
- fi-byt-clapper: FAIL [fdo#103191] / [fdo#107362] -> PASS
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103182]: https://bugs.freedesktop.org/show_bug.cgi?id=103182
[fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
[fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558
[fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108
[fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602
[fdo#107362]: https://bugs.freedesktop.org/show_bug.cgi?id=107362
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#107773]: https://bugs.freedesktop.org/show_bug.cgi?id=107773
[fdo#108767]: https://bugs.freedesktop.org/show_bug.cgi?id=108767
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
Participating hosts (45 -> 42)
------------------------------
Additional (2): fi-hsw-4770r fi-skl-6700hq
Missing (5): fi-kbl-soraka fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-icl-y
Build changes
-------------
* Linux: CI_DRM_5453 -> Patchwork_11991
CI_DRM_5453: a6193985349eec23ebddef0c393cfbc6005b6c7e @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4779: d4199510374514489b1ab56e3416f53f6c1d6291 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_11991: 1620746a0d8512c7a859d99dbf8d91bb615e3073 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
1620746a0d85 iommu/intel: quirk to disable DMAR for QM57 igfx
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_11991/
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✓ Fi.CI.IGT: success for iommu/intel: quirk to disable DMAR for QM57 igfx
In reply to Eric Wong== Series Details ==
== Series Details ==
Series: iommu/intel: quirk to disable DMAR for QM57 igfx
URL : https://patchwork.freedesktop.org/series/55481/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5453_full -> Patchwork_11991_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_11991_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_available_modes_crc@available_mode_test_crc:
- shard-iclb: NOTRUN -> FAIL [fdo#106641]
* igt@kms_busy@extended-modeset-hang-newfb-with-reset-render-c:
- shard-iclb: NOTRUN -> DMESG-WARN [fdo#107956]
* igt@kms_ccs@pipe-a-crc-primary-rotation-180:
- shard-iclb: NOTRUN -> FAIL [fdo#107725] +1
* igt@kms_cursor_crc@cursor-128x128-dpms:
- shard-apl: PASS -> FAIL [fdo#103232]
- shard-glk: PASS -> FAIL [fdo#103232]
* igt@kms_cursor_crc@cursor-128x128-suspend:
- shard-apl: PASS -> FAIL [fdo#103191] / [fdo#103232]
* igt@kms_cursor_crc@cursor-256x256-suspend:
- shard-skl: PASS -> INCOMPLETE [fdo#104108]
* igt@kms_cursor_crc@cursor-64x64-onscreen:
- shard-iclb: NOTRUN -> FAIL [fdo#103232]
* igt@kms_flip@flip-vs-expired-vblank:
- shard-snb: PASS -> INCOMPLETE [fdo#105411]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-pwrite:
- shard-iclb: PASS -> FAIL [fdo#103167] +4
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-onoff:
- shard-apl: PASS -> FAIL [fdo#103167]
* igt@kms_plane@pixel-format-pipe-a-planes-source-clamping:
- shard-glk: PASS -> FAIL [fdo#108948]
* igt@kms_plane@pixel-format-pipe-c-planes:
- shard-skl: NOTRUN -> DMESG-WARN [fdo#106885]
* igt@kms_plane@plane-position-covered-pipe-b-planes:
- shard-glk: PASS -> FAIL [fdo#103166]
* igt@kms_plane_alpha_blend@pipe-a-alpha-basic:
- shard-skl: NOTRUN -> FAIL [fdo#107815] / [fdo#108145]
* igt@kms_plane_alpha_blend@pipe-b-constant-alpha-max:
- shard-apl: NOTRUN -> FAIL [fdo#108145]
* igt@kms_plane_multiple@atomic-pipe-b-tiling-y:
- shard-iclb: PASS -> FAIL [fdo#103166] +1
* igt@kms_plane_multiple@atomic-pipe-c-tiling-y:
- shard-apl: PASS -> FAIL [fdo#103166]
* igt@kms_setmode@basic:
- shard-apl: PASS -> FAIL [fdo#99912]
* igt@kms_sysfs_edid_timing:
- shard-iclb: PASS -> FAIL [fdo#100047]
* igt@pm_rps@min-max-config-loaded:
- shard-iclb: NOTRUN -> FAIL [fdo#102250]
#### Possible fixes ####
* igt@kms_busy@extended-pageflip-modeset-hang-oldfb-render-c:
- shard-iclb: DMESG-WARN [fdo#107956] -> PASS
* igt@kms_color@pipe-c-ctm-max:
- shard-apl: FAIL [fdo#108147] -> PASS
* igt@kms_color@pipe-c-legacy-gamma:
- shard-apl: FAIL [fdo#104782] -> PASS
* igt@kms_cursor_crc@cursor-256x85-onscreen:
- shard-apl: FAIL [fdo#103232] -> PASS +1
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-mmap-gtt:
- shard-apl: FAIL [fdo#103167] -> PASS +1
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move:
- shard-iclb: FAIL [fdo#103167] -> PASS +3
* igt@kms_plane@plane-position-covered-pipe-a-planes:
- shard-apl: FAIL [fdo#103166] -> PASS
- shard-iclb: FAIL [fdo#103166] -> PASS +3
* igt@kms_plane_multiple@atomic-pipe-b-tiling-none:
- shard-glk: FAIL [fdo#103166] -> PASS +1
* igt@kms_rotation_crc@multiplane-rotation-cropping-bottom:
- shard-glk: DMESG-FAIL [fdo#105763] / [fdo#106538] -> PASS
#### Warnings ####
* igt@pm_rpm@dpms-mode-unset-non-lpsp:
- shard-iclb: {SKIP} [fdo#109308] -> INCOMPLETE [fdo#108840]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#100047]: https://bugs.freedesktop.org/show_bug.cgi?id=100047
[fdo#102250]: https://bugs.freedesktop.org/show_bug.cgi?id=102250
[fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103191]: https://bugs.freedesktop.org/show_bug.cgi?id=103191
[fdo#103232]: https://bugs.freedesktop.org/show_bug.cgi?id=103232
[fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108
[fdo#104782]: https://bugs.freedesktop.org/show_bug.cgi?id=104782
[fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411
[fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763
[fdo#106538]: https://bugs.freedesktop.org/show_bug.cgi?id=106538
[fdo#106641]: https://bugs.freedesktop.org/show_bug.cgi?id=106641
[fdo#106885]: https://bugs.freedesktop.org/show_bug.cgi?id=106885
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107725]: https://bugs.freedesktop.org/show_bug.cgi?id=107725
[fdo#107815]: https://bugs.freedesktop.org/show_bug.cgi?id=107815
[fdo#107956]: https://bugs.freedesktop.org/show_bug.cgi?id=107956
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#108147]: https://bugs.freedesktop.org/show_bug.cgi?id=108147
[fdo#108840]: https://bugs.freedesktop.org/show_bug.cgi?id=108840
[fdo#108948]: https://bugs.freedesktop.org/show_bug.cgi?id=108948
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109277]: https://bugs.freedesktop.org/show_bug.cgi?id=109277
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109281]: https://bugs.freedesktop.org/show_bug.cgi?id=109281
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109286]: https://bugs.freedesktop.org/show_bug.cgi?id=109286
[fdo#109287]: https://bugs.freedesktop.org/show_bug.cgi?id=109287
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109290]: https://bugs.freedesktop.org/show_bug.cgi?id=109290
[fdo#109291]: https://bugs.freedesktop.org/show_bug.cgi?id=109291
[fdo#109293]: https://bugs.freedesktop.org/show_bug.cgi?id=109293
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#109305]: https://bugs.freedesktop.org/show_bug.cgi?id=109305
[fdo#109308]: https://bugs.freedesktop.org/show_bug.cgi?id=109308
[fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912
Participating hosts (7 -> 7)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_5453 -> Patchwork_11991
CI_DRM_5453: a6193985349eec23ebddef0c393cfbc6005b6c7e @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_4779: d4199510374514489b1ab56e3416f53f6c1d6291 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_11991: 1620746a0d8512c7a859d99dbf8d91bb615e3073 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_11991/
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx