Re: [gentoo-user] What program produces message like these?

[Vladimir G. Ivanovic]

Many thanks for the hints. It looks like I (accidentally) had driver
debugging turned on. I'm recompiling my kernel to see if that fixes my
problem.

--- Vladimir

On Wed, 2006-03-29 at 10:34 -0700, Richard Fish wrote:

> On 3/29/06, Vladimir G. Ivanovic <vgivanovic@×××××××.net> wrote:
> >         CLASS: registering class device: ID = 'vcs7'
> >         class_uevent - name = vcs7
> >         class_device_create_uevent called for vcs7
> >         CLASS: registering class device: ID = 'vcsa7'
> >         class_uevent - name = vcsa7
> >         class_device_create_uevent called for vcsa7
> >
> > And, more importantly, how do I get rid of them? They fill up my kernel
> > ring buffer, and I can't see boot-time messages from the kernel.
>
> AFAIK if they are showing up in dmesg output, they are coming from the
> kernel.  Looks like you enabled DEBUG in your kernel:
>
> # cd /usr/src/linux-2.6.16.1 && grep -r class_device_create_uevent .
> ./drivers/base/class.c:static int class_device_create_uevent(struct
> class_device *class_dev,
>
> # less drivers/base/class.c
> ...
>         pr_debug("%s called for %s\n", __FUNCTION__, class_dev->class_id);
> ...
>
> # grep -r pr_debug . | grep "define"
> ...
> ./include/linux/kernel.h:#define pr_debug(fmt,arg...) \
> ...
>
> # less include/linux/kernel.h
> ...
> #ifdef DEBUG
> #define pr_debug(fmt,arg...) \
>         printk(KERN_DEBUG fmt,##arg)
> ...
>
> But the boot-time messages should be saved in /var/log/dmesg.
>
> -Richard
>


Vladimir G. Ivanovic
Palo Alto, CA 94306
[phone]