[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <05c40a0a-d2b0-4f55-981f-6da3765eebb2@redhat.com>
Date: Wed, 16 Jul 2025 00:00:56 +0200
From: Jocelyn Falempe <jfalempe@...hat.com>
To: Askar Safin <safinaskar@...omail.com>
Cc: ryasuoka <ryasuoka@...hat.com>, airlied <airlied@...il.com>,
dri-devel <dri-devel@...ts.freedesktop.org>, kraxel <kraxel@...hat.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
"maarten.lankhorst" <maarten.lankhorst@...ux.intel.com>,
mripard <mripard@...nel.org>, simona <simona@...ll.ch>,
tzimmermann <tzimmermann@...e.de>,
virtualization <virtualization@...ts.linux.dev>
Subject: Re: [PATCH drm-next] drm/bochs: Add support for drm_panic
On 15/07/2025 22:35, Askar Safin wrote:
> ---- On Tue, 15 Jul 2025 12:57:04 +0400 Jocelyn Falempe <jfalempe@...hat.com> wrote ---
> > "Normal panics", is just the console logs through fbcon. The problem is
>
> Thank you for answer! Is this possible to configure system such that fbcon works normally,
> VTs work normally (i. e. via framebuffer), but when panic happens, it is displayed via drm_panic? This seems to
> be solution to the problem.
Yes, that's the default if you use a drm driver like bochs with fbdev
emulation enabled. (Of course you can't have DRM panic on a pure fbdev
driver).
There was a concurrency problem between fbcon and DRM panic, and I've
solved it a year ago with:
https://patchwork.freedesktop.org/series/136182/
So make sure you have the following in your .config:
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_DRM_FBDEV_EMULATION=y
CONFIG_DRM_PANIC=y
CONFIG_DRM_PANIC_SCREEN="kmsg"
Best regards,
--
Jocelyn
>
> --
> Askar Safin
> https://types.pl/@safinaskar
>
Powered by blists - more mailing lists