2.6.26rc9+git bluetooth/rfcomm oops
From: Soeren Sonnenburg
Date: Sun Jul 13 2008 - 06:34:38 EST
Hi,
this oops happened after a couple of s2ram cycles so it might be very
well crap. However I somehow triggered it by /etc/init.d/bluetooth
stop/start's which also call hid2hci maybe even a connection was about
to be established at that time. As I remember having seen a problem like
this before I thought I report it (even though I have a madwifi tainted
kernel).
[drm] Num pipes: 1
kobject_add_internal failed for rfcomm0 with -EEXIST, don't try to register things with the same name in the same directory.
Pid: 22041, comm: rfcomm Tainted: P 2.6.26-rc9-sonne #39
[<c026be97>] kobject_add_internal+0xf7/0x1a0
[<c0273123>] ? kvasprintf+0x43/0x60
[<c026bfcb>] kobject_add_varg+0x3b/0x70
[<c026c05c>] kobject_add+0x2c/0x60
[<c02efb0f>] device_add+0x8f/0x490
[<c0270990>] ? vsnprintf+0x3a0/0x740
[<c02eff22>] device_register+0x12/0x20
[<c02effdb>] device_create_vargs+0xab/0xc0
[<c02f0019>] device_create+0x29/0x30
[<c02d954d>] tty_register_device+0xcd/0x100
[<f8ba84d3>] rfcomm_dev_ioctl+0x5f3/0x840 [rfcomm]
[<f8ba673c>] rfcomm_sock_ioctl+0x2c/0x50 [rfcomm]
[<c0375db0>] sock_ioctl+0x60/0x230
[<c0375d50>] ? sock_ioctl+0x0/0x230
[<c0192468>] vfs_ioctl+0x28/0x90
[<c019252e>] do_vfs_ioctl+0x5e/0x2c0
[<c01927c9>] sys_ioctl+0x39/0x70
[<c01032d1>] sysenter_past_esp+0x6a/0x91
=======================
Soeren
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/