linux-kernel - Re: [Bluez-devel] trouble with sysfs and bluetooth

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1170154328.27519.27.camel@violet>
Date:	Tue, 30 Jan 2007 11:52:08 +0100
From:	Marcel Holtmann <marcel@...tmann.org>
To:	BlueZ development <bluez-devel@...ts.sourceforge.net>
Cc:	linux-kernel@...r.kernel.org, maxk@...lcomm.com,
	bluez-devel@...ts.sf.net
Subject: Re: [Bluez-devel] trouble with sysfs and bluetooth

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/