The oops file has a better description:

<4>[    6.285553] general protection fault: 0000 [#1] PREEMPT SMP PTI
<4>[    6.285619] CPU: 0 PID: 626 Comm: kworker/0:3 Not tainted 4.18.0-rc3-CI-CI_DRM_4454+ #1
<4>[    6.285685] Hardware name: Intel Corporation NUC8i7HVK/NUC8i7HVB, BIOS HNKBLi70.86A.0040.2018.0516.1521 05/16/2018
<4>[    6.285741] Workqueue: pm pm_runtime_work
<4>[    6.285765] RIP: 0010:__x86_indirect_thunk_rax+0x10/0x20
<4>[    6.285793] Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 e8 07 00 00 00 f3 90 0f ae e8 eb f9 48 89 04 24 <c3> 0f 1f 44 00 00 66 2e 0f 1f 84 00 00 00 00 00 e8 07 00 00 00 f3 
<4>[    6.285963] RSP: 0018:ffffc900010c3d20 EFLAGS: 00010202
<4>[    6.285991] RAX: 6b6b6b6b6b6b6b6b RBX: ffff880270118008 RCX: 0000000000000001
<4>[    6.286029] RDX: 0000000000000000 RSI: 00000000aafad925 RDI: ffff880270118008
<4>[    6.286065] RBP: ffff8802591db3f8 R08: 00000000d381941d R09: 0000000000000001
<4>[    6.286103] R10: 0000000000000000 R11: 0000000000000000 R12: ffff880270118560
<4>[    6.286139] R13: 0000000000000000 R14: ffffffffa0194a30 R15: 0000000000000008
<4>[    6.286176] FS:  0000000000000000(0000) GS:ffff88027ec00000(0000) knlGS:0000000000000000
<4>[    6.286218] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4>[    6.286248] CR2: 000055f779ae60a8 CR3: 0000000005210005 CR4: 00000000003606f0
<4>[    6.286285] Call Trace:
<4>[    6.286303]  ? alc_suspend+0x36/0x50 [snd_hda_codec_realtek]
<6>[    6.286331] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15
<4>[    6.286383]  ? hda_call_codec_suspend+0x1d/0xa0 [snd_hda_codec]
<4>[    6.286416]  ? hda_codec_runtime_suspend+0x54/0xa0 [snd_hda_codec]
<4>[    6.286450]  ? __rpm_callback+0xb3/0x1b0
<4>[    6.286471]  ? hda_codec_runtime_resume+0x40/0x40 [snd_hda_codec]
<4>[    6.286502]  ? rpm_callback+0x1a/0x70
<4>[    6.286522]  ? hda_codec_runtime_resume+0x40/0x40 [snd_hda_codec]
<4>[    6.286555]  ? rpm_suspend+0x125/0x6d0
<4>[    6.286577]  ? pm_runtime_work+0x6e/0xb0
<4>[    6.286599]  ? process_one_work+0x248/0x6c0
<4>[    6.287861]  ? worker_thread+0x37/0x380
<4>[    6.289111]  ? process_one_work+0x6c0/0x6c0
<4>[    6.290352]  ? kthread+0x119/0x130
<4>[    6.291593]  ? kthread_flush_work_fn+0x10/0x10
<4>[    6.292822]  ? ret_from_fork+0x3a/0x50
<4>[    6.294046] Modules linked in: snd_hda_codec_realtek(+) snd_hda_codec_generic amdgpu i915 x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul btusb btrtl btbcm snd_hda_codec_hdmi btintel bluetooth snd_hda_intel snd_hda_codec ghash_clmulni_intel chash gpu_sched e1000e ecdh_generic snd_hwdep ttm snd_hda_core igb snd_pcm mei_me mei prime_numbers pinctrl_sunrisepoint pinctrl_intel
<6>[    6.295228] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16
<4>[    6.296904] ---[ end trace 8b569215a2200dc6 ]---

How can I reproduce the bug?

(In reply to Takashi Iwai from comment #2)
> How can I reproduce the bug?

Try suspending/resuming in a loop for a couple of thousand times :s I hope this will not require one of these bad boys to reproduce: https://www.intel.com/content/www/us/en/products/boards-kits/nuc/kits/nuc8i7hvk.html

So far, we have only seen this issue once. I will keep you updated when we get more runs with this issue.

Do you mean S4 or S3?  The log you showed indicates the GPF at early boot, and is this while suspend/resume testing?  Somehow the information doesn't match with the description...

The more information is appreciated.  Thanks.

Sorry about that. I followed the code and it looks like the test is verifying that hibernating while the GPU is active is done properly.

The hibernation is triggered like this:

# echo devices > /sys/power/pm_test 
# echo disk > /sys/power/state

I hope this helps!

Last seen CI_DRM_4454 (7 months, 1 week / 4171 runs ago). This issue is not seen lately.

Still have not reproduced 8 months later. So much has changed since this bug was filed that it makes no sense to keep it open. Closing!