From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: bluez-devel@lists.sf.net, linux-kernel@vger.kernel.org,
maxk@qualcomm.com
Subject: Re: [Bluez-devel] trouble with sysfs and bluetooth
Date: Tue, 30 Jan 2007 11:52:08 +0100 [thread overview]
Message-ID: <1170154328.27519.27.camel@violet> (raw)
In-Reply-To: <200701301135.53178.oliver@neukum.name>
Hi Oliver,
> I am constantly getting these messages in 2.6.20-rc6 Greg's tree:
>
> Jan 30 11:26:42 valisk kernel: Bluetooth: Core ver 2.11
> Jan 30 11:26:42 valisk kernel: PM: Adding info for platform:bluetooth
> Jan 30 11:26:42 valisk kernel: kobject_add failed for bluetooth with -EEXIST, don't try to register things with the same name in the same directory.
> Jan 30 11:26:42 valisk kernel:
> Jan 30 11:26:42 valisk kernel: Call Trace:
> Jan 30 11:26:42 valisk kernel: [<ffffffff802f4e3b>] kobject_shadow_add+0x147/0x17b
> Jan 30 11:26:42 valisk kernel: [<ffffffff802f5162>] subsystem_register+0x1b/0x2a
> Jan 30 11:26:42 valisk kernel: [<ffffffff803773db>] class_register+0xbf/0x1bd
> Jan 30 11:26:42 valisk kernel: [<ffffffff80377a7e>] class_create+0x53/0x71
> Jan 30 11:26:42 valisk kernel: [<ffffffff881c711c>] :bluetooth:bt_sysfs_init+0x5a/0x8b
> Jan 30 11:26:42 valisk kernel: [<ffffffff881c701b>] :bluetooth:bt_init+0x1b/0x53
> Jan 30 11:26:42 valisk kernel: [<ffffffff8023bf0a>] sys_init_module+0x1467/0x15c3
> Jan 30 11:26:42 valisk kernel: [<ffffffff80208fee>] system_call+0x7e/0x83
> Jan 30 11:26:42 valisk kernel:
> Jan 30 11:26:42 valisk kernel: PM: Removing info for platform:bluetooth
> Jan 30 11:26:43 valisk kernel: Bluetooth: Core ver 2.11
> Jan 30 11:26:44 valisk kernel: PM: Adding info for platform:bluetooth
> Jan 30 11:26:44 valisk kernel: kobject_add failed for bluetooth with -EEXIST, don't try to register things with the same name in the same directory.
> Jan 30 11:26:44 valisk kernel:
> Jan 30 11:26:44 valisk kernel: Call Trace:
> Jan 30 11:26:45 valisk kernel: [<ffffffff802f4e3b>] kobject_shadow_add+0x147/0x17b
> Jan 30 11:26:45 valisk kernel: [<ffffffff802f5162>] subsystem_register+0x1b/0x2a
> Jan 30 11:26:45 valisk kernel: [<ffffffff803773db>] class_register+0xbf/0x1bd
> Jan 30 11:26:45 valisk kernel: [<ffffffff80377a7e>] class_create+0x53/0x71
> Jan 30 11:26:46 valisk kernel: [<ffffffff881c711c>] :bluetooth:bt_sysfs_init+0x5a/0x8b
> Jan 30 11:26:46 valisk kernel: [<ffffffff881c701b>] :bluetooth:bt_init+0x1b/0x53
> Jan 30 11:26:46 valisk kernel: [<ffffffff8023bf0a>] sys_init_module+0x1467/0x15c3
> Jan 30 11:26:46 valisk kernel: [<ffffffff80208fee>] system_call+0x7e/0x83
> Jan 30 11:26:46 valisk kernel:
do you see them also with the plain vanilla 2.6.20-rc6 kernel or are
these only coming up in Greg's tree?
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
WARNING: multiple messages have this Message-ID (diff)
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: linux-kernel@vger.kernel.org, maxk@qualcomm.com,
bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] trouble with sysfs and bluetooth
Date: Tue, 30 Jan 2007 11:52:08 +0100 [thread overview]
Message-ID: <1170154328.27519.27.camel@violet> (raw)
In-Reply-To: <200701301135.53178.oliver@neukum.name>
Hi Oliver,
> I am constantly getting these messages in 2.6.20-rc6 Greg's tree:
>
> Jan 30 11:26:42 valisk kernel: Bluetooth: Core ver 2.11
> Jan 30 11:26:42 valisk kernel: PM: Adding info for platform:bluetooth
> Jan 30 11:26:42 valisk kernel: kobject_add failed for bluetooth with -EEXIST, don't try to register things with the same name in the same directory.
> Jan 30 11:26:42 valisk kernel:
> Jan 30 11:26:42 valisk kernel: Call Trace:
> Jan 30 11:26:42 valisk kernel: [<ffffffff802f4e3b>] kobject_shadow_add+0x147/0x17b
> Jan 30 11:26:42 valisk kernel: [<ffffffff802f5162>] subsystem_register+0x1b/0x2a
> Jan 30 11:26:42 valisk kernel: [<ffffffff803773db>] class_register+0xbf/0x1bd
> Jan 30 11:26:42 valisk kernel: [<ffffffff80377a7e>] class_create+0x53/0x71
> Jan 30 11:26:42 valisk kernel: [<ffffffff881c711c>] :bluetooth:bt_sysfs_init+0x5a/0x8b
> Jan 30 11:26:42 valisk kernel: [<ffffffff881c701b>] :bluetooth:bt_init+0x1b/0x53
> Jan 30 11:26:42 valisk kernel: [<ffffffff8023bf0a>] sys_init_module+0x1467/0x15c3
> Jan 30 11:26:42 valisk kernel: [<ffffffff80208fee>] system_call+0x7e/0x83
> Jan 30 11:26:42 valisk kernel:
> Jan 30 11:26:42 valisk kernel: PM: Removing info for platform:bluetooth
> Jan 30 11:26:43 valisk kernel: Bluetooth: Core ver 2.11
> Jan 30 11:26:44 valisk kernel: PM: Adding info for platform:bluetooth
> Jan 30 11:26:44 valisk kernel: kobject_add failed for bluetooth with -EEXIST, don't try to register things with the same name in the same directory.
> Jan 30 11:26:44 valisk kernel:
> Jan 30 11:26:44 valisk kernel: Call Trace:
> Jan 30 11:26:45 valisk kernel: [<ffffffff802f4e3b>] kobject_shadow_add+0x147/0x17b
> Jan 30 11:26:45 valisk kernel: [<ffffffff802f5162>] subsystem_register+0x1b/0x2a
> Jan 30 11:26:45 valisk kernel: [<ffffffff803773db>] class_register+0xbf/0x1bd
> Jan 30 11:26:45 valisk kernel: [<ffffffff80377a7e>] class_create+0x53/0x71
> Jan 30 11:26:46 valisk kernel: [<ffffffff881c711c>] :bluetooth:bt_sysfs_init+0x5a/0x8b
> Jan 30 11:26:46 valisk kernel: [<ffffffff881c701b>] :bluetooth:bt_init+0x1b/0x53
> Jan 30 11:26:46 valisk kernel: [<ffffffff8023bf0a>] sys_init_module+0x1467/0x15c3
> Jan 30 11:26:46 valisk kernel: [<ffffffff80208fee>] system_call+0x7e/0x83
> Jan 30 11:26:46 valisk kernel:
do you see them also with the plain vanilla 2.6.20-rc6 kernel or are
these only coming up in Greg's tree?
Regards
Marcel
next prev parent reply other threads:[~2007-01-30 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 10:35 [Bluez-devel] trouble with sysfs and bluetooth Oliver Neukum
2007-01-30 10:52 ` Marcel Holtmann [this message]
2007-01-30 10:52 ` Marcel Holtmann
2007-01-30 16:12 ` Oliver Neukum
2007-01-30 16:21 ` Marcel Holtmann
2007-01-30 16:21 ` Marcel Holtmann
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=1170154328.27519.27.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sf.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.