From: Ingo Molnar <mingo@elte.hu>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch] add ignore_loglevel boot option
Date: Wed, 6 Dec 2006 10:00:26 +0100 [thread overview]
Message-ID: <20061206090026.GB28160@elte.hu> (raw)
In-Reply-To: <20061205144709.9c50194d.randy.dunlap@oracle.com>
* Randy Dunlap <randy.dunlap@oracle.com> wrote:
> > sometimes the kernel prints something interesting while userspace
> > bootup keeps messages turned off via loglevel. Enable the printing
> > of /all/ kernel messages via the "ignore_loglevel" boot option. Off
> > by default.
>
> Hi,
>
> Is this equivalent to using the "debug" kernel parameter except that
> userspace (init scripts) cannot muck it up (modify the setting)?
yeah.
> I've seen init scripts modify the loglevel, much to my dismay.
yeah - i once lost a few hours of debugging to such an incident.
> I'd say that this is useful, but it's really userspace that needs to
> be fixed.
well, loglevel /can/ be managed by userspace, and sometimes an important
kernel message might have a too high loglevel. Also, sometimes the
kernel does spurious messages during hardware detect, etc., so userspace
naturally wants to prevent them from going to the console. So it's
really a mix of a problem and i wouldnt put the blame on user-space.
User-space used the only control they have to fix the situation.
Ingo
prev parent reply other threads:[~2006-12-06 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 12:09 Ingo Molnar
2006-12-05 22:47 ` Randy Dunlap
2006-12-06 9:00 ` Ingo Molnar [this message]
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=20061206090026.GB28160@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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®