From: Carlos AM <Carlos@naxus.biz>
To: bluez-devel lista <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] BCSP not working
Date: Wed, 18 Aug 2004 16:00:24 +0200 [thread overview]
Message-ID: <1092837623.28955.120.camel@localhost.localdomain> (raw)
In-Reply-To: <001201c48529$3b309710$5000005a@naxus>
Hi
The machine is an arm running uclinux. I used the linux kernel version
2.4.22 and bluez-2.7. Yesterday I patched the kernel with this patch:
http://www.holtmann.org/linux/kernel/patch-2.4.22-mh7.gz
And got the following kernel log:
<3>bcsp_recv: Out-of-order packet arrived, got 1 expected 0
<3>bcsp_recv: Out-of-order packet arrived, got 1 expected 0
<4>Warning: kfree_skb passed an skb still on a list (from 00093a14).
<2>kernel BUG at skbuff.c:319!
(hanged)
The only difference with the last kernel messages was:
"<3>bcsp_recv: Short BCSP packet" that didn't appear anymore.
According to the kernel patch changelog this is normal.
I execute the following script to start all the bluetooth stuff:
------------------------------------------------------------
#!/bin/sh
/bluez/hcid -n &
/bluez/bluezmain hciattach -n /dev/tts/2 csr 115200 &
/bluez/bluezmain hciconfig hci0 up
/bluez/sdpd -n &
/bluez/bluezmain sdptool add sp
#my own program
/bluez/rfcomm-server 1
------------------------------------------------------------
I used "-n" because the uclinux fork call does not behave as normal linux.
The uclinux hangs in hciattach.
I successfully executed this script with the same bluetooth hardware in a Linux 2.6 PC with bluez 2.7.
Everything worked fine.
Regards.
Carlos.
> > These messages appear on the kernel log when I am using BCSP:
> >
> > <3>bcsp_recv: Out-of-order packet arrived, got 1 expected 0
> > <3>bcsp_recv: Checksum failed: computed b237 received 0000
> > <4>Warning: kfree_skb passed an skb still on a list (from 000f77a4).
> > <2>kernel BUG at skbuff.c:319!
> > <3>bcsp_recv: Short BCSP packet
> >
> > Then the computer hangs.
> >
> > I enabled "Send CRC with every hci packet" in the kernel and in the
> > bluetooth device.
>
> I asked for more information not some extra text. What kernel version
> are using, what library version, what tools. What hardware, what command
> for reproducing etc. Is there an oops?
>
> Regards
>
> Marcel
>
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next parent reply other threads:[~2004-08-18 14:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001201c48529$3b309710$5000005a@naxus>
2004-08-18 14:00 ` Carlos AM [this message]
2004-08-18 17:42 ` [Bluez-devel] BCSP not working Marcel Holtmann
2004-08-17 17:01 Carlos AM
2004-08-18 8:42 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-08-17 16:49 [Bluez-devel] bcsp " Carlos AM
2004-08-17 21:40 ` 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=1092837623.28955.120.camel@localhost.localdomain \
--to=carlos@naxus.biz \
--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