From: Oliver Neukum <oliver@neukum.name>
To: linux-kernel@vger.kernel.org, marcel@holtmann.org,
maxk@qualcomm.com, bluez-devel@lists.sourceforge.net
Subject: trouble with sysfs and bluetooth
Date: Tue, 30 Jan 2007 15:55:04 +0100 (MET) [thread overview]
Message-ID: <200701301555.14763.oliver@neukum.name> (raw)
[-- 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 --]
reply other threads:[~2007-01-30 14:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200701301555.14763.oliver@neukum.name \
--to=oliver@neukum.name \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®