mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_LOG_BUF_SHIFT hardwired in 2.6.0-test4-bk2 ?
Date: Fri, 29 Aug 2003 20:57:40 +0200	[thread overview]
Message-ID: <1062183460.4847.6.camel@rousalka.dyndns.org> (raw)
In-Reply-To: <20030829114111.18ec26d0.rddunlap@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 1751 bytes --]

Le ven 29/08/2003 à 20:41, Randy.Dunlap a écrit :
> On Fri, 29 Aug 2003 11:36:34 -0700 "Randy.Dunlap" <rddunlap@osdl.org> wrote:
> 
> | On Fri, 29 Aug 2003 20:30:19 +0200 Nicolas Mailhot <Nicolas.Mailhot@laPoste.net> wrote:
> | 
> | | Hi,
> | | 
> | | 	I'm testing acpi changes and unfortunately all the debug messages
> | | overflow the log buffer. So I decided to increase CONFIG_LOG_BUF_SHIFT 
> | | in .config (there was a menu entry for this at some time in menuconfig
> | | but I can't find it anymore).
> | | 
> | | 	Anyway no matter what I do the value seems to be reseted to 14 at build
> | | time. Is there a way to cleanly change it without poking directly into
> | | the kernel source code ?
> | 
> | You need to enable DEBUG_KERNEL (kernel debugging) to see it in the menu.
> | 
> | After you edit .config, run 'make oldconfig' and that should fix it.
> 
> More accurately, you cannot edit .config and make oldconfig on this
> config option if DEBUG_KERNEL is not set.  It won't take effect.
> It will be lost by make oldconfig, so enable DEBUG_KERNEL first.

More accurately if DEBUG_KERNEL is not set you won't get the menuconfig
entry to set it *and* whatever manual changes you to to it in your
.config won't be taken into account.

Which is just plain stupid - if it's linked this hard to DEBUG_KERNEL
what the hell is it doing in another config section ? It's not like it
depended on another option (like usb-storage on usb & scsi). I missed it
both in menuconfig (duh - didn't thought of re-reading the whole menu
structure after enabling debug) and during manual .config edit.

(anyway you solved my problem at light speed and for this you're my day
god - thanks a lot)

-- 
Nicolas Mailhot

[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-08-29 18:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-29 18:30 Nicolas Mailhot
2003-08-29 18:36 ` Randy.Dunlap
2003-08-29 18:41   ` Randy.Dunlap
2003-08-29 18:57     ` Nicolas Mailhot [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=1062183460.4847.6.camel@rousalka.dyndns.org \
    --to=nicolas.mailhot@laposte.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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

all inboxes | Powered by JetHome®