Bug 111538

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_355/fi-skl-iommu/igt@kms_flip@flip-vs-suspend.html

<6> [120.585524] pcieport 0000:00:1b.0: Intel SPT PCH root port ACS workaround enabled
<6> [120.614749] PM: suspend exit
<6> [120.656407] PM: suspend entry (deep)
<6> [120.658357] Filesystems sync: 0.001 seconds
<6> [120.658997] Freezing user space processes ... (elapsed 0.001 seconds) done.
<6> [120.660440] OOM killer disabled.
<6> [120.660441] Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
<6> [120.663693] printk: Suspending console(s) (use no_console_suspend to debug)
<6> [120.670679] e1000e: EEE TX LPI TIMER: 00000011
<3> [120.670855] mei_me 0000:00:16.0: hbm: properties response: state mismatch, [5, 4]
<4> [120.670887] ------------[ cut here ]------------
<4> [120.670888] hbm: wrong command 0
<4> [120.670908] WARNING: CPU: 1 PID: 1397 at drivers/misc/mei/hbm.c:1358 mei_hbm_dispatch+0xc5/0xe20 [mei]
<4> [120.670909] Modules linked in: vgem snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic mei_hdcp i915 x86_pkg_temp_thermal coretemp btusb snd_hda_intel btrtl snd_intel_nhlt btbcm crct10dif_pclmul btintel snd_hda_codec crc32_pclmul bluetooth snd_hwdep ghash_clmulni_intel snd_hda_core e1000e snd_pcm ecdh_generic ptp ecc pps_core mei_me mei prime_numbers
<4> [120.670923] CPU: 1 PID: 1397 Comm: irq/137-mei_me Tainted: G     U            5.3.0-rc6-g36fe82b28ff0-drmtip_355+ #1
<4> [120.670925] Hardware name: System manufacturer System Product Name/Z170I PRO GAMING, BIOS 1809 07/11/2016
<4> [120.670928] RIP: 0010:mei_hbm_dispatch+0xc5/0xe20 [mei]
<4> [120.670930] Code: 40 80 fe 11 0f 84 d3 04 00 00 40 80 fe 81 0f 84 d5 01 00 00 40 80 fe 0f 0f 84 3b 05 00 00 48 c7 c7 76 21 21 c0 e8 4b ca ea f4 <0f> 0b b8 b9 ff ff ff eb 8d 48 8b 33 48 c7 c2 08 2e 21 c0 48 c7 c7
<4> [120.670931] RSP: 0018:ffff97cb00f53d78 EFLAGS: 00010286
<4> [120.670933] RAX: 0000000000000000 RBX: ffff8f94256f6800 RCX: 0000000000000001
<4> [120.670934] RDX: 0000000080000001 RSI: ffff8f9426c8b0c8 RDI: 00000000ffffffff
<4> [120.670936] RBP: ffff8f94256f6bc0 R08: ffff8f9426c8b0c8 R09: 0000000000000000
<4> [120.670938] R10: ffff97cb00f53e38 R11: 0000000000000000 R12: ffff97cb00f53e44
<4> [120.670940] R13: ffff8f94256f6dc0 R14: ffff97cb00f53e48 R15: ffff8f9426c8a840
<4> [120.670942] FS:  0000000000000000(0000) GS:ffff8f942e880000(0000) knlGS:0000000000000000
<4> [120.670943] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4> [120.670945] CR2: 000055e9e44a3d80 CR3: 000000007a210002 CR4: 00000000003606e0
<4> [120.670946] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
<4> [120.670948] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
<4> [120.670950] Call Trace:
<4> [120.670954]  ? finish_task_switch+0x96/0x250
<4> [120.670957]  ? mei_me_irq_thread_handler+0x37/0x950 [mei_me]
<4> [120.670960]  mei_irq_read_handler+0x125/0x700 [mei]
<4> [120.670965]  mei_me_irq_thread_handler+0x229/0x950 [mei_me]
<4> [120.670967]  ? __schedule+0x316/0x860
<4> [120.670971]  ? irq_forced_thread_fn+0x70/0x70
<4> [120.670973]  irq_thread_fn+0x1c/0x60
<4> [120.670975]  ? irq_thread+0x9c/0x1a0
<4> [120.670977]  irq_thread+0x102/0x1a0
<4> [120.670979]  ? wake_threads_waitq+0x30/0x30
<4> [120.670982]  ? irq_thread_dtor+0x90/0x90
<4> [120.670984]  kthread+0x119/0x130
<4> [120.670985]  ? kthread_park+0xa0/0xa0
<4> [120.670988]  ret_from_fork+0x3a/0x50
<4> [120.670994] irq event stamp: 184
<4> [120.670995] hardirqs last  enabled at (183): [<ffffffffb51312f5>] vprintk_emit+0x315/0x340
<4> [120.670997] hardirqs last disabled at (184): [<ffffffffb5001a8a>] trace_hardirqs_off_thunk+0x1a/0x20
<4> [120.671000] softirqs last  enabled at (0): [<ffffffffb50b176f>] copy_process+0x52f/0x1fc0
<4> [120.671001] softirqs last disabled at (0): [<0000000000000000>] 0x0
<4> [120.671004] WARNING: CPU: 1 PID: 1397 at drivers/misc/mei/hbm.c:1358 mei_hbm_dispatch+0xc5/0xe20 [mei]

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

### New filters associated

* SKL:  igt@kms_flip@flip-vs-suspend - dmesg-warn - mei_me 0000:00:16.0: hbm: properties response: state mismatch
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_355/fi-skl-iommu/igt@kms_flip@flip-vs-suspend.html

A CI Bug Log filter associated to this bug has been updated:

{- SKL:  igt@kms_flip@flip-vs-suspend - dmesg-warn - mei_me 0000:00:16.0: hbm: properties response: state mismatch -}
{+ SKL:  igt@kms_flip@flip-vs-suspend-* - dmesg-warn - mei_me 0000:00:16.0: hbm: properties response: state mismatch +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_370/fi-skl-iommu/igt@kms_flip@flip-vs-suspend-interruptible.html

A CI Bug Log filter associated to this bug has been updated:

{- SKL:  igt@kms_flip@flip-vs-suspend-* - dmesg-warn - mei_me 0000:00:16.0: hbm: properties response: state mismatch -}
{+ SKL:  igt@kms_flip@flip-vs-suspend-* - dmesg-warn - mei_me 0000:00:16.0: hbm: properties response: state mismatch +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7150/shard-kbl1/igt@kms_flip@flip-vs-suspend-interruptible.html

A CI Bug Log filter associated to this bug has been updated:

{- SKL:  igt@kms_flip@flip-vs-suspend-* - dmesg-warn - mei_me 0000:00:16.0: hbm: properties response: state mismatch -}
{+ SKL KBL:  igt@kms_flip@flip-vs-suspend-* - dmesg-warn - mei_me 0000:00:16.0: hbm: properties response: state mismatch +}


  No new failures caught with the new filter

Over the last three months this issue has occurred 3 times, with an approximate frequency on once every month. The error logged is from the Intel Management Engine driver (mei_me) right after resuming from sleep - could indicate some error with resuming from sleep state for the Management Engine.

Given that this error is potentially pointing to a device other than graphics and has very low occurance, I'm marking this as low priority. Also, the test during which this error is reproduced is also passing.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/391.