From: Soeren Sonnenburg <kernel@nn7.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.26rc9+git bluetooth/rfcomm oops
Date: Sun, 13 Jul 2008 12:32:05 +0200 [thread overview]
Message-ID: <1215945125.4842.13.camel@localhost> (raw)
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
next reply other threads:[~2008-07-13 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 10:32 Soeren Sonnenburg [this message]
2008-07-13 16:25 ` 2.6.26rc9+git bluetooth/rfcomm oops Vegard Nossum
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=1215945125.4842.13.camel@localhost \
--to=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
/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 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.