That's an artifact of hitting the debugobject spam early on during boot:

<6>[    1.353329] Registered efivars operations
<4>[    1.353329] ODEBUG: object 0000000015ac3fa7 is NOT on stack 00000000cd66b6c5, but annotated.
<4>[    1.353329] WARNING: CPU: 0 PID: 1 at lib/debugobjects.c:369 __debug_object_init+0x281/0x560
<4>[    1.353329] Modules linked in:
<4>[    1.353329] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.20.0-rc1-CI-CI_DRM_5089+ #1
<4>[    1.353329] Hardware name: System manufacturer System Product Name/Z170M-PLUS, BIOS 3610 03/29/2018
<4>[    1.353329] RIP: 0010:__debug_object_init+0x281/0x560
<4>[    1.353329] Code: 84 55 fe ff ff 83 c0 01 48 89 de 48 c7 c7 50 6f 0d 82 89 05 1d 77 22 02 65 48 8b 04 25 00 4f 01 00 48 8b 50 18 e8 28 d4 c5 ff <0f> 0b 41 8b 44 24 10 83 f8 03 0f 85 2e fe ff ff 4c 89 e7 48 c7 c6
<4>[    1.353329] RSP: 0000:ffffc9000002bd10 EFLAGS: 00010082
<4>[    1.353329] RAX: 0000000000000050 RBX: ffffffff83ff98d0 RCX: 0000000000000000
<4>[    1.353329] RDX: 0000000000000000 RSI: ffffffff82128772 RDI: 00000000ffffffff
<4>[    1.353329] RBP: ffffffff8223c8a0 R08: 0000000000000000 R09: 0000000000000001
<4>[    1.353329] R10: ffffc9000002bc90 R11: 0000000000000000 R12: ffff88022c2982f8
<4>[    1.353329] R13: ffffffff83747dc8 R14: 0000000000000206 R15: 0000000000081900
<4>[    1.353329] FS:  0000000000000000(0000) GS:ffff88022ea00000(0000) knlGS:0000000000000000
<4>[    1.353329] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4>[    1.353329] CR2: 0000000000000000 CR3: 0000000005210001 CR4: 00000000003606f0
<4>[    1.353329] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
<4>[    1.353329] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
<4>[    1.353333] Call Trace:
<4>[    1.353343]  virt_efi_get_next_variable+0x9d/0x190
<4>[    1.353352]  efivar_init+0x11f/0x3a0
<4>[    1.353361]  ? efivar_ssdt_setup+0x3a/0x3a
<4>[    1.353370]  ? _raw_spin_unlock_irqrestore+0x4c/0x60
<4>[    1.353380]  ? lockdep_hardirqs_on+0xe0/0x1b0
<4>[    1.353389]  ? match_config_table.part.0+0x129/0x129
<4>[    1.353398]  ? efisubsys_init+0x155/0x2fc
<4>[    1.353405]  efisubsys_init+0x155/0x2fc
<4>[    1.353413]  ? match_config_table.part.0+0x129/0x129
<4>[    1.353422]  ? set_debug_rodata+0xc/0xc
<4>[    1.353430]  do_one_initcall+0x58/0x2e0
<4>[    1.353438]  ? set_debug_rodata+0xc/0xc
<4>[    1.353447]  kernel_init_freeable+0x2c0/0x352
<4>[    1.353455]  ? rest_init+0x250/0x250
<4>[    1.353463]  kernel_init+0x5/0x100
<4>[    1.353470]  ret_from_fork+0x3a/0x50
<4>[    1.353480] irq event stamp: 2233218
<4>[    1.353487] hardirqs last  enabled at (2233217): [<ffffffff81953d2c>] _raw_spin_unlock_irqrestore+0x4c/0x60
<4>[    1.353503] hardirqs last disabled at (2233218): [<ffffffff81953b9d>] _raw_spin_lock_irqsave+0xd/0x50
<4>[    1.353517] softirqs last  enabled at (2232116): [<ffffffff81c0033a>] __do_softirq+0x33a/0x4b9
<4>[    1.353532] softirqs last disabled at (2232107): [<ffffffff8108df29>] irq_exit+0xa9/0xc0
<4>[    1.353545] WARNING: CPU: 0 PID: 1 at lib/debugobjects.c:369 __debug_object_init+0x281/0x560
<4>[    1.353564] ---[ end trace 982afa883b783f4b ]---

Caused by

commit 9dbbedaa6171247c4c7c40b83f05b200a117c2e0
Author: Sai Praneeth <sai.praneeth.prakhya@intel.com>
Date:   Tue Sep 11 12:15:21 2018 -0700

    efi: Make efi_rts_work accessible to efi page fault handler
    
    After the kernel has booted, if any accesses by firmware causes a page
    fault, the efi page fault handler would freeze efi_rts_wq and schedules
    a new process. To do this, the efi page fault handler needs
    efi_rts_work. Hence, make it accessible.
    
    There will be no race conditions in accessing this structure, because
    all the calls to efi runtime services are already serialized.
    
    Tested-by: Bhupesh Sharma <bhsharma@redhat.com>
    Suggested-by: Matt Fleming <matt@codeblueprint.co.uk>
    Based-on-code-from: Ricardo Neri <ricardo.neri@intel.com>
    Signed-off-by: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>
    Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>

Fix en route: 1540304307-2806-1-git-send-email-longman@redhat.com

Full link for the lazy (like me):

https://lore.kernel.org/lkml/1540304307-2806-1-git-send-email-longman@redhat.com/

The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* BSW: igt@runner@aborted - fail - kms_pipe_crc_basic (suspend-read-crc-pipe-c)
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_207/fi-bsw-n3050/igt@runner@aborted.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_208/fi-bsw-n3050/igt@runner@aborted.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_209/fi-bsw-n3050/igt@runner@aborted.html

(In reply to CI Bug Log from comment #5)
> The CI Bug Log issue associated to this bug has been updated.
> 
> ### New filters associated
> 
> * BSW: igt@runner@aborted - fail - kms_pipe_crc_basic
> (suspend-read-crc-pipe-c)
>   -
> https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_207/fi-bsw-n3050/
> igt@runner@aborted.html
>   -
> https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_208/fi-bsw-n3050/
> igt@runner@aborted.html
>   -
> https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_209/fi-bsw-n3050/
> igt@runner@aborted.html

The fix has landed (https://cgit.freedesktop.org/drm-tip/commit/?id=ef1491e791308317bb9851a0ad380c4a68b58d54), and the issues you filed here are different. Please file a new bug for:

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_216/fi-bsw-n3050/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes.html

<4> [61.382515] 
<4> [61.382525] ======================================================
<4> [61.382528] WARNING: possible circular locking dependency detected
<4> [61.382532] 5.0.0-rc5-g041ba1d6aa0f-drmtip_216+ #1 Tainted: G     U           
<4> [61.382535] ------------------------------------------------------
<4> [61.382538] kms_plane/1072 is trying to acquire lock:
<4> [61.382542] 00000000e7bea55b (&dev->struct_mutex){+.+.}, at: i915_gem_fault+0x1f8/0x850 [i915]
<4> [61.382656] 
but task is already holding lock:
<4> [61.382658] 00000000c73dd26a (&mm->mmap_sem){++++}, at: __do_page_fault+0x133/0x500
<4> [61.382668] 
which lock already depends on the new lock.

<4> [61.382670] 
the existing dependency chain (in reverse order) is:
<4> [61.382673] 
-> #4 (&mm->mmap_sem){++++}:
<4> [61.382682]        _copy_to_user+0x1e/0x70
<4> [61.382687]        perf_read+0x232/0x2a0
<4> [61.382693]        __vfs_read+0x31/0x190
<4> [61.382697]        vfs_read+0x9e/0x150
<4> [61.382700]        ksys_read+0x50/0xc0
<4> [61.382705]        do_syscall_64+0x55/0x190
<4> [61.382711]        entry_SYSCALL_64_after_hwframe+0x49/0xbe
<4> [61.382713] 
-> #3 (&cpuctx_mutex){+.+.}:
<4> [61.382719]        perf_event_init_cpu+0x5a/0x90
<4> [61.382725]        perf_event_init+0x1c9/0x1f9
<4> [61.382729]        start_kernel+0x339/0x4c0
<4> [61.382733]        secondary_startup_64+0xa4/0xb0
<4> [61.382735] 
-> #2 (pmus_lock){+.+.}:
<4> [61.382741]        perf_event_init_cpu+0x21/0x90
<4> [61.382746]        cpuhp_invoke_callback+0x9b/0xa10
<4> [61.382750]        _cpu_up+0xa2/0x140
<4> [61.382754]        do_cpu_up+0x6d/0xb0
<4> [61.382758]        smp_init+0x5d/0xa4
<4> [61.382762]        kernel_init_freeable+0x16f/0x359
<4> [61.382765]        kernel_init+0x5/0x100
<4> [61.382769]        ret_from_fork+0x3a/0x50
<4> [61.382771] 
-> #1 (cpu_hotplug_lock.rw_sem){++++}:
<4> [61.382778]        stop_machine+0x12/0x30
<4> [61.382865]        bxt_vtd_ggtt_insert_entries__BKL+0x36/0x50 [i915]
<4> [61.382947]        ggtt_bind_vma+0x59/0x90 [i915]
<4> [61.383034]        i915_vma_bind+0xe8/0x2c0 [i915]
<4> [61.383121]        __i915_vma_do_pin+0x99/0xdc0 [i915]
<4> [61.383205]        i915_gem_init+0x318/0xa20 [i915]
<4> [61.383282]        i915_driver_load+0xd5c/0x15a0 [i915]
<4> [61.383360]        i915_pci_probe+0x29/0xa0 [i915]
<4> [61.383365]        pci_device_probe+0xa1/0x130
<4> [61.383370]        really_probe+0xf3/0x3e0
<4> [61.383374]        driver_probe_device+0x10a/0x120
<4> [61.383378]        __driver_attach+0xdb/0x100
<4> [61.383382]        bus_for_each_dev+0x74/0xc0
<4> [61.383386]        bus_add_driver+0x15f/0x250
<4> [61.383389]        driver_register+0x56/0xe0
<4> [61.383393]        do_one_initcall+0x58/0x2e0
<4> [61.383397]        do_init_module+0x56/0x1ea
<4> [61.383401]        load_module+0x2718/0x29f0
<4> [61.383404]        __se_sys_finit_module+0xd3/0xf0
<4> [61.383408]        do_syscall_64+0x55/0x190
<4> [61.383412]        entry_SYSCALL_64_after_hwframe+0x49/0xbe
<4> [61.383414] 
-> #0 (&dev->struct_mutex){+.+.}:
<4> [61.383420]        __mutex_lock+0x8c/0x960
<4> [61.383504]        i915_gem_fault+0x1f8/0x850 [i915]
<4> [61.383509]        __do_fault+0x2c/0xb0
<4> [61.383512]        __handle_mm_fault+0x8ee/0xfa0
<4> [61.383515]        handle_mm_fault+0x196/0x3a0
<4> [61.383520]        __do_page_fault+0x246/0x500
<4> [61.383524]        page_fault+0x1e/0x30
<4> [61.383526] 
other info that might help us debug this:

<4> [61.383528] Chain exists of:
  &dev->struct_mutex --> &cpuctx_mutex --> &mm->mmap_sem

<4> [61.383533]  Possible unsafe locking scenario:

<4> [61.383536]        CPU0                    CPU1
<4> [61.383538]        ----                    ----
<4> [61.383540]   lock(&mm->mmap_sem);
<4> [61.383543]                                lock(&cpuctx_mutex);
<4> [61.383546]                                lock(&mm->mmap_sem);
<4> [61.383549]   lock(&dev->struct_mutex);
<4> [61.383552] 
 *** DEADLOCK ***

<4> [61.383555] 1 lock held by kms_plane/1072:
<4> [61.383557]  #0: 00000000c73dd26a (&mm->mmap_sem){++++}, at: __do_page_fault+0x133/0x500
<4> [61.383564] 
stack backtrace:
<4> [61.383569] CPU: 0 PID: 1072 Comm: kms_plane Tainted: G     U            5.0.0-rc5-g041ba1d6aa0f-drmtip_216+ #1
<4> [61.383572] Hardware name:  /NUC5CPYB, BIOS PYBSWCEL.86A.0058.2016.1102.1842 11/02/2016
<4> [61.383574] Call Trace:
<4> [61.383583]  dump_stack+0x67/0x9b
<4> [61.383590]  print_circular_bug.isra.16+0x1c8/0x2b0
<4> [61.383595]  __lock_acquire+0x183a/0x1b00
<4> [61.383603]  ? lock_acquire+0xa6/0x1c0
<4> [61.383607]  lock_acquire+0xa6/0x1c0
<4> [61.383694]  ? i915_gem_fault+0x1f8/0x850 [i915]
<4> [61.383699]  __mutex_lock+0x8c/0x960
<4> [61.383784]  ? i915_gem_fault+0x1f8/0x850 [i915]
<4> [61.383869]  ? i915_gem_fault+0x1f8/0x850 [i915]
<4> [61.383874]  ? mark_held_locks+0x50/0x80
<4> [61.383878]  ? _raw_spin_unlock_irqrestore+0x4c/0x60
<4> [61.383883]  ? lockdep_hardirqs_on+0xe0/0x1b0
<4> [61.383969]  ? i915_gem_fault+0x1f8/0x850 [i915]
<4> [61.384053]  i915_gem_fault+0x1f8/0x850 [i915]
<4> [61.384058]  ? ptlock_alloc+0x15/0x30
<4> [61.384063]  ? lockdep_init_map+0x4d/0x1b0
<4> [61.384067]  __do_fault+0x2c/0xb0
<4> [61.384072]  __handle_mm_fault+0x8ee/0xfa0
<4> [61.384078]  handle_mm_fault+0x196/0x3a0
<4> [61.384083]  __do_page_fault+0x246/0x500
<4> [61.384089]  ? page_fault+0x8/0x30
<4> [61.384093]  page_fault+0x1e/0x30
<4> [61.384097] RIP: 0033:0x7fc103499a80
<4> [61.384102] Code: 04 89 38 48 83 c0 04 39 f1 89 ca 75 ed 83 fa 7f 7e 45 83 c2 80 89 d6 c1 ee 07 89 f1 48 83 c1 01 48 c1 e1 07 48 01 c1 0f 1f 00 <0f> 29 00 48 83 e8 80 0f 29 40 90 0f 29 40 a0 0f 29 40 b0 0f 29 40
<4> [61.384105] RSP: 002b:00007ffdb8605b40 EFLAGS: 00010206
<4> [61.384109] RAX: 00007fc0f88c3000 RBX: 0000000000001e00 RCX: 00007fc0f88c4e00
<4> [61.384112] RDX: 0000000000001d80 RSI: 000000000000003b RDI: 00000000ffff0000
<4> [61.384115] RBP: 0000000000000000 R08: 00000000ffff0000 R09: 00007fc0f88c3000
<4> [61.384118] R10: 0000000000000437 R11: 0000000000001e00 R12: 0000000000000000
<4> [61.384121] R13: 0000000000000020 R14: 0000000000000780 R15: 00007fc0f88c3000

The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.

Original fix landed, but this bug was reopened for a new circular lockdep.