Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • intel intel
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 682
    • Issues 682
    • List
    • Boards
    • Service Desk
    • Milestones
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • drm
  • intelintel
  • Issues
  • #6599
Closed
Open
Issue created Aug 17, 2022 by Ravi V@rveesamReporter

igt@i915_module_load@load | igt@runner@aborted - dmesg-warn/fail - WARNING: inconsistent lock state, inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage, at: iommu_flush_dev_iotlb.part.*, intel_iommu_attach_device.*

boot log: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11991/shard-tglu-6/boot13.txt

<4>[    6.824299] ================================
<4>[    6.824303] WARNING: inconsistent lock state
<4>[    6.824306] 6.0.0-rc1-CI_DRM_11991-g4753c139edec+ #1 Not tainted
<4>[    6.824312] --------------------------------
<4>[    6.824315] inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
<4>[    6.824320] swapper/4/0 [HC0[0]:SC1[1]:HE1:SE0] takes:
<4>[    6.824325] ffff8881034a5678 (&domain->lock){+.?.}-{2:2}, at: iommu_flush_dev_iotlb.part.61+0x23/0x80
<4>[    6.824340] {SOFTIRQ-ON-W} state was registered at:
<4>[    6.824344]   lock_acquire+0xd3/0x310
<4>[    6.824350]   _raw_spin_lock+0x2a/0x40
<4>[    6.824355]   domain_update_iommu_cap+0x20b/0x2c0
<4>[    6.824360]   intel_iommu_attach_device+0x5bd/0x860
<4>[    6.824365]   __iommu_attach_device+0x18/0xe0
<4>[    6.824370]   bus_iommu_probe+0x1f3/0x2d0
<4>[    6.824376]   bus_set_iommu+0x82/0xd0
<4>[    6.824380]   intel_iommu_init+0xe45/0x102a
<4>[    6.824388]   pci_iommu_init+0x9/0x31
<4>[    6.824394]   do_one_initcall+0x53/0x2f0
<4>[    6.824400]   kernel_init_freeable+0x18f/0x1e1
<4>[    6.824405]   kernel_init+0x11/0x120
<4>[    6.824410]   ret_from_fork+0x1f/0x30
<4>[    6.824414] irq event stamp: 69232
<4>[    6.824418] hardirqs last  enabled at (69232): [<ffffffff81b59274>] _raw_spin_unlock_irqrestore+0x54/0x70
<4>[    6.824427] hardirqs last disabled at (69231): [<ffffffff81b5901b>] _raw_spin_lock_irqsave+0x4b/0x50
<4>[    6.824435] softirqs last  enabled at (69198): [<ffffffff81e00323>] __do_softirq+0x323/0x48e
<4>[    6.824443] softirqs last disabled at (69227): [<ffffffff810c1588>] irq_exit_rcu+0xb8/0xe0
<4>[    6.824451] 
                  other info that might help us debug this:
<4>[    6.824456]  Possible unsafe locking scenario:

<4>[    6.824460]        CPU0
<4>[    6.824463]        ----
<4>[    6.824465]   lock(&domain->lock);
<4>[    6.824470]   <Interrupt>
<4>[    6.824472]     lock(&domain->lock);
<4>[    6.824477] 
                   *** DEADLOCK ***

<4>[    6.824481] 1 lock held by swapper/4/0:
<4>[    6.824485]  #0: ffffc90000218ea8 ((&cookie->fq_timer)){+.-.}-{0:0}, at: call_timer_fn+0x0/0x2c0
<4>[    6.824496] 
                  stack backtrace:
<4>[    6.824500] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 6.0.0-rc1-CI_DRM_11991-g4753c139edec+ #1
<4>[    6.824508] Hardware name: Intel(R) Client Systems NUC11TNHi5/NUC11TNBi5, BIOS TNTGL357.0042.2020.1221.1743 12/21/2020
<4>[    6.824516] Call Trace:
<4>[    6.824519]  <IRQ>
<4>[    6.824523]  dump_stack_lvl+0x56/0x7f
<4>[    6.824528]  mark_lock.part.47+0x8d1/0xdb0
<4>[    6.824535]  __lock_acquire+0x824/0xb70
<4>[    6.824540]  lock_acquire+0xd3/0x310
<4>[    6.824544]  ? iommu_flush_dev_iotlb.part.61+0x23/0x80
<4>[    6.824550]  ? iommu_dma_map_sg+0x400/0x400
<4>[    6.824555]  _raw_spin_lock+0x2a/0x40
<4>[    6.824559]  ? iommu_flush_dev_iotlb.part.61+0x23/0x80
<4>[    6.824564]  iommu_flush_dev_iotlb.part.61+0x23/0x80
<4>[    6.824569]  intel_flush_iotlb_all+0x95/0x110
<4>[    6.824575]  fq_flush_iotlb+0x1d/0x30
<4>[    6.824578]  fq_flush_timeout+0x28/0xc0
<4>[    6.824583]  ? iommu_dma_map_sg+0x400/0x400
<4>[    6.824587]  ? iommu_dma_map_sg+0x400/0x400
<4>[    6.824591]  call_timer_fn+0x9c/0x2c0
<4>[    6.824596]  run_timer_softirq+0x548/0x570
<4>[    6.824602]  __do_softirq+0xda/0x48e
<4>[    6.824607]  irq_exit_rcu+0xb8/0xe0
<4>[    6.824611]  sysvec_apic_timer_interrupt+0x9e/0xc0
<4>[    6.824617]  </IRQ>
<4>[    6.824619]  <TASK>
<4>[    6.824622]  asm_sysvec_apic_timer_interrupt+0x16/0x20
<4>[    6.824627] RIP: 0010:cpuidle_enter_state+0x104/0x5c0
<4>[    6.824634] Code: 02 00 00 31 ff e8 4c db 83 ff 45 84 ff 74 12 9c 58 f6 c4 02 0f 85 31 04 00 00 31 ff e8 25 cb 8a ff e8 f0 f3 8e ff fb 45 85 f6 <0f> 88 b9 01 00 00 49 63 d6 4c 2b 24 24 48 8d 04 52 48 8d 04 82 49
<4>[    6.824647] RSP: 0018:ffffc90000147e88 EFLAGS: 00000202
<4>[    6.824652] RAX: 0000000000000004 RBX: 0000000000000001 RCX: 0000000000000000
<4>[    6.824658] RDX: 0000000000000000 RSI: ffffffff823ad288 RDI: ffffffff8234c5e7
<4>[    6.824663] RBP: ffffe8ffffc2e690 R08: 0000000000000001 R09: 0000000000000001
<4>[    6.824669] R10: 0000000000000001 R11: ffff8884a003a344 R12: 0000000196c0935d
<4>[    6.824675] R13: ffffffff827a85e0 R14: 0000000000000001 R15: 0000000000000000
<4>[    6.824682]  ? cpuidle_enter_state+0x100/0x5c0
<4>[    6.824687]  cpuidle_enter+0x24/0x40
<4>[    6.824692]  do_idle+0x253/0x2a0
<4>[    6.824698]  cpu_startup_entry+0x14/0x20
<4>[    6.824703]  start_secondary+0x10f/0x130
<4>[    6.824709]  secondary_startup_64_no_verify+0xce/0xdb
<4>[    6.824716]  </TASK>
Edited Aug 17, 2022 by Ravi V
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking