* [Bluez-devel] trouble with sysfs and bluetooth
@ 2007-01-30 10:35 Oliver Neukum
2007-01-30 10:52 ` Marcel Holtmann
0 siblings, 1 reply; 6+ messages in thread
From: Oliver Neukum @ 2007-01-30 10:35 UTC (permalink / raw)
To: lnux-kernel, marcel, maxk, bluez-devel
[-- Attachment #1: Type: text/plain, Size: 2442 bytes --]
Hi,
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:
There's currently no bluetooth device plugged in.
The module seems to not finish loading:
valisk:/home/oliver/Desktop/linux-2.6.20-6-greg # hciconfig -a
Can't open HCI socket.: Address family not supported by protocol
Regards
Oliver
[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 14565 bytes --]
[-- Attachment #3: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
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
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bluez-devel] trouble with sysfs and bluetooth
2007-01-30 10:35 [Bluez-devel] trouble with sysfs and bluetooth Oliver Neukum
@ 2007-01-30 10:52 ` Marcel Holtmann
0 siblings, 0 replies; 6+ messages in thread
From: Marcel Holtmann @ 2007-01-30 10:52 UTC (permalink / raw)
To: BlueZ development; +Cc: bluez-devel, linux-kernel, maxk
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bluez-devel] trouble with sysfs and bluetooth
@ 2007-01-30 10:52 ` Marcel Holtmann
0 siblings, 0 replies; 6+ messages in thread
From: Marcel Holtmann @ 2007-01-30 10:52 UTC (permalink / raw)
To: BlueZ development; +Cc: linux-kernel, maxk, bluez-devel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bluez-devel] trouble with sysfs and bluetooth
2007-01-30 10:52 ` Marcel Holtmann
(?)
@ 2007-01-30 16:12 ` Oliver Neukum
2007-01-30 16:21 ` Marcel Holtmann
-1 siblings, 1 reply; 6+ messages in thread
From: Oliver Neukum @ 2007-01-30 16:12 UTC (permalink / raw)
To: Marcel Holtmann; +Cc: BlueZ development, linux-kernel, maxk
> do you see them also with the plain vanilla 2.6.20-rc6 kernel or are
> these only coming up in Greg's tree?
Hi,
they are limited to Greg's tree.
Regards
Oliver
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bluez-devel] trouble with sysfs and bluetooth
2007-01-30 16:12 ` Oliver Neukum
@ 2007-01-30 16:21 ` Marcel Holtmann
0 siblings, 0 replies; 6+ messages in thread
From: Marcel Holtmann @ 2007-01-30 16:21 UTC (permalink / raw)
To: Oliver Neukum; +Cc: BlueZ development, linux-kernel, maxk
Hi Oliver,
> > do you see them also with the plain vanilla 2.6.20-rc6 kernel or are
> > these only coming up in Greg's tree?
>
> they are limited to Greg's tree.
my first guess would that there is something wrong with Greg's tree or
that one of this patches changes some behavior of the driver model.
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [Bluez-devel] trouble with sysfs and bluetooth
@ 2007-01-30 16:21 ` Marcel Holtmann
0 siblings, 0 replies; 6+ messages in thread
From: Marcel Holtmann @ 2007-01-30 16:21 UTC (permalink / raw)
To: Oliver Neukum; +Cc: BlueZ development, linux-kernel, maxk
Hi Oliver,
> > do you see them also with the plain vanilla 2.6.20-rc6 kernel or are
> > these only coming up in Greg's tree?
>
> they are limited to Greg's tree.
my first guess would that there is something wrong with Greg's tree or
that one of this patches changes some behavior of the driver model.
Regards
Marcel
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2007-01-30 16:21 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-01-30 10:35 [Bluez-devel] trouble with sysfs and bluetooth Oliver Neukum
2007-01-30 10:52 ` Marcel Holtmann
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
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.