Bug 110446

Summary: [CI][DRMTIP] igt@runner@aborted - WARNING: CPU: 0 PID: 12 at kernel/locking/lockdep.c:4920 lockdep_unregister_key+0xa8/0x130
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED NOTOURBUG QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: BSW/CHT, G45 i915 features:

Description Lakshmi 2019-04-16 08:30:50 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_255/fi-bsw-n3050/igt@runner@aborted.html

Aborting.
Previous test: gem_eio (hibernate)
Next test: kms_frontbuffer_tracking (psr-shrfb-scaledprimary)

Kernel badly tainted (0x240) (check dmesg for details):
	(0x200) TAINT_WARN: WARN_ON has happened.
Comment 2 Chris Wilson 2019-04-16 13:46:01 UTC
<4>[  335.117647] WARNING: CPU: 0 PID: 12 at kernel/locking/lockdep.c:4920 lockdep_unregister_key+0xa8/0x130
<4>[  335.117653] Modules linked in: vgem btusb btrtl btbcm btintel snd_hda_codec_hdmi bluetooth snd_hda_codec_realtek snd_hda_codec_generic ecdh_generic i915 coretemp snd_hda_intel crct10dif_pclmul crc32_pclmul snd_hda_codec ghash_clmulni_intel snd_hwdep snd_hda_core r8169 snd_pcm lpc_ich realtek prime_numbers pinctrl_cherryview
<4>[  335.117696] CPU: 0 PID: 12 Comm: kworker/0:1 Tainted: G     U            5.1.0-rc5-g6ba1335cf9df-drmtip_255+ #1
<4>[  335.117700] Hardware name:  /NUC5CPYB, BIOS PYBSWCEL.86A.0058.2016.1102.1842 11/02/2016
<4>[  335.117708] Workqueue: events pwq_unbound_release_workfn
<4>[  335.117718] RIP: 0010:lockdep_unregister_key+0xa8/0x130
<4>[  335.117725] Code: 34 49 a6 48 c1 e5 04 48 81 c5 78 b4 48 a6 48 85 c0 48 89 c2 74 14 48 39 c3 75 07 eb 52 48 39 c3 74 4a 48 8b 00 48 85 c0 75 f3 <0f> 0b ba 01 00 00 00 48 89 de 48 89 ef e8 66 ed ff ff 48 89 ef e8
<4>[  335.117730] RSP: 0018:ffff9d844007be10 EFLAGS: 00010046
<4>[  335.117738] RAX: 0000000000000000 RBX: ffff91daa83db2d0 RCX: 0000000000000000
<4>[  335.117742] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000ffffffff
<4>[  335.117746] RBP: ffffffffa648b478 R08: 0000000000000000 R09: 0000000000000000
<4>[  335.117750] R10: ffff9d844007be00 R11: fefefefefefefeff R12: 0000000000000246
<4>[  335.117754] R13: 000000000000009e R14: ffff91daa83db1b8 R15: 0000000000000000
<4>[  335.117760] FS:  0000000000000000(0000) GS:ffff91dabba00000(0000) knlGS:0000000000000000
<4>[  335.117764] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4>[  335.117768] CR2: 0000558b9aa13f48 CR3: 0000000176214000 CR4: 00000000001006f0
<4>[  335.117772] Call Trace:
<4>[  335.117784]  pwq_unbound_release_workfn+0xb8/0xe0
<4>[  335.117796]  process_one_work+0x245/0x610
<4>[  335.117807]  worker_thread+0x37/0x380
<4>[  335.117817]  ? process_one_work+0x610/0x610
<4>[  335.117824]  kthread+0x119/0x130
<4>[  335.117832]  ? kthread_park+0x80/0x80
<4>[  335.117843]  ret_from_fork+0x3a/0x50
<4>[  335.117856] irq event stamp: 77416
<4>[  335.117863] hardirqs last  enabled at (77415): [<ffffffffa49b5b94>] _raw_spin_unlock_irq+0x24/0x50
<4>[  335.117870] hardirqs last disabled at (77416): [<ffffffffa49ae79a>] __schedule+0xaa/0xb40
<4>[  335.117880] softirqs last  enabled at (77350): [<ffffffffa416b205>] css_release_work_fn+0x195/0x310
<4>[  335.117888] softirqs last disabled at (77348): [<ffffffffa416b1ee>] css_release_work_fn+0x17e/0x310
<4>[  335.117897] WARNING: CPU: 0 PID: 12 at kernel/locking/lockdep.c:4920 lockdep_unregister_key+0xa8/0x130
Comment 3 CI Bug Log 2019-05-27 12:57:35 UTC
A CI Bug Log filter associated to this bug has been updated:

{- BSW: igt@runner@aborted - fail - Kernel badly tainted (0x240)  -}
{+ BSW ELK: igt@runner@aborted - fail - Kernel badly tainted (0x240)  +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_293/fi-elk-e7500/igt@runner@aborted.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_293/fi-elk-e7500/igt@runner@aborted.html

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.