Subscriptions Downloads Containers Support Cases

Products & Services Base de conocimiento Kernel panic in a kworker executing drm_fb_helper_dirty_work() function

3 A translation for your language preference does not exist.

Kernel panic in a kworker executing drm_fb_helper_dirty_work()

function
$ SOLUTION VERIFICADA - Actualizado 8 de Junio de 2022 a las 04:57 - English

Red Hat Insights can detect this issue

Proactively detect and remediate issues impacting your systems.

View matching systems and remediation

Medio Ambiente
Red Hat Enterprise Linux 8
The system is running as a KVM virtual machine guest
However, theoretically, the same issue can happen on a physical machine as well.
qxl video driver is enabled

Cuestión
Kernel panic in memcpy_erms() function called by drm_fb_helper_dirty_work() .

Resolución
The issue has been fixed in...
rhel8.4.z errata RHSA-2021:3548. Upgrade the kernel to version 4.18.0-305.19.1.el8_4 or more recent.
rhel8.5 errata RHSA-2021:4356. Upgrade the kernel to version 4.18.0-348.el8 or newer.

Causa Raíz
The root cause of the issue is not sufficient locking during access to qxl_bo structure used internally by qxl driver.
We are aware that the quite similar issue can happen not with qxl_bo but with bochs_drm driver being loaded. If that's
the case and the issue persists after upgrating to either of the patched kernels that are mentioned in the Resolution
section, please feel free to open a new support case with Red Hat Support Team.

Procedimientos para el Diagnóstico

 In most cases the issue happens in early stage of the boot process, so vmcore is not generated by kdump and the VM appears to be
hanged. In this case please capture a snapshot of the virtual machine (Creating a virtual machine core dump file).

An example of a kworker back trace which triggered kernel panic:

crash> bt

PID: 426 TASK: ffff992bb4b49840 CPU: 2 COMMAND: "kworker/2:2"

#0 [ffffae190091fc78] panic at ffffffffa4ab1642

#1 [ffffae190091fd18] no_context at ffffffffa4a6872e

#2 [ffffae190091fd70] do_page_fault at ffffffffa4a69262

#3 [ffffae190091fda0] async_page_fault at ffffffffa540123e

[exception RIP: memcpy_erms+0x6]

RIP: ffffffffa5284fb6 RSP: ffffae190091fe58 RFLAGS: 00010206

RAX: ffffae1908a6b000 RBX: ffff992bb43116d0 RCX: 0000000000001000

RDX: 0000000000001000 RSI: ffffae1900dac000 RDI: ffffae1908a6b000

RBP: 000000000000026c R8: 000fffffffffffff R9: ffffae190091fc70

R10: 0000000000000001 R11: 0000000000000000 R12: ffffae1900dac000

R13: 0000000000001000 R14: ffff992bb419ad00 R15: ffff992bb43116d8

ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018

#4 [ffffae190091fe58] drm_fb_helper_dirty_work at ffffffffc04a9e93 [drm_kms_helper]

#5 [ffffae190091fe98] process_one_work at ffffffffa4ace7d7

#6 [ffffae190091fed8] worker_thread at ffffffffa4aceef0

#7 [ffffae190091ff10] kthread at ffffffffa4ad4802

#8 [ffffae190091ff50] ret_from_fork at ffffffffa5400255

The symptom of this issue is an invalid memory reference in memcpy_erms() function which was called by
drm_fb_helper_dirty_work() .

Producto(s) Red Hat Enterprise Linux Componente kernel Categoría Troubleshoot Etiquetas kernel panic

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have
created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may
be presented in a raw and unedited form.

People who viewed this solution also viewed

Kernel panic's at How to determine the system Kernel Panic - Not Syncing |
qxl_release_list_add() during boot-time from the kernel LVM issues seen
DB backup and restore crash dump?

Solution - Jun 28, 2021 Solution - Jun 19, 2022 Solution - Nov 7, 2013

Comentarios

Copyright © 2022 Red Hat, Inc.