From: Mauro Tortonesi <mtortonesi@ing.unife.it>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] bluez stability problems?
Date: Wed, 28 Jan 2004 15:10:36 +0100 [thread overview]
Message-ID: <200401281510.36476.mtortonesi@ing.unife.it> (raw)
hi to everybody,
sometimes when i start playing with bluez the bluetooth subsystem hangs:
[mauro@daneel nc6]$ cat src/main.c | ./src/nc6 -vvv --mtu=672 -b
00:0D:88:8E:CA:07 10
nc6: unable to connect to remote address bluez socket
[mauro@daneel nc6]$ hcitool scan
Scanning ...
[mauro@daneel nc6]$
[mauro@daneel nc6]$ l2ping 00:0D:88:8E:CA:07
Can't create socket.: Operation not permitted
[mauro@daneel audiotest2]$ ./oggread -f
/mnt/disk/mauro/art_blakey_and_the_jazz_messengers-impulse/01_alamode.ogg -d
00:0D:88:8E:CA:07 -p 10
oggread[18536]: Can't connect. Operation already in progress(114)
Cannot connect to Bluetooth device 00:0D:88:8E:CA:07
i have experienced this problem with both recent 2.4 (2.4.25-pre7 included)
and 2.6 kernels.
--
Aequam memento rebus in arduis servare mentem...
Mauro Tortonesi mtortonesi@ing.unife.it
mauro@deepspace6.net
mauro@ferrara.linux.it
Deep Space 6 - IPv6 with Linux http://www.deepspace6.net
Ferrara Linux User Group http://www.ferrara.linux.it
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-01-28 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 14:10 Mauro Tortonesi [this message]
2004-01-28 16:29 ` [Bluez-devel] bluez stability problems? 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=200401281510.36476.mtortonesi@ing.unife.it \
--to=mtortonesi@ing.unife.it \
--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