From: Jocelyn Falempe <jfalempe@redhat.com>
To: Askar Safin <safinaskar@zohomail.com>
Cc: ryasuoka <ryasuoka@redhat.com>, airlied <airlied@gmail.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
kraxel <kraxel@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"maarten.lankhorst" <maarten.lankhorst@linux.intel.com>,
mripard <mripard@kernel.org>, simona <simona@ffwll.ch>,
tzimmermann <tzimmermann@suse.de>,
virtualization <virtualization@lists.linux.dev>
Subject: Re: [PATCH drm-next] drm/bochs: Add support for drm_panic
Date: Wed, 16 Jul 2025 00:00:56 +0200 [thread overview]
Message-ID: <05c40a0a-d2b0-4f55-981f-6da3765eebb2@redhat.com> (raw)
In-Reply-To: <1980fcccefe.10a7c92b36705.2744765212931179004@zohomail.com>
On 15/07/2025 22:35, Askar Safin wrote:
> ---- On Tue, 15 Jul 2025 12:57:04 +0400 Jocelyn Falempe <jfalempe@redhat.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
>
next prev parent reply other threads:[~2025-07-15 22:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 13:20 Ryosuke Yasuoka
2025-06-19 6:12 ` Jocelyn Falempe
2025-06-19 6:37 ` Ryosuke Yasuoka
2025-06-19 6:42 ` Jocelyn Falempe
2025-06-23 10:12 ` Jocelyn Falempe
2025-07-14 0:04 ` Askar Safin
2025-07-15 8:57 ` Jocelyn Falempe
2025-07-15 20:35 ` Askar Safin
2025-07-15 22:00 ` Jocelyn Falempe [this message]
2025-07-16 21:48 ` Askar Safin
2025-07-17 9:54 ` Jocelyn Falempe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=05c40a0a-d2b0-4f55-981f-6da3765eebb2@redhat.com \
--to=jfalempe@redhat.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ryasuoka@redhat.com \
--cc=safinaskar@zohomail.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®