<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:zbyszek@in.waw.pl" title="Zbigniew Jedrzejewski-Szmek <zbyszek@in.waw.pl>"> <span class="fn">Zbigniew Jedrzejewski-Szmek</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Sysctl parametr (kernel.printk) don't apply at boot"
href="https://bugs.freedesktop.org/show_bug.cgi?id=71148">bug 71148</a>
<br>
<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>NEEDINFO
</td>
<td>NEW
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Sysctl parametr (kernel.printk) don't apply at boot"
href="https://bugs.freedesktop.org/show_bug.cgi?id=71148#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Sysctl parametr (kernel.printk) don't apply at boot"
href="https://bugs.freedesktop.org/show_bug.cgi?id=71148">bug 71148</a>
from <span class="vcard"><a class="email" href="mailto:zbyszek@in.waw.pl" title="Zbigniew Jedrzejewski-Szmek <zbyszek@in.waw.pl>"> <span class="fn">Zbigniew Jedrzejewski-Szmek</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=71148#c8">comment #8</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=71148#c6">comment #6</a>)
> >
> > > I read that this is related to udev: <a href="https://bugs.archlinux.org/task/33620">https://bugs.archlinux.org/task/33620</a>
> > This is also unrelated. 33620 is about sysctl settings for network devices
> > which are only created after those settings have been already set. printk is
> > always there.
> yes and whole <a href="show_bug.cgi?id=71148#c5">Comment 5</a> is about 'tcp_allowed_congestion_control' variable,
> not printk. should I open another bug report for this?</span >
Just debug this one first.
<span class="quote">> > Can you install the attached service in
> > /etc/systemd/system/monitor_printk.service, enable it with 'systemctl enable
> > monitor_printk', and post the output from the 'journalctl -b' after a reboot?
> ok, log attached</span >
>From the log:
Nov 26 22:06:15 dell1210 cat[190]: 3 3 3 3
Nov 26 22:06:15 dell1210 inotifywait[176]: /proc/sys/kernel/printk OPEN
Nov 26 22:06:15 dell1210 inotifywait[176]: /proc/sys/kernel/printk ACCESS
Nov 26 22:06:15 dell1210 inotifywait[176]: /proc/sys/kernel/printk
CLOSE_NOWRITE,CLOSE
Nov 26 22:06:15 dell1210 systemd[1]: Started Apply Kernel Variables.
... and it doesn't seem to be set afterwards. Could you please check again
that it *is* actually set to something different after the boot?
So maybe your hypothesis that it is reset during the kernel oops is true.
What happens if you disable the restoring of the backlight, which should remove
the oops
(systemctl mask <a href="mailto:systemd-backlight@acpi_video0.service">systemd-backlight@acpi_video0.service</a>
<a href="mailto:systemd-backlight@acpi_video1.service">systemd-backlight@acpi_video1.service</a>)?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>