printk's - i dont want any limit howto?

printk's - i dont want any limit howto?

[Ram]

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.


   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.


please advice.


Regards,
sriram

Re: printk's - i dont want any limit howto?

[Paulo Marques]

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?

Re: printk's - i dont want any limit howto?

[Ram]

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

Re: printk's - i dont want any limit howto?

[Bernd Eckenfels]

Ram <vshrirama@gmail.com> wrote:
>  Actually even though the printks are getting executed.
>  ONLY some appear. I have given both KERN_ERR and KERN_DEBUG

do u use "dmesg" to see them? so you do not have to be sure your syslog is
logging them (and not aggregating some).

>   i have given printk_ratelimit_burst= 1000 ; printk_ratelimit_jiffies = 0 ;

If ratelimit is the problem I think it will write a message that you missed
some output as level warning. So it is unlikely the issue.

Gruss
Bernd

Re: printk's - i dont want any limit howto?

[Aurélien Francillon]

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