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@xxxxxxxxxxxx> 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?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/