Summary: | [BDW] i915: GPU hang with intel_iommu=on | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | stsp2 | ||||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Severity: | normal | ||||||||||
Priority: | medium | CC: | intel-gfx-bugs, pothos, yunying.sun | ||||||||
Version: | XOrg git | ||||||||||
Hardware: | Other | ||||||||||
OS: | All | ||||||||||
Whiteboard: | ReadyForDev | ||||||||||
i915 platform: | BDW | i915 features: | GPU hang | ||||||||
Attachments: |
|
Created attachment 130222 [details]
lspci
Created attachment 130223 [details]
/sys/class/drm/card0/error
There are a few similar reports in this bugzilla, but please note that my dmesg ends with Oops. So probably it gives more info. Adding tag into "Whiteboard" field - ReadyForDev *Status is correct *Platform is included *Feature is included *Priority and Severity correctly set *Logs included *** Bug 100076 has been marked as a duplicate of this bug. *** |
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.
Created attachment 130221 [details] dmesg With intel_iommu=on in command line, GPU hangs at boot, after which, the entire machine freeze happens. I managed to retrieve logs by using "linux=single" - it helps to avoid the full machine freeze sometimes (maybe because X doesn't start then), but its still a blank screen. intel_iommu=on,igfx_off fixes the problem but I guess this will not allow to pass-through the video card, is this correct?