| Summary: | [SKL]Webglc sporadically causes system hang | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | lu hua <huax.lu> | ||||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
| Severity: | normal | ||||||||||
| Priority: | high | CC: | intel-gfx-bugs | ||||||||
| Version: | unspecified | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux (All) | ||||||||||
| URL: | while :; do sudo ./gem_exec_lut_handle ; done | ||||||||||
| Whiteboard: | |||||||||||
| i915 platform: | i915 features: | ||||||||||
| Attachments: |
|
||||||||||
|
Description
lu hua
2015-04-22 08:10:00 UTC
Created attachment 115263 [details]
dmesg
output shows: glxinfo failed to connect to X X not responsible, or DRI disabled, kill it glxinfo failed to connect to X Mika has been discussing this. The basic problem is that we didn't pin the vma prior to the shrinker potentially running and ruining our day. The fix is in http://cgit.freedesktop.org/~ickle/linux-2.6/commit/?h=nightly&id=3c84cdac9285bf13b69fccbb19816d287f214c4c Created attachment 115283 [details]
dmesg(70614661)
Test on commit 70614661341ffb26de05e84c6958563b45964223, system hang.
Clean boot system, wait 5 minutes or run xinit, system hang.
dmesg:
[ 175.024940] ------------[ cut here ]------------
[ 175.024984] WARNING: CPU: 1 PID: 5255 at drivers/gpu/drm/drm_mm.c:367 i915_vma_unbind+0x112/0x1bc [i915]()
[ 175.024995] Modules linked in: dm_mod ppdev snd_hda_codec_realtek snd_hda_codec_generic pcspkr snd_hda_intel snd_hda_controller snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundcore i2c_i801 joydev wmi battery parport_pc parport ac acpi_cpufreq i915 button video drm_kms_helper drm
[ 175.025030] CPU: 1 PID: 5255 Comm: X Not tainted 4.0.0_kcloud_706146_20150423+ #364
[ 175.025034] Hardware name: Intel Corporation Skylake Client platform/Skylake Y LPDDR3 RVP3, BIOS SKLSE2R1.86C.B067.R00.1412310711 12/31/2014
[ 175.025038] 0000000000000000 0000000000000009 ffffffff81795a87 0000000000000000
[ 175.025044] ffffffff8103bd5a ffff88009ad86d00 ffffffffa00a166b ffff88009ad86d00
[ 175.025050] ffff8801483c3380 ffff88009ad86d00 0000000000000001 ffff8801442d0000
[ 175.025056] Call Trace:
[ 175.025068] [<ffffffff81795a87>] ? dump_stack+0x40/0x50
[ 175.025078] [<ffffffff8103bd5a>] ? warn_slowpath_common+0x98/0xb0
[ 175.025109] [<ffffffffa00a166b>] ? i915_vma_unbind+0x112/0x1bc [i915]
[ 175.025137] [<ffffffffa00a166b>] ? i915_vma_unbind+0x112/0x1bc [i915]
[ 175.025163] [<ffffffffa00a1740>] ? i915_vma_close+0x2b/0x80 [i915]
[ 175.025188] [<ffffffffa00a17fb>] ? i915_gem_close_object+0x66/0x125 [i915]
[ 175.025205] [<ffffffffa0003d35>] ? drm_gem_handle_delete+0xaa/0xbd [drm]
[ 175.025221] [<ffffffffa00047ae>] ? drm_ioctl+0x322/0x38d [drm]
[ 175.025241] [<ffffffffa0003f97>] ? drm_gem_handle_create+0x37/0x37 [drm]
[ 175.025248] [<ffffffff8105ede9>] ? set_next_entity+0x32/0x55
[ 175.025257] [<ffffffff8111dcde>] ? do_vfs_ioctl+0x360/0x424
[ 175.025265] [<ffffffff817987d2>] ? __schedule+0x589/0x7c9
[ 175.025271] [<ffffffff8104fad2>] ? task_work_run+0x84/0x96
[ 175.025278] [<ffffffff8111ddeb>] ? SyS_ioctl+0x49/0x7a
[ 175.025284] [<ffffffff8179b472>] ? system_call_fastpath+0x12/0x17
[ 175.025288] ---[ end trace eab6accbedda9078 ]---
[ 175.025301] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
(In reply to lu hua from comment #4) > Created attachment 115283 [details] > dmesg(70614661) > > Test on commit 70614661341ffb26de05e84c6958563b45964223, system hang. > Clean boot system, wait 5 minutes or run xinit, system hang. > > dmesg: > [ 175.024940] ------------[ cut here ]------------ > [ 175.024984] WARNING: CPU: 1 PID: 5255 at drivers/gpu/drm/drm_mm.c:367 > i915_vma_unbind+0x112/0x1bc [i915]() > [ 175.024995] Modules linked in: dm_mod ppdev snd_hda_codec_realtek > snd_hda_codec_generic pcspkr snd_hda_intel snd_hda_controller snd_hda_codec > snd_hda_core snd_hwdep snd_pcm snd_timer snd soundcore i2c_i801 joydev wmi > battery parport_pc parport ac acpi_cpufreq i915 button video drm_kms_helper > drm > [ 175.025030] CPU: 1 PID: 5255 Comm: X Not tainted > 4.0.0_kcloud_706146_20150423+ #364 > [ 175.025034] Hardware name: Intel Corporation Skylake Client > platform/Skylake Y LPDDR3 RVP3, BIOS SKLSE2R1.86C.B067.R00.1412310711 > 12/31/2014 > [ 175.025038] 0000000000000000 0000000000000009 ffffffff81795a87 > 0000000000000000 > [ 175.025044] ffffffff8103bd5a ffff88009ad86d00 ffffffffa00a166b > ffff88009ad86d00 > [ 175.025050] ffff8801483c3380 ffff88009ad86d00 0000000000000001 > ffff8801442d0000 > [ 175.025056] Call Trace: > [ 175.025068] [<ffffffff81795a87>] ? dump_stack+0x40/0x50 > [ 175.025078] [<ffffffff8103bd5a>] ? warn_slowpath_common+0x98/0xb0 > [ 175.025109] [<ffffffffa00a166b>] ? i915_vma_unbind+0x112/0x1bc [i915] > [ 175.025137] [<ffffffffa00a166b>] ? i915_vma_unbind+0x112/0x1bc [i915] > [ 175.025163] [<ffffffffa00a1740>] ? i915_vma_close+0x2b/0x80 [i915] > [ 175.025188] [<ffffffffa00a17fb>] ? i915_gem_close_object+0x66/0x125 > [i915] > [ 175.025205] [<ffffffffa0003d35>] ? drm_gem_handle_delete+0xaa/0xbd [drm] > [ 175.025221] [<ffffffffa00047ae>] ? drm_ioctl+0x322/0x38d [drm] > [ 175.025241] [<ffffffffa0003f97>] ? drm_gem_handle_create+0x37/0x37 [drm] > [ 175.025248] [<ffffffff8105ede9>] ? set_next_entity+0x32/0x55 > [ 175.025257] [<ffffffff8111dcde>] ? do_vfs_ioctl+0x360/0x424 > [ 175.025265] [<ffffffff817987d2>] ? __schedule+0x589/0x7c9 > [ 175.025271] [<ffffffff8104fad2>] ? task_work_run+0x84/0x96 > [ 175.025278] [<ffffffff8111ddeb>] ? SyS_ioctl+0x49/0x7a > [ 175.025284] [<ffffffff8179b472>] ? system_call_fastpath+0x12/0x17 > [ 175.025288] ---[ end trace eab6accbedda9078 ]--- > [ 175.025301] BUG: unable to handle kernel NULL pointer dereference at > 0000000000000008 Sure but that is a bug from another commit. Only meet once. I am unable to reproduce it again. Close it. Verified.Fixed. Closing old verified+fixed. |
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.