* Re: PROBLEM: CONFIG_DEFAULT_MESSAGE_LOGLEVEL option seems not to work
[not found] <20130315225636.2baf75ae@gmail.com>
@ 2013-03-16 4:54 ` Randy Dunlap
0 siblings, 0 replies; only message in thread
From: Randy Dunlap @ 2013-03-16 4:54 UTC (permalink / raw)
To: Manolo Díaz; +Cc: linux-kbuild, LKML
On 03/15/13 14:56, Manolo Díaz wrote:
> Hi,
>
> It seems that the kernel loglevel is set to 7 ignoring the
> CONFIG_DEFAULT_MESSAGE_LOGLEVEL option (set to 4 in my config file)
>
> The /proc/sys/kernel/printk output is
>
> 7 4 1 7
>
> Passing the boot parameter "loglevel=4" or echoing "4 4 1 7"
> to /proc/sys/kernel/printk solves my problem and then this proc file
> contains
>
> 4 4 1 7
>
> as expected.
>
> kernel version:
> Linux version 3.8.3 (root@alcyone) (gcc version 4.7.2 (Debian 4.7.2-5)
> ) #2 SMP Fri Mar 15 08:23:50 CET 2013
>
> config file is gziped and attached.
Hi,
CONFIG_DEFAULT_MESSAGE_LOGLEVEL modifies the second field (value) in /proc/sys/kernel/printk,
not the first value. OTOH, the "loglevel" kernel parameter modifies the first value in
that /proc file, not the second value.
Does that clarify/help?
--
~Randy
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-03-16 4:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20130315225636.2baf75ae@gmail.com>
2013-03-16 4:54 ` PROBLEM: CONFIG_DEFAULT_MESSAGE_LOGLEVEL option seems not to work Randy Dunlap
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox