From: David Herrmann <dh.herrmann@googlemail.com>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: "Keren, Doron" <doronkeren@ti.com>,
Marcel Holtmann <marcel@holtmann.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Ilia, Kolominsky" <iliak@ti.com>, "Hadar, Amir" <a-hadar@ti.com>
Subject: Re: [PATCH] Bluetooth-next: Add incremental indexing in sysfs HCI connection name.
Date: Wed, 24 Aug 2011 21:27:43 +0200 [thread overview]
Message-ID: <CANq1E4SnHHRUV6PQpgxyiXvFyebjmfF9UVahG3VUOk2w+m4=FQ@mail.gmail.com> (raw)
In-Reply-To: <1314114448.4095.40.camel@THOR>
Hi Peter
On Tue, Aug 23, 2011 at 5:47 PM, Peter Hurley <peter@hurleysoftware.com> wrote:
> David,
> I know you already posted a patch for this (which looks ok for fixing
> the oops specifically), but it'd still be helpful to see a debug kernel
> log that led up to that. There's only a couple of reasons -- all bad --
> why the hci connection could not be found in the connection list while
> the ctrl & intr sockets are connected (which are tested just prior to
> hidp_add_connection).
Sorry for the delay. I currently have no other machine to run a debug
kernel and I really don't like provoking oopses on my working machine.
However, the next days I will setup a machine and try to send a full
trace.
Are there any useful config symbols for bluetooth debug? Despite the
standard kernel-wide debug symbols.
What are possible reasons why an l2cap connection can be available
without an underlying ACL connection? My fix eliminates the oops but I
still think that it is not fixing the real problem (anyway, I'd really
like to see it upstream).
I will try to send a debug log if I can reproduce it.
> Regards,
> Peter Hurley
Cheers
David
next prev parent reply other threads:[~2011-08-24 19:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 16:01 [PATCH] Bluetooth-next: Add incremental indexing in sysfs HCI connection name doron.keren.bluez
2011-08-17 21:42 ` Marcel Holtmann
2011-08-18 11:21 ` Keren, Doron
2011-08-18 11:44 ` David Herrmann
2011-08-23 15:47 ` Peter Hurley
2011-08-24 19:27 ` David Herrmann [this message]
2011-08-24 21:51 ` Peter Hurley
2011-08-25 17:11 ` David Herrmann
2011-09-14 14:42 ` Marcel Holtmann
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='CANq1E4SnHHRUV6PQpgxyiXvFyebjmfF9UVahG3VUOk2w+m4=FQ@mail.gmail.com' \
--to=dh.herrmann@googlemail.com \
--cc=a-hadar@ti.com \
--cc=doronkeren@ti.com \
--cc=iliak@ti.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=peter@hurleysoftware.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 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.