public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: "Manolo Díaz" <diaz.manolo@gmail.com>
To: linux-kbuild@vger.kernel.org
Subject: Re: PROBLEM: CONFIG_DEFAULT_MESSAGE_LOGLEVEL option seems not to work
Date: Sat, 16 Mar 2013 12:01:46 +0100	[thread overview]
Message-ID: <20130316120146.298f3064@gmail.com> (raw)
In-Reply-To: <5143FB1F.9010509@infradead.org>

>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?
>

Yes, I misunderstood the meaning of default_message_loglevel. Sorry.

Regards,
-- 
Manolo Díaz

  reply	other threads:[~2013-03-16 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 21:56 PROBLEM: CONFIG_DEFAULT_MESSAGE_LOGLEVEL option seems not to work Manolo Díaz
2013-03-16  4:54 ` Randy Dunlap
2013-03-16 11:01   ` Manolo Díaz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-03-15 22:43 Manolo Díaz
2013-04-08 10:50 ` Michal Marek

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=20130316120146.298f3064@gmail.com \
    --to=diaz.manolo@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    /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