All of lore.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 09:52:35 +0200	[thread overview]
Message-ID: <1186386755.20129.1.camel@violet> (raw)
In-Reply-To: <46B6CC07.9010105@idlum.be>

Hi Pierre-Yves,

> Trying to perform a full SDP extraction on a nokia N70, I got several 
> time the error below (full hcidump log attached).
> 
>    > ACL data: handle 11 flags 0x02 dlen 14
>        L2CAP(s): Command rej: reason 2 dcid 0x0000 scid 0x0040
>          Invalid CID in request
>    > ACL data: handle 11 flags 0x02 dlen 14
>        L2CAP(s): Command rej: reason 2 dcid 0x0000 scid 0x0040
>          Invalid CID in request
> 
> In don't understand what happens here, nor the meaning of this error. 
> Could someone please explain it?

what kernel are you using? And I need the full trace from the HCI create
connection to the HCI disconnect.

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  7:52 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 [this message]
2007-08-06  8:07   ` Pierre-Yves Paulus
2007-08-06  8:14     ` 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=1186386755.20129.1.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 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.