Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
RFE:
Steps to Reproduce:
Any chance of having a debug mode option already setup in
/etc/grub.d/10_linux (or wherever is appropriate) as it's tedious and
prone to user errors to:-
a) add systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M to
the kernel command line;
b) enable the debug-shell.service.
Also, enabling the debug-shell service activates tty9 which is not
accessible for a KVM right? Is there another option for KVMs?
psklenar, this should be rejected in QA. The problem is that you've now overridden the well known, well documented, and heavily used kernel boot parameter "debug" which has been in the kernel since 2.5.3.
As a result when debug is specified as a kernel parameter (which a lot of our internal scripts do) the result is a huge amount of debug code from systemd rendering kernel debugging via console useless. There are *thousands* of lines of messages from systemd that cause important kernel debug messages to scroll of the console screen.
If people want a short systemd debug message, then implement systemd.debug or some such parameter. Do not, however, overload the kernel's debug parameter.
Same goes for the "quiet" parameter FWIW.
P.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
The comment above is incorrect. The correct version is bellow.
I'm sorry for any inconvenience.
---------------------------------------------------------------
This request was NOT resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you need
to escalate this bug.