Bug 111048 - [CI][DRMTIP][icl-dsi] igt@i915_selftest@live_workarounds - Invalid RING_NONPRIV[3], expected 0x10002349, found 0x00002348
Summary: [CI][DRMTIP][icl-dsi] igt@i915_selftest@live_workarounds - Invalid RING_NONPR...
Status: RESOLVED NOTABUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: highest normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-03 12:24 UTC by Lakshmi
Modified: 2019-07-16 08:36 UTC (History)
1 user (show)

See Also:
i915 platform: ICL
i915 features: GEM/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-07-03 12:24:29 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6401/fi-icl-dsi/igt@i915_selftest@live_workarounds.html

------------[ cut here ]------------
<4> [360.210689] WARN_ON(dev_priv->mm.shrink_count)
<4> [360.210882] WARNING: CPU: 5 PID: 4317 at drivers/gpu/drm/i915/i915_gem.c:1686 i915_gem_cleanup_early+0x102/0x110 [i915]
<4> [360.210887] Modules linked in: i915(+) amdgpu gpu_sched ttm vgem snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic mei_hdcp x86_pkg_temp_thermal coretemp ax88179_178a usbnet mii crct10dif_pclmul crc32_pclmul e1000e snd_hda_codec ghash_clmulni_intel snd_hwdep snd_hda_core ptp pps_core snd_pcm mei_me mei prime_numbers [last unloaded: i915]
<4> [360.210925] CPU: 5 PID: 4317 Comm: i915_selftest Tainted: G     U            5.2.0-rc7-CI-CI_DRM_6401+ #1
<4> [360.210930] Hardware name: Intel Corporation Ice Lake Client Platform/IceLake Y LPDDR4x T4 RVP TLC, BIOS ICLSFWR1.R00.3102.A00.1903052247 03/05/2019
<4> [360.211063] RIP: 0010:i915_gem_cleanup_early+0x102/0x110 [i915]
<4> [360.211070] Code: 00 00 48 c7 c2 80 d5 a5 a0 48 c7 c7 18 4b 97 a0 e8 93 0c 82 e0 0f 0b 48 c7 c6 88 92 a8 a0 48 c7 c7 44 3e ab a0 e8 ce 9c 73 e0 <0f> 0b e9 42 ff ff ff 0f 1f 80 00 00 00 00 e8 9b 34 fe ff 31 c0 c3
<4> [360.211075] RSP: 0018:ffffc90000717ab0 EFLAGS: 00010286
<4> [360.211080] RAX: 0000000000000000 RBX: ffff888226c70000 RCX: 0000000000000005
<4> [360.211084] RDX: 0000000000000006 RSI: ffff88827c9e88b8 RDI: ffffffff8212e9d1
<4> [360.211088] RBP: ffff888226c70000 R08: 00000000a7749b50 R09: 0000000000000000
<4> [360.211092] R10: 0000000000000000 R11: 0000000000000000 R12: ffff888226c772d0
<4> [360.211096] R13: ffffffffa0b35250 R14: ffffffffa0b351e0 R15: ffffc90000717e88
<4> [360.211101] FS:  00007f7e51d6a240(0000) GS:ffff88829be80000(0000) knlGS:0000000000000000
<4> [360.211105] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [360.211109] CR2: 000055bc30d82588 CR3: 000000025cf08003 CR4: 0000000000760ee0
<4> [360.211113] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
<4> [360.211117] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
<4> [360.211121] PKRU: 55555554
<4> [360.211124] Call Trace:
<4> [360.211264]  i915_driver_cleanup_early+0x32/0x80 [i915]
<4> [360.211368]  i915_driver_release+0x67/0x90 [i915]
<4> [360.211437]  i915_pci_remove+0x21/0x30 [i915]
<4> [360.211437]  i915_pci_probe+0x93/0x1a0 [i915]
<4> [360.211437]  pci_device_probe+0x9e/0x120
<4> [360.211437]  really_probe+0xea/0x3c0
<4> [360.211437]  driver_probe_device+0x10b/0x120
<4> [360.211437]  device_driver_attach+0x4a/0x50
<4> [360.211437]  __driver_attach+0x97/0x130
<4> [360.211437]  ? device_driver_attach+0x50/0x50
<4> [360.211437]  bus_for_each_dev+0x74/0xc0
<4> [360.211437]  bus_add_driver+0x13f/0x210
<4> [360.211437]  ? 0xffffffffa01c0000
<4> [360.211437]  driver_register+0x56/0xe0
<4> [360.211437]  ? 0xffffffffa01c0000
<4> [360.211437]  do_one_initcall+0x58/0x300
<4> [360.211437]  ? do_init_module+0x1d/0x1f6
<4> [360.211437]  ? rcu_read_lock_sched_held+0x6f/0x80
<4> [360.211437]  ? kmem_cache_alloc_trace+0x261/0x290
<4> [360.211437]  do_init_module+0x56/0x1f6
<4> [360.211437]  load_module+0x24d1/0x2990
<4> [360.211437]  ? __se_sys_finit_module+0xd3/0xf0
<4> [360.211437]  __se_sys_finit_module+0xd3/0xf0
<4> [360.211437]  do_syscall_64+0x55/0x1c0
<4> [360.211437]  entry_SYSCALL_64_after_hwframe+0x49/0xbe
<4> [360.211437] RIP: 0033:0x7f7e51424839
<4> [360.211437] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 1f f6 2c 00 f7 d8 64 89 01 48
<4> [360.211437] RSP: 002b:00007ffe72ea2e58 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
<4> [360.211437] RAX: ffffffffffffffda RBX: 000055cd1c7a8150 RCX: 00007f7e51424839
<4> [360.211437] RDX: 0000000000000000 RSI: 000055cd1c7a1b40 RDI: 0000000000000006
<4> [360.211437] RBP: 000055cd1c7a1b40 R08: 0000000000000004 R09: 000055cd1a5f5c1b
<4> [360.211437] R10: 00007ffe72ea30a0 R11: 0000000000000246 R12: 0000000000000000
<4> [360.211437] R13: 000055cd1c7a2060 R14: 0000000000000020 R15: 000000000000004a
<4> [360.211437] irq event stamp: 324422
<4> [360.211437] hardirqs last  enabled at (324421): [<ffffffff8112889c>] vprintk_emit+0xcc/0x340
<4> [360.211437] hardirqs last disabled at (324422): [<ffffffff810019f0>] trace_hardirqs_off_thunk+0x1a/0x1c
<4> [360.211437] softirqs last  enabled at (324314): [<ffffffff81c0033a>] __do_softirq+0x33a/0x4b9
<4> [360.211437] softirqs last disabled at (324303): [<ffffffff810b6499>] irq_exit+0xa9/0xc0
<4> [360.211437] WARNING: CPU: 5 PID: 4317 at drivers/gpu/drm/i915/i915_gem.c:1686 i915_gem_cleanup_early+0x102/0x110 [i915]
<4> [360.211437] ---[ end trace 01007527877e0221 ]---
Comment 2 Chris Wilson 2019-07-03 12:30:43 UTC
That's just a warning, the fail is:

<7> [360.066418] [drm:intel_power_well_enable [i915]] enabling always-on
<6> [360.069945] RING_NONPRIV[0]: expected 0x0000731c, found 0x0000731c
<6> [360.069948] RING_NONPRIV[1]: expected 0x0000e18c, found 0x0000e18c
<6> [360.069951] RING_NONPRIV[2]: expected 0x0000e194, found 0x0000e194
<6> [360.069955] RING_NONPRIV[3]: expected 0x10002349, found 0x00002348
<6> [360.069958] RING_NONPRIV[4]: expected 0x00002094, found 0x00002094
<6> [360.069961] RING_NONPRIV[5]: expected 0x00002094, found 0x00002094
<6> [360.069964] RING_NONPRIV[6]: expected 0x00002094, found 0x00002094
<6> [360.069967] RING_NONPRIV[7]: expected 0x00002094, found 0x00002094
<6> [360.069970] RING_NONPRIV[8]: expected 0x00002094, found 0x00002094
<6> [360.069973] RING_NONPRIV[9]: expected 0x00002094, found 0x00002094
<6> [360.069976] RING_NONPRIV[10]: expected 0x00002094, found 0x00002094
<6> [360.069980] RING_NONPRIV[11]: expected 0x00002094, found 0x00002094
<3> [360.069983] Invalid RING_NONPRIV[3], expected 0x10002349, found 0x00002348
<3> [360.070035] Invalid whitelist *before* engine reset!

I think it is just the stepping in use on icl-dsi.
Comment 3 CI Bug Log 2019-07-03 14:03:41 UTC
A CI Bug Log filter associated to this bug has been updated:

{- icl-dsi: igt@i915_selftest@live_workarounds - dmesg-fail - WARN_ON(dev_priv-&gt;mm.shrink_count) -}
{+ icl-dsi: igt@i915_selftest@live_workarounds - dmesg-fail - WARN_ON(dev_priv-&gt;mm.shrink_count) +}


  No new failures caught with the new filter
Comment 4 CI Bug Log 2019-07-03 14:04:03 UTC
A CI Bug Log filter associated to this bug has been updated:

{- icl-dsi: igt@i915_selftest@live_workarounds - dmesg-fail - WARN_ON(dev_priv-&gt;mm.shrink_count) -}
{+ icl-dsi: igt@i915_selftest@live_workarounds - dmesg-fail -Invalid RING_NONPRIV[3], expected 0x10002349, found 0x00002348 +}


  No new failures caught with the new filter
Comment 5 Radosław Szwichtenberg 2019-07-12 07:06:45 UTC
Chris,
What is user impact of this failure?
Comment 6 Chris Wilson 2019-07-12 14:06:21 UTC
(In reply to Radosław Szwichtenberg from comment #5)
> Chris,
> What is user impact of this failure?

They should return their preproduction icl in exchange for a production model.
Comment 7 Lakshmi 2019-07-16 08:36:50 UTC
Adding comments from  Kumar Valsan, Prathap:

This is not actual BUG and expected on this stepping.  We need to run this test with on machines that is not PPOR:POR_M1.

Closing this bug as NOTABUG.


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.