linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bcsp problem
Date: Wed, 21 Dec 2005 12:12:56 +0100	[thread overview]
Message-ID: <1135163576.26233.60.camel@localhost> (raw)
In-Reply-To: <F6E1228667B6D411BAAA00306E00F2A506A75557@pdc2.nestec.net>

Hi Jibin,

> 	I am using bluez stack.  I found a Bluetooth Problem with Mobile
> 	 phone.
>      It's happen when bluetooth device  connect to Mobile Phone for a long
>      time,it shows the following error message.
> 
>  	 bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
>  	 bcsp_pkt_cull: Peer acked invalid packet
>  	
>  	I Think thehe above messages shows that the  bluetooth device was
>   reset during the 	communication with mobile.So the bluecore firmware
>   embedded in the chip will start sending 	Sync packets again to bcsp
>   stack to establish the link between bluecore and bcsp stack.

run "hciconfig hci0 revision" (as root) and show us the output. What
versions of the BlueZ packages and Linux kernel are you using?

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-12-21 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21 11:04 [Bluez-devel] bcsp problem JIBIN K
2005-12-21 11:12 ` 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=1135163576.26233.60.camel@localhost \
    --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;
as well as URLs for NNTP newsgroup(s).