[bdw-u iommu] DMAR error -> GPU hang
Submitted by Stefan Junker
Assigned to Joonas Lahtinen @dolphin
Description
Created attachment 113867
kernel log
The system randomly freezes and doesn't react to anything afterwards. Not even the magic keys can reboot the system.
Processor model is Intel Core-i7 5500U with the integrated GPU.
Kernel version is 4.0.0-rc1, which is required to even get X / gdm working with the system.
I've attached the kernel log messages which shows an instance of this problem.
Please request any information needed and I'll happily provide it.
steveeJ
Attachment 113867, "kernel log":
drm_i915_crash.log
Activity
added Community GPU hang feature: GEM platform: BDW priority::high severity::critical + 1 deleted label
Short version
---
adding 'intel_iommu=igfx_off' helped
Long version
---
I've tried many things to resolve this issue, from kernel reconfiguration to installing mesa, libdrm, intel drivers from latest repository masters, which all didn't help. I reverted back to the most recent releases of the packages.
From an older forum entry somewhere on the webs I found that this could be related to virtualization techologies and memory remapping, so I added the following arguments to my kernel commandline: 'intel_iommu=igfx_off'
Ever since (about 10-15 hours of very active usage) I haven't had a single freeze.
I still think this is not normal behavior, since turning off iommu for the GPU can't be the right or necessary thing to do.
Attachment 113998, "bpowers' dmesg":
gpu.hang.1Attachment 113999, "bpowers' GPU crash dump":
gpu.hang.error.1some additional info - my BIOS (3rd gen x1 carbon) apparently marks x2apic as broken. I booted a number of times with intremap=no_x2apic_optout on the kernel command line, and saw what steveej mentioned: a hard freeze.
The system did have the foresight to save the dmesg into the EFI pstore. I have those logs if they are useful.
After removing no_x2apic_optout, the kernel "Enabled IRQ remapping in xapic mode", and under xapic some of the time the kernel was able to recover/reset the chip to an ok-enough state that I could save dmesg and grap the GPU dump from /sys/class/drm/card0/error.
@ickleclosed a related bug:*** Bug 90823 has been marked as a duplicate of this bug. ***
@ickleclosed a related bug:*** Bug 90091 has been marked as a duplicate of this bug. ***
@ickleclosed a related bug:*** Bug 91076 has been marked as a duplicate of this bug. ***
@icklesaid:In bug 91076, the hangs are anything but random. Simply initialising execlists is enough for the GPU to die.
@ickleclosed a related bug:*** Bug 91152 has been marked as a duplicate of this bug. ***
@icklesaid:Quick experiment from bug 91152 indicates that this is a problem with or without execlists enabled.
@ickleclosed a related bug:*** Bug 91458 has been marked as a duplicate of this bug. ***
I found the same problem as in comment 4. If I disable VT-d in the BIOS the crashes disappear. But then I get random segmentation faults from GCC if I try to compile QtWebKit (N.b: I have gentoo and compile all packages by myself.) Hence, I have two options
(1) Disable VT-d for daily work such that i915 does not crash
(2) Enable VT-d and only boot into text console mode if I need to compile QtWebKit
My hardware is
Lenovo Thinkpad X1 Carbon (3rd generation, type 20BT)
Processor Intel Core i5-5200U
Memory: 8 GB PC3-12800L
BIOS: Phoenix, ver. 1.09, 7/22/2015
Interestingly, MemTest86 does not report any memory error in either case (with and without VT-d)@ickleclosed a related bug:*** Bug 91633 has been marked as a duplicate of this bug. ***
@ickleclosed a related bug:*** Bug 91764 has been marked as a duplicate of this bug. ***
I'm not sure if 91764 really is a duplicate of this bug. intel_iommu=igfx_off doesn't help in my case.
In my case this issue (googling for the opcode hanging the GPU lead me to this bug) was solved by disabling the EFI Framebuffer on the kernel configuration.
If the devs want I can open a second bug to request the Intel GFX drivers taking over from early framebuffers (for example EFI or VGA) to prevent my particular issues.@dwmw2said:Looking at the first two dumps, this looks like it might be a simple driver bug. The driver forgets to use the DMA API and wrongly just hands a physical address to the device. The device does DMA to that invalid address, takes a well-deserved fault, and is subsequently unhappy.
The faulting addresses do not look like addresses which would be given out as virtual DMA addresses by the DMA API. Such addresses would typically start at 0xfffff000 and grow downwards.I reported bug #90091 initially, which was marked as duplicate of this one.
I've tried to reproduce with 4.2.2, and it still happens. Two dmesgs are attached, the second one with i915.enable_execlists=0. In the latter case I only have the DMAR fault but not the GPU hang.Attachment 118605, "kernel log on 4.2.2":
dmesg.txtSecond log, with execlists disabled. Actually in the meantime I managed to get a GPU hang.
Attachment 118606, "kernel log on 4.2.2 with execlists disabled":
dmesg-execlist_0.txt@ickleclosed a related bug:*** Bug 92531 has been marked as a duplicate of this bug. ***
I have the same problem, and Google Chrome (as in the binary release, not Chromium) seems to trigger it. Disabling 3D rendering in X has helped, as now I get a crash and hang every couple of weeks instead of around once a day.
Here's my uname output, in case it helps:
Linux laurana 4.0.5-gentoo #5 (closed) SMP Tue Sep 22 09:45:32 CEST 2015 x86_64 Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz GenuineIntel GNU/Linux
I'll try the 'intel_iommu=igfx_off' kernel option and see if that improves matters. Failing that, I'll disable VT-d, unless it is required by Docker.
If I can provide any helpful info, please let me know and I'll be happy to do so.*** Bug 92905 has been marked as a duplicate of this bug. ***
@ickleclosed a related bug:*** Bug 94229 has been marked as a duplicate of this bug. ***
I have here an Dell XPS 13 9350 2016 (Intel Core i7-6560U ) and have installed Fedora 23 (GNOME), currently on Kernel 4.4.5-300.fc23.x86_64.
As soon I open Chrome or Firefox and let’s say open YouTube after few second whole laptop will hang, totally unresponsible. Need to press Power ON button for few seconds to power of the device.
Once I was able to get log and its attached.
I added "intel_iommu=igfx_off" to /etc/default/grub and regenerated GRUB ( grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg) but it does not solve the problem here.
If any more info is needed I would be glad to provide them to you. I hope I will be able to use my new Notebook without issue.Attachment 122465, "Resetting chip after gpu hang":
xps13_gpuhang01.txt[Mon Mar 21 18:02:39 2016] i915 0000:00:02.0: Invalid ROM contents
[Mon Mar 21 18:04:52 2016] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[Mon Mar 21 18:05:54 2016] [drm] stuck on render ring
[Mon Mar 21 18:05:54 2016] [drm] GPU HANG: ecode 9:0:0x85dfbfff, in chrome [3398], reason: Ring hung, action: reset
[Mon Mar 21 18:05:54 2016] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[Mon Mar 21 18:05:54 2016] [drm] Please file a new bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[Mon Mar 21 18:05:54 2016] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[Mon Mar 21 18:05:54 2016] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[Mon Mar 21 18:05:54 2016] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[Mon Mar 21 18:05:54 2016] ------------[ cut here ]------------
[Mon Mar 21 18:05:54 2016] WARNING: CPU: 1 PID: 423 at drivers/gpu/drm/i915/intel_display.c:11289 intel_mmio_flip_work_func+0x387/0x3d0 i915
[Mon Mar 21 18:05:54 2016] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
[Mon Mar 21 18:05:54 2016] Modules linked in:
[Mon Mar 21 18:05:54 2016] rfcomm fuse cmac xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_broute bridge stp llc ebtable_filter ebtable_nat ebtables ip6table_security ip6table_mangle ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables iptable_security iptable_mangle iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bnep hid_multitouch snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal coretemp snd_soc_skl dell_led snd_soc_skl_ipc snd_hda_ext_core kvm_intel snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm snd_hda_codec_realtek vfat snd_hda_codec_generic fat snd_compress snd_pcm_dmaengine ac97_bus
[Mon Mar 21 18:05:54 2016] dell_wmi sparse_keymap dw_dmac_core i2c_designware_platform dell_laptop i2c_designware_core snd_hda_intel irqbypass dcdbas brcmfmac snd_hda_codec brcmutil snd_hda_core snd_hwdep cfg80211 snd_seq snd_seq_device uvcvideo rtsx_pci_ms snd_pcm videobuf2_vmalloc memstick videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common joydev snd_timer videodev snd mei_me btusb i2c_i801 soundcore btrtl idma64 media mei shpchp intel_lpss_pci hci_uart wmi btbcm btqca btintel bluetooth pinctrl_sunrisepoint pinctrl_intel rfkill intel_lpss_acpi intel_lpss processor_thermal_device int3403_thermal int340x_thermal_zone int3400_thermal intel_soc_dts_iosf acpi_als iosf_mbi acpi_thermal_rel kfifo_buf acpi_pad industrialio tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt i915 rtsx_pci_sdmmc mmc_core
[Mon Mar 21 18:05:54 2016] crct10dif_pclmul crc32_pclmul crc32c_intel i2c_algo_bit drm_kms_helper drm serio_raw nvme rtsx_pci i2c_hid video fjes
[Mon Mar 21 18:05:54 2016] CPU: 1 PID: 423 Comm: kworker/1:3 Not tainted 4.4.5-300.fc23.x86_64 #1 (moved)
[Mon Mar 21 18:05:54 2016] Hardware name: Dell Inc. XPS 13 9350/XXXXX, BIOS 1.2.3 01/08/2016
[Mon Mar 21 18:05:54 2016] Workqueue: events intel_mmio_flip_work_func [i915]
[Mon Mar 21 18:05:54 2016] 0000000000000286 0000000093832e83 ffff880272cb7d20 ffffffff813b54ae
[Mon Mar 21 18:05:54 2016] ffff880272cb7d68 ffffffffa01f9de8 ffff880272cb7d58 ffffffff810a40f2
[Mon Mar 21 18:05:54 2016] ffff880215ebf0c0 ffff880280c96600 ffff880280c9b000 0000000000000040
[Mon Mar 21 18:05:54 2016] Call Trace:
[Mon Mar 21 18:05:54 2016] [<ffffffff813b54ae>] dump_stack+0x63/0x85
[Mon Mar 21 18:05:54 2016] [<ffffffff810a40f2>] warn_slowpath_common+0x82/0xc0
[Mon Mar 21 18:05:54 2016] [<ffffffff810a418c>] warn_slowpath_fmt+0x5c/0x80
[Mon Mar 21 18:05:54 2016] [<ffffffffa01937d7>] intel_mmio_flip_work_func+0x387/0x3d0 [i915]
[Mon Mar 21 18:05:54 2016] [<ffffffff810bc596>] process_one_work+0x156/0x430
[Mon Mar 21 18:05:54 2016] [<ffffffff810bc8be>] worker_thread+0x4e/0x450
[Mon Mar 21 18:05:54 2016] [<ffffffff8179bd55>] ? __schedule+0x3a5/0xa00
[Mon Mar 21 18:05:54 2016] [<ffffffff810bc870>] ? process_one_work+0x430/0x430
[Mon Mar 21 18:05:54 2016] [<ffffffff810bc870>] ? process_one_work+0x430/0x430
[Mon Mar 21 18:05:54 2016] [<ffffffff810c2648>] kthread+0xd8/0xf0
[Mon Mar 21 18:05:54 2016] [<ffffffff810c2570>] ? kthread_worker_fn+0x160/0x160
[Mon Mar 21 18:05:54 2016] [<ffffffff817a088f>] ret_from_fork+0x3f/0x70
[Mon Mar 21 18:05:54 2016] [<ffffffff810c2570>] ? kthread_worker_fn+0x160/0x160
[Mon Mar 21 18:05:54 2016] ---[ end trace b5a5acfc195b296b ]---
[Mon Mar 21 18:05:54 2016] drm/i915: Resetting chip after gpu hang
[Mon Mar 21 18:05:56 2016] [drm] RC6 on
[Mon Mar 21 21:23:31 2016] [drm] stuck on render ring
[Mon Mar 21 21:23:31 2016] [drm] GPU HANG: ecode 9:0:0x85df9fff, in chrome [5196], reason: Ring hung, action: reset
[Mon Mar 21 21:23:31 2016] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[Mon Mar 21 21:23:31 2016] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[Mon Mar 21 21:23:31 2016] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[Mon Mar 21 21:23:31 2016] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[Mon Mar 21 21:23:31 2016] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[Mon Mar 21 21:23:31 2016] ------------[ cut here ]------------
[Mon Mar 21 21:23:31 2016] WARNING: CPU: 2 PID: 120 at drivers/gpu/drm/i915/intel_display.c:11289 intel_mmio_flip_work_func+0x387/0x3d0 [i915]()
[Mon Mar 21 21:23:31 2016] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
[Mon Mar 21 21:23:31 2016] Modules linked in:
[Mon Mar 21 21:23:31 2016] rfcomm fuse cmac xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast xt_conntrack ip_set nfnetlink ebtable_nat ebtable_filter ebtable_broute bridge stp llc ebtables ip6_tables iptable_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_raw iptable_mangle bnep hid_multitouch intel_rapl snd_soc_skl x86_pkg_temp_thermal snd_soc_skl_ipc coretemp snd_hda_ext_core snd_soc_sst_ipc snd_hda_codec_hdmi kvm_intel snd_soc_sst_dsp dell_led kvm snd_soc_core brcmfmac vfat snd_hda_codec_realtek fat snd_compress snd_hda_codec_generic snd_pcm_dmaengine ac97_bus dw_dmac_core brcmutil dell_wmi dell_laptop i2c_designware_platform snd_hda_intel i2c_designware_core sparse_keymap dcdbas cfg80211 irqbypass snd_hda_codec
[Mon Mar 21 21:23:31 2016] snd_hda_core snd_hwdep snd_seq uvcvideo rtsx_pci_ms videobuf2_vmalloc memstick videobuf2_memops videobuf2_v4l2 snd_seq_device snd_pcm joydev btusb videobuf2_core btrtl v4l2_common videodev snd_timer snd mei_me media i2c_i801 soundcore mei hci_uart idma64 processor_thermal_device shpchp intel_lpss_pci intel_soc_dts_iosf iosf_mbi wmi btbcm btqca btintel bluetooth pinctrl_sunrisepoint pinctrl_intel rfkill intel_lpss_acpi int3403_thermal intel_lpss int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad acpi_als kfifo_buf industrialio tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt i915 rtsx_pci_sdmmc mmc_core i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel drm nvme serio_raw rtsx_pci i2c_hid video fjes
[Mon Mar 21 21:23:31 2016] CPU: 2 PID: 120 Comm: kworker/2:1 Not tainted 4.4.5-300.fc23.x86_64 #1 (moved)
[Mon Mar 21 21:23:31 2016] Hardware name: Dell Inc. XPS 13 9350/0JXC1H, BIOS 1.2.3 01/08/2016
[Mon Mar 21 21:23:31 2016] Workqueue: events intel_mmio_flip_work_func [i915]
[Mon Mar 21 21:23:31 2016] 0000000000000286 000000005e30db05 ffff880273f0fd20 ffffffff813b54ae
[Mon Mar 21 21:23:31 2016] ffff880273f0fd68 ffffffffa01f4de8 ffff880273f0fd58 ffffffff810a40f2
[Mon Mar 21 21:23:31 2016] ffff8802318a8140 ffff880280d16600 ffff880280d1b000 0000000000000080
[Mon Mar 21 21:23:31 2016] Call Trace:
[Mon Mar 21 21:23:31 2016] [``] dump_stack+0x63/0x85
[Mon Mar 21 21:23:31 2016] [``] warn_slowpath_common+0x82/0xc0
[Mon Mar 21 21:23:31 2016] [``] warn_slowpath_fmt+0x5c/0x80
[Mon Mar 21 21:23:31 2016] [``] intel_mmio_flip_work_func+0x387/0x3d0 [i915]
[Mon Mar 21 21:23:31 2016] [``] process_one_work+0x156/0x430
[Mon Mar 21 21:23:31 2016] [``] worker_thread+0x4e/0x450
[Mon Mar 21 21:23:31 2016] [``] ? __schedule+0x3a5/0xa00
[Mon Mar 21 21:23:31 2016] [``] ? process_one_work+0x430/0x430
[Mon Mar 21 21:23:31 2016] [``] ? process_one_work+0x430/0x430
[Mon Mar 21 21:23:31 2016] [``] kthread+0xd8/0xf0
[Mon Mar 21 21:23:31 2016] [``] ? kthread_worker_fn+0x160/0x160
[Mon Mar 21 21:23:31 2016] [``] ret_from_fork+0x3f/0x70
[Mon Mar 21 21:23:31 2016] [``] ? kthread_worker_fn+0x160/0x160
[Mon Mar 21 21:23:31 2016] ---[ end trace 2e1339ae2448560b ]---
[Mon Mar 21 21:23:31 2016] drm/i915: Resetting chip after gpu hang
[Mon Mar 21 21:23:33 2016] [drm] RC6 on
[Mon Mar 21 21:23:47 2016] [drm] stuck on render ring
[Mon Mar 21 21:23:47 2016] [drm] GPU HANG: ecode 9:0:0x85dfbfff, in chrome [5273], reason: Ring hung, action: reset
[Mon Mar 21 21:23:47 2016] ------------[ cut here ]------------
[Mon Mar 21 21:23:47 2016] WARNING: CPU: 2 PID: 120 at drivers/gpu/drm/i915/intel_display.c:11289 intel_mmio_flip_work_func+0x387/0x3d0 [i915]()
[Mon Mar 21 21:23:47 2016] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
[Mon Mar 21 21:23:47 2016] Modules linked in:
[Mon Mar 21 21:23:47 2016] rfcomm fuse cmac xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast xt_conntrack ip_set nfnetlink ebtable_nat ebtable_filter ebtable_broute bridge stp llc ebtables ip6_tables iptable_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_raw iptable_mangle bnep hid_multitouch intel_rapl snd_soc_skl x86_pkg_temp_thermal snd_soc_skl_ipc coretemp snd_hda_ext_core snd_soc_sst_ipc snd_hda_codec_hdmi kvm_intel snd_soc_sst_dsp dell_led kvm snd_soc_core brcmfmac vfat snd_hda_codec_realtek fat snd_compress snd_hda_codec_generic snd_pcm_dmaengine ac97_bus dw_dmac_core brcmutil dell_wmi dell_laptop i2c_designware_platform snd_hda_intel i2c_designware_core sparse_keymap dcdbas cfg80211 irqbypass snd_hda_codec
[Mon Mar 21 21:23:47 2016] snd_hda_core snd_hwdep snd_seq uvcvideo rtsx_pci_ms videobuf2_vmalloc memstick videobuf2_memops videobuf2_v4l2 snd_seq_device snd_pcm joydev btusb videobuf2_core btrtl v4l2_common videodev snd_timer snd mei_me media i2c_i801 soundcore mei hci_uart idma64 processor_thermal_device shpchp intel_lpss_pci intel_soc_dts_iosf iosf_mbi wmi btbcm btqca btintel bluetooth pinctrl_sunrisepoint pinctrl_intel rfkill intel_lpss_acpi int3403_thermal intel_lpss int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad acpi_als kfifo_buf industrialio tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt i915 rtsx_pci_sdmmc mmc_core i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel drm nvme serio_raw rtsx_pci i2c_hid video fjes
[Mon Mar 21 21:23:47 2016] CPU: 2 PID: 120 Comm: kworker/2:1 Tainted: G W 4.4.5-300.fc23.x86_64 #1 (moved)
[Mon Mar 21 21:23:47 2016] Hardware name: Dell Inc. XPS 13 9350/0JXC1H, BIOS 1.2.3 01/08/2016
[Mon Mar 21 21:23:47 2016] Workqueue: events intel_mmio_flip_work_func [i915]
[Mon Mar 21 21:23:47 2016] 0000000000000286 000000005e30db05 ffff880273f0fd20 ffffffff813b54ae
[Mon Mar 21 21:23:47 2016] ffff880273f0fd68 ffffffffa01f4de8 ffff880273f0fd58 ffffffff810a40f2
[Mon Mar 21 21:23:47 2016] ffff880066669440 ffff880280d16600 ffff880280d1b000 0000000000000080
[Mon Mar 21 21:23:47 2016] Call Trace:
[Mon Mar 21 21:23:47 2016] [``] dump_stack+0x63/0x85
[Mon Mar 21 21:23:47 2016] [``] warn_slowpath_common+0x82/0xc0
[Mon Mar 21 21:23:47 2016] [``] warn_slowpath_fmt+0x5c/0x80
[Mon Mar 21 21:23:47 2016] [``] intel_mmio_flip_work_func+0x387/0x3d0 [i915]
[Mon Mar 21 21:23:47 2016] [``] process_one_work+0x156/0x430
[Mon Mar 21 21:23:47 2016] [``] worker_thread+0x4e/0x450
[Mon Mar 21 21:23:47 2016] [``] ? __schedule+0x3a5/0xa00
[Mon Mar 21 21:23:47 2016] [``] ? process_one_work+0x430/0x430
[Mon Mar 21 21:23:47 2016] [``] ? process_one_work+0x430/0x430
[Mon Mar 21 21:23:47 2016] [``] kthread+0xd8/0xf0
[Mon Mar 21 21:23:47 2016] [``] ? kthread_worker_fn+0x160/0x160
[Mon Mar 21 21:23:47 2016] [``] ret_from_fork+0x3f/0x70
[Mon Mar 21 21:23:47 2016] [``] ? kthread_worker_fn+0x160/0x160
[Mon Mar 21 21:23:47 2016] ---[ end trace 2e1339ae2448560c ]---
[Mon Mar 21 21:23:47 2016] drm/i915: Resetting chip after gpu hang
[Mon Mar 21 21:23:49 2016] [drm] RC6 onAttachment 122775, "Kernel log with i915 hang":
kernel_logAttachment 122776, "Error from intel card":
sys_errorI have a Dell Latitude e7250 with:
- Intel(R) Core(TM) i7-5600U CPU
- Intel Corporation Broadwell-U Integrated Graphics (rev 09)
With the same behavior here. I've tried to disable other framebuffer devices such as EFI, but in the meanwhile the only process which worked for me was disabling the iommu in the i915 kernel module, which is not a clean approach.
I've attached my dumps and hope it helps. I'll try Arch Linux anyway to see if has the same problem.
Sergi- Intel(R) Core(TM) i7-5600U CPU
@ickleclosed a related bug:*** Bug 94959 has been marked as a duplicate of this bug. ***
It is still unfixed as of now - more than one year after reported. It is crucial - makes laptop unusable for ANY kind of video tasks, as with igfx_off it works really slow. Will such a critical bug finally be assigned to someone? It was reported so many times and affected so many users... Or at least any thoughts, like where to watch this damn DMAR code for this bug?
I built and tried 4.7.2 last night and enabling VT-d still causes the freezes to happen so I don't think it is fixed yet. Kernel log messages when the freezes happen contain the following when it was able to recover from the freeze:
[ 1936.694513] [drm] stuck on render ring
[ 1936.694899] [drm] GPU HANG: ecode 8:0:0x85dffffb, in X [3356], reason: Engine(s) hung, action: reset
[ 1936.696494] drm/i915: Resetting chip after gpu hang
And the last one that killed it, requiring the power button to be held to turn the machine off, had a different ecode:
[ 1944.706379] [drm] stuck on render ring
[ 1944.706694] [drm] GPU HANG: ecode 8:0:0xbf9fffff, reason: Engine(s) hung, action: reset
[ 1944.708378] drm/i915: Resetting chip after gpu hangAttachment 127048, "drm_error crash dump of brots ThinkPad X250":
drm_error-dmar_freeze-intel_thinkpad_x250_brotHello everyone,
First of all, sorry i forgot to add the comment to the file.
I think am also hitting this bug, i think. The system is a Lenovo ThinkPad X250 - Intel(R) Core(TM) i5-5200U and the HD Graphics 5500.
Since i started using the IOMMU i have been getting hangs and also some X restarts. This is what dmesg says after the fact:
[ 1409.513438] DMAR: DRHD: handling fault status reg 3
[ 1409.513451] DMAR: [DMA Read] Request device [00:02.0] fault addr f5995000 [fault reason 05] PTE Write access is not set
[ 1409.513468] DMAR: DRHD: handling fault status reg 3
[ 1409.513471] DMAR: [DMA Write] Request device [00:02.0] fault addr f5968000 [fault reason 23] Unknown
[ 1418.830396] [drm] GPU HANG: ecode 8:0:0x85dffffb, in kwin_x11 [2191], reason: Hang on render ring, action: reset
[ 1418.830407] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1418.830409] [drm] Please file a new bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1418.830410] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1418.830412] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 1418.830413] [drm] GPU crash dump saved to /sys/class/drm/card0/error
I will upload said crash dump here. If i can provide you with any more debug-logs or should test something, i would be glad to help.
Thanks,
Michael*** Bug 98309 has been marked as a duplicate of this bug. ***
@icklesaid:(In reply to yann from comment 42)
*** Bug 98309 has been marked as a duplicate of this bug. ***
I would be careful not to mix gen8/gen9 reports for the moment, not until we have the root cause.(In reply to Chris Wilson from comment 43)
(In reply to yann from comment 42)
*** Bug 98309 has been marked as a duplicate of this bug. ***
I would be careful not to mix gen8/gen9 reports for the moment, not until we
have the root cause.
Well I pointed out early that one of the causes seems to be a conflict between the UEFI framebuffer driver and the intel one, most likely because of some race conditions or both trying to access the same hardware at the same time.
For me disabling the EFI framebuffer solved the issue so far so maybe other reporters may want to test and see if that solves the issue for them too.@madslsaid:(In reply to klondike from comment 44)
For me disabling the EFI framebuffer solved the issue so far so maybe other
reporters may want to test and see if that solves the issue for them too.
I've neither had efifb nor fbsimple enabled on my XPS 15 9550, but I didn't get rid of this problem until I added "intel_iommu=igfx_off" to my bootargs.(In reply to Mads from comment 45)
(In reply to klondike from comment 44)
For me disabling the EFI framebuffer solved the issue so far so maybe other
reporters may want to test and see if that solves the issue for them too.
I've neither had efifb nor fbsimple enabled on my XPS 15 9550, but I didn't
get rid of this problem until I added "intel_iommu=igfx_off" to my bootargs.
Interesting, it seems then that there is more than one different instance of this bug then. Do you have any other FB or driver that interacts with the intel card other than the Intel's modesetting one? The VGA console could be one such driver.@madslsaid:(In reply to Mads from comment 45)
(In reply to klondike from comment 44)
For me disabling the EFI framebuffer solved the issue so far so maybe other
reporters may want to test and see if that solves the issue for them too.
I've neither had efifb nor fbsimple enabled on my XPS 15 9550, but I didn't
get rid of this problem until I added "intel_iommu=igfx_off" to my bootargs.
I failed to mention that I didn't come across this bug until trying some drm-intel-nightly based on 4.9.0, but efifb was never involved.
intel_iommu=igfx_off also solved a long standing bug with suspend on my machine, bug 97211@madslsaid:VGA_CONSOLE is built in. But so is also DRM_I915, with firmware, so this appears is dmesg:
...
[ 1.051229] [drm] Replacing VGA console driver
...
But, I don't know if what I'm experiencing is relevant here, since I didn't see this bug appear until just recently with drm-intel-nightly (and fixed again by using intel_iommu=igfx_off)I guess we both are experiencing different bugs with similar symptoms.
In my case at least, the UEFI display driver clashes with the Intel one resulting in the IOMMU violations. This seems to be some kind of firmware bug where the firmware isn't playing along with the MMU settings and Intel's driver.
In yours, the cause may come from somewhere else, hopefully the devs can provide more guidance on what is triggering your case, but if sleep is involved chances are that firmware is somehow part of the issue.
