public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kobject: 'vcs1' (d2172ad8): kobject_add_internal: parent: 'vc', set: 'devices'
Date: Wed, 19 Nov 2008 10:12:38 -0800	[thread overview]
Message-ID: <20081119101238.c46ad0cd.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20081119095934.GF4370@vanheusden.com>

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

      reply	other threads:[~2008-11-19 18:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19  9:59 kobject: 'vcs1' (d2172ad8): kobject_add_internal: parent: 'vc', set: 'devices' Folkert van Heusden
2008-11-19 18:12 ` Randy Dunlap [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081119101238.c46ad0cd.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=folkert@vanheusden.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox