public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] "Invalid CID in request"
Date: Mon, 06 Aug 2007 10:14:31 +0200	[thread overview]
Message-ID: <1186388071.20129.4.camel@violet> (raw)
In-Reply-To: <46B6D6B1.5030007@idlum.be>

Hi Pierre-Yves,

> > what kernel are you using? And I need the full trace from the HCI create
> > connection to the HCI disconnect.
> 
> The kernel used is 2.6.21-2-486 (from debian).
> 
> The file I attached to my last e-mail (re-attached to this one) contains 
> the output of "hcidump -XV", are you requesting something else?

this is unlikely, but try it with only one adapter attached to your
system. I don't expect that to be a problem, because the kernel is
designed to handle the case. However I wanna rule out that it is a
multiple adapter issue.

Second, please try a 2.6.23-rc2 kernel. My wild guess is that the L2CAP
configuration process screws up the phone. We added a fix for that to
make it fully specification compliant.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-08-06  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06  7:21 [Bluez-devel] "Invalid CID in request" Pierre-Yves Paulus
2007-08-06  7:52 ` Marcel Holtmann
2007-08-06  8:07   ` Pierre-Yves Paulus
2007-08-06  8:14     ` Marcel Holtmann [this message]

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=1186388071.20129.4.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox