[Bluez-devel] Problem with RFCOMM kernel module

[Bluez-devel] Problem with RFCOMM kernel module

[Pierre-Yves Paulus]

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

Re: [Bluez-devel] Problem with RFCOMM kernel module

[Pierre-Yves Paulus]

I just got a kernel crash on the same box. Here is the trace I was able 
to gather (was connected per ssh and this suddenly appeared). No screen 
was connected to the box at the time of the crash, I connected one, and 
there was some more info. There is a pic of the screen there if it may 
help: http://img409.imageshack.us/my.php?image=kernelcrashif0.jpg

In userspace, there was (as for my previous message) only hcid running, 
and obviously my app performing dbus calls to it.

Message from syslogd@p2a at Fri Mar  9 15:47:40 2007 ...
kernel: Oops: 0000 [#1]
kernel: CPU:    0
kernel: EIP is at rfcomm_tty_chars_in_buffer+0x6/0x18 [rfcomm]
kernel: eax: 00000000   ebx: c6c51800   ecx: 00000000   edx: c773f000
kernel: esi: 00000000   edi: c5c1e4a0   ebp: c6c5180c   esp: c3837c08
kernel: ds: 007b   es: 007b   ss: 0068
kernel: Process hcid (pid: 16185, ti=c3836000 task=c2f87ab0 
task.ti=c3836000)
kernel: Stack: c01ef32b c01ef253 c6c51800 c5c1e4a0 c01eb873 00000000 
00000000 c3837eb0
kernel:        c5c1e4a0 c3837e98 c01574aa c3837fb0 080808f0 08080920 
00000000 c3837e98
kernel:        c3837e98 c3837e98 c3837ed0 00000000 c0157f5e 00000000 
00000000 00000008
kernel: Call Trace:
kernel: Code: 8b 98 70 01 00 00 8b 43 3c 8b 48 48 8b 50 54 85 d2 75 02 
b2 01 8b 43 60 0f af ca 29 c1 89 c8 79 02 31 c0 5b c3 8b 80 70 01 00 00 
<8b> 50 3c 8d 42 0c 39 42 0c 75 03 31 c0 c3 8b 42 48 c3
c3 c3 31
kernel: EIP: [<c82d6d50>] rfcomm_tty_chars_in_buffer+0x6/0x18 [rfcomm] 
SS:ESP 0068:c3837c08

What happened?

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

Re: [Bluez-devel] Problem with RFCOMM kernel module

[Pierre-Yves Paulus]

Hello,

I got this a few minutes ago. It was on a Xubuntu edgy box, running 
2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 unknown. Hcid 
v3.7 was running at the time it happened, and data was sent over one or 
more /dev/rfcommX.

There has been no answer to my previous messages to the list regarding 
those crashes. Should I give more details? Which ones? Are those 
problems known and perhaps already fixed upstream?

Please let me know!

Best Regards,
Pierre-Yves Paulus


Mar 15 08:51:58 uber2 kernel: [20442837.220000] BUG: unable to handle 
kernel NULL pointer dereference at virtual address 0000003c
Mar 15 08:51:58 uber2 kernel: [20442837.220000]  printing eip:
Mar 15 08:51:58 uber2 kernel: [20442837.220000] f8f46b7a
Mar 15 08:51:58 uber2 kernel: [20442837.220000] *pde = 00000000
Mar 15 08:51:58 uber2 kernel: [20442837.220000] Oops: 0000 [#1]
Mar 15 08:51:58 uber2 kernel: [20442837.220000] SMP
Mar 15 08:51:58 uber2 kernel: [20442837.220000] Modules linked in: 
usbhid nls_utf8 nls_iso8859_1 nls_cp437 vfat fat usb_storage libusual 
ppdev vmnet vmmon rfcomm l2cap cpufreq_powersave cpufreq_stats 
cpufreq_userspace cpufreq_ondemand cpufreq_conservative freq_table 
tc1100_wmi video battery container sbs button pcc_acpi sony_acpi i2c_ec 
ac dev_acpi asus_acpi hotkey af_packet ext2 lp tsdev nvidia snd_intel8x0 
snd_ac97_codec snd_ac97_bus ipv6 psmouse serio_raw hci_usb bluetooth 
snd_pcm_oss snd_mixer_oss sg snd_pcm snd_timer snd soundcore evdev 
pcspkr parport_pc parport floppy analog gameport snd_page_alloc shpchp 
pci_hotplug nvidia_agp agpgart i2c_nforce2 i2c_core reiserfs forcedeth 
ohci_hcd usbcore ide_generic sd_mod ide_disk sata_nv libata scsi_mod 
generic amd74xx thermal processor fan fbcon tileblit font bitblit 
softcursor vesafb capability commoncap
Mar 15 08:51:58 uber2 kernel: [20442837.220000] CPU:    0
Mar 15 08:51:58 uber2 kernel: [20442837.220000] EIP: 
0060:[pg0+950709114/1068901376]    Tainted: P      VLI
Mar 15 08:51:58 uber2 kernel: [20442837.220000] EFLAGS: 00010206 
(2.6.17-10-generic #2)
Mar 15 08:51:58 uber2 kernel: [20442837.220000] EIP is at 
rfcomm_tty_write+0x1a/0x190 [rfcomm]
Mar 15 08:51:58 uber2 kernel: [20442837.220000] eax: 00000000   ebx: 
ef725e00   ecx: 00000003   edx: ea0ca000
Mar 15 08:51:58 uber2 kernel: [20442837.220000] esi: 00000003   edi: 
dc0f0800   ebp: ea0ca000   esp: c574deec
Mar 15 08:51:58 uber2 kernel: [20442837.220000] ds: 007b   es: 007b 
ss: 0068
Mar 15 08:51:58 uber2 kernel: [20442837.220000] Process java (pid: 4807, 
threadinfo=c574c000 task=c6c25050)
Mar 15 08:51:58 uber2 kernel: [20442837.220000] Stack: 00000003 ea0ca000 
00000000 c043b1e0 00000246 ef725e00 00000003 dc0f0800
Mar 15 08:51:58 uber2 kernel: [20442837.220000]        ea0ca000 c0229369 
dc0f0934 ea0ca000 dfa879e0 dc0f0800 00000000 c6c25050
Mar 15 08:51:58 uber2 kernel: [20442837.220000]        c011bde0 dc0f0938 
dc0f0938 00000003 dc0f0800 dfa879e0 00000003 c02267d8
Mar 15 08:51:58 uber2 kernel: [20442837.220000] Call Trace:
Mar 15 08:51:58 uber2 kernel: [20442837.220000]  <c0229369> 
write_chan+0x219/0x320  <c011bde0> default_wake_function+0x0/0x10
Mar 15 08:51:58 uber2 kernel: [20442837.220000]  <c02267d8> 
tty_write+0x138/0x1f0  <c0229150> write_chan+0x0/0x320
Mar 15 08:51:58 uber2 kernel: [20442837.220000]  <c016aece> 
vfs_write+0xbe/0x190  <c02266a0> tty_write+0x0/0x1f0
Mar 15 08:51:58 uber2 kernel: [20442837.220000]  <c016b641> 
sys_write+0x41/0x70  <c0102fbb> sysenter_past_esp+0x54/0x79
Mar 15 08:51:58 uber2 kernel: [20442837.220000] Code: d8 e8 fb f1 ff ff 
eb e1 89 f6 8d bc 27 00 00 00 00 55 57 56 53 83 ec 14 85 c9 89 54 24 04 
89 0c 24 8b 80 80 01 00 00 89 44 24 08 <8b> 40 3c c7 44 24 10 00 00 00 
00 89 44 24 0c 0f 84 e8 00 00 00
Mar 15 08:51:58 uber2 kernel: [20442837.220000] EIP: 
[pg0+950709114/1068901376] rfcomm_tty_write+0x1a/0x190 [rfcomm] SS:ESP 
0068:c574deec


-------------------------------------------------------------------------
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

Re: [Bluez-devel] Problem with RFCOMM kernel module

[Pierre-Yves Paulus]

Hello,

I got several kernel Oops'es similar to the one I described before since 
my last message.

I'm definitely not knowledgeable in that kernel matter, but would be 
more than happy if I can give more information, or perform some 
operations (more details? run some debbugger software? ...? just ask) on 
my computer if that can help someone to better understand what's the 
cause of those errors, which are more than problematic (I experience 
various problems with virtual ttys (/dev/rfcommX) after such an Oops has 
happened, and only a reboot solves them... until next Oops)

Please let me know what to do.

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