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

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

[Vladimir G. Ivanovic]

        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.

I just emerged klogd, and so now I can at least grep
through /var/log/messages for kernel messages ... which is what dmesg is
supposed to be for.

Thanks for any help.

--- Vladimir

Vladimir G. Ivanovic
Palo Alto, CA 94306
+1 650 678 8014

Vladimir G. Ivanovic
Palo Alto, CA 94306
+1 650 678 8014

-- 
gentoo-user@gentoo.org mailing list

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

[Thomas T. Veldhouse]

Vladimir G. Ivanovic 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
USB devices attached?  Perhaps one is flaky and is going on and 
offline?  Do you have usbd or coldplug/hotplug installed?

Tom Veldhouse


-- 
gentoo-user@gentoo.org mailing list

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

[Richard Fish]

On 3/29/06, Vladimir G. Ivanovic <vgivanovic@comcast.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

-- 
gentoo-user@gentoo.org mailing list

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

[James]

Vladimir G. Ivanovic <vgivanovic <at> comcast.net> writes:

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


Here's a trick I use in root's /root/.bashrc
just for such issues:

 alias dmesg='dmesg -s 264000 | less'

the trick is to set the size to a larger limit than
you want. I through mine into less, but, you do 
not have to do this.

hth,

James



-- 
gentoo-user@gentoo.org mailing list

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

[Vladimir G. Ivanovic]

[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]

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@comcast.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
+1 650 678 8014

[-- Attachment #2: Type: text/html, Size: 2899 bytes --]

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

[Vladimir G. Ivanovic]

[-- Attachment #1: Type: text/plain, Size: 1834 bytes --]

Fixed by turning off DEBUG_DRIVER.

---- Vladimir

On Wed, 2006-03-29 at 13:57 -0800, Vladimir G. Ivanovic wrote:

> 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@comcast.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
> +1 650 678 8014


Vladimir G. Ivanovic
Palo Alto, CA 94306
+1 650 678 8014

[-- Attachment #2: Type: text/html, Size: 3371 bytes --]