From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Oops with multiple hcitool commands
Date: Mon, 12 Feb 2007 20:33:11 +0100 [thread overview]
Message-ID: <1171308791.11774.6.camel@violet> (raw)
In-Reply-To: <2EB6297382462046A9427D7324788A4801A3898D@MCLNEXVS06.resource.ds.bah.com>
Hi Richard,
> I am building a project that will use multiple HCI devices on a single
> Linux PC. I have a USB hub, and several Linksys Bluetooth dongles. On
> my PC I open two terminal windows and then run the following commands:
>
> window 1# hcitool -i hci0 info 00:18:C5:2C:5E:C2
> window 2# hcitool -i hci1 info 00:18:C5:2C:5E:C2
>
> The two commands must run simultaneously. Just these two commands run
> quickly one after the other will almost always cause the oops. The
> problem does not occur if the two hcitool info commands are examining
> different remote devices. You must go after the same remote device.
please post the oops message from the kernel.
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-02-12 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 16:09 [Bluez-devel] Oops with multiple hcitool commands Williams, Richard
2007-02-12 19:33 ` Marcel Holtmann [this message]
2007-02-13 14:02 ` Williams, Richard
2007-02-13 14:04 ` Marcel Holtmann
2007-02-13 14:08 ` Williams, Richard
2007-02-13 14:12 ` Marcel Holtmann
2007-03-16 14:52 ` Williams, Richard
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=1171308791.11774.6.camel@violet \
--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