From: Petr Mladek <pmladek@suse.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: Make CONSOLE_LOGLEVEL_QUIET configurable
Date: Mon, 25 Jun 2018 16:56:53 +0200 [thread overview]
Message-ID: <20180625145653.knkugqikkxpvz67z@pathway.suse.cz> (raw)
In-Reply-To: <f60d844d-9d3b-3154-4eec-982432c8e502@redhat.com>
On Wed 2018-06-20 15:37:47, Hans de Goede wrote:
> Hi,
>
> On 20-06-18 13:03, Petr Mladek wrote:
> > On Tue 2018-06-19 13:57:26, Hans de Goede wrote:
> > > The goal of passing the "quiet" option to the kernel is for the kernel
> > > to be quiet unless something really is wrong.
> > >
> > > Sofar passing quiet has been (mostly) equivalent to passing
> > > loglevel=4 on the kernel commandline. Which means to show any messages
> > > with a level of KERN_ERR or higher severity on the console.
> > >
> > > In practice this often does not result in a quiet boot though, since
> > > there are many false-positive or otherwise harmless error messages printed,
> > > defeating the purpose of the quiet option. Esp. the ACPICA code is really
> > > bad wrt this, but there are plenty of others too.
> >
> > I see your pain. But this sounds like a workaround for a broken code.
> > This change might just encourage people to create even more mess.
>
> I've been submitting patches upstream to fix false-positive KERN_ERR
> messages for more then a year now and getting a KERN_ERR free kernel
> (on more then 1 specific model hw) is just undoable. Every release some
> new nonsense error comes up, like e.g.:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1568276
>
> Besides this random KERN_ERR cases (of which there are plenty
> by themselves) I've also had long discussions with the ACPICA upstream
> maintainers, but they refuse to change this instead insisting that:
>
> a) Vendors should fix there DSDTs to be perfect; and
> b) end-users should then update their BIOS to fix this
>
> Neither of which is a realistic expectation in anyway.
Thanks for the many examples. It would help me to argue if anyone
later complains about this change ;-)
> > > This commit makes CONSOLE_LOGLEVEL_QUIET configurable.
> > >
> > > This for example will allow distros which want quiet to really mean quiet
> > > to set CONSOLE_LOGLEVEL_QUIET so that only messages with a higher severity
> > > then KERN_ERR (CRIT, ALERT, EMERG) get printed, avoiding an endless game
> > > of whack-a-mole silencing harmless error messages.
> >
> > I find it a bit confusing that "quiet" would mean something different
> > on different systems.
>
> The kernel is so configurable already that I don't think this really is much
> of an issue, quiet will still mean quiet on all systems, some might just
> be a tad more quiet (or actually be quiet) compared to others.
Just for record. Some people actually do a lot to prevent adding new
configure options. The many possibilities cause troubles to users
and even experienced developers.
A common argument against adding new options is: "How users could be
able to choose reasonable value when even experts (maintainers,
developers) are not able to agree on it".
> I went with making this configurable because I expect that to
> be a controversial change.
Exactly, I thought about changing the default. But it might just
bring a lot of bike-shedding.
I do not see any other good option. More people like this patch.
So I pushed it into printk.git, branch for-4.19.
Best Regards,
Petr
next prev parent reply other threads:[~2018-06-25 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 11:57 Hans de Goede
2018-06-19 13:31 ` Steven Rostedt
2018-06-20 6:34 ` Sergey Senozhatsky
2018-06-20 11:03 ` Petr Mladek
2018-06-20 11:24 ` Sergey Senozhatsky
2018-06-20 13:43 ` Hans de Goede
2018-06-21 1:43 ` Sergey Senozhatsky
2018-06-20 13:37 ` Hans de Goede
2018-06-25 14:56 ` Petr Mladek [this message]
2018-06-20 14:07 ` Steven Rostedt
2018-06-20 14:18 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180625145653.knkugqikkxpvz67z@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®