Bug 106062

Summary: [CI] igt@drv_module_reload@basic-no-display - i915: unknown parameter 'enable_guc_loading' ignored && WARNING: CPU: 7 PID: 1530 at lib/plist.c:42 plist_check_prev_next+0x2d/0x40
Product: DRI Reporter: Marta Löfstedt <marta.lofstedt>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs, martin.peres
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard: ReadyForDev
i915 platform: SKL i915 features: firmware/guc

Description Marta Löfstedt 2018-04-16 06:44:22 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_21/fi-skl-guc/igt@drv_module_reload@basic-no-display.html

	

[   64.850230] i915: unknown parameter 'enable_guc_loading' ignored
[   64.850233] i915: unknown parameter 'enable_guc_submission' ignored
[   64.850235] Setting dangerous option enable_guc - tainting kernel
[   64.865188] ------------[ cut here ]------------
[   64.865203] top: 000000004314fee6, n: 000000007bb37754, p: 0000000079f2c5fd
               prev: 000000007bb37754, n: 0000000079f2c5fd, p: 000000004314fee6
               next: 0000000079f2c5fd, n: 00000000b6ebf97b, p: 0000000045aea537
[   64.865218] WARNING: CPU: 7 PID: 1530 at lib/plist.c:42 plist_check_prev_next+0x2d/0x40
[   64.865220] Modules linked in: i915(+) snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec crct10dif_pclmul snd_hwdep crc32_pclmul snd_hda_core ghash_clmulni_intel e1000e snd_pcm mei_me mei prime_numbers [last unloaded: i915]
[   64.865257] CPU: 7 PID: 1530 Comm: drv_module_relo Tainted: G     U           4.16.0-rc7-ga0e39233b887-drmtip_21+ #1
[   64.865259] Hardware name: System manufacturer System Product Name/Z170 PRO GAMING, BIOS 3402 04/26/2017
[   64.865262] RIP: 0010:plist_check_prev_next+0x2d/0x40
[   64.865265] RSP: 0018:ffffbba04093fa60 EFLAGS: 00010082
[   64.865268] RAX: 0000000000000000 RBX: ffffa3cfdbf076b8 RCX: 0000000000000002
[   64.865270] RDX: 0000000080000002 RSI: ffffffffa6076ce6 RDI: 00000000ffffffff
[   64.865272] RBP: ffffa3cfdbf076b8 R08: 0000000000000000 R09: 0000000000000001
[   64.865274] R10: ffffbba04093fa68 R11: ffffa3cfd4075040 R12: ffffffffa6244ca0
[   64.865276] R13: ffffffffa6244ca0 R14: ffffa3cfd7ca76b8 R15: ffffa3cfd7ca76a0
[   64.865278] FS:  00007f0615bdc980(0000) GS:ffffa3cff6dc0000(0000) knlGS:0000000000000000
[   64.865280] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   64.865283] CR2: 0000560c2b0bd7d0 CR3: 000000022a2c8005 CR4: 00000000003606e0
[   64.865285] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   64.865286] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[   64.865288] Call Trace:
[   64.865294]  plist_check_list+0x2e/0x40
[   64.865298]  plist_add+0x24/0x130
[   64.865304]  pm_qos_update_target+0xd7/0x2c0
[   64.865341]  i915_driver_load+0xe58/0x1060 [i915]
[   64.865346]  ? trace_hardirqs_on_caller+0xde/0x1c0
[   64.865385]  i915_pci_probe+0x2e/0x90 [i915]
[   64.865389]  pci_device_probe+0x9c/0x120
[   64.865395]  driver_probe_device+0x2a4/0x480
[   64.865399]  __driver_attach+0xd9/0xe0
[   64.865402]  ? driver_probe_device+0x480/0x480
[   64.865404]  ? driver_probe_device+0x480/0x480
[   64.865407]  bus_for_each_dev+0x62/0xb0
[   64.865412]  bus_add_driver+0x168/0x260
[   64.865416]  driver_register+0x52/0xc0
[   64.865418]  ? 0xffffffffc0a21000
[   64.865421]  do_one_initcall+0x49/0x180
[   64.865426]  ? rcu_read_lock_sched_held+0x6f/0x80
[   64.865430]  ? kmem_cache_alloc_trace+0x245/0x2b0
[   64.865435]  do_init_module+0x56/0x1ea
[   64.865439]  load_module+0x2431/0x2e00
[   64.865444]  ? show_coresize+0x20/0x20
[   64.865460]  ? SyS_finit_module+0xd3/0x100
[   64.865462]  SyS_finit_module+0xd3/0x100
[   64.865474]  do_syscall_64+0x65/0x1a0
[   64.865479]  entry_SYSCALL_64_after_hwframe+0x42/0xb7
[   64.865481] RIP: 0033:0x7f061528b839
[   64.865483] RSP: 002b:00007ffd4fd4e3f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[   64.865487] RAX: ffffffffffffffda RBX: 00005634733fb7a0 RCX: 00007f061528b839
[   64.865489] RDX: 0000000000000000 RSI: 00005634733fbab0 RDI: 0000000000000003
[   64.865490] RBP: 00005634733fbab0 R08: 0000000000000000 R09: 0000000000000011
[   64.865492] R10: 0000000000000003 R11: 0000000000000246 R12: 0000000000000000
[   64.865494] R13: 00005634733fc020 R14: 0000000000000000 R15: 0000000000000011
[   64.865505] Code: 42 08 48 39 f0 74 2b 49 89 f0 48 8b 4f 08 50 ff 32 52 48 89 fe 41 ff 70 08 48 8b 17 48 c7 c7 c8 d5 10 a6 4d 8b 08 e8 f3 bd 76 ff <0f> 0b 48 83 c4 20 c3 48 3b 10 75 d0 f3 c3 0f 1f 44 00 00 41 54 
[   64.865610] WARNING: CPU: 7 PID: 1530 at lib/plist.c:42 plist_check_prev_next+0x2d/0x40
[   64.865612] ---[ end trace 9ff0694864413486 ]---
Comment 1 Marta Löfstedt 2018-04-16 06:47:03 UTC 
Then there is owatch softdog on the next test.

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_21/fi-skl-guc/igt@kms_cursor_crc@cursor-128x128-sliding.html
Comment 2 Chris Wilson 2018-04-16 08:43:42 UTC 
I believe,

commit 9f172f6fbd243759c808d97bd83c95e49325b2c9
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Sat Apr 14 10:12:33 2018 +0100

    drm/i915: Call i915_perf_fini() on init_hw error unwind
    
    We have to cleanup after i915_perf_init(), even on the error path, as it
    passes a pointer into the module to the sysfs core. If we fail to
    unregister the sysctl table, we leave a dangling pointer which then may
    explode anytime later.
    
    Fixes: 9f9b2792b6d3 ("drm/i915/perf: reuse timestamp frequency from device info")
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
    Cc: Matthew Auld <matthew.auld@intel.com>
    Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
    Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/20180414091233.32224-1-chris@chris-wilson.co.uk

It's hard to be sure since it causes memcorruption and dies in various ways on subsequent tests.
Comment 3 Jani Saarinen 2018-04-20 20:17:21 UTC 
Martin, seen on CI still?
Comment 4 Martin Peres 2018-04-21 11:17:02 UTC 
(In reply to Jani Saarinen from comment #3)
> Martin, seen on CI still?

Let's check this out on Monday, after the weekend's runs.
Comment 5 Martin Peres 2018-04-23 10:52:31 UTC 
(In reply to Martin Peres from comment #4)
> (In reply to Jani Saarinen from comment #3)
> > Martin, seen on CI still?
> 
> Let's check this out on Monday, after the weekend's runs.

No issues in drmtip_24 and 25. Closing

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.