Bug 109219

Summary: iommu_intel=on + i915 incompatibility in 4.17, 4.19.13 and drm-tip
Product: DRI Reporter: e+i915
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED WORKSFORME QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: e+i915, intel-gfx-bugs, joonas.lahtinen
Version: DRI git   
Hardware: Other   
OS: All   
URL: https://lore.kernel.org/lkml/20181227114948.ev4b3jte3ubsc5us@dcvr/T/
Whiteboard: Triaged
i915 platform: ILK i915 features:
Attachments:
Description Flags
dmesg output with without iommu_intel set
none
dmesg output with iommu_on
none
Debian 4.17 config none

Description e+i915 2019-01-04 00:55:28 UTC
Created attachment 142968 [details]
dmesg output with without iommu_intel set

iommu_intel=on fails with i915 on x201 Thinkpad.

Thread on LKML: https://lore.kernel.org/lkml/20181227114948.ev4b3jte3ubsc5us@dcvr/T/
Comment 1 e+i915 2019-01-04 00:56:17 UTC
Created attachment 142969 [details]
dmesg output with iommu_on
Comment 2 e+i915 2019-01-04 00:57:12 UTC
Created attachment 142970 [details]
Debian 4.17 config
Comment 3 Lakshmi 2019-07-03 08:28:00 UTC
My apologies for responding on this issue so late.

@Joonas, any suggestion how to proceed with this issue?
Comment 4 Lakshmi 2019-08-28 10:07:03 UTC
> 
> Thread on LKML:
> https://lore.kernel.org/lkml/20181227114948.ev4b3jte3ubsc5us@dcvr/T/
In the attached logs I can not find the same warnings as mentioned in link.

Reporter, do you still see the kernel panics? Can you reproduce the issue with drmtip? (https://cgit.freedesktop.org/drm-tip).
Comment 5 Chris Wilson 2019-09-07 17:21:53 UTC
Note that Ironlake igfx + iommu is known to be a bad mix -- the gpu cannot be active while iommu is remapped, it seems doubtful that we are able to do that or if that is the only workaround required.
Comment 6 Lakshmi 2019-10-03 06:47:27 UTC
No response from the user for more than 2 months. Resolving this issue as WORKSFORME.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.