[Bug 103707] [CI] igt at drv_selftest@ - dmesg-fail/dmesg-warn - BUG: MAX_LOCKDEP_CHAINS too low!
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Nov 14 11:43:46 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=103707
Marta Löfstedt <marta.lofstedt at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Whiteboard| |ReadyForDev
i915 platform| |GLK, BXT
--- Comment #5 from Marta Löfstedt <marta.lofstedt at intel.com> ---
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3343/shard-apl7/igt@drv_selftest@live_evict.html
<7>[ 1875.409195] [drm:__bxt_hpd_detection_setup [i915]] Invert bit setting:
hp_ctl:10001818 hp_port:30
<7>[ 1875.409885] BUG: MAX_LOCKDEP_CHAINS too low!
<7>[ 1875.409886] turning off the locking correctness validator.
<4>[ 1875.409887] CPU: 3 PID: 16400 Comm: drv_selftest Tainted: G U
4.14.0-rc8-CI-CI_DRM_3343+ #1
<4>[ 1875.409888] Hardware name: /NUC6CAYB, BIOS
AYAPLCEL.86A.0040.2017.0619.1722 06/19/2017
<4>[ 1875.409888] Call Trace:
<4>[ 1875.409889] dump_stack+0x68/0x9f
<4>[ 1875.409889] __lock_acquire+0x19d5/0x1b00
<4>[ 1875.409890] lock_acquire+0xb0/0x200
<4>[ 1875.409891] ? lock_acquire+0xb0/0x200
<4>[ 1875.409891] ? console_unlock+0x97/0x570
<4>[ 1875.409892] _raw_spin_lock+0x32/0x50
<4>[ 1875.409892] ? console_unlock+0x97/0x570
<4>[ 1875.409893] console_unlock+0x97/0x570
<4>[ 1875.409893] vprintk_emit+0x254/0x3b0
<4>[ 1875.409894] ? try_to_wake_up+0x2b4/0x620
<4>[ 1875.409894] vprintk_default+0x1f/0x30
<4>[ 1875.409895] vprintk_func+0x2c/0x90
<4>[ 1875.409896] printk+0x43/0x4b
<4>[ 1875.409896] ? __bxt_hpd_detection_setup+0x56/0xe0 [i915]
<4>[ 1875.409897] drm_printk+0x8e/0x90
<4>[ 1875.409897] ? fwtable_read32+0x251/0x2c0 [i915]
<4>[ 1875.409898] ? fwtable_read32+0x8d/0x2c0 [i915]
<4>[ 1875.409899] __bxt_hpd_detection_setup+0x56/0xe0 [i915]
<4>[ 1875.409899] bxt_hpd_irq_setup+0x72/0x80 [i915]
<4>[ 1875.409900] intel_hpd_init+0x93/0xa0 [i915]
<4>[ 1875.409900] i915_driver_load+0x14b8/0x1600 [i915]
<4>[ 1875.409901] i915_pci_probe+0x37/0x90 [i915]
<4>[ 1875.409902] pci_device_probe+0xa8/0x130
<4>[ 1875.409902] driver_probe_device+0x29c/0x450
<4>[ 1875.409903] __driver_attach+0xe3/0xf0
<4>[ 1875.409903] ? driver_probe_device+0x450/0x450
<4>[ 1875.409904] bus_for_each_dev+0x62/0xa0
<4>[ 1875.409904] driver_attach+0x1e/0x20
<4>[ 1875.409905] bus_add_driver+0x173/0x270
<4>[ 1875.409906] driver_register+0x60/0xe0
<4>[ 1875.409906] __pci_register_driver+0x6b/0x70
<4>[ 1875.409907] i915_init+0x6f/0x78 [i915]
<4>[ 1875.409908] ? 0xffffffffa04c8000
<4>[ 1875.409908] do_one_initcall+0x43/0x170
<4>[ 1875.409909] ? rcu_read_lock_sched_held+0x7a/0x90
<4>[ 1875.409909] ? kmem_cache_alloc_trace+0x270/0x2d0
<4>[ 1875.409910] do_init_module+0x5f/0x206
<4>[ 1875.409910] load_module+0x2581/0x2dd0
<4>[ 1875.409911] ? show_coresize+0x30/0x30
<4>[ 1875.409912] ? kernel_read+0x31/0x50
<4>[ 1875.409912] SyS_finit_module+0xc1/0x100
<4>[ 1875.409913] ? SyS_finit_module+0xc1/0x100
<4>[ 1875.409913] entry_SYSCALL_64_fastpath+0x1c/0xb1
<4>[ 1875.409914] RIP: 0033:0x7fe4d9d839f9
<4>[ 1875.409915] RSP: 002b:00007ffe7bb1cbf8 EFLAGS: 00000202 ORIG_RAX:
0000000000000139
<4>[ 1875.409916] RAX: ffffffffffffffda RBX: ffffffff81492083 RCX:
00007fe4d9d839f9
<4>[ 1875.409917] RDX: 0000000000000000 RSI: 00007fe4dacb6e23 RDI:
0000000000000003
<4>[ 1875.409918] RBP: ffffc90000517f88 R08: 0000000000000000 R09:
0000000000000000
<4>[ 1875.409919] R10: 0000000000000003 R11: 0000000000000202 R12:
0000000000000000
<4>[ 1875.409919] R13: 000055e26b46ced0 R14: 0000000000000000 R15:
000055e26b464990
<4>[ 1875.409920] ? __this_cpu_preempt_check+0x13/0x20
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20171114/e37a4d0f/attachment.html>
More information about the intel-gfx-bugs
mailing list