Bug 108551 - [CI][BAT] igt@drv_module_reload@basic-no-display - dmesg-warn - Acquiring modeset locks failed with -22
Summary: [CI][BAT] igt@drv_module_reload@basic-no-display - dmesg-warn - Acquiring mod...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-25 11:36 UTC by Martin Peres
Modified: 2019-02-22 13:50 UTC (History)
1 user (show)

See Also:
i915 platform: GLK
i915 features:


Attachments
dmesg for boom (4.03 MB, text/x-log)
2018-10-25 11:45 UTC, Daniel Vetter
no flags Details

Description Martin Peres 2018-10-25 11:36:11 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4693/fi-glk-j4005/igt@drv_module_reload@basic-no-display.html

<4> [306.685966] ------------[ cut here ]------------
<4> [306.685970] Acquiring modeset locks failed with -22
<4> [306.686057] WARNING: CPU: 1 PID: 107 at drivers/gpu/drm/i915/intel_ddi.c:3703 intel_ddi_hotplug+0x11f/0x2e0 [i915]
<4> [306.686061] Modules linked in: i915(-) vgem snd_hda_codec_hdmi btusb btrtl btbcm btintel x86_pkg_temp_thermal snd_hda_codec_realtek coretemp snd_hda_codec_generic crct10dif_pclmul crc32_pclmul bluetooth ghash_clmulni_intel ecdh_generic r8169 i2c_hid snd_hda_codec snd_hwdep snd_hda_core snd_pcm pinctrl_geminilake pinctrl_intel mei_me mei prime_numbers [last unloaded: snd_hda_intel]
<4> [306.686139] CPU: 1 PID: 107 Comm: kworker/1:3 Tainted: G     U  W         4.19.0-rc8-CI-CI_DRM_5033+ #1
<4> [306.686142] Hardware name: Intel Corporation NUC7CJYH/NUC7JYB, BIOS JYGLKCPX.86A.0027.2018.0125.1347 01/25/2018
<4> [306.686195] Workqueue: events i915_hotplug_work_func [i915]
<4> [306.686250] RIP: 0010:intel_ddi_hotplug+0x11f/0x2e0 [i915]
<4> [306.686254] Code: ff 48 8d 7c 24 10 41 bc f4 ff ff ff e8 ba 5b e0 e0 48 8d 7c 24 10 e8 a0 5d e0 e0 44 89 e6 48 c7 c7 88 b8 8b a0 e8 21 e8 87 e0 <0f> 0b e9 58 ff ff ff 49 8d bc 24 98 05 00 00 48 8d 74 24 10 e8 d8
<4> [306.686257] RSP: 0018:ffffc90000b87d40 EFLAGS: 00010286
<4> [306.686262] RAX: 0000000000000000 RBX: ffff880268dec2a8 RCX: 0000000000000001
<4> [306.686265] RDX: 0000000080000001 RSI: ffffffff820c30ce RDI: 00000000ffffffff
<4> [306.686267] RBP: ffff8802697aae98 R08: 000000005216d197 R09: 0000000000000000
<4> [306.686270] R10: 0000000000000000 R11: 0000000000000000 R12: 00000000ffffffea
<4> [306.686272] R13: 0000000000000000 R14: ffff8802116db7e8 R15: ffff8802308392a8
<4> [306.686275] FS:  0000000000000000(0000) GS:ffff880277e80000(0000) knlGS:0000000000000000
<4> [306.686278] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [306.686281] CR2: 00007fbfb722a4a0 CR3: 0000000269744000 CR4: 0000000000340ee0
<4> [306.686283] Call Trace:
<4> [306.686349]  i915_hotplug_work_func+0x1a9/0x240 [i915]
<4> [306.686361]  process_one_work+0x245/0x610
<4> [306.686372]  worker_thread+0x37/0x380
<4> [306.686380]  ? process_one_work+0x610/0x610
<4> [306.686383]  kthread+0x119/0x130
<4> [306.686387]  ? kthread_park+0x80/0x80
<4> [306.686395]  ret_from_fork+0x24/0x50
<4> [306.686409] irq event stamp: 3532226
<4> [306.686414] hardirqs last  enabled at (3532225): [<ffffffff810f827a>] console_unlock+0x3fa/0x5f0
<4> [306.686419] hardirqs last disabled at (3532226): [<ffffffff81001930>] trace_hardirqs_off_thunk+0x1a/0x1c
<4> [306.686422] softirqs last  enabled at (3531368): [<ffffffff81c0031d>] __do_softirq+0x31d/0x483
<4> [306.686427] softirqs last disabled at (3531361): [<ffffffff8108c539>] irq_exit+0xa9/0xc0
<4> [306.686479] WARNING: CPU: 1 PID: 107 at drivers/gpu/drm/i915/intel_ddi.c:3703 intel_ddi_hotplug+0x11f/0x2e0 [i915]
<4> [306.686482] ---[ end trace 2446ff6c8945ee0b ]---
Comment 1 Daniel Vetter 2018-10-25 11:44:45 UTC
Note that first in the logs things go totally sideways with bug #107425, then later on we go boom here.

I have no idea whether these are related or not.
Comment 2 Daniel Vetter 2018-10-25 11:45:42 UTC
Created attachment 142195 [details]
dmesg for boom
Comment 3 Lakshmi 2019-02-22 13:06:40 UTC
This issue occurred only once IGT_4693 (4 months / 2360 runs ago).
Closing this bug.
Comment 4 CI Bug Log 2019-02-22 13:50:09 UTC
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.


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.