From: Erwin Authried <eauth@softsys.co.at>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] lockup problem with larger packets
Date: Fri, 22 Oct 2004 23:21:55 +0200 [thread overview]
Message-ID: <1098480115.3258.61.camel@justakiss> (raw)
I have cross-compiled bluez for uClinux-2.4.20 for ARM7, with the bluez
kernel patch applied, and bluez-utils 2.10. I'm using the Conceptronic
CBT100C PCMCIA card on the system. The card is initialized with
"hciattach ttyS2 bcsp". Basically, the system works fine, but I see
occasional overrun errors on the UART, maybe because the ARM7 is running
with 40MHz only. When I transmit larger packets (l2ping -s 300 ...), the
number of overrun errors increases, and sometimes the system locks up.
I'm getting an endless sequence of:
bcsp_pkt_cull: Peer acked invalid packet
bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
bcsp_pkt_cull: Peer acked invalid packet
bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
bcsp_pkt_cull: Peer acked invalid packet
...
Regards,
Erwin
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-10-22 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 21:21 Erwin Authried [this message]
2004-10-23 13:55 ` [Bluez-users] lockup problem with larger packets Marcel Holtmann
[not found] ` <1098928778.23859.32.camel@kabel>
2004-10-28 11:47 ` Marcel Holtmann
2004-10-28 14:31 ` Erwin Authried
2004-10-28 17:30 ` 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=1098480115.3258.61.camel@justakiss \
--to=eauth@softsys.co.at \
--cc=bluez-users@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