kobject: 'vcs1' (d2172ad8): kobject_add_internal: parent: 'vc', set: 'devices'

kobject: 'vcs1' (d2172ad8): kobject_add_internal: parent: 'vc', set: 'devices'

[Folkert van Heusden]

Hi,

What switch is responsible for this logging:
[   94.025172] kobject: 'vcsa1': free name
[   94.025231] kobject: 'vcs1' (d2172ad8): kobject_add_internal: parent: 'vc', set: 'devices'
[   94.025308] kobject: 'vcs1' (d2172ad8): kobject_uevent_env
[   94.025315] kobject: 'vcs1' (d2172ad8): fill_kobj_path: path = '/class/vc/vcs1'
[   94.025352] kobject: 'vcsa1' (d23f00d8): kobject_add_internal: parent: 'vc', set: 'devices'
[   94.025398] kobject: 'vcsa1' (d23f00d8): kobject_uevent_env

I can't find it and it removes an oops from dmesg before i can capture it.


Folkert van Heusden

-- 
MultiTail är en flexibel redskap för att fälja logfilar, utför av
commandoer, filtrera, ge färg, sammanfoga, o.s.v. följa.
http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

Re: kobject: 'vcs1' (d2172ad8): kobject_add_internal: parent: 'vc', set: 'devices'

[Randy Dunlap]

On Wed, 19 Nov 2008 10:59:41 +0100 Folkert van Heusden wrote:

> Hi,
> 
> What switch is responsible for this logging:
> [   94.025172] kobject: 'vcsa1': free name
> [   94.025231] kobject: 'vcs1' (d2172ad8): kobject_add_internal: parent: 'vc', set: 'devices'
> [   94.025308] kobject: 'vcs1' (d2172ad8): kobject_uevent_env
> [   94.025315] kobject: 'vcs1' (d2172ad8): fill_kobj_path: path = '/class/vc/vcs1'
> [   94.025352] kobject: 'vcsa1' (d23f00d8): kobject_add_internal: parent: 'vc', set: 'devices'
> [   94.025398] kobject: 'vcsa1' (d23f00d8): kobject_uevent_env
> 
> I can't find it and it removes an oops from dmesg before i can capture it.

Those prints use pr_debug() from include/linux/kernel.h, which was changed
most recently in

commit d091c2f58ba32029495a933b721e8e02fbd12caa
Author: Martin Schwidefsky <schwidefsky@de.ibm.com>
Date:   Wed Nov 12 21:16:43 2008 +0100

    Add 'pr_fmt()' format modifier to pr_xyz macros.

Do you have CONFIG_DYNAMIC_PRINTK_DEBUG enabled?  That could affect the
kernel log output.

---
~Randy