From: "Aurélien Francillon" <aurel@naurel.org>
To: Ram <vshrirama@gmail.com>
Cc: "Paulo Marques" <pmarques@grupopie.com>, linux-kernel@vger.kernel.org
Subject: Re: printk's - i dont want any limit howto?
Date: Fri, 2 Jun 2006 16:40:25 +0200 [thread overview]
Message-ID: <200606021640.25531.aurel@naurel.org> (raw)
In-Reply-To: <8bf247760606020037x7eedab52qa9c736bdba740cb8@mail.gmail.com>
On Friday 02 June 2006 09:37, Ram wrote:
> Hi,
> Actually even though the printks are getting executed.
>
> ONLY some appear. I have given both KERN_ERR and KERN_DEBUG
>
>
> Its not the log level problem. probably the buffer or something else.
> am not sure on that.
...
Increasing the "Kernel log buffer size" (under Kernel hacking config menu) to
a bigger value helps to prevent overwriting the kernel circular buffer.
Using synchronous writes in syslog usually helps to get all the messages
written to disk before a kernel crash
HTH,
Aurélien
prev parent reply other threads:[~2006-06-02 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 7:25 printk's - i dont want any limit howto? Ram
2006-06-01 13:38 ` Paulo Marques
2006-06-02 7:37 ` Ram
2006-06-02 8:34 ` Bernd Eckenfels
2006-06-02 14:40 ` Aurélien Francillon [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=200606021640.25531.aurel@naurel.org \
--to=aurel@naurel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.com \
--cc=vshrirama@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.