Attachment 122775 Details for Bug 89360 – Kernel log with i915 hang

Kernel log with i915 hang

kernel_log (text/plain), 4.43 KB, created by Sergi Barroso on 2016-04-06 18:36:24 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Sergi Barroso

Created: 2016-04-06 18:36:24 UTC

Size: 4.43 KB

patch

obsolete

>[  199.575264] DMAR: DRHD: handling fault status reg 3
>[  199.575269] DMAR: DMAR:[DMA Write] Request device [00:02.0] fault addr fe3ab000 
>               DMAR:[fault reason 23] Unknown
>[  199.775235] DMAR: DRHD: handling fault status reg 3
>[  199.775238] DMAR: DMAR:[DMA Write] Request device [00:02.0] fault addr fe3ab000 
>               DMAR:[fault reason 23] Unknown
>[  199.973998] DMAR: DRHD: handling fault status reg 3
>[  199.974001] DMAR: DMAR:[DMA Write] Request device [00:02.0] fault addr fe3ab000 
>               DMAR:[fault reason 23] Unknown
>[  200.291846] DMAR: DRHD: handling fault status reg 3
>[  200.291850] DMAR: DMAR:[DMA Write] Request device [00:02.0] fault addr fe3ab000 
>               DMAR:[fault reason 23] Unknown
>[  200.295439] DMAR: DRHD: handling fault status reg 3
>[  200.295443] DMAR: DMAR:[DMA Write] Request device [00:02.0] fault addr fe3ac000 
>               DMAR:[fault reason 23] Unknown
>[  200.391863] DMAR: DRHD: handling fault status reg 3
>[  200.391867] DMAR: DMAR:[DMA Write] Request device [00:02.0] fault addr fe3ac000 
>               DMAR:[fault reason 23] Unknown
>[  200.591827] DMAR: DRHD: handling fault status reg 3
>[  200.591831] DMAR: DMAR:[DMA Write] Request device [00:02.0] fault addr fe3ac000 
>               DMAR:[fault reason 23] Unknown
>[  200.790271] DMAR: DRHD: handling fault status reg 3
>[  200.790275] DMAR: DMAR:[DMA Write] Request device [00:02.0] fault addr fe3ac000 
>               DMAR:[fault reason 23] Unknown
>[  940.908845] DMAR: DRHD: handling fault status reg 3
>[  940.908850] DMAR: DMAR:[DMA Write] Request device [00:02.0] fault addr fdd43000 
>               DMAR:[fault reason 23] Unknown
>[  946.670387] [drm] stuck on render ring
>[  946.670588] [drm] GPU HANG: ecode 8:0:0x85dffffb, in X [4766], reason: Ring hung, action: reset
>[  946.670590] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
>[  946.670590] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
>[  946.670591] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
>[  946.670591] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
>[  946.670592] [drm] GPU crash dump saved to /sys/class/drm/card0/error
>[  946.670641] ------------[ cut here ]------------
>[  946.670646] WARNING: CPU: 0 PID: 4722 at drivers/gpu/drm/i915/intel_display.c:11438 intel_mmio_flip_work_func+0x41a/0x440()
>[  946.670647] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
>[  946.670647] Modules linked in:
>[  946.670648]  ccm iTCO_wdt iTCO_vendor_support dell_wmi x86_pkg_temp_thermal kvm_intel kvm iwlmvm irqbypass mac80211 psmouse btusb iwlwifi btrtl btintel bluetooth cfg80211 lpc_ich sdhci_pci mei_me e1000e rfkill mei wmi sdhci_acpi int3403_thermal sdhci mmc_core int3402_thermal processor_thermal_device intel_soc_dts_iosf iosf_mbi int340x_thermal_zone int3400_thermal acpi_thermal_rel tpm_tis tpm nls_iso8859_15 nls_cp850 sch_fq_codel ip_tables ipv6 xfs nfs lockd grace sunrpc ext2 sg
>[  946.670665] CPU: 0 PID: 4722 Comm: kworker/0:1 Not tainted 4.5.0-gentoo-r1 #2
>[  946.670666] Hardware name: Dell Inc. Latitude E7250/0TVD2T, BIOS A11 03/15/2016
>[  946.670667] Workqueue: events intel_mmio_flip_work_func
>[  946.670668]  ffff8800da1b7d68 0000000098e19943 ffff8800da1b7d20 ffffffff812cab9c
>[  946.670670]  ffff8800da1b7d58 ffffffff81079fbb ffff88040b25c8c0 ffff880409428480
>[  946.670671]  ffff8800da14a000 ffff88041e7cfd00 0000000000000000 ffff8800da1b7dc0
>[  946.670672] Call Trace:
>[  946.670675]  [<ffffffff812cab9c>] dump_stack+0x19/0x1d
>[  946.670677]  [<ffffffff81079fbb>] warn_slowpath_common+0x7b/0xb0
>[  946.670679]  [<ffffffff8107a047>] warn_slowpath_fmt+0x57/0x70
>[  946.670680]  [<ffffffff8144e92a>] intel_mmio_flip_work_func+0x41a/0x440
>[  946.670682]  [<ffffffff8108ee24>] process_one_work+0x124/0x3a0
>[  946.670683]  [<ffffffff8108f3d8>] worker_thread+0x58/0x460
>[  946.670685]  [<ffffffff8108f380>] ? rescuer_thread+0x2e0/0x2e0
>[  946.670686]  [<ffffffff8108f380>] ? rescuer_thread+0x2e0/0x2e0
>[  946.670687]  [<ffffffff810939a2>] kthread+0xd2/0xf0
>[  946.670689]  [<ffffffff810938d0>] ? kthread_create_on_node+0x170/0x170
>[  946.670691]  [<ffffffff816da91f>] ret_from_fork+0x3f/0x70
>[  946.670692]  [<ffffffff810938d0>] ? kthread_create_on_node+0x170/0x170
>[  946.670693] ---[ end trace 68769bb6f81da2ef ]---
>[  946.672646] drm/i915: Resetting chip after gpu hang

Actions: View

Attachments on bug 89360: 113867 | 113998 | 113999 | 118605 | 118606 | 122465 | 122775 | 122776 | 127048 | 130657 | 134746 | 134747 | 138682 | 142592 | 142593 | 143757 | 144746

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.