From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] problems with high-speed rfcomm transfers
Date: Thu, 29 Sep 2005 10:31:11 +0200 [thread overview]
Message-ID: <1127982671.5123.11.camel@localhost.localdomain> (raw)
In-Reply-To: <433ADB96.5080100@flander.com>
Hi Simo,
> Has anyone else had problems with high-speed rfcomm transfers with
> BlueZ?
>
> I am using simple rfcomm test setup. The client dumps data to rfcomm
> socket, and the server receives the data. Sometimes the data
> transfer just freezes, without any error messages. The client has
> sent the data, but it does not arrive at the server program.
>
> Tested with the bluez version that comes with 2.6.12 kernel, using
> usb bt dongle.
>
> Anyway, I understand that more detailed error description is surely
> needed, but I just wanted to know if anyone else has had these
> problems.
please provide some test programs to reproduce it.
> With amd64 machine it sometimes crashes with this error message:
>
> Unable to handle kernel NULL pointer dereference at 0000000000000050
> RIP:
Try the latest 2.6.14-rc2 kernel.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-09-29 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 18:06 [Bluez-users] problems with high-speed rfcomm transfers Simo Salminen
2005-09-28 21:02 ` Seba T.
2005-09-29 8:31 ` 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=1127982671.5123.11.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--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 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.