Gentoo Archives: gentoo-user

From: Richard Fish <bigfish@××××××××××.org>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] What program produces message like these?
Date: Wed, 29 Mar 2006 17:57:46
Message-Id: 7573e9640603290934s2f745cbex6d7c31dc0b2e445d@mail.gmail.com
In Reply to: [gentoo-user] What program produces message like these? by "Vladimir G. Ivanovic"
1 On 3/29/06, Vladimir G. Ivanovic <vgivanovic@×××××××.net> wrote:
2 > CLASS: registering class device: ID = 'vcs7'
3 > class_uevent - name = vcs7
4 > class_device_create_uevent called for vcs7
5 > CLASS: registering class device: ID = 'vcsa7'
6 > class_uevent - name = vcsa7
7 > class_device_create_uevent called for vcsa7
8 >
9 > And, more importantly, how do I get rid of them? They fill up my kernel
10 > ring buffer, and I can't see boot-time messages from the kernel.
11
12 AFAIK if they are showing up in dmesg output, they are coming from the
13 kernel. Looks like you enabled DEBUG in your kernel:
14
15 # cd /usr/src/linux-2.6.16.1 && grep -r class_device_create_uevent .
16 ./drivers/base/class.c:static int class_device_create_uevent(struct
17 class_device *class_dev,
18
19 # less drivers/base/class.c
20 ...
21 pr_debug("%s called for %s\n", __FUNCTION__, class_dev->class_id);
22 ...
23
24 # grep -r pr_debug . | grep "define"
25 ...
26 ./include/linux/kernel.h:#define pr_debug(fmt,arg...) \
27 ...
28
29 # less include/linux/kernel.h
30 ...
31 #ifdef DEBUG
32 #define pr_debug(fmt,arg...) \
33 printk(KERN_DEBUG fmt,##arg)
34 ...
35
36 But the boot-time messages should be saved in /var/log/dmesg.
37
38 -Richard
39
40 --
41 gentoo-user@g.o mailing list

Replies

Subject Author
Re: [gentoo-user] What program produces message like these? "Vladimir G. Ivanovic" <vgivanovic@×××××××.net>