v5.5 is missing multiple urgent patches from v5.6-rc1

Crashes reported so far for lack of:

76f9764cc3d5 ("drm/i915: Introduce a vma.kref")
bbca083de291 ("drm/i915: Serialise i915_active_acquire() with __active_retire()")

added priority::highest severity::critical labels

added kernel:5.5 label

assigned to @baleboy

marked #1196 (closed) as a duplicate of this issue

marked #1179 (closed) as a duplicate of this issue

mentioned in issue #1189 (closed)

marked #1207 (closed) as a duplicate of this issue

How often does drmtip get merged into the kernel? What's the ballpark time frame we can expect to see these commits into an RC kernel?

drm-tip doesn't get merged anywhere, it's an integration testing branch.

You're referring to drm-fixes branches, but I presume they take time to assemble: https://cgit.freedesktop.org/drm/drm/

Both patches landed on Linus master targeting 5.6.

The second one (bbca083de291) contains the Fixes tag so it should be collected by Greg's script soon on his 5.5.y stable branch. However, the first one (76f9764cc3d5) needs a backported version on top of stable/5.5.y and be sent to stable. @ickle could you provide this backported version please? And when sending to stable also cc the second one.

changed title from v5.5 is missing multiple urgent patches from dinf to v5.5 is missing multiple urgent patches from v5.6-rc1

As said the commits referenced in the description are in v5.6-rc1, and need stable backports from there.

The latest fixes pull request targeting v5.6-rc2 is [1], from drm-intel-next-fixes branch as is common for early -rc's. The next one is likely from drm-intel-fixes, rebased on -rc2. But this is mostly off-topic for the issue at hand.

[1] http://lore.kernel.org/r/878sl6yfrn.fsf@intel.com

Thanks for the explanations. I will try and get a 5.6rc kernel as this is making life hard.

mentioned in issue #673 (closed)

Is there any update on this?

mentioned in issue #1258 (closed)

Any idea on which 5.5.y kernel we can expect bbca083de291?

Not on future 5.5.5 - https://lore.kernel.org/stable/

and what about 5.4?

not a concern there AIUI

Fedora 31 is now testing 5.5.5 with bbca083de291. There is still no backport of 76f9764cc3d5: https://bodhi.fedoraproject.org/updates/FEDORA-2020-cf2eacc932#comment-1247675

It looks like both patches are applied to the Manjaro 5.5.5 kernel, however this has not hit stable yet.

https://gitlab.manjaro.org/packages/core/linux55/blob/master/0008-drm-i915-serialise-i915_active_acquire()with__active_retire().patch https://gitlab.manjaro.org/packages/core/linux55/blob/master/0014-drm-i915-introduce-a-vma.kref.patch

Also not queued for 5.5.6 https://lore.kernel.org/stable/dea062e3-48c7-f878-c733-addf39a9c4f3@nvidia.com/T/#m1cb47760f51e12db7a5a541922a5fffa928f0f02 the stable queued must be huge =/

Well, I tried Fedora 31 5.5.5 (as they apparently brought in bbca083de291). The kernel isn't usable.

Feb 23 21:19:46 ai-karellen-lap kernel: watchdog: BUG: soft lockup - CPU#8 stuck for 22s! [Xorg:2182]
Feb 23 21:19:46 ai-karellen-lap kernel: Modules linked in: dm_crypt loop vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm rfcomm xt_MASQUERADE nf_conntrack_netlink xt_addrtype br_netfilter bridge stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_REJECT >
Feb 23 21:19:46 ai-karellen-lap kernel:  snd_hda_codec_hdmi snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress snd_hda_codec_realtek ac97_bus snd_hda_codec_generic snd_pcm_dmaengine snd_hda_intel x86_pkg_>
Feb 23 21:19:46 ai-karellen-lap kernel:  binfmt_misc ip_tables xfs libcrc32c uas usb_storage rfkill r8152 mii i915 rtsx_pci_sdmmc hid_multitouch mmc_core i2c_algo_bit drm_kms_helper nvme mxm_wmi drm crc32c_intel nvme_core serio_raw rtsx_pci i2c_hid pinctrl_cannonlak>
Feb 23 21:19:46 ai-karellen-lap kernel: CPU: 8 PID: 2182 Comm: Xorg Tainted: G     U     OEL    5.5.5-200.fc31.x86_64 #1
Feb 23 21:19:46 ai-karellen-lap kernel: Hardware name: Dell Inc. Precision 5540/0V030K, BIOS 1.5.0 12/25/2019
Feb 23 21:19:46 ai-karellen-lap kernel: RIP: 0010:i915_gem_evict_something+0x150/0x450 [i915]
Feb 23 21:19:46 ai-karellen-lap kernel: Code: 89 ea 4c 89 e7 48 8b b0 f0 01 00 00 48 89 74 24 08 e8 34 8d fc d6 84 c0 74 21 48 8b 74 24 08 48 8b 04 24 4c 89 a0 f0 01 00 00 <4d> 89 ae 00 02 00 00 49 89 b6 08 02 00 00 4c 89 26 49 8b 87 00 02
Feb 23 21:19:46 ai-karellen-lap kernel: RSP: 0018:ffffb5f480fbf940 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff13
Feb 23 21:19:46 ai-karellen-lap kernel: RAX: ffff988ee9b45700 RBX: ffff988d96e1c200 RCX: 0000000000000000
Feb 23 21:19:46 ai-karellen-lap kernel: RDX: ffff988ee7a3d480 RSI: ffff988ee7a3d480 RDI: ffff988ee7a3bbc0
Feb 23 21:19:46 ai-karellen-lap kernel: RBP: ffffb5f480fbf960 R08: ffff988ee9b458e8 R09: ffff988ee9b458e8
Feb 23 21:19:46 ai-karellen-lap kernel: R10: ffff988ee646a018 R11: ffff988efc5aae78 R12: ffff988ee7a3bbc0
Feb 23 21:19:46 ai-karellen-lap kernel: R13: ffff988ee9b458e8 R14: ffff988ee7a3b9c0 R15: ffff988ee7a3a3c0
Feb 23 21:19:46 ai-karellen-lap kernel: FS:  00007f1414f27f00(0000) GS:ffff988efc600000(0000) knlGS:0000000000000000
Feb 23 21:19:46 ai-karellen-lap kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 23 21:19:46 ai-karellen-lap kernel: CR2: 00000e3b00b03000 CR3: 0000001002bf8003 CR4: 00000000003606e0
Feb 23 21:19:46 ai-karellen-lap kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 23 21:19:46 ai-karellen-lap kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Feb 23 21:19:46 ai-karellen-lap kernel: Call Trace:
Feb 23 21:19:46 ai-karellen-lap kernel:  i915_gem_gtt_insert+0x174/0x250 [i915]
Feb 23 21:19:46 ai-karellen-lap kernel:  i915_vma_pin+0x62f/0x6f0 [i915]
Feb 23 21:19:46 ai-karellen-lap kernel:  i915_gem_object_pin+0x12d/0x1a0 [i915]
Feb 23 21:19:46 ai-karellen-lap kernel:  i915_gem_object_pin_to_display_plane+0xa9/0xf0 [i915]
Feb 23 21:19:46 ai-karellen-lap kernel:  intel_pin_and_fence_fb_obj+0x9d/0x1c0 [i915]
Feb 23 21:19:46 ai-karellen-lap kernel:  intel_plane_pin_fb+0x44/0xd0 [i915]
Feb 23 21:19:46 ai-karellen-lap kernel:  intel_prepare_plane_fb+0xe0/0x310 [i915]
Feb 23 21:19:46 ai-karellen-lap kernel:  drm_atomic_helper_prepare_planes+0x8a/0x110 [drm_kms_helper]
Feb 23 21:19:46 ai-karellen-lap kernel:  intel_atomic_commit+0xd9/0x350 [i915]
Feb 23 21:19:46 ai-karellen-lap kernel:  drm_atomic_helper_page_flip+0x5c/0xc0 [drm_kms_helper]
Feb 23 21:19:46 ai-karellen-lap kernel:  drm_mode_page_flip_ioctl+0x54b/0x5d0 [drm]
Feb 23 21:19:46 ai-karellen-lap kernel:  ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
Feb 23 21:19:46 ai-karellen-lap kernel:  drm_ioctl_kernel+0xaa/0xf0 [drm]
Feb 23 21:19:46 ai-karellen-lap kernel:  drm_ioctl+0x208/0x390 [drm]
Feb 23 21:19:46 ai-karellen-lap kernel:  ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
Feb 23 21:19:46 ai-karellen-lap kernel:  ? vfs_writev+0xc3/0xf0
Feb 23 21:19:46 ai-karellen-lap kernel:  do_vfs_ioctl+0x461/0x6d0
Feb 23 21:19:46 ai-karellen-lap kernel:  ksys_ioctl+0x5e/0x90
Feb 23 21:19:46 ai-karellen-lap kernel:  __x64_sys_ioctl+0x16/0x20
Feb 23 21:19:46 ai-karellen-lap kernel:  do_syscall_64+0x5b/0x1c0
Feb 23 21:19:46 ai-karellen-lap kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Feb 23 21:19:46 ai-karellen-lap kernel: RIP: 0033:0x7f14153a238b
Feb 23 21:19:46 ai-karellen-lap kernel: Code: 0f 1e fa 48 8b 05 fd 9a 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d cd 9a 0c 00 f7 d8 64 89 01 48
Feb 23 21:19:46 ai-karellen-lap kernel: RSP: 002b:00007fffb769fb48 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Feb 23 21:19:46 ai-karellen-lap kernel: RAX: ffffffffffffffda RBX: 00007fffb769fc00 RCX: 00007f14153a238b
Feb 23 21:19:46 ai-karellen-lap kernel: RDX: 00007fffb769fc00 RSI: 00000000c01864b0 RDI: 000000000000000f
Feb 23 21:19:46 ai-karellen-lap kernel: RBP: 00000000c01864b0 R08: 0000000000000ac8 R09: 0000000000000001
Feb 23 21:19:46 ai-karellen-lap kernel: R10: 00007f140ed40000 R11: 0000000000000246 R12: 0000000000000000

Kernels 5.4–5.5 (all from Fedora) cause issues with 2 of my machines.

1. Lenovo Yoga 900 with i7-6500U/Skylake GT2 [HD Graphics 520]: screen flickers. With Fedora 31 5.5.5 kernel, the flickering is gone if I disable power saving auto-tuning via PowerTop.
2. Dell Inspiron 3593 with i5-1035G1/Icelake [Intel Corporation Device 8a12 in lspci]: Kernel 5.3.17 works okay, but GPU crashes every 30 mins or so, especially when running PyCharm. Kernel 5.4.y all crashes immediately on opening PyCharm. 5.5.5 kernel doesn't even bring up SDDM login screen.

Both machines are running Fedora 31, KDE.

@rajeeshknambiar please report this in https://bodhi.fedoraproject.org/updates/FEDORA-2020-3cd64d683c

I have tested 5.5.6 Fedora kernel now on both machines, and it seem to work as good as 5.3.y kernels. The GPU hang on Icelake is still present (every 30–60 mins), but not unusable like 5.4.y/5.5.5 kernels.

According to a post to the ML (https://lists.freedesktop.org/archives/dri-devel/2020-February/256831.html) there are over 400 patches queued for 5.7

I'm ecstatic that all the problems will be fixed 8 months from now

5.5.7 seems to be getting a whole bunch of drm/i915 patches, but the above don't seem to be in them (unless they got renamed).

2020-02-27 13:36 ` [PATCH 5.5 069/150] MAINTAINERS: Update drm/i915 bug filing URL Greg Kroah-Hartman
2020-02-27 13:37 ` [PATCH 5.5 084/150] drm/i915: Wean off drm_pci_alloc/drm_pci_free Greg Kroah-Hartman
2020-02-27 13:37 ` [PATCH 5.5 085/150] drm/i915: Update drm/i915 bug filing URL Greg Kroah-Hartman
2020-02-27 13:37 ` [PATCH 5.5 097/150] drm/i915/execlists: Always force a context reload when rewinding RING_TAIL Greg Kroah-Hartman
2020-02-27 13:37 ` [PATCH 5.5 111/150] drm/i915/selftests: Add a mock i915_vma to the mock_ring Greg Kroah-Hartman
2020-02-27 13:37 ` [PATCH 5.5 112/150] drm/i915/gvt: more locking for ppgtt mm LRU list Greg Kroah-Hartman
2020-02-27 13:37 ` [PATCH 5.5 115/150] drm/i915/gem: Require per-engine reset support for non-persistent contexts Greg Kroah-Hartman
2020-02-27 13:37 ` [PATCH 5.5 116/150] drm/i915/gt: Protect defer_request() from new waiters Greg Kroah-Hartman
2020-02-27 13:37 ` [PATCH 5.5 117/150] drm/i915/ehl: Update port clock voltage level requirements Greg Kroah-Hartman

5.5.7 seems to be fairing much better - PyCharm is working like a champ, haven't had any lockups, will report more in a few hours.

mentioned in issue #1344 (closed)

5.5.7 is the release where my issue #1179 (closed) was resolved. I've been running for ~24hrs already and the flight has been as smooth as a baby's bottom: 2x4K monitors + 1080P eDP1, SNI, DRI3 + VAAPI-enabled chromium, resizing windows across screen boundaries, dragging windows across screen boundaries, PyCharm on one screen + 4K video running on the other - no issues whatsoever, no GPU hangs. Thanks so much!

Ha! Within the hour of me posting the above I got the #1179 (closed) on 5.5.7 locking up. The issue isn't fixed, but the rate it triggers on is much lower on 5.5.7:

Mar 01 06:00:24 ai-karellen-lap kernel: CPU: 10 PID: 1746 Comm: Xorg Tainted: G     U     OEL    5.5.7-200.fc31.x86_64 #1
Mar 01 06:00:24 ai-karellen-lap kernel: Hardware name: Dell Inc. Precision 5540/0V030K, BIOS 1.5.0 12/25/2019
Mar 01 06:00:24 ai-karellen-lap kernel: RIP: 0010:i915_gem_evict_something+0xff/0x450 [i915]
Mar 01 06:00:24 ai-karellen-lap kernel: Code: 00 00 00 31 db 83 e0 04 89 44 24 1c e9 9e 00 00 00 49 39 de 0f 84 af 01 00 00 48 83 fb f5 0f 84 9a 00 00 00 48 85 db 4c 89 e7 <49> 0f 44 de e8 78 a1 e1 d2 84 c0 74 15 49 8b 96 00 02 00 00 49 8b
Mar 01 06:00:24 ai-karellen-lap kernel: RSP: 0018:ffffa45080de3940 EFLAGS: 00000286 ORIG_RAX: ffffffffffffff13
Mar 01 06:00:24 ai-karellen-lap kernel: RAX: 0000000000000001 RBX: ffff89e9623ea100 RCX: 0000000000000000
Mar 01 06:00:24 ai-karellen-lap kernel: RDX: ffff89eae9bd3bc0 RSI: ffff89eae9bd3bc0 RDI: ffff89eae9bd5f80
Mar 01 06:00:24 ai-karellen-lap kernel: RBP: ffffa45080de3960 R08: ffff89eae8f25960 R09: ffff89eae8f25960
Mar 01 06:00:24 ai-karellen-lap kernel: R10: 000000000000040c R11: ffff89ddc5661b80 R12: ffff89eae9bd5f80
Mar 01 06:00:24 ai-karellen-lap kernel: R13: ffff89eae8f25960 R14: ffff89eae9bd5d80 R15: ffff89eae9bd3f40
Mar 01 06:00:24 ai-karellen-lap kernel: FS:  00007f07379bef00(0000) GS:ffff89eafc680000(0000) knlGS:0000000000000000
Mar 01 06:00:24 ai-karellen-lap kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 01 06:00:24 ai-karellen-lap kernel: CR2: 00001954e2713000 CR3: 000000100874a004 CR4: 00000000003606e0
Mar 01 06:00:24 ai-karellen-lap kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Mar 01 06:00:24 ai-karellen-lap kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Mar 01 06:00:24 ai-karellen-lap kernel: Call Trace:
Mar 01 06:00:24 ai-karellen-lap kernel:  i915_gem_gtt_insert+0x174/0x250 [i915]
Mar 01 06:00:24 ai-karellen-lap kernel:  i915_vma_pin+0x62f/0x6f0 [i915]
Mar 01 06:00:24 ai-karellen-lap kernel:  i915_gem_object_pin+0x12d/0x1a0 [i915]
Mar 01 06:00:24 ai-karellen-lap kernel:  i915_gem_object_pin_to_display_plane+0xa9/0xf0 [i915]

mentioned in issue #1313 (closed)

It's been 3 weeks. We're now at 5.5.8 and the kernel is still unusable on my Coffeelake.

Mar 06 22:36:00 ai-karellen-lap kernel: watchdog: BUG: soft lockup - CPU#14 stuck for 22s! [Xorg:2176]
Mar 06 22:36:00 ai-karellen-lap kernel: Modules linked in: dm_crypt loop vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm rfcomm xt_MASQUERADE nf_conntrack_netlink xt_addrtype br_netfilter bridge stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_REJECT >
Mar 06 22:36:00 ai-karellen-lap kernel:  snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core x86_pkg_temp_thermal snd_soc_acpi_intel_match snd_soc_acpi intel_powerclamp snd_hda_codec_hdmi coretemp iwlmvm mei_wdt mei_hdcp snd_soc_core kvm_intel snd_hda_codec_realtek iTC>
Mar 06 22:36:00 ai-karellen-lap kernel:  binfmt_misc ip_tables xfs libcrc32c uas usb_storage rfkill r8152 mii i915 rtsx_pci_sdmmc hid_multitouch mmc_core i2c_algo_bit drm_kms_helper mxm_wmi nvme drm nvme_core rtsx_pci serio_raw crc32c_intel i2c_hid pinctrl_cannonlak>
Mar 06 22:36:00 ai-karellen-lap kernel: CPU: 14 PID: 2176 Comm: Xorg Tainted: G     U     OEL    5.5.8-200.fc31.x86_64 #1
Mar 06 22:36:00 ai-karellen-lap kernel: Hardware name: Dell Inc. Precision 5540/0V030K, BIOS 1.5.0 12/25/2019
Mar 06 22:36:00 ai-karellen-lap kernel: RIP: 0010:i915_gem_evict_something+0x161/0x450 [i915]
Mar 06 22:36:00 ai-karellen-lap kernel: Code: e8 44 41 f6 d0 84 c0 74 21 48 8b 74 24 08 48 8b 04 24 4c 89 a0 f0 01 00 00 4d 89 ae 00 02 00 00 49 89 b6 08 02 00 00 4c 89 26 <49> 8b 87 00 02 00 00 4d 8d a7 00 02 00 00 4d 89 fe 48 2d 00 02 00
Mar 06 22:36:00 ai-karellen-lap kernel: RSP: 0018:ffffb6ed80e2f940 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff13
Mar 06 22:36:00 ai-karellen-lap kernel: RAX: ffff99a0a8585778 RBX: ffff99a07b0a44c0 RCX: 0000000000000000
Mar 06 22:36:00 ai-karellen-lap kernel: RDX: ffff99a0aa348fc0 RSI: ffff99a0aa348fc0 RDI: ffff99a0aa34be80
Mar 06 22:36:00 ai-karellen-lap kernel: RBP: ffffb6ed80e2f960 R08: ffff99a0a8585960 R09: ffff99a0a8585960
Mar 06 22:36:00 ai-karellen-lap kernel: R10: 000000000000040c R11: ffff99a0b22f8580 R12: ffff99a0aa34be80
Mar 06 22:36:00 ai-karellen-lap kernel: R13: ffff99a0a8585960 R14: ffff99a0aa34bc80 R15: ffff99a0aa34e880
Mar 06 22:36:00 ai-karellen-lap kernel: FS:  00007feb12fccf00(0000) GS:ffff99a0bc780000(0000) knlGS:0000000000000000
Mar 06 22:36:00 ai-karellen-lap kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 06 22:36:00 ai-karellen-lap kernel: CR2: 00002142f2f29000 CR3: 0000001002240001 CR4: 00000000003606e0
Mar 06 22:36:00 ai-karellen-lap kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Mar 06 22:36:00 ai-karellen-lap kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Mar 06 22:36:00 ai-karellen-lap kernel: Call Trace:
Mar 06 22:36:00 ai-karellen-lap kernel:  i915_gem_gtt_insert+0x174/0x250 [i915]
Mar 06 22:36:00 ai-karellen-lap kernel:  i915_vma_pin+0x62f/0x6f0 [i915]
Mar 06 22:36:00 ai-karellen-lap kernel:  i915_gem_object_pin+0x12d/0x1a0 [i915]
Mar 06 22:36:00 ai-karellen-lap kernel:  i915_gem_object_pin_to_display_plane+0xa9/0xf0 [i915]
Mar 06 22:36:00 ai-karellen-lap kernel:  intel_pin_and_fence_fb_obj+0x9d/0x1c0 [i915]
Mar 06 22:36:00 ai-karellen-lap kernel:  intel_plane_pin_fb+0x44/0xd0 [i915]
Mar 06 22:36:00 ai-karellen-lap kernel:  intel_prepare_plane_fb+0xe0/0x310 [i915]
Mar 06 22:36:00 ai-karellen-lap kernel:  drm_atomic_helper_prepare_planes+0x8a/0x110 [drm_kms_helper]
Mar 06 22:36:00 ai-karellen-lap kernel:  intel_atomic_commit+0xd9/0x350 [i915]
Mar 06 22:36:00 ai-karellen-lap kernel:  drm_atomic_helper_page_flip+0x5c/0xc0 [drm_kms_helper]
Mar 06 22:36:00 ai-karellen-lap kernel:  drm_mode_page_flip_ioctl+0x54b/0x5d0 [drm]
Mar 06 22:36:00 ai-karellen-lap kernel:  ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
Mar 06 22:36:00 ai-karellen-lap kernel:  drm_ioctl_kernel+0xaa/0xf0 [drm]
Mar 06 22:36:00 ai-karellen-lap kernel:  drm_ioctl+0x208/0x390 [drm]
Mar 06 22:36:00 ai-karellen-lap kernel:  ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
Mar 06 22:36:00 ai-karellen-lap kernel:  ? hrtimer_init_sleeper+0x90/0x90
Mar 06 22:36:00 ai-karellen-lap kernel:  do_vfs_ioctl+0x461/0x6d0
Mar 06 22:36:00 ai-karellen-lap kernel:  ? do_setitimer+0xad/0x1f0
Mar 06 22:36:00 ai-karellen-lap kernel:  ? wake_up_q+0xa0/0xa0
Mar 06 22:36:00 ai-karellen-lap kernel:  ksys_ioctl+0x5e/0x90
Mar 06 22:36:00 ai-karellen-lap kernel:  __x64_sys_ioctl+0x16/0x20
Mar 06 22:36:00 ai-karellen-lap kernel:  do_syscall_64+0x5b/0x1c0
Mar 06 22:36:00 ai-karellen-lap kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Mar 06 22:36:00 ai-karellen-lap kernel: RIP: 0033:0x7feb1344738b
Mar 06 22:36:00 ai-karellen-lap kernel: Code: 0f 1e fa 48 8b 05 fd 9a 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d cd 9a 0c 00 f7 d8 64 89 01 48
Mar 06 22:36:00 ai-karellen-lap kernel: RSP: 002b:00007fffee20fce8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Mar 06 22:36:00 ai-karellen-lap kernel: RAX: ffffffffffffffda RBX: 00007fffee20fda0 RCX: 00007feb1344738b
Mar 06 22:36:00 ai-karellen-lap kernel: RDX: 00007fffee20fda0 RSI: 00000000c01864b0 RDI: 000000000000000f
Mar 06 22:36:00 ai-karellen-lap kernel: RBP: 00000000c01864b0 R08: 0000000000000ac8 R09: 0000000000000000
Mar 06 22:36:00 ai-karellen-lap kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
Mar 06 22:36:00 ai-karellen-lap kernel: R13: 000000000000000f R14: 0000564d14413af0 R15: 0000564d1401d480
Mar 06 22:36:01 ai-karellen-lap kernel: rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 14-... } 60918 jiffies s: 5481 root: 0x4000/.
Mar 06 22:36:01 ai-karellen-lap kernel: rcu: blocking rcu_node structures:
Mar 06 22:36:01 ai-karellen-lap kernel: Task dump for CPU 14:
Mar 06 22:36:01 ai-karellen-lap kernel: Xorg            R  running task        0  2176   2128 0x80400008
Mar 06 22:36:01 ai-karellen-lap kernel: Call Trace:
Mar 06 22:36:01 ai-karellen-lap kernel:  ? drm_ioctl_kernel+0xaa/0xf0 [drm]
Mar 06 22:36:01 ai-karellen-lap kernel:  ? drm_ioctl+0x208/0x390 [drm]
Mar 06 22:36:01 ai-karellen-lap kernel:  ? drm_mode_cursor2_ioctl+0x10/0x10 [drm]
Mar 06 22:36:01 ai-karellen-lap kernel:  ? hrtimer_init_sleeper+0x90/0x90
Mar 06 22:36:01 ai-karellen-lap kernel:  ? do_vfs_ioctl+0x461/0x6d0
Mar 06 22:36:01 ai-karellen-lap kernel:  ? do_setitimer+0xad/0x1f0
Mar 06 22:36:01 ai-karellen-lap kernel:  ? wake_up_q+0xa0/0xa0
Mar 06 22:36:01 ai-karellen-lap kernel:  ? ksys_ioctl+0x5e/0x90
Mar 06 22:36:01 ai-karellen-lap kernel:  ? __x64_sys_ioctl+0x16/0x20
Mar 06 22:36:01 ai-karellen-lap kernel:  ? do_syscall_64+0x5b/0x1c0
Mar 06 22:36:01 ai-karellen-lap kernel:  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9

Is @baleboy on vacation? He seem to haven't even appeared on this report. I'm wondering, should maybe an issue with highest priority and severity "critical" be assigned to someone else at Intel?

@ickle hello, sorry to bother you. You initially assigned this to @baleboy, and I'm wondering if, given the circumstances, it would make sense to reassign issue to someone else at Intel? Rebasing a couple of patches sounds trivial too, so I'm not sure it's worth waiting the fifth week from the current assignee.

Tried 5.6.0-rc5 (from Fedora kernel build) and still results in GPU crash, when using PyCharm. /sys/class/drm/card0/error is attached.sys_class_drm_card0_error

I apologise for the lack of responses. Patches were sent to the stable mailing list by @ickle.

mentioned in issue #1504 (closed)

@baleboy @ickle I guess something happened, I saw that Chris sent the patch but Greg did not picked it up for past 2 5.5 releases.

mentioned in issue libinput/libinput#451 (closed)

marked #1661 (closed) as a duplicate of this issue

mentioned in issue #1700 (closed)

I'm still getting freezes on 5.6.3-300.fc32.x86_64

GNOME is unusable (Wayland or Xorg) as it never recovers and Firefox seems to trigger it almost everytime I run it

Using Ephy on WindowMaker was fun at first but a month+ later the novelty value is seriously wearing off :-)

Not that WindowMaker is immune, it's just unlike shell it recovers most of the time

Had this as well for months on Fedora 31 and 32 on an old CQ60 laptop with Intel Mobile 4 Series graphics chipset. A hard freeze would happen randomly, but like the others commenting here most often triggered when using an IntelliJ IDE like Goland, Rider, or Pycharm. The mouse would stutter for a second, then complete lockup that can only be resolved by a hard power cycle. (If sound was playing, it would halt and play in a loop.) Logs would never mention that anything had gone wrong (other than an unclean shutdown, of course).

So for anyone else on the net desperately searching this issue, what finally solved it for me was installing the 5.7.0-0.rc6 Fedora rawhide kernel. Both 5.5 and 5.6 kernels were broken. https://fedoraproject.org/wiki/RawhideKernelNodebug

I lied, the lockups still happen on 5.7.0-0.rc6. I thought I had finally solved it and had backed out a bunch of kernel parameters (enable_guc, disable_power_well, etc.) that may have actually solved it in combination with 5.7.0-0.rc6, or I was just really lucky. I'll report back if I can find a combination that fixes it as I can't be the only one out there facing these constant hangs.

mentioned in issue #2631 (closed)

Hi Reporter, please confirm if this issue is still seen on latest kernel also.

If yes, provide the steps to reproduce it for further debugging.

This is no longer relevant, I presume as patches went into 5.6.

It still crashes on my Dell xps 9380 on kernel 5.10.16-200.fc33.x86_64. i915.psr_enable=0 fixes it though.

Sure 5.10 has the patches. If you experience problems, please create a new report.

I found a bug report about it. It has been fixed on drm-intel-next about a month ago. So fedora 34 will probably this problem.

Hi @baleboy , @ickle Hope patches have merged to the latest kernel. Do you want this GitLab still open? Thanks.

5.5 is long gone. Closing.

closed