<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body><a class="email" href="mailto:zbyszek@in.waw.pl" title="Zbigniew Jedrzejewski-Szmek <zbyszek@in.waw.pl>"> Zbigniew Jedrzejewski-Szmek</a> changed <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Do not parse "debug" command line parameter" href="https://bugs.freedesktop.org/show_bug.cgi?id=76935">bug 76935</a> <table border="1" cellspacing="0" cellpadding="8"> <tr> <th>What</th> <th>Removed</th> <th>Added</th> </tr> <tr> <td style="text-align:right;">Status</td> <td>REOPENED </td> <td>RESOLVED </td> </tr> <tr> <td style="text-align:right;">Resolution</td> <td>--- </td> <td>NOTABUG </td> </tr></table> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Do not parse "debug" command line parameter" href="https://bugs.freedesktop.org/show_bug.cgi?id=76935#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - Do not parse "debug" command line parameter" href="https://bugs.freedesktop.org/show_bug.cgi?id=76935">bug 76935</a> from <a class="email" href="mailto:zbyszek@in.waw.pl" title="Zbigniew Jedrzejewski-Szmek <zbyszek@in.waw.pl>"> Zbigniew Jedrzejewski-Szmek</a> <pre>(In reply to <a href="show_bug.cgi?id=76935#c0">comment #0</a>) > Supplying "debug" on the kernel command line gets parsed by systemd. If > a random assertion in it fires, something like this, for example: > > [ 150.308000] systemd-journald[1559]: Assertion > 'dual_timestamp_is_set(&e->timestamp)' failed at > src/libsystemd/sd-event/sd-event.c:2191, function > sd_event_get_now_monotonic(). Ignoring. > [ 150.308000] systemd-journald[1559]: Assertion > 'dual_timestamp_is_set(&e->timestamp)' failed at > src/libsystemd/sd-event/sd-event.c:2191, function > sd_event_get_now_monotonic(). Ignoring. > > it floods dmesg and I cannot log into the machine anymore. I have to > reboot and remove "debug" from the command line so that the machine can > boot. BUT(!), I want to see kernel debug messages so I have to be able > to supply "debug" *without* systemd interfering. Yep, this looks like a bug, and the assertion should be fixed. If this is still occuring, can you file a new bug specifying what systemd version you are using, or post to the mailing list? > What it should do, instead, is *not* parse "debug" but something else > with a namespace, i.e. "systemd.debug" or whatever as "debug" is a > kernel cmdline parameter and not aimed for systemd. Yes, systemd.log_level is that. > And while we're at it, we'd need a configurable option to tell systemd > *not* to log to dmesg for when one wants to see only output from the > kernel in the kernel ring buffer, i.e. something like "systemd.nodmesg" > or so. Yes, use loglevel=, and or just systemd.log_level=. (In reply to <a href="show_bug.cgi?id=76935#c5">comment #5</a>) > No, I want to say "debug" on the kernel command line and *not* see > systemd output at all but kernel output only. Is this possible? Yes, use 'loglevel=...'. Or .debug systemd.log_target=...., or .debug systemd.log_level=...'. As has been said, plain 'debug' turns more than just the kernel debugging, and this is extremely useful for general boot problems, where it is not clear what is a bug in the kernel, and what is a but in systemd, or plymouth, or elsewhere. Available options are listed in <a href="http://www.freedesktop.org/software/systemd/man/systemd.html#Kernel%20Command%20Line">http://www.freedesktop.org/software/systemd/man/systemd.html#Kernel%20Command%20Line</a>. If a combination of options which implements the functionality you need is not available, please holler.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>