From: Ram <vshrirama@gmail.com>
To: "Paulo Marques" <pmarques@grupopie.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: printk's - i dont want any limit howto?
Date: Fri, 2 Jun 2006 00:37:58 -0700 [thread overview]
Message-ID: <8bf247760606020037x7eedab52qa9c736bdba740cb8@mail.gmail.com> (raw)
In-Reply-To: <447EEDCB.1070002@grupopie.com>
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.
i have given printk_ratelimit_burst= 1000 ; printk_ratelimit_jiffies = 0 ;
but it does not work.
Please Advice,
Regards,
sriram
On 6/1/06, Paulo Marques <pmarques@grupopie.com> wrote:
> Ram wrote:
> > Hi,
>
> Hi,
>
> > I have a driver full of printks. i am trying to understand the way
> > the driver functions using printks
> >
> > So, i have a situation where i want all the printk's to be printed
> > come whatever.
>
> That is the normal behavior.
>
> > I dont want any rate limiting or anything else that prevents from
> > my printks from appearing on the screen or dmesg.
> >
> > Its really confusing when only one of your printks appear and some
> > just dont appear even though you expect them to appear.
> >
> > Is there any way to make all the printks to appear come what may?.
> > If so, how do i do it?.
> >
> > Went through the printk.c am not sure setting the
> > printk_ratelimit_jiffies = 0 and printk_ratelimit_burst= 1000 will do?
> >
> > am not sure if printk_ratelimit_jiffies = 0 is valid.
>
> These are just used by "printk_ratelimit()" in constructs such as:
>
> if (printk_ratelimit())
> printk(KERN_INFO "some message that may appear very often");
>
> If you simply use printk, there should be no rate limiting.
>
> > please advice.
>
> I would say your printk's are not getting called at all or the log level
> of the messages is not sufficient for them to appear on the console or
> on the log. See Documentation/filesystems/proc.txt ->
> proc/sys/kernel/printk and syslog(2) for more documentation on this.
>
> I hope this helps,
>
> --
> Paulo Marques - www.grupopie.com
>
> Pointy-Haired Boss: I don't see anything that could stand in our way.
> Dilbert: Sanity? Reality? The laws of physics?
>
next prev parent reply other threads:[~2006-06-02 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 7:25 Ram
2006-06-01 13:38 ` Paulo Marques
2006-06-02 7:37 ` Ram [this message]
2006-06-02 8:34 ` Bernd Eckenfels
2006-06-02 14:40 ` Aurélien Francillon
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=8bf247760606020037x7eedab52qa9c736bdba740cb8@mail.gmail.com \
--to=vshrirama@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.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®