Bug 69831 - [IVB/BYT Bisected]glxgears causes calltrace and kernel BUG at drivers/gpu/drm/i915/intel_ringbuffer.h:268!
Summary: [IVB/BYT Bisected]glxgears causes calltrace and kernel BUG at drivers/gpu/drm...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-26 03:14 UTC by lu hua
Modified: 2017-10-06 14:42 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (94.91 KB, text/plain)
2013-09-26 03:14 UTC, lu hua
no flags Details

Description lu hua 2013-09-26 03:14:56 UTC
Created attachment 86609 [details]
dmesg

System Environment:
--------------------------
Platform:  Ivybridge
Kernel: (drm-intel-nightly)532fcf286aa6feba529587d0288a0097ba8b713e

Bug detailed description:
-----------------------------
glxgears causes calltrace and kernel BUG at drivers/gpu/drm/i915/intel_ringbuffer.h:268! on ivybridge with -ququed and -nightly kernel. It works well on -fixes kernel. It doesn't exit testing.
The latest know good commit:1b068ee25776533074251f1c6276c5f720c0284b
The latest know bad commit: 13992eba94ab34220e8e754c5cd6beb89c96bd73
I will bisect it later.

output:
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.

dmesg:
[   33.052248] ------------[ cut here ]------------
[   33.052272] kernel BUG at drivers/gpu/drm/i915/intel_ringbuffer.h:268!
[   33.052297] invalid opcode: 0000 [#1] SMP
[   33.052315] Modules linked in: dm_mod snd_hda_codec_hdmi snd_hda_codec_realtek dcdbas pcspkr serio_raw i2c_i801 snd_hda_intel iTCO_wdt iTCO_vendor_support snd_hda_codec lpc_ich snd_hwdep snd_pcm mfd_core snd_page_alloc snd_timer snd soundcore acpi_cpufreq i915 video button drm_kms_helper drm freq_table
[   33.052441] CPU: 2 PID: 3628 Comm: X Not tainted 3.12.0-rc2_drm-intel-next-queued_13992e_20130925_+ #262
[   33.052474] Hardware name: Dell Inc. OptiPlex 9010/03JR84, BIOS A01 05/04/2012
[   33.052501] task: ffff880118ca06f0 ti: ffff88000271a000 task.ti: ffff88000271a000
[   33.052528] RIP: 0010:[<ffffffffa00709ef>]  [<ffffffffa00709ef>] i915_vma_move_to_active+0x5c/0x17e [i915]
[   33.052571] RSP: 0018:ffff88000271bc58  EFLAGS: 00010246
[   33.052590] RAX: ffff8800daa0c800 RBX: ffff8800dabced80 RCX: ffff8800dabccad8
[   33.052616] RDX: ffff880002768ad8 RSI: ffff8800dabcc1d8 RDI: ffff8800dabcca80
[   33.052641] RBP: ffff8800051b15a0 R08: 0000000000000000 R09: 0000000000000003
[   33.052666] R10: ffff88000271bfd8 R11: ffff880002768780 R12: ffff8800051b0000
[   33.052692] R13: 0000000000000000 R14: ffff88000271bdf8 R15: 0000000000000000
[   33.052717] FS:  00007f50626998c0(0000) GS:ffff88011e300000(0000) knlGS:0000000000000000
[   33.052746] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   33.052767] CR2: 0000000002159ff0 CR3: 0000000002781000 CR4: 00000000001407e0
[   33.052792] Stack:
[   33.052801]  0000000000000000 ffff8800051b15a0 ffff880002777980 0000000000000001
[   33.052831]  ffffffffa0079657 ffffffffa0078683 0000000000000292 ffffffffa0007a3d
[   33.052861]  ffff88000271be28 ffff8800051b0000 ffff880004e99d80 ffffffff81707294
[   33.052891] Call Trace:
[   33.052907]  [<ffffffffa0079657>] ? gen6_ppgtt_insert_entries+0x114/0x114 [i915]
[   33.052937]  [<ffffffffa0078683>] ? i915_gem_do_execbuffer.isra.16+0xa4e/0xf08 [i915]
[   33.052969]  [<ffffffffa0007a3d>] ? drm_vblank_get+0x20f/0x220 [drm]
[   33.052994]  [<ffffffff81707294>] ? mutex_lock_interruptible+0xe/0x3b
[   33.053021]  [<ffffffffa007901a>] ? i915_gem_execbuffer2+0x15e/0x1e4 [i915]
[   33.053049]  [<ffffffffa000501d>] ? drm_ioctl+0x2a5/0x3c4 [drm]
[   33.053073]  [<ffffffff8164d1b3>] ? sock_aio_read.part.11+0xe6/0xf6
[   33.053099]  [<ffffffffa0078ebc>] ? i915_gem_execbuffer+0x37f/0x37f [i915]
[   33.053125]  [<ffffffff810e81f2>] ? vfs_ioctl+0x1e/0x31
[   33.053145]  [<ffffffff810e89c8>] ? do_vfs_ioctl+0x3ad/0x3ef
[   33.053166]  [<ffffffff810e8a58>] ? SyS_ioctl+0x4e/0x7e
[   33.053186]  [<ffffffff8170e722>] ? system_call_fastpath+0x16/0x1b
[   33.053208] Code: 05 e0 00 00 00 48 89 47 58 48 89 57 60 48 89 0a 48 8b 5f 48 44 8b ad 18 01 00 00 48 8b 43 08 45 85 ed 4c 8b a0 b8 02 00 00 75 02 <0f> 0b 48 85 ed 75 02 0f 0b 48 39 ab 38 01 00 00 74 10 83 bb 44
[   33.053343] RIP  [<ffffffffa00709ef>] i915_vma_move_to_active+0x5c/0x17e [i915]
[   33.053374]  RSP <ffff88000271bc58>
[   33.056879] ---[ end trace 00bc62bccea5219c ]---

Reproduce steps:
----------------------------
1. xinit
2. ./glxgears
Comment 1 lu hua 2013-09-26 06:18:40 UTC
./gem_storedw_batches_loop --run-subtest secure-dispatch also causes calltrace and kernel BUG at drivers/gpu/drm/i915/intel_ringbuffer.h:268! on haswell with -queued kernel.
output:
running storedw loop with stall every 1 batch
Comment 2 Daniel Vetter 2013-09-26 07:50:09 UTC
Yeah, that's in both cases the secure batch dispatch that's been broken in

commit c6916417c8575637659686ff0e4f744babf0cb4e
Author: Ben Widawsky <ben@bwidawsk.net>
Date:   Tue Sep 24 09:58:00 2013 -0700

    drm/i915: Use the new vm [un]bind functions

Can you please confirm this bisect?
Comment 3 lu hua 2013-09-27 07:34:41 UTC
Bisect shows:c6916417c8575637659686ff0e4f744babf0cb4e is the first bad commit. 
commit c6916417c8575637659686ff0e4f744babf0cb4e
Author: Ben Widawsky <ben@bwidawsk.net>
Date:   Tue Sep 24 09:58:00 2013 -0700

    drm/i915: Use the new vm [un]bind functions
Comment 4 lu hua 2013-09-29 08:21:32 UTC
It also happens on Baytrail.
Comment 5 Daniel Vetter 2013-09-29 12:45:19 UTC
Offending patch dropped for now.
Comment 6 lu hua 2013-09-30 02:44:03 UTC
Verified.Fixed.
Comment 7 Elizabeth 2017-10-06 14:42:51 UTC
Closing old verified.


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.