Bug 102705

Summary: [BAT][BXT] igt@kms_cursor_legacy@basic-flip-before-cursor-atomic - Incompete
Product: DRI Reporter: Marta Löfstedt <marta.lofstedt>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: highest CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: BXT i915 features: GEM/Other

Description Marta Löfstedt 2017-09-13 13:13:37 UTC
CI_DRM_3084 fi-bxt-j4205 incomplete.

All data:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3084/fi-bxt-j4205/igt@kms_cursor_legacy@basic-flip-before-cursor-atomic.html

from pstore:
<14>[  399.979530] [IGT] kms_cursor_legacy: exiting, ret=0
<4>[  399.989161] ------------[ cut here ]------------
<2>[  399.989238] kernel BUG at drivers/gpu/drm/i915/intel_lrc.c:598!
<4>[  399.989274] invalid opcode: 0000 [#1] PREEMPT SMP
<4>[  399.989318] Modules linked in: vgem snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic i915 x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul snd_hda_intel crc32_pclmul snd_hda_codec ghash_clmulni_intel snd_hwdep snd_hda_core snd_pcm r8169 mii mei_me mei prime_numbers lpc_ich i2c_hid pinctrl_broxton pinctrl_intel
<4>[  399.989419] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G     U          4.13.0-CI-CI_DRM_3084+ #1
<4>[  399.989437] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./J4205-ITX, BIOS P1.10 09/29/2016
<4>[  399.989492] task: ffff88027650a780 task.stack: ffffc90000094000
<4>[  399.989557] RIP: 0010:intel_lrc_irq_handler+0x261/0x500 [i915]
<4>[  399.989569] RSP: 0018:ffff88027fd03ea0 EFLAGS: 00010202
<4>[  399.989582] RAX: 0000000000000000 RBX: 0000000000000003 RCX: ffff88026d2f2440
<4>[  399.989598] RDX: 0000000000000006 RSI: ffffc90008e1a3a0 RDI: 00000000ffffffff
<4>[  399.989613] RBP: ffff88027fd03f00 R08: ffff8802656a0000 R09: 0000000000000001
<4>[  399.989629] R10: ffff8802656b21a8 R11: 0000000000000000 R12: ffff8802656b2158
<4>[  399.989644] R13: 0000000000008002 R14: 0000000000000003 R15: ffffc90008e1a370
<4>[  399.989659] FS:  0000000000000000(0000) GS:ffff88027fd00000(0000) knlGS:0000000000000000
<4>[  399.989678] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4>[  399.989691] CR2: 00007efec9c9e000 CR3: 0000000003e0f000 CR4: 00000000003406e0
<4>[  399.989705] Call Trace:
<4>[  399.989714]  <IRQ>
<4>[  399.989729]  tasklet_hi_action+0x98/0x120
<4>[  399.989744]  __do_softirq+0xc0/0x4ae
<4>[  399.989756]  irq_exit+0xae/0xc0
<4>[  399.989767]  do_IRQ+0x71/0x130
<4>[  399.989778]  common_interrupt+0x90/0x90
<4>[  399.989790] RIP: 0010:cpuidle_enter_state+0x136/0x370
<4>[  399.989803] RSP: 0018:ffffc90000097e80 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff6d
<4>[  399.989822] RAX: ffff88027650a780 RBX: 0000000000086825 RCX: 0000000000000001
<4>[  399.989837] RDX: 0000000000000000 RSI: ffffffff81cf7904 RDI: ffffffff81cae6ee
<4>[  399.989852] RBP: ffffc90000097eb8 R08: 00000000000001e4 R09: 0000000000000018
<4>[  399.989867] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000004
<4>[  399.989882] R13: 0000000000000004 R14: ffff88027fd24c18 R15: 0000005d2123ec51
<4>[  399.989899]  </IRQ>
<4>[  399.989911]  cpuidle_enter+0x17/0x20
<4>[  399.989923]  call_cpuidle+0x23/0x40
<4>[  399.989933]  do_idle+0x192/0x1e0
<4>[  399.989945]  cpu_startup_entry+0x1d/0x20
<4>[  399.989957]  start_secondary+0x102/0x120
<4>[  399.989971]  secondary_startup_64+0x9f/0x9f
<4>[  399.989984] Code: ff 41 83 e5 08 0f 85 d8 fe ff ff 0f 0b 0f 0b 0f 0b 48 89 cf 4c 89 45 c0 4c 89 55 c8 e8 e9 d4 47 e1 4c 8b 45 c0 4c 8b 55 c8 eb 92 <0f> 0b 0f 0b 49 8d 84 24 40 03 00 00 48 83 e2 fc 48 89 45 a8 74 
<1>[  399.990150] RIP: intel_lrc_irq_handler+0x261/0x500 [i915] RSP: ffff88027fd03ea0
<4>[  399.990187] ---[ end trace eb7a85f987a701b4 ]---
Comment 1 Chris Wilson 2017-09-13 13:19:23 UTC

*** This bug has been marked as a duplicate of bug 102035 ***

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.