On 15/07/2024 12:04, Barry wrote:
On 15 Jul 2024, at 10:21, Jocelyn Falempe <jfalempe@xxxxxxxxxx> 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 chance to journal
the logs.
We see this when supporting users on
https://discussion.fedoraproject.org/
<https://discussion.fedoraproject.org/> regularly.
I think you are saying that if drm panic is enabled we cannot see logs
that would allow debugging an issue?
Yes, there is a small gap, between when VT_CONSOLE starts to log, and
when /init is executed, and can start logging.
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 ideal, but that should at least allows to see those logs.
Barry
Best regards,
--
Jocelyn
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
