Summary: | crash when switching from plasma to tty console | ||
---|---|---|---|
Product: | Mesa | Reporter: | Paulo Dias <paulo.miguel.dias> |
Component: | Drivers/DRI/i915 | Assignee: | Ian Romanick <idr> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | critical | ||
Priority: | medium | CC: | intel-gfx-bugs, paulo.miguel.dias |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | HSW | i915 features: | GPU hang |
Attachments: |
/sys/class/drm/card0/error
xorg.log |
Description
Paulo Dias
2016-01-23 22:18:53 UTC
Please attach the /sys/class/drm/card0/error. Created attachment 121341 [details]
/sys/class/drm/card0/error
when i jumped from plasma to tty2 (alt-f2), the radeon dedicated card kicked in and trashed the console (black screen), when i jumped back to plasma (alt-f7), the intel gpu reseted (error attached above) --- Jan 28 03:06:04 hydra kernel: [drm] ring test on 7 succeeded in 3 usecs Jan 28 03:06:04 hydra kernel: [drm] VCE initialized successfully. Jan 28 03:06:04 hydra kernel: [drm] ib test on ring 0 succeeded in 0 usecs Jan 28 03:06:04 hydra kernel: [drm] ib test on ring 1 succeeded in 0 usecs Jan 28 03:06:04 hydra kernel: [drm] ib test on ring 2 succeeded in 0 usecs Jan 28 03:06:04 hydra kernel: [drm] ib test on ring 3 succeeded in 0 usecs Jan 28 03:06:04 hydra kernel: [drm] ib test on ring 4 succeeded in 0 usecs Jan 28 03:06:05 hydra kernel: [drm] ib test on ring 5 succeeded Jan 28 03:06:05 hydra kernel: [drm] ib test on ring 6 succeeded Jan 28 03:06:06 hydra kernel: [drm] ib test on ring 7 succeeded Jan 28 03:06:12 hydra kernel: [drm] stuck on render ring Jan 28 03:06:12 hydra kernel: [drm] GPU HANG: ecode 7:0:0x85dffff8, in Compositor [20732], reason: Ring hung, action: reset Jan 28 03:06:12 hydra kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Jan 28 03:06:12 hydra kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Jan 28 03:06:12 hydra kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Jan 28 03:06:12 hydra kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Jan 28 03:06:12 hydra kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error Jan 28 03:06:12 hydra kernel: drm/i915: Resetting chip after gpu hang Jan 28 03:06:12 hydra kernel: [drm] probing gen 2 caps for device 8086:9c18 = 5323c42/0 Jan 28 03:06:12 hydra kernel: [drm] PCIE gen 2 link speeds already enabled Jan 28 03:06:12 hydra kernel: [drm] PCIE GART of 2048M enabled (table at 0x00000000002E8000). Jan 28 03:06:12 hydra kernel: radeon 0000:03:00.0: WB enabled Jan 28 03:06:12 hydra kernel: radeon 0000:03:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff8801a3ab5c00 Jan 28 03:06:12 hydra kernel: radeon 0000:03:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04 and cpu addr 0xffff8801a3ab5c04 Jan 28 03:06:12 hydra kernel: radeon 0000:03:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08 and cpu addr 0xffff8801a3ab5c08 Jan 28 03:06:12 hydra kernel: radeon 0000:03:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff8801a3ab5c0c Jan 28 03:06:12 hydra kernel: radeon 0000:03:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10 and cpu addr 0xffff8801a3ab5c10 Jan 28 03:06:12 hydra kernel: radeon 0000:03:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90001435a18 Jan 28 03:06:12 hydra kernel: radeon 0000:03:00.0: fence driver on ring 6 use gpu addr 0x0000000080000c18 and cpu addr 0xffff8801a3ab5c18 Jan 28 03:06:12 hydra kernel: radeon 0000:03:00.0: fence driver on ring 7 use gpu addr 0x0000000080000c1c and cpu addr 0xffff8801a3ab5c1c Jan 28 03:06:13 hydra kernel: [drm] ring test on 0 succeeded in 1 usecs Jan 28 03:06:13 hydra kernel: [drm] ring test on 1 succeeded in 1 usecs Jan 28 03:06:13 hydra kernel: [drm] ring test on 2 succeeded in 1 usecs Jan 28 03:06:13 hydra kernel: [drm] ring test on 3 succeeded in 11 usecs Jan 28 03:06:13 hydra kernel: [drm] ring test on 4 succeeded in 4 usecs Jan 28 03:06:13 hydra kernel: [drm] ring test on 5 succeeded in 2 usecs Jan 28 03:06:13 hydra kernel: [drm] UVD initialized successfully. Jan 28 03:06:13 hydra kernel: [drm] ring test on 6 succeeded in 9 usecs Jan 28 03:06:13 hydra kernel: [drm] ring test on 7 succeeded in 3 usecs Jan 28 03:06:13 hydra kernel: [drm] VCE initialized successfully. Jan 28 03:06:13 hydra kernel: [drm] ib test on ring 0 succeeded in 0 usecs Jan 28 03:06:13 hydra kernel: [drm] ib test on ring 1 succeeded in 0 usecs Jan 28 03:06:13 hydra kernel: [drm] ib test on ring 2 succeeded in 0 usecs Jan 28 03:06:13 hydra kernel: [drm] ib test on ring 3 succeeded in 0 usecs Jan 28 03:06:13 hydra kernel: [drm] ib test on ring 4 succeeded in 0 usecs Jan 28 03:06:14 hydra kernel: [drm] ib test on ring 5 succeeded Jan 28 03:06:15 hydra kernel: [drm] ib test on ring 6 succeeded Jan 28 03:06:15 hydra kernel: [drm] ib test on ring 7 succeeded Jan 28 03:06:18 hydra kernel: [drm] stuck on render ring Jan 28 03:06:18 hydra kernel: [drm] GPU HANG: ecode 7:0:0x85dffff8, in Compositor [20732], reason: Ring hung, action: reset Jan 28 03:06:18 hydra kernel: ------------[ cut here ]------------ Jan 28 03:06:18 hydra kernel: WARNING: CPU: 0 PID: 21699 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:11289 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]() Jan 28 03:06:18 hydra kernel: WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips)) Jan 28 03:06:18 hydra kernel: Modules linked in: Jan 28 03:06:18 hydra kernel: cpuid ctr ccm rfcomm drbg ansi_cprng bnep pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) rtsx_usb_ms memstick vboxdrv(OE) binfmt_misc nls_iso8859_1 dell_wmi sparse_keymap dell_laptop dcdbas dell_smm_hwmon uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev dell_led media ath3k intel_rapl btusb x86_pkg_temp_thermal btrtl snd_hda_codec_realtek btbcm intel_powerclamp snd_hda_codec_generic btintel bluetooth coretemp snd_hda_intel snd_hda_codec snd_usb_audio kvm_intel snd_hda_core snd_usbmidi_lib snd_hwdep kvm snd_pcm irqbypass crct10dif_pclmul crc32_pclmul arc4 aesni_intel ath9k ath9k_common snd_seq_midi aes_x86_64 ath9k_hw snd_seq_midi_event lrw gf128mul ath glue_helper snd_rawmidi ablk_helper mac80211 cryptd snd_seq input_leds snd_seq_device Jan 28 03:06:18 hydra kernel: joydev snd_timer serio_raw cfg80211 snd mei_me mei lpc_ich shpchp soundcore soc_button_array dell_rbtn mac_hid parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq rtsx_usb_sdmmc rtsx_usb hid_generic usbhid hid amdkfd amd_iommu_v2 radeon i915 ttm i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm ahci libahci r8169 mii wmi video fjes Jan 28 03:06:18 hydra kernel: CPU: 0 PID: 21699 Comm: kworker/0:0 Tainted: G OE 4.4.0-040400-generic #201601101930 Jan 28 03:06:18 hydra kernel: Hardware name: Dell Inc. Latitude 3540/02R0J9, BIOS A10 01/28/2015 Jan 28 03:06:18 hydra kernel: Workqueue: events intel_mmio_flip_work_func [i915] Jan 28 03:06:18 hydra kernel: 0000000000000000 0000000096b27b61 ffff88002d5b7d20 ffffffff813c8d94 Jan 28 03:06:18 hydra kernel: ffff88002d5b7d68 ffff88002d5b7d58 ffffffff8107dba2 ffff880194a2eec0 Jan 28 03:06:18 hydra kernel: ffff8801af2162c0 ffff8801af21aa00 0000000000000000 ffff880194a2eec0 Jan 28 03:06:18 hydra kernel: Call Trace: Jan 28 03:06:18 hydra kernel: [<ffffffff813c8d94>] dump_stack+0x44/0x60 Jan 28 03:06:18 hydra kernel: [<ffffffff8107dba2>] warn_slowpath_common+0x82/0xc0 Jan 28 03:06:18 hydra kernel: [<ffffffff8107dc3c>] warn_slowpath_fmt+0x5c/0x80 Jan 28 03:06:18 hydra kernel: [<ffffffff810158b0>] ? __switch_to+0x420/0x5a0 Jan 28 03:06:18 hydra kernel: [<ffffffffc0209ffe>] intel_mmio_flip_work_func+0x38e/0x3d0 [i915] Jan 28 03:06:18 hydra kernel: [<ffffffff8109688a>] process_one_work+0x1aa/0x440 Jan 28 03:06:18 hydra kernel: [<ffffffff81096b6b>] worker_thread+0x4b/0x4c0 Jan 28 03:06:18 hydra kernel: [<ffffffff81096b20>] ? process_one_work+0x440/0x440 Jan 28 03:06:18 hydra kernel: [<ffffffff81096b20>] ? process_one_work+0x440/0x440 Jan 28 03:06:18 hydra kernel: [<ffffffff8109cce8>] kthread+0xd8/0xf0 Jan 28 03:06:18 hydra kernel: [<ffffffff8109cc10>] ? kthread_create_on_node+0x1a0/0x1a0 Jan 28 03:06:18 hydra kernel: [<ffffffff817fdd4f>] ret_from_fork+0x3f/0x70 Jan 28 03:06:18 hydra kernel: [<ffffffff8109cc10>] ? kthread_create_on_node+0x1a0/0x1a0 Jan 28 03:06:18 hydra kernel: ---[ end trace 9126c1345035de97 ]--- Jan 28 03:06:18 hydra kernel: drm/i915: Resetting chip after gpu hang --- Created attachment 121342 [details]
xorg.log
Paulo, after updating your kernel and Mesa, is this issue still occuring? In the meantime, assigning to Mesa product (please let me know if I am mistaken with this GPU Hang). From this error dump, hung is happening in render ring batch with active head at 0x03f58690, with 0x7a000003 (PIPE_CONTROL) as IPEHR. Batch extract (around 0x03f58690): 0x03f58660: 0x7b000005: 3DPRIMITIVE: 0x03f58664: 0x0000000f: rect list sequential 0x03f58668: 0x00000003: vertex count 0x03f5866c: 0x00000000: start vertex 0x03f58670: 0x00000001: instance count 0x03f58674: 0x00000000: start instance 0x03f58678: 0x00000000: index bias 0x03f5867c: 0x7a000003: PIPE_CONTROL 0x03f58680: 0x00101c11: no write, cs stall, render target cache flush, instruction cache invalidate, texture cache invalidate, vf fetch invalidate, depth cache flush, 0x03f58684: 0x00000000: destination address 0x03f58688: 0x00000000: immediate dword low 0x03f5868c: 0x00000000: immediate dword high 0x03f58690: 0x78210000: 3DSTATE_VIEWPORT_STATE_POINTERS_SF_CLIP 0x03f58694: 0x00007d80: pointer to SF_CLIP viewport 0x03f58698: 0x78240000: 3DSTATE_BLEND_STATE_POINTERS 0x03f5869c: 0x00007d41: pointer to BLEND_STATE at 0x00007d40 (changed) -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/759. |
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.