Re: [PATCH drm-next] drm/bochs: Add support for drm_panic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 14/07/2025 02:04, Askar Safin wrote:
Are normal panics (i. e. not drm panics) still supposed to work with bochs?

"Normal panics", is just the console logs through fbcon. The problem is that this is not designed to work in a panic context, so on some driver it can work, but it's not reliable. Also depending on the panic source (Like if the panic occurs in IRQ context), you probably won't see anything. I think the regression is likely because the driver switched to use a shadow buffer (ie: fbcon draws to a buffer in system memory, which is copied to the "VRAM" in a workqueue, and workqueues are disabled in a panic context). So there is no easy fix for the fbcon panic.

This patch series, only take care of DRM panic. You can get the same output as fbcon, by selecting CONFIG_DRM_PANIC_SCREEN"kmsg".

--

Jocelyn


If yes, then I want to point out that they, in fact, don't work since 2019.
I. e. panics are not shown in Qemu if:
1) bochs is used
2) we use "normal" panics (not drm panics)

I already reported this here: https://lore.kernel.org/regressions/197f290e30b.eaadc7bc7913.7315623184036672946@xxxxxxxxxxxx/T/#u ,
but nobody answered.

--
Askar Safin






[Index of Archives]     [KVM Development]     [Libvirt Development]     [Libvirt Users]     [CentOS Virtualization]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux