All of lore.kernel.org
 help / color / mirror / Atom feed
* [Bluez-devel] Problem with RFCOMM kernel module
@ 2007-03-09 15:01 Pierre-Yves Paulus
  2007-03-09 16:03 ` Pierre-Yves Paulus
  0 siblings, 1 reply; 4+ messages in thread
From: Pierre-Yves Paulus @ 2007-03-09 15:01 UTC (permalink / raw)
  To: BlueZ development

Hello,

On a Debian "testing" box running stock debian 2.6.18-3-486 kernel, I 
sometimes get this in my syslog:

kernel: Bluetooth: RFCOMM socket layer initialized
kernel: Bluetooth: RFCOMM TTY layer initialized
kernel: Bluetooth: RFCOMM ver 1.8
kernel: kobject_add failed for rfcomm0 with -EEXIST, don't try to 
register things with the same name in the same directory.
kernel:  [<c01a99d3>] kobject_add+0x12e/0x154
kernel:  [<c020186b>] class_device_add+0x9b/0x3a6
kernel:  [<c01a977d>] kobject_get+0xf/0x13
kernel:  [<c0201bfd>] class_device_create+0x77/0x96
kernel:  [<c01eafcb>] tty_register_device+0xa0/0xab
kernel:  [<c01ac3c1>] sprintf+0x1d/0x20
kernel:  [<c82d9520>] rfcomm_dev_ioctl+0x215/0x47a [rfcomm]
kernel:  [<c82d86f4>] rfcomm_sock_ioctl+0x1c/0x2b [rfcomm]
kernel:  [<c021adf8>] sock_ioctl+0x198/0x1ba
kernel:  [<c021ac60>] sock_ioctl+0x0/0x1ba
kernel:  [<c0156bea>] do_ioctl+0x16/0x42
kernel:  [<c0156df9>] vfs_ioctl+0x1e3/0x1f1
kernel:  [<c021c219>] sys_socketcall+0x9f/0x177
kernel:  [<c0156e51>] sys_ioctl+0x4a/0x61
kernel:  [<c0102a47>] syscall_call+0x7/0xb

When it does happen, BT related operations are pretty much screwed up 
until next reboot. For background purposes, the box runs a custom 
application which makes use of Bluez through the DBus bindings, mainly 
to get /dev/rfcommX sockets to various devices, and sending data to them.

What's happening? How to prevent it?

Also, I all the time(obviously when the app is running) get a lot of 
statements like the followings:

l2cap_recv_acldata: Unexpected continuation frame (len 0)
l2cap_recv_acldata: Unexpected continuation frame (len 0)
l2cap_recv_acldata: Unexpected continuation frame (len 0)
l2cap_recv_acldata: Unexpected continuation frame (len 0)
l2cap_recv_acldata: Unexpected continuation frame (len 0)
l2cap_recv_acldata: Unexpected continuation frame (len 0)
l2cap_recv_acldata: Unexpected continuation frame (len 0)
hci_acldata_packet: hci1 ACL packet for unknown connection handle 11
hci_acldata_packet: hci1 ACL packet for unknown connection handle 11
hci_acldata_packet: hci1 ACL packet for unknown connection handle 11
hci_acldata_packet: hci1 ACL packet for unknown connection handle 11
hci_acldata_packet: hci1 ACL packet for unknown connection handle 11
hci_acldata_packet: hci1 ACL packet for unknown connection handle 11
l2cap_recv_acldata: Unexpected continuation frame (len 0)
l2cap_recv_acldata: Unexpected continuation frame (len 0)


What do they mean? What's happening there?


Thanks in advance,
Best Regards

Pierre-Yves Paulus


-------------------------------------------------------------------------
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] 4+ messages in thread
end of thread, other threads:[~2007-03-15 15:02 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-09 15:01 [Bluez-devel] Problem with RFCOMM kernel module Pierre-Yves Paulus
2007-03-09 16:03 ` Pierre-Yves Paulus
2007-03-15  8:01   ` Pierre-Yves Paulus
2007-03-15 15:02     ` Pierre-Yves Paulus

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.