From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] HCI Events and errors
Date: Wed, 02 Feb 2005 07:18:05 +0100 [thread overview]
Message-ID: <1107325085.9276.15.camel@pegasus> (raw)
In-Reply-To: <37D1FAB2FA7B7E4993785B956F853C73181467@ednex506.dsto.defence.gov.au>
Hi Victor,
> > the "hci_num_comp_pkts_evt: hci0 num_hndl 1" is missing here and this
> > means that the flow is suspended and we can't send HCI commands or
> > data anymore. You may run into an memory problem if you keep
> > sending and the hardware never wakes up again,
>
> The user-space app doesn't see any problem at the point where the
> hardware error is raised, so it keeps calling send() until eventually
> send() fails with a 'resource unavailable' error status, presumably
> because of the lack of sk_buf's.
maybe it is a good idea to forward the hardware error up to the L2CAP
layer so that you will see the error there.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-02-02 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 5:51 [Bluez-devel] HCI Events and errors Wodecki, Victor (Contractor)
2005-02-02 6:18 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-02 4:05 Wodecki, Victor (Contractor)
2005-02-02 4:40 ` Marcel Holtmann
2005-02-02 2:59 Wodecki, Victor (Contractor)
2005-02-02 3:18 ` 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=1107325085.9276.15.camel@pegasus \
--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