On Mon, 21 Jul 2025 18:18:48 +0400 Pingfan Liu wrote
---
> IMHO, you could try blacklisting the i915 module to see if
I did this. Problem is in i915.
Here you can see our discussion with i915 devs:
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14598
--
Askar Safin
ht
rything is mounted read-only.
And this is exactly what happens, when I try to catch that kexec-related bug:
immediately before issuing "kexec -e" command I mount everything read-only.
The only remaining workaround is to redirect everything to /dev/kmsg.
I. e. put "exec > /dev/kmsg 2>&1" to the script.
This will work.
But I still don't like this.
--
Askar Safin
https://types.pl/@safinaskar
ut when panic happens, it is
displayed via drm_panic? This seems to
be solution to the problem.
--
Askar Safin
https://types.pl/@safinaskar
is here:
https://lore.kernel.org/regressions/197f290e30b.eaadc7bc7913.7315623184036672...@zohomail.com/T/#u
,
but nobody answered.
--
Askar Safin
g is reproducible with standard Debian kernels (if we use them as guests).
Reproduction steps are so:
- Install Debian Trixie to Qemu VM
- Boot it with "init=/bin/true" added (to cause kernel panic)
You will not see panic message.
I minimized this Debian bug to small config shown in the
by i915 people. (But I may be wrong.)
But okay, I reported it to that bug tracker anyway:
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14598
Maybe there is separate kexec bug tracker?
Also, your bug tracker is cool. One can attach files in the middle of report.
Why not whole kernel
ve is already enough, I think this link is not needed.
I will be available for testing in coming days, then I will switch to other
things, and so will not be available for testing.
If you want more time, then, please, ask for it, i. e. say me something like
"Please, be available for testing in more 10 days".
--
Askar Safin
https://types.pl/@safinaskar
