On 25/07/2024 18:50, Daniel P. Berrangé wrote:
On Mon, Jul 15, 2024 at 11:20:27AM +0200, Jocelyn Falempe wrote:
On 15/07/2024 10:30, Zbigniew Jędrzejewski-Szmek wrote:
There's just so many different and special ways in how people hook up
console logging from VMs and other systems. Disabling
On Mon, Jul 15, 2024 at 11:20:27AM +0200, Jocelyn Falempe wrote:
>
> On 15/07/2024 10:30, Zbigniew Jędrzejewski-Szmek wrote:
> >
> > There's just so many different and special ways in how people hook up
> > console logging from VMs and other systems. Disabling VT_CONSOLE at
> > compile time is ha
Once upon a time, Jocelyn Falempe said:
> It's no longer necessary to disable VT_CONSOLE to enable DRM_PANIC.
> So I have updated the wiki page, and also moved it to
> self-contained-change, as there are no more system-wide impact by
> enabling DRM_PANIC.
Thanks for the additional work on this.
-
On Tue, Jul 23, 2024 at 8:32 AM Jocelyn Falempe wrote:
>
> Hi,
>
> It's no longer necessary to disable VT_CONSOLE to enable DRM_PANIC.
> So I have updated the wiki page, and also moved it to
> self-contained-change, as there are no more system-wide impact by
> enabling DRM_PANIC.
>
> I've also mad
Hi,
It's no longer necessary to disable VT_CONSOLE to enable DRM_PANIC.
So I have updated the wiki page, and also moved it to
self-contained-change, as there are no more system-wide impact by
enabling DRM_PANIC.
I've also made a new kernel build, with VT_CONSOLE and DRM_PANIC
enabled, so you
Am 16.07.24 um 09:26 schrieb Barry:
On 15 Jul 2024, at 18:29, Jocelyn Falempe wrote:
I will also check if I can patch VT_CONSOLE, so that it can be disabled on the
kernel command line, instead of compile time, to avoid this gap.
I'm currently preparing a test kernel, so that you can test o
> On 16 Jul 2024, at 22:19, Michel Lind wrote:
>
> Server does not install Plymouth either AIUI; compare
I have not installed server for a few releases, but have always
dns removed plymouth* as one of my first config changes.
Barry
--
___
devel mai
> On 16 Jul 2024, at 12:49, Jocelyn Falempe wrote:
>
> i915, amdgpu, and nvidia are not yet supported, so you need to blacklist
> them, in order to use simpledrm, if you want to see the panic screen.
Let me know when amdgpu or i915 are supported then I can test.
Barry
--
On Sun, Jul 14, 2024 at 08:24:58PM +0200, Javier Martinez Canillas wrote:
> Ian Pilcher writes:
>
> > On 7/13/24 4:32 AM, Javier Martinez Canillas wrote:
> >> Zbigniew Jędrzejewski-Szmek writes:
> > The idea for DRM_PANIC is nice, but I worry about the impact of
> > disabling
> > VT
Hi,
> > > Do you expect to see the rest of the drivers supported by the time
> > > Fedora 42 rolls around? Because if it only works with nouveau, it's
> > > probably not worth enabling.
> >
> > I think it's a bit of a chicken and egg problem. If no distro enables
> > it, there will be little inc
On 16/07/2024 14:53, Neal Gompa wrote:
On Tue, Jul 16, 2024 at 8:35 AM Jocelyn Falempe wrote:
On 16/07/2024 14:05, Neal Gompa wrote:
On Tue, Jul 16, 2024 at 7:49 AM Jocelyn Falempe wrote:
I've made a test kernel build with drm_panic enabled (and VT_CONSOLE
disabled):
https://koji.fedo
On Tue, Jul 16, 2024 at 8:35 AM Jocelyn Falempe wrote:
>
>
>
> On 16/07/2024 14:05, Neal Gompa wrote:
> > On Tue, Jul 16, 2024 at 7:49 AM Jocelyn Falempe wrote:
> >>
> >> I've made a test kernel build with drm_panic enabled (and VT_CONSOLE
> >> disabled):
> >>
> >> https://koji.fedoraproject.org/
On 16/07/2024 14:05, Neal Gompa wrote:
On Tue, Jul 16, 2024 at 7:49 AM Jocelyn Falempe wrote:
I've made a test kernel build with drm_panic enabled (and VT_CONSOLE
disabled):
https://koji.fedoraproject.org/koji/taskinfo?taskID=120544794
I've backported a few patches, that are not in v6.10,
On Tue, Jul 16, 2024 at 7:49 AM Jocelyn Falempe wrote:
>
> I've made a test kernel build with drm_panic enabled (and VT_CONSOLE
> disabled):
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=120544794
>
> I've backported a few patches, that are not in v6.10, like:
> short panic description:
I've made a test kernel build with drm_panic enabled (and VT_CONSOLE
disabled):
https://koji.fedoraproject.org/koji/taskinfo?taskID=120544794
I've backported a few patches, that are not in v6.10, like:
short panic description:
https://patchwork.freedesktop.org/series/135356/
kmsg panic_screen:
> On 15 Jul 2024, at 18:29, Jocelyn Falempe wrote:
>
> I will also check if I can patch VT_CONSOLE, so that it can be disabled on
> the kernel command line, instead of compile time, to avoid this gap.
>
> I'm currently preparing a test kernel, so that you can test on your own, and
> report i
> On 15 Jul 2024, at 18:29, Jocelyn Falempe wrote:
>
> Yes, but I don't think this happens often in practice. And in this case there
> is little chance the kernel logs will help you much anyway, because when it
> hangs, you don't have the call trace, and the last kernel log might be
> unrela
On Mon, 15 Jul 2024 at 13:28, Jocelyn Falempe wrote:
>
>
>
> On 15/07/2024 18:13, Barry wrote:
> >
> >> On 15 Jul 2024, at 14:05, Jocelyn Falempe wrote:
> >>
> >> If you want to see the kernel boot log, before userspace is started,
> >> you can add "init=/does_not_exist drm.panic_screen=kmsg" to
On 15/07/2024 18:13, Barry wrote:
On 15 Jul 2024, at 14:05, Jocelyn Falempe wrote:
If you want to see the kernel boot log, before userspace is started,
you can add "init=/does_not_exist drm.panic_screen=kmsg" to the kernel command
line. It will panic, and you will see all relevant logs wit
On 7/15/24 09:12, Petr Pisar wrote:
V Sat, Jul 13, 2024 at 11:32:49AM +0200, Javier Martinez Canillas napsal(a):
For the non-panic case, as Jocelyn mentioned in the change proposal plymouth
already supports redirecting the kernel messages (reading /dev/kmsg) to the
VT and for systems without ply
> On 15 Jul 2024, at 14:05, Jocelyn Falempe wrote:
>
> If you want to see the kernel boot log, before userspace is started,
> you can add "init=/does_not_exist drm.panic_screen=kmsg" to the kernel
> command line. It will panic, and you will see all relevant logs with
> drm_panic.
> It's not id
On 15/07/2024 12:04, Barry wrote:
On 15 Jul 2024, at 10:21, Jocelyn Falempe wrote:
Normally, systemd logging should fill the gap, (and a userspace daemon
could do the same, by copying /proc/kmsg to /dev/tty0), but it is
started a bit later than what we had.
The hard to fix issues are wh
> On 15 Jul 2024, at 10:21, Jocelyn Falempe wrote:
>
> Normally, systemd logging should fill the gap, (and a userspace daemon could
> do the same, by copying /proc/kmsg to /dev/tty0), but it is started a bit
> later than what we had.
The hard to fix issues are when systemd does not get a cha
On 15/07/2024 10:30, Zbigniew Jędrzejewski-Szmek wrote:
On Sat, Jul 13, 2024 at 10:20:53AM -0500, Chris Adams wrote:
Once upon a time, Javier Martinez Canillas said:
In other words, a user should still be able to log into a VT and fbcon is
still attached to an (DRM emulated) fbdev. The only
On Sat, Jul 13, 2024 at 10:20:53AM -0500, Chris Adams wrote:
> Once upon a time, Javier Martinez Canillas said:
> > In other words, a user should still be able to log into a VT and fbcon is
> > still attached to an (DRM emulated) fbdev. The only difference is that the
> > kernel messages are not g
V Sat, Jul 13, 2024 at 11:32:49AM +0200, Javier Martinez Canillas napsal(a):
> For the non-panic case, as Jocelyn mentioned in the change proposal plymouth
> already supports redirecting the kernel messages (reading /dev/kmsg) to the
> VT and for systems without plymouth, a serial console could be
On Sun, 2024-07-14 at 12:29 -0500, Ian Pilcher wrote:
> On 7/13/24 4:39 AM, Sérgio Basto wrote:
> >
> >
> > if I don't like this functionality, can I have my vt consoles back
> > ?
> >
>
> It seems that you will need to compile your own kernel in order to do
> so.
>
"this is not about enablin
Ian Pilcher writes:
> On 7/13/24 4:32 AM, Javier Martinez Canillas wrote:
>> Zbigniew Jędrzejewski-Szmek writes:
> The idea for DRM_PANIC is nice, but I worry about the impact of disabling
> VT_CONSOLE. Plymouth is not used everywhere, e.g. what about cloud images
> and such? Also, w
On 7/13/24 4:32 AM, Javier Martinez Canillas wrote:
Zbigniew Jędrzejewski-Szmek writes:
The idea for DRM_PANIC is nice, but I worry about the impact of disabling
VT_CONSOLE. Plymouth is not used everywhere, e.g. what about cloud images
and such? Also, when debugging boot troubles, removing 'rhb
On 7/13/24 4:39 AM, Sérgio Basto wrote:
if I don't like this functionality, can I have my vt consoles back ?
It seems that you will need to compile your own kernel in order to do
so.
--
If your user interface is intuit
Once upon a time, Javier Martinez Canillas said:
> In other words, a user should still be able to log into a VT and fbcon is
> still attached to an (DRM emulated) fbdev. The only difference is that the
> kernel messages are not going to the VT.
This still seems like a big step back for anything n
ment to me.
On Fri, 2024-07-12 at 17:53 +0100, Aoife Moloney wrote:
> Wiki - https://fedoraproject.org/wiki/Changes/EnableDrmPanic
> Discussion Thread -
> https://discussion.fedoraproject.org/t/f42-change-proposal-enable-drm-panic-system-wide/125542
>
> This is a proposed Change
Zbigniew Jędrzejewski-Szmek writes:
> On Fri, Jul 12, 2024 at 01:21:41PM -0400, Neal Gompa wrote:
>> On Fri, Jul 12, 2024 at 1:12 PM Zbigniew Jędrzejewski-Szmek
>> wrote:
>> >
>> > On Fri, Jul 12, 2024 at 05:53:25PM +0100, Aoife Moloney wrote:
>> > > In order to enable DRM_PANIC, you need to dis
On Fri, Jul 12, 2024 at 01:21:41PM -0400, Neal Gompa wrote:
> On Fri, Jul 12, 2024 at 1:12 PM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Fri, Jul 12, 2024 at 05:53:25PM +0100, Aoife Moloney wrote:
> > > In order to enable DRM_PANIC, you need to disable VT_CONSOLE in the
> > > kernel
> >
> > T
On 7/12/24 11:53 AM, Aoife Moloney wrote:
Supported drivers are simpledrm, mgag200, ast, (and imx, tidss, on
aarch64). I'm working on nouveau support, and I hope i915 and amdgpu
will add support too.
If the driver is not supported, you won't see the panic screen, but it
won't be worse than what y
On Fri, Jul 12, 2024 at 1:12 PM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Fri, Jul 12, 2024 at 05:53:25PM +0100, Aoife Moloney wrote:
> > In order to enable DRM_PANIC, you need to disable VT_CONSOLE in the
> > kernel
>
> The idea for DRM_PANIC is nice, but I worry about the impact of disabling
> V
On Fri, Jul 12, 2024 at 05:53:25PM +0100, Aoife Moloney wrote:
> In order to enable DRM_PANIC, you need to disable VT_CONSOLE in the
> kernel
The idea for DRM_PANIC is nice, but I worry about the impact of disabling
VT_CONSOLE. Plymouth is not used everywhere, e.g. what about cloud images
and such
Wiki - https://fedoraproject.org/wiki/Changes/EnableDrmPanic
Discussion Thread -
https://discussion.fedoraproject.org/t/f42-change-proposal-enable-drm-panic-system-wide/125542
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process
38 matches
Mail list logo
